Seller Due Diligence Checklist: How to Prepare for Buyer Review

What a Seller Due Diligence Review May Cover

The parts of the business that generate worklist rows depend on your company and the active request. Still, one filed checklist illustrates how widely the questions can range.

A checklist attached to a January 23, 2004 asset purchase agreement filed with the U.S. Securities and Exchange Commission covers corporate, ownership, employment, contractual, property, intellectual-property, regulatory, insurance, legal, accounting, and operating matters. It is one transaction’s checklist, so its value here is as an example of possible breadth rather than a standard for every sale.

Use this map to spot possible questions, then decide which ones apply. If a request concerns an operating agreement, create a row that connects the agreement to the entity named in the request. An equipment question may call for warranty records or maintenance history. Whether either subject belongs in your file depends on the business and the request in front of you.

Apply the same discipline across the map. “Contracts” names an area, but a useful row identifies the question, the relevant entity and period, and the particular record offered in response. That connection lets a reviewer understand why the document is present without assuming that the file resolves the question.

Keep breadth separate from applicability because a review may reach many parts of the business without requiring every possible item. We would judge the checklist by whether the relevant questions have intelligible support and whether any limits remain visible, not by its length.

Financial information makes that test especially concrete because a single number may appear at several levels of detail.

Which Financial Records Support the Numbers Under Review?

A financial statement presents summarized results or balances. The accounting books contain more detailed entries, related listings organize particular balances or assets, and transaction-level documents support entries in the books. These records perform different jobs, even when they all concern the same figure.

The SEC-filed checklist requests a general ledger, trial balance, and subledgers that tie to the financial statements. It separately requests accounts-payable and accounts-receivable listings tied to the most recent year-end and interim statements, as well as an inventory listing tied to current financial statements.

Those requests create parallel tests:

• Do the general ledger, trial balance, or relevant subledger agree with the financial statements?
• Does the accounts-payable, accounts-receivable, or inventory listing agree with the corresponding amount in the applicable statements?
• Do underlying documents support the entries recorded in the books?

The third question reaches below the accounting summaries. In federal tax-recordkeeping guidance, the Internal Revenue Service describes accounting journals and ledgers as summaries of business transactions. It names sales slips, paid bills, invoices, receipts, deposit slips, and canceled checks among the documents that support entries in the books and on a tax return. It also notes that more than one supporting document may be needed to substantiate every element of a purchase.

Here is how the record layers relate:

Financial statements
                           ↑               ↑
             books and accounting       related listings
             records                    (payables, receivables,
             (general ledger,           or inventory)
             trial balance,
             subledgers)
                    ↑
        supporting transaction documents

Treat the diagram as a guide rather than a fixed path. The SEC-filed checklist supports tie-outs from accounting records and specified listings to the statements. The IRS guidance explains the separate relationship between entries in the books and their supporting documents.

A tie-out asks whether the amount carried at one level agrees with the relevant detail. For the recurring accounts-payable row, possession of the listing and the statements is only the beginning. The row should identify the applicable company and periods and preserve whether the listing agrees with the year-end and interim statements.

If the figures agree, the connection is visible. If they don’t, the mismatch belongs beside the original question. Otherwise, a reviewer may see two files and reasonably assume that someone has already tested the relationship between them.

Underlying documents answer another question: what supports the entries recorded in the books? In the IRS recordkeeping context, an invoice, paid bill, receipt, deposit slip, canceled check, or combination of documents may support a recorded transaction. These documents do not determine business value or prove a sale claim. They show why a financial statement alone may not complete the review.

This is where the worklist earns its keep. It preserves the connection that a folder structure can hide: which record supports which question, whether the numbers agree, and where the evidence stops.

How Should Sellers Handle Missing or Inconsistent Records?

A missing copy, an identified problem, an obtained record, and an inapplicable request are different conditions. Calling all four “pending” makes the worklist shorter but much less informative.

The SEC-filed transaction checklist uses four compact status labels:

These labels came from one transaction, but their distinctions are useful. Not Applicable does not mean that a record is missing. Keep Problem Identified separate from ordinary collection work. Copy Obtained confirms possession and nothing more: it doesn’t establish that the document is current, responsive, internally consistent, reconciled, sufficient for the question, or ready to share.

Use the comments column for detail that a status cannot carry. On the accounts-payable row, for example, the status can show whether you have the listing. The comment can record whether someone checked it against the applicable year-end and interim statements and whether an inconsistency or missing support remains.

That comment should stay attached to the original question. Separating the issue into a general notes file weakens the connection between what the buyer asked, what you have, and what remains unresolved. A concise explanation on the row lets the next reviewer understand why an item marked as obtained may still require attention.

We would keep the status vocabulary compact and allow the comment to carry the necessary distinction. An ever-growing set of labels can become harder to interpret than the underlying records. The important thing is that the file doesn’t confuse applicability with collection or possession with resolution.

Use these statuses to show the current condition, not to decide how to cure a gap or what to disclose. Once you have the records and understand their connections, access remains a separate decision.

When Should Sensitive Due Diligence Records Be Shared?

You may still decide not to share a complete, relevant, and reconciled record with a particular recipient at a particular stage. If the checklist uses one “done” status for both preparation and release, that distinction disappears.

The risk is especially clear when a transaction involves competitors or potential competitors. The Federal Trade Commission advises parties in that context to share the least information needed for effective due diligence, tailor the information to the specific issue, and adjust disclosure to the stage of the process. Its guidance explains that earlier stages may involve more viewers but less information, while later stages may involve fewer viewers and require greater detail. It identifies current and future prices, strategic plans, costs, and non-aggregated customer-specific information as potentially sensitive.

So keep collection status and access decisions in separate fields. A row can show Copy Obtained while you decide whether to share it based on the recipient, process stage, sensitivity, safeguards, contracts, privacy obligations, competitive circumstances, and qualified advice.

An access field should record the decision relevant to that row without pretending the checklist can make it. The correct result will depend on the transaction. The FTC’s competitor-focused guidance doesn’t supply a universal disclosure protocol, and preparation alone can’t answer a legal or contractual access question.

Use a separate business sale data room checklist to manage folder structure, filenames, versions, permissions, delivery stages, and activity records. If the next issue is who may receive information, what an NDA covers, or how to approach competitor-sensitive or customer information, see confidentiality before selling a business.

For an owner who doesn’t yet have an active or reasonably anticipated request, a sale readiness checklist is a better starting point than building an assumed diligence inventory.

At the end, each relevant question should connect to the right entity and period, the record layer meant to answer it, any inconsistency or missing support, a meaningful status and comment, and a separate access decision. When those connections remain visible, the review file explains what the documents mean instead of merely proving that someone collected them.