Acquisition Financing Transactions

How to build a closing deliverables checklist for Acquisition Financing Transactions

Build a borrower-side acquisition financing closing checklist with a copyable template, funding dependencies, payoff checks, and a fictional worked example.

October 18, 2026  ·  10 min read
Book a Demo →

Build a borrower-side closing deliverables checklist by translating the operative financing documents into documents, actions, owners, acceptance criteria, and funding dependencies. Separate agreement effectiveness, acquisition completion, and loan funding; connect authority documents, payoff arrangements, collateral requirements, certificates, opinions, and funds-flow instructions to the correct milestone. The resulting checklist should establish who prepares and accepts each item, what evidence supports completion, and whether unfinished work blocks funding, requires an authorized waiver, or falls within an express post-closing arrangement.

When to use this workflow

Use this workflow when borrower’s counsel or an in-house finance team has a developed financing package and needs to coordinate execution and funding. Start before signature circulation, while authority documents, payoff mechanics, and closing certificates can still be corrected.

The scope is US acquisition-financing practice, coordinated with acquisition counsel, treasury, target counsel, and financing counsel. Tailor the checklist to the acquisition structure and the entities borrowing, guaranteeing, or granting collateral. An unsecured facility should not inherit secured-loan deliverables without a contractual basis.

Determine applicable law separately for entity authority, contractual obligations, and collateral. A credit agreement’s governing-law clause does not alone determine perfection law; Delaware Sections 9-301 and 9-304 illustrate distinct debtor-location and bank-jurisdiction rules. Delaware Article 9, Part 3. This is a general professional workflow guide, not advice for a particular closing. (delcode.delaware.gov)

What you need

Collect the sources and information needed to produce the deliverables:

  • Commitment documents, fee letters, credit agreement, guarantees, security documents, amendments, and written condition modifications.
  • Acquisition agreement, relevant schedules and amendments, closing sequence, and purchase-price calculation.
  • Borrower, target, and guarantor organizational documents, entity chart, signing authorities, and officer availability.
  • Existing debt and lien information, payoff drafts, release arrangements, and collateral-specific requirements.
  • Financial information supporting certificates, borrowing requests, equity contributions, fees, and funds flow.
  • Closing contacts, delivery mechanics, document versions, and written waivers or deferrals.

Assign stable document IDs. Distinguish executed documents, agreed forms, and negotiating drafts. Missing schedules should generate open items, not assumptions that omitted requirements are inapplicable.

Use the template

Use the Acquisition Financing Transactions — Closing deliverables checklist as the working record. You can copy this table into your working document or spreadsheet. Keep row IDs stable as items change.

ID / milestone Deliverable / entity Source / version Preparer / signer / recipient Timing / dependency Acceptance / evidence Status / gap Action / owner

Distinguish effectiveness, acquisition completion, funding, and expressly deferred work in the milestone field. Record the document ID, section or page, and version in the source field, including definitions that qualify the requirement.

Separate the preparer from the signatory and recipient. For unsigned actions, identify the approver instead. Acceptance describes the required content or event; evidence identifies what proves completion. Receiving a certificate is different from verifying its required statements.

Use statuses such as drafting, under review, agreed form, signed/held, delivered, accepted, waived, or deferred. These are team conventions, not independent conclusions about contractual satisfaction. Link related rows and record approval evidence in the acceptance field.

Step by step

1. Establish the operative sources and milestones

Compare the commitment package with the definitive financing documents. Identify which provisions govern each milestone and whether execution or effectiveness changes earlier obligations. Escalate inconsistencies rather than assuming the latest draft controls.

Keep effectiveness distinct from borrowing. Portland General Electric’s filed credit agreement separates effectiveness conditions in Section 4.1 from closing-date borrowing conditions in Section 4.2. Effectiveness deliverables include organizational documents, resolutions, incumbency certification, and an outside-counsel opinion. These are negotiated requirements, not a universal checklist. Sections 4.1–4.2. (sec.gov)

Record: source IDs, versions, milestone labels, and an owner for each unresolved source conflict.

2. Translate conditions into discrete deliverables

Read each condition with its definitions and referenced documents. Separate rows when preparers, signatories, or acceptance standards differ. One “corporate documents” row can conceal a missing guarantor resolution or incorrectly named entity.

For certificates, identify required statements, covered entities, testing time, supporting information, and authorized signer. For opinions, identify scope, counsel, addressees, and agreed form. For borrowing requests, capture contractual delivery mechanics and timing rather than assuming a standard notice period.

Separate delivery tasks from substantive conditions. If a certificate depends on financial information that remains unavailable, show both the document task and the unresolved support requirement.

Record: a row for each deliverable or action, its source citation, acceptance criteria, and supporting dependencies.

3. Assign preparation, signature, and acceptance responsibility

Allocate preparation among borrower’s counsel, acquisition counsel, target counsel, treasury, officers, and other providers. Confirm that each proposed signer acts for the correct entity and will be available.

Identify the recipient and the person responsible for assessing compliance. Separately identify contractual approval or waiver authority. Do not infer that authority from who manages the closing emails.

Set internal preparation and review targets backward from funding. Label them as internal targets, distinct from contractual deadlines. Where a third party must act—such as an existing lender providing release documentation—assign a borrower-side follow-up owner rather than listing only the external contact.

Record: preparer, signer or approver, recipient, timing, and unresolved authority questions.

4. Build the payoff, release, and collateral package

Connect each payoff to its obligor, calculation date, payment instructions, release authorization, and implementation evidence. Distinguish authority to release a lien from the filing or other action implementing that release.

An acquisition does not itself establish that assets are lien-free. Where applicable, Delaware Section 9-315(a) generally continues a security interest after collateral disposition unless the secured party authorizes disposition free of it, subject to statutory exceptions. In an equity acquisition, separately examine liens remaining on the target’s assets. Section 9-315. (delcode.delaware.gov)

Do not reduce collateral work to financing statements. Delaware Sections 9-310 and 9-312 provide filing rules and exceptions; deposit-account perfection generally requires control, subject to the proceeds exception. Confirm applicable law before selecting the required documents and actions. Sections 9-310 and 9-312. (delcode.delaware.gov)

Record: linked payoff, release, and new-security rows, with required evidence and unresolved collateral questions.

5. Connect deliverables to acquisition completion and funds flow

Map equity contributions, available cash, loan proceeds, acquisition payments, refinancing, and fees. Reconcile entity names and amounts with the funds-flow schedule. Assign treasury responsibility for independently confirming payment instructions under the team’s procedures.

Identify acquisition events required before or substantially concurrently with borrowing. Portland General Electric’s Section 4.2(ii), for example, requires substantially concurrent acquisition consummation and regulates specified adverse acquisition-agreement changes, with express purchase-price provisions. It does not establish a general lender-consent rule for every amendment. Section 4.2(ii). (sec.gov)

Test a changed purchase price, delayed equity receipt, or revised payoff amount against the actual requirements. Identify who confirms each simultaneous-closing event and authorizes release of held documents.

Record: funds-flow references, sequencing dependencies, required approvals, and unresolved funding decisions.

6. Resolve blockers without inventing deferrals

Classify open rows as drafting problems, factual gaps, substantive compliance issues, or delivery tasks. Identify the cure, decision-maker, and completion evidence.

Do not postpone collateral work merely because it is inconvenient. Shutterfly’s historical commitment letter permitted certain unavailable collateral and insurance items to follow closing after commercially reasonable efforts, under agreed timing and express carve-outs for defined UCC filing collateral and stock certificates. It created no general grace period. Certain Funds Provisions. (sec.gov)

For an authorized deferral, preserve its scope, trigger, deadline, extension authority, and approval evidence. Transfer follow-up responsibility to a separate calendar while retaining the checklist reference. Borrower acceptance of commercial risk is not a substitute for required financing-party approval.

Record: cure or authorized waiver/deferral, supporting document, approving authority, and follow-up owner.

7. Verify completion and preserve the closing snapshot

Before funding, reconcile the checklist with final documents and funds flow. Confirm that signatures are not merely held pending release and that delivery evidence concerns the correct version.

Obtain reviewer confirmation where required. Do not infer acceptance from silence unless the operative documents expressly provide a deemed-acceptance mechanism and its prerequisites are satisfied. Portland General Electric’s Section 4.1 contains such a mechanism for specified lender approvals; it should not be generalized beyond its terms. Section 4.1. (sec.gov)

Preserve the dated checklist used for the funding decision, acceptance evidence, and deferred-item handoff. Distinguish subsequent administrative completion from satisfaction at funding.

Record: final status, evidence location, reviewer confirmation, unresolved decision owner, and snapshot reference.

Worked example

Fictional scenario: Harbor Ridge Components LLC is acquiring the equity of Mesa Precision LLC for $84 million, using a $52 million secured term loan and buyer cash. All parties, documents, amounts, and terms in this example are fictional.

The fictional agreed credit agreement, FIN-01 v8, separates effectiveness from funding. Section 4.1 requires authority documents; Section 4.2 requires a specified target-debt payoff package and substantially concurrent acquisition completion. Section 6.14 expressly permits one identified account-control agreement to follow funding within 20 days. No other collateral deferral is stated.

The payoff draft references an absent release schedule. The authority certificate is signed but held for release. These facts support different checklist statuses:

ID / milestone Deliverable / entity Source / version Preparer / signer / recipient Timing / dependency Acceptance / evidence Status / gap Action / owner
C01 / effectiveness Harbor Ridge authority certificate FIN-01 v8 §4.1; CORP-03 p.2 Borrower counsel / officer / agent counsel Before effectiveness Required attachments verified; delivery evidence Signed/held; attachments and release unconfirmed Borrower counsel verifies attachments and release before marking delivered
C02 / funding Mesa payoff and lien releases FIN-01 v8 §4.2; PAY-02 v3 p.3 Existing lender counsel / lender / agent counsel Funds-flow line 7 Approved payoff; complete release authorization Open; release schedule missing Acquisition counsel obtains schedule; release scope cannot yet be assessed
C03 / deferred Named account-control agreement FIN-01 v8 §6.14 Borrower counsel / required parties / collateral agent Within 20 days after funding Executed agreement for identified account Expressly deferred; execution outstanding Finance counsel records funding date, calculates deadline, and collects completion evidence

C01 is not delivered merely because it is signed. C02 remains unresolved: the supplied draft cannot establish the release scope, so counsel must obtain the schedule before deciding whether the package satisfies the funding condition. C03 is not a blocker solely because execution remains outstanding; the fictional agreement permits that specific deferral. Its permission cannot be extended to other accounts or collateral.

Common mistakes

  • Copying a generic financing checklist. Remove unsupported items and add acquisition-specific payoff, equity, purchase-price, and simultaneous-closing dependencies.
  • Treating every target issue as a funding blocker. Identify the operative financing condition and required evidence before assigning that consequence.
  • Marking signed documents complete. Distinguish holding, release, delivery, and acceptance where relevant.
  • Combining payoff and release into one checkmark. Identify payment triggers, release scope, and remaining implementation actions.
  • Treating correspondence as an unrestricted waiver. Verify authority, scope, conditions, and required formalities before changing status.

Final quality check

  • Every required item has a verified source, section, and version.
  • Entity names and capacities match the acquisition and financing structure.
  • Effectiveness, acquisition completion, and funding remain distinct.
  • Preparation, signature, receipt, and acceptance responsibilities are assigned.
  • Payoff amounts, payment instructions, releases, and funds-flow dependencies have responsible reviewers.
  • Completion statuses correspond to actual evidence and applicable acceptance mechanics.
  • Every open issue is resolved or assigned for an identified closing decision.
  • Deferred items have documented authority, timing, and follow-up ownership.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use contract review and tabular review to examine requirements across financing documents. In Word, choose the borrower as the represented party and provide deal-specific instructions; findings quote and locate clauses, rank severity, and identify missing language as not present. Counsel builds the checklist and verifies satisfaction. Book a demo to discuss reviewing your closing-document set.

Frequently asked questions

Should the checklist include acquisition deliverables?

Include acquisition deliverables affecting financing readiness or sequencing. Cross-reference acquisition counsel’s checklist rather than duplicating every acquisition item and creating conflicting completion records.

Can one row cover every guarantor’s authority documents?

Only if each entity’s documents, signer, and evidence remain identifiable. Use separate rows when entities have different counsel, authority structures, or outstanding approvals.

Does receipt of a closing certificate establish satisfaction?

Receipt establishes delivery, not necessarily support for its statements. Assign review of the required certification, testing time, and underlying information before recording substantive acceptance.

What happens if the closing date moves?

Recheck date-sensitive certificates, payoff calculations, borrowing notices, funds flow, and commitment availability against the documents. Notify owners and refresh affected evidence; do not assume an acquisition extension extends financing commitments.

Sources

Filed agreements illustrate their own wording, not general law or market standards. Checklist design and verification steps are workflow recommendations, not independent legal requirements.

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.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo