How to build a closing deliverables checklist for Share Purchase Transactions

Build a buyer-side closing deliverables checklist by extracting each delivery obligation from the signed share purchase agreement and ancillary documents, linking it to the relevant condition, and assigning preparation, signature, review, and release responsibility. Reconcile the share-transfer package against ownership evidence rather than treating signed forms as sufficient. The resulting checklist should show what must be delivered, by whom, in what form, and on what release conditions, with source references and unresolved issues visible to the lawyer coordinating closing authorization.

When to use this workflow

Use this workflow once the purchase agreement is sufficiently settled to identify closing obligations, then reconcile the checklist to the executed agreement. It serves buyer’s counsel, in-house transaction teams, and closing coordinators exchanging share-transfer documents, certificates, ancillary agreements, and funds.

The scope is the closing package—not a replacement for diligence, a title opinion, or a complete post-closing tracker. Include diligence findings where they produce a delivery, approval, evidence requirement, or release dependency. Track buyer deliveries as well as seller deliveries: a buyer-side checklist must capture both sides of the exchange.

This is a general US legal-workflow guide. Delaware statutory points apply to Delaware corporations; other jurisdictions and regulatory regimes require separate analysis. The statutory and contractual sources below support specific propositions, not a universal list of required deliveries. The remaining checks are workflow recommendations.

What you need

Start with the executed purchase agreement, schedules, exhibits, amendments, and agreed ancillary forms. Add the current issues list so negotiated solutions remain visible at closing.

For the share-transfer package, collect the stock ledger, capitalization table, certificates or uncertificated-share records, seller details, transfer restrictions, and evidence addressing liens or consents. For payment deliveries, obtain the purchase-price provisions, estimated closing statement if required, funds flow, payment instructions, and applicable payoff or release documents.

Also gather:

• The conditions analysis, identifying beneficiaries, satisfaction standards, evidence requirements, and potential waiver authority.
• Required approvals, signatory capacities, recipient instructions, and responsibility for updating ownership records.
• Regulatory counsel’s status assessment and supporting evidence, where applicable.
• The proposed closing sequence, signature custodian, and release arrangements.

Give the working source set an identifiable version. A checklist built from an unsigned draft can omit a late delivery obligation or retain one that was deleted.

Use the template

The Share Purchase Transactions — Closing deliverables checklist is a working template. You can copy this table into your working document or spreadsheet. Create one row per independently reviewable delivery or release gate.

Use stable row IDs such as CD-01. In “Source / evidence,” distinguish the obligation citation from proof of performance: for example, SPA § 3.2(a); file ST-04, page 2. Identify the relevant seller, shares, certificate, or agreement rather than writing “transfer documents.”

Name preparer and signatory separately, and distinguish the recipient from the buyer reviewer. Record exact contractual timing, including deliveries due before closing; use other row IDs for dependencies.

Use statuses such as requested, draft received, form agreed, executed and held, released, and receipt confirmed. Put the open question, named decision-maker, and decision reference in the last two columns. Link longer analysis to an issue note.

Step by step

1. Extract deliveries from the operative documents

Read closing mechanics and delivery provisions alongside conditions, covenants, exhibits, and ancillary agreements. Include buyer certificates, payment evidence, escrow documents, or other reciprocal deliveries where required. Separate a document to be delivered from a factual condition that must be true.

The AMD–ZT agreement illustrates this connection: § 8.2 conditions the buyer’s closing obligation on specified matters, while § 8.2(e)(i)–(ii) specifies share-transfer documentation and a CEO certificate addressing designated conditions. These are negotiated requirements, not universal closing rules. AMD–ZT Stock Purchase Agreement, § 8.2.

Record: each delivery, precise source, required form, contractual timing, and related condition. Label additional buyer requests separately from contractual obligations.

2. Reconcile the transfer package to the purchased shares

Build transfer rows around actual sellers and holdings. Check names, classes, quantities, certificate identifiers, and uncertificated-share treatment against the transaction perimeter. Confirm how options, warrants, or other outstanding rights are addressed under the agreed structure; do not assume every security is transferred in the same way.

For Delaware corporations, DGCL § 219(c) defines the stock ledger by reference to record holders, addresses, registered share amounts, and recorded issuances and transfers. Treat it as an ownership-reconciliation input, not a clean-title conclusion or complete beneficial-ownership record. Delaware Code, § 219(c).

Record: seller-specific items, ownership evidence IDs, discrepancies, and the responsible reviewer. Assign any required ledger update or transfer acknowledgment without treating it as a substitute for the underlying transfer evidence.

3. Identify restriction, consent, and release dependencies

Review the charter, bylaws, holder agreements, relevant financing documents, and identified change-of-control provisions. Distinguish share-transfer restrictions from contractual ownership-change triggers; do not assume an assignment clause necessarily answers both questions.

For Delaware corporations, § 202 addresses restrictions in specified corporate and holder documents. Its notice rule accounts for actual knowledge, so absence of a certificate legend alone does not establish unrestricted transferability. Delaware Code, § 202(a)–(b).

Determine whether the agreed closing structure calls for a waiver, consent, payoff, release, or other evidence. A diligence concern does not itself create a contractual delivery entitlement.

Record: restriction source, required response, approver, and dependent row. Assign unresolved applicability questions rather than inventing consent requirements.

4. Assign preparation, signature, and substantive review

Identify who produces, signs, receives, and reviews each item. Check the signer’s identity and capacity against the relevant authority materials. Route entity-specific documents to the correct signer.

For an officer certificate, compare the text with the exact conditions, qualifiers, and measurement dates it must address. In the AMD–ZT example, the CEO certificate addresses the specified conditions in §§ 8.2(a)–(c), not every closing condition. AMD–ZT Stock Purchase Agreement, § 8.2(e)(ii).

Ask the responsible team about known facts inconsistent with the proposed certification. Keep receipt of a certificate separate from the buyer’s assessment of the underlying condition.

Record: named owners, signature capacity, approved form, reviewer, and outstanding factual support. “Seller counsel” is not enough where several entities or officers must act.

5. Separate evidence receipt from closing authorization

Classify each gate as a delivery, contractual condition, or regulatory restriction. Identify who confirms satisfaction and who may authorize a contractual waiver. Preserve the distinction between satisfaction, waiver, and an unresolved blocker.

FTC guidance explains that certain acquisitions require premerger notification and observance of a waiting period, which a Second Request extends. Applicability and exemptions require transaction-specific analysis. Obtain regulatory counsel’s confirmation rather than calculating a permissible closing date from assumptions. FTC, Premerger Notification and the Merger Review Process.

Record: evidence, reviewing counsel, condition beneficiary where relevant, and decision authority. Do not classify a regulatory restriction as buyer-waivable merely because a related contractual condition benefits the buyer.

6. Build the document-and-funds release sequence

Walk through the exchange with transaction counsel and treasury. Identify which documents may be signed early, who holds them, and what authorization permits release. Map payment, payoff, share-transfer, and ancillary-document dependencies under the actual closing arrangements.

Distinguish an agreed draft from an executed document, and execution from effective release. Check that the reviewed version is the released version. Independently confirm payment instructions through the team’s approved verification procedure. Reconcile the funds flow with required deductions, holdbacks, escrow payments, and seller allocations under the agreement.

Record: release custodian, prerequisite row IDs, authorization reference, and receipt evidence where appropriate. Document any simultaneous-exchange arrangement; do not create circular dependencies that nobody can satisfy first.

7. Resolve exceptions and preserve the closing record

Review every open row with its accountable owner. Resolve the gap, obtain an authorized contractual decision where available, or retain it as a blocker. Do not move an overdue closing delivery into a post-closing list merely to clear the checklist.

If the parties agree to defer an item, document the arrangement and assess its effect on the delivery obligation and related conditions. Cross-reference genuine post-closing obligations in a separate tracker.

Record: final disposition, decision authority, release evidence, and delivered-version location. Preserve a closing snapshot showing what was delivered, what was released, and how any remaining exceptions were addressed.

Worked example

Fictional scenario: North Quay Holdings, Inc. agrees to buy all 10,000 shares of Alder Circuit Systems, Inc., a Delaware corporation, from two sellers for $24 million. The invented SPA requires transfer instruments under § 3.2(a), a payoff-and-release package under § 3.2(c), and an officer certificate under § 8.2(d). All parties, amounts, provisions, and documents in this example are fictional.

Ledger LG-01 attributes 6,000 shares to Seller A and 4,000 to Seller B. Seller A’s proposed instrument covers only 5,800 shares. A signed lender payoff letter exists, but its coverage of pledged target shares remains unconfirmed. The officer certificate is agreed but unsigned. These three representative rows are not the entire closing checklist.

CD-01 prevents approval based solely on execution: no evidence explains the missing 200 shares, so the reviewer cannot assume a typo or prior transfer. Seller B’s 4,000 shares do not resolve that discrepancy.

CD-02 makes release scope and effectiveness—not receipt of a signed payoff letter—the decisive questions. CD-03 separates drafting completion from delivery and substantive condition review. On the available evidence, none supports unconditional release. The checklist identifies the missing evidence without inventing a cure.

Common mistakes

• Copying an asset-deal checklist. Replace irrelevant asset conveyances with seller-and-holding reconciliation, share-transfer requirements, and relevant ownership-change checks.
• Combining every seller in one status row. Split items where holdings, capacities, or execution can fail independently.
• Marking agreed forms complete. Track substantive approval, execution, custody, release, and receipt distinctly.
• Treating every request as an entitlement. Cite the obligation or identify an additional request; assess refusal under the actual agreement.
• Ignoring reciprocal deliveries. Include buyer documents and payment responsibilities so seller releases are not scheduled against an incomplete buyer package.
• Relabeling blockers as follow-ups. Identify the permissible decision path and authorized decision-maker before treating a gap as nonblocking.

Final quality check

• Every contractual delivery cites the executed source and relevant amendment.
• Seller identities, holdings, classes, and certificate references reconcile, or discrepancies remain expressly blocking.
• Forms, preparers, signatories, recipients, and reviewers are identified.
• Executed versions match approved versions, including attachments.
• Regulatory restrictions remain distinct from contractual waiver decisions.
• Funds and document releases have workable dependencies and authorization evidence.
• Open issues are resolved or assigned to named decision-makers with explicit blocking status.
• The closing snapshot links delivered documents, release confirmations, and documented deferrals.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review supports buyer-specific instructions in Word and findings that quote clauses, rank severity, locate text, and identify missing language as not present. Tabular review supports work across multiple documents. Use those capabilities to support extraction and comparison; the checklist, evidence assessment, and release decisions remain lawyer-controlled. To discuss this closing workflow, book a demo.

Frequently asked questions

Should the checklist include conditions requiring no document?

Yes, as labeled gates. Record the condition, assessment evidence, reviewer, and decision authority. Do not invent a certificate requirement merely because documentary confirmation would be convenient.

Can one row cover all share-transfer instruments?

Only if individual completeness remains visible elsewhere. Multiple sellers, classes, capacities, or ownership discrepancies generally justify separate rows linked to a common package.

What if a seller promises delivery after closing?

Check the obligation and related conditions before accepting deferral. Obtain the authorized buyer decision and document the agreed treatment. A promise of later delivery is not present performance.

Does a signed payoff letter establish release?

Not by itself for checklist purposes. Review the covered debt, collateral, conditions, effective timing, and any further release documents. Record what evidence establishes the required release under the agreed arrangements.

Sources

• Delaware Code, Title 8, § 219(c): stock ledger definition.
• Delaware Code, Title 8, § 202: transfer restrictions.
• FTC: Premerger Notification and the Merger Review Process.
• AMD–ZT Stock Purchase Agreement, § 8.2: negotiated buyer conditions and deliveries.

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.