Product
Analyze
Review
Produce
Draft
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Prepare a company-side post-closing tracker by extracting continuing obligations from the executed purchase agreement, notes, side letters, amendments, and closing record. Separate filing deadlines from contractual dates and internal reminders, then assign an owner, verified trigger, and completion standard to each item. Reconcile funding and interest records with finance, and identify conversion, maturity, and notice dependencies without assuming identical treatment across notes. The deliverable is a source-linked working table showing what must happen next, who is responsible, and what evidence establishes completion.
When to use this workflow
Use this workflow when company counsel hands a completed convertible note financing to in-house legal, finance, or the corporate secretary. Refresh it after an additional closing, advance, amendment, or holder transfer affecting performance. Start with executed documents rather than the term sheet.
The scope is post-closing administration: filings, reporting, advance records, interest, notices, agreed follow-up deliverables, and preparation for conversion or repayment. It does not replace closing diligence or establish that every closing condition was satisfied.
This guide addresses US practice, with Delaware corporate-law requirements identified separately. Rights and obligations depend on actual language, governing law, exemption, and facts. State securities notices, secured-note requirements, tax, and usury issues need separate analysis where applicable. The process recommendations below are not independent legal requirements.
What you need
Collect the executed purchase agreement, issued notes, investor schedules, side letters, amendments, waivers, and incorporated exhibits. Include closing approvals, delivery receipts, charter documents, capitalization records, and senior-debt or intercreditor restrictions relevant to payments or conversion.
Finance should supply actual funding dates, amounts received, payments made on the company’s behalf, and the opening debt ledger. Counsel should supply the exemption analysis, evidence of investor commitment dates, and filing confirmations. Identify missing evidence rather than treating wire receipt as the controlling date for every purpose.
Assign stable document identifiers, such as N-01 for a note and SL-01 for its side letter. Link amendments to affected instruments. Identify both a custodian for missing evidence and an operational owner for performance; those responsibilities may belong to different people.
Use the template
Convertible Note Financing Transactions — Post-closing obligations tracker
Copy this table into your working document or spreadsheet. Keep one obligation or independently provable occurrence per row.
| ID / note | Source / citation | Obligation / basis | Trigger / due | Owner / reviewer | Dependencies / gaps | Status / next action | Completion proof |
|---|---|---|---|---|---|---|---|
Use Obligation / basis to distinguish legal requirements, contractual duties, and internal controls. In Trigger / due, preserve the operative event, calculated deadline, and separately labeled internal preparation date. Reference supporting date calculations where necessary.
Owner / reviewer identifies the performer and validator. Dependencies / gaps captures missing attachments, elections, approvals, or unresolved interpretations. Completion proof points to an identifiable receipt, delivered report, approved ledger, or corporate record—not simply “done.”
For recurring duties, retain the governing obligation and create dated occurrence rows. For contingent duties, name the person responsible for recognizing the event. Keep calculations in a supporting worksheet linked by row ID, preserving the source assumptions.
Step by step
1. Establish the executed baseline and handoff boundary
Reconcile the closing binder, investor schedule, and finance ledger. Confirm issued notes, committed investors, funded amounts, and whether additional closings remain possible. Associate each side letter with its beneficiary rather than extending its rights to all holders.
Separate completed closing deliverables from express post-closing undertakings. If a closing condition lacks satisfaction evidence, retain it as an unresolved closing issue unless a documented waiver or deferral supports another classification. Identify the person authorized to decide its treatment.
Record: affected note IDs, source versions, missing evidence, and responsibility for establishing the baseline.
2. Extract obligations and classify their authority
Read operative provisions with definitions, schedules, and notice clauses. Extract reporting, payment, ledger, collateral follow-up, and event-notice duties. Preserve qualifications involving requests, thresholds, recipients, or information availability.
For offerings under Rules 504 or 506 or Securities Act § 4(a)(5), the SEC states that Form D is due within 15 days after the first investor becomes irrevocably contractually committed. A Saturday, Sunday, or holiday deadline moves to the next business day. This is not a filing rule for every exemption; evaluate state notices separately. See SEC guidance on filing Form D. (sec.gov)
Create separate applicability rows for unresolved filing questions. Do not classify an unverified filing as unnecessary.
Record: obligation, legal or contractual basis, precise citation, and assigned applicability decision.
3. Translate triggers into dates and event checks
Distinguish fixed dates, recurring periods, and contingent events. “Before repayment,” “after a qualified financing,” and “upon holder request” require different controls. Capture the contractual business-day definition, delivery method, recipient, and any deemed-receipt provision affecting timing.
Assign event recognition to the company contact likely to learn of it: treasury for proposed payments, corporate development for sale activity, or legal for holder elections. Require referral early enough to evaluate notices and consent dependencies before the proposed action.
Keep internal preparation dates distinct from legal deadlines. If a deadline may already have passed, escalate promptly rather than replacing it with a new target date.
Record: trigger evidence, calculated due date, event contact, notice mechanics, and internal preparation date.
4. Reconcile principal, interest, and payment mechanics
Validate a ledger by note and advance. Check accrual commencement, funding dates, day-count convention, simple or compound treatment, cash or payment-in-kind mechanics, allocation, and default provisions. Finance should review calculations and cash requirements independently.
The MiNK–Agenus agreement illustrates a consent-based drawdown structure requiring an updated schedule of advances and payments made on the company’s behalf, including dates for tracking interest. It is a parent-subsidiary example, not a startup financing standard. Its filed page does not substantively reproduce the note attachment or establish the interest rate. See Article I.1. (sec.gov)
Do not convert missing funding evidence into a final conclusion that nothing is owed. Isolate the disputed amount and obtain the underlying records.
Record: ledger reference, reviewer, payment or capitalization dates, discrepancies, and resolution owner.
5. Map conversion, maturity, and repayment dependencies
Create rows for the financing, sale, maturity, and other events specified in the instruments. Distinguish automatic conversion from holder elections; preserve thresholds, notices, accrued-interest treatment, share class, and approval dependencies. Link a conversion model documenting capitalization definitions and rounding assumptions.
A historical Core Scientific note illustrates why automatic conversion and repayment at par cannot be assumed: it provided optional conversion following defined Offering events and separate conditional prepayment terms. These are negotiated examples, not benchmarks. See Exhibit A, §§ 1(b)(i) and 2(a). (sec.gov)
For Delaware companies, separately assess whether conversion shares require charter action. DGCL § 151(g) requires an effective certificate of designations when the relevant rights are established by board resolutions under charter-granted authority rather than already stated in the charter. It does not require that procedure for every conversion. See DGCL § 151(g). (delcode.delaware.gov)
Record: event treatment, model reference, elections, approvals, and legal questions requiring resolution.
6. Assign performance, verification, and escalation
Review the draft with finance and the company legal contact. Confirm each owner has the documents, authority, information, and access needed to perform. For reporting, assign preparation, confidentiality review, recipient verification, and delivery. For payments, identify calculation approval and review of applicable debt restrictions.
Set a review cadence proportionate to upcoming dates and transaction activity. Assign unresolved interpretations to decision-makers with internal target dates. Keep a row open when interpretation or evidence remains missing, even if preparatory work is complete.
Record: accepted ownership, reviewer, escalation contact, target date, and specific next action.
7. Validate completion and preserve changes
Test completed rows against their proof requirements. A prepared report is not delivery evidence; a filing draft is not confirmation; a calculation is not a payment receipt. Preserve the evidence and reviewer’s dated approval.
When a note is amended, transferred, repaid, or converted, reconcile affected rows against supporting documents before retiring or replacing tasks. Verify recipient changes before redirecting reports or payments. Preserve prior obligations and their disposition so later reviewers can explain why tasks changed.
Record: completion evidence, reviewer, superseding document, and remaining exceptions.
Worked example
Fictional scenario: Harbor Lantern Robotics, Inc., a Delaware company, completes an initial closing under a financing permitting up to $1.8 million of commitments from Alder Path Ventures and three other fictional investors. This is not a statement that $1.8 million was funded. All parties, documents, amounts, and terms below are fictional.
Note N-01 permits up to $600,000 of advances and provides 6% simple interest on funded principal, actual/365, payable at repayment or included in conversion under § 4. Side letter SL-01 requires quarterly management accounts for Alder Path only, within 40 calendar days after quarter-end.
Finance’s opening ledger shows $600,000 for N-01, but receipt B-01 establishes only $450,000 funded on September 30, 2026. An email describes $150,000 as “committed”; no further advance evidence is available. Counsel has not confirmed the exemption or first irrevocable commitment date. The following entries reflect the team’s October 13, 2026 handoff:
| ID / note | Source / citation | Obligation / basis | Trigger / due | Owner / reviewer | Dependencies / gaps | Status / next action | Completion proof |
|---|---|---|---|---|---|---|---|
| PC-01 / offering | CM-01 § 2; SEC guidance | Determine Form D applicability; legal | Commitment trigger unresolved; urgent review October 13 | Company counsel / GC | Exemption and subscription evidence missing | Open: obtain evidence; assess deadline immediately | Approved analysis; filing receipt if required |
| PC-02 / N-01 | N-01 § 2; L-01; B-01 | Reconcile funded principal; contractual | Before next accrual; internal target October 14 | Controller / CFO | $150,000 unsupported; $450,000 evidenced | Open: isolate disputed balance and request advance records | Approved ledger tied to evidence |
| PC-03 / SL-01 | SL-01 § 3 | Deliver quarterly accounts; contractual | September 30 quarter-end; November 9 due | Controller / GC | Confirm recipient and approved report | Scheduled: internal preparation November 2 | Final report and delivery record |
The tracker changes three decisions. Counsel investigates the commitment date immediately rather than using the wire date. Finance separates the evidenced interest base from the unresolved balance without deciding that the disputed amount is legally extinguished. Reporting personnel schedule a specific delivery to Alder Path rather than circulating its side-letter report to every holder.
The filing row remains unresolved: neither the exemption nor commitment evidence has been invented to produce a convenient deadline.
Common mistakes
- Reusing the closing checklist unchanged. Extract continuing duties; retain unresolved closing conditions with their actual status.
- Using one row for every holder. Group only matching obligations and identify all covered instruments. Separate side-letter rights and different advance dates.
- Accruing on headline commitments. Apply the contractual accrual basis to verified records and isolate discrepancies for resolution.
- Recording maturity alone. Add event-driven elections, notices, payment restrictions, and recognition owners.
- Closing tasks on assurances. Require the specified proof or retain an assigned exception; do not confuse preparation with performance.
Final quality check
- Each row traces to an executed source or identified legal authority.
- Filing applicability, trigger evidence, and potentially overdue items receive counsel review.
- Contractual deadlines and internal targets are distinguishable.
- Principal and interest records reconcile, or discrepancies have assigned resolution owners.
- Conversion and repayment entries preserve elections, notices, and approval dependencies.
- Every task has an accepted owner, reviewer, and completion standard.
- Open issues have a next action and target date; closed rows retain proof.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review and tabular review capabilities can support examining notes, side letters, and amendments across documents. Give deal-specific instructions and verify extracted obligations against executed sources. The tracker remains the legal team’s work product; lawyers determine applicability, interpretation, and completion. To discuss this company-side handoff within a transactional workflow, book a demo.
Frequently asked questions
Should completed closing obligations appear in the tracker?
Retain completion references where they explain ongoing dependencies. Do not recreate the full closing checklist. Carry unresolved items forward with their actual status and any documented waiver or deferral.
Can identical notes share a reporting or payment row?
Yes, if terms, dates, recipients, and completion evidence align. List covered note IDs. Split the row when an amendment, advance, election, or side letter changes performance.
What happens when a conversion trigger is uncertain?
Record the known event, controlling definition, missing facts, and legal reviewer. Resolve treatment promptly; do not let administrative uncertainty obscure a potentially automatic contractual event or substitute for reviewing its consequences.
Who maintains the tracker after outside counsel’s handoff?
Assign a company custodian in legal or finance, retaining task-specific owners. Specify when counsel must review interpretations, amendments, repayments, and conversion events rather than leaving those decisions to the custodian alone.
Sources
- SEC: Filing a Form D Notice
- Delaware General Corporation Law, § 151(g)
- MiNK–Agenus purchase agreement, Article I.1
- Core Scientific purchase agreement, Exhibit A
Historical filed agreements illustrate particular wording, not current obligations or market standards.
This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.
