Which records should a buyer retain to resolve a post-close dispute?

What should the record set be able to explain?

The records should show what the parties agreed, what information was disclosed, what occurred, how an amount was calculated, and how it was resolved or paid. The buyer hub treats that evidence as part of a workable acquisition process. A collection of screenshots without context is difficult to reconcile with a signed agreement.

Start before closing. Determine which records must transfer, which remain with the seller, which need controlled shared access, and how the parties will obtain evidence for agreed adjustments. Do not wait until a disputed payment is due to discover that the relevant source records are unavailable or the client population was never defined.

Which signed documents belong in the transaction record?

Preserve the executed purchase agreement, amendments, disclosure schedules, seller note, transition agreement, applicable consents, and closing statement. Distinguish executed versions from drafts. Keep attachments and exhibits with their parent document so a reference to a schedule can be followed without guessing which file was intended.

Record the closing date and any later amendment dates. If the parties resolve an issue through a signed change or settlement, preserve that document with the original provision and payment reconciliation. An email discussing a proposed solution should not silently replace an executed agreement in the working file.

How should records connect to a potential claim?

Identify the relevant provision and the factual question it creates. A representation about a known client departure requires different evidence from a working-capital calculation or a transition-services obligation. Organize the records around that question rather than collecting every possible document without a purpose.

The offset rights guide explains why a claimed loss and an authorized payment remedy are distinct. Preserve the facts needed to assess both. A well-supported operating event may still fall outside a particular contractual provision; qualified advisors must evaluate the actual agreement and law.

Why do client population definitions matter?

Retain the client identifiers and service categories that the agreed formula uses, with appropriate confidentiality controls. Distinguish transferred clients, excluded clients, new buyer clients, and later service additions. A change in software identifier should not make the same client appear twice or disappear from the measurement population.

Preserve how the parties treated a client with multiple entities, household members, or service lines. Do not create a new definition after seeing the financial result. Where the documents are ambiguous, identify the ambiguity and seek an authorized resolution rather than adjusting the population invisibly inside a spreadsheet.

What should collections evidence include?

Keep the relevant invoices, payment dates, credits, refunds, write-offs, and supporting ledger entries. Reconcile receipts to the measurement period and the agreement’s allocation rules. Identify payments applied to pre-closing receivables separately from post-closing service fees when that distinction matters to the formula.

A client can remain active while collections fall because billing timing, scope, credits, or payment behavior changed. A client can also leave after paying an old invoice. Preserve those distinctions. The evidence should explain the contractual measurement rather than using the word retained as an undefined substitute for the records.

What does an illustrative reconciliation show?

Suppose a fictional retention calculation begins with $100,000 of receipts. The records identify $12,000 for excluded pre-closing receivables and $8,000 for new services outside the assumed formula. Under those invented definitions, the qualifying receipts would be $80,000. This is arithmetic based on stated assumptions, not a standard retention clause.

The working file should show which transactions make up each deduction and why the agreement treats them that way. If a $5,000 payment was reclassified later, preserve the original treatment, reason, date, and reviewer. Another person should be able to reproduce the result without relying on the spreadsheet author’s memory.

Which transition records deserve attention?

Document requested assistance, availability, work performed, client introductions, unresolved questions, and substitute support. Distinguish a request from an agreed obligation and a scheduled meeting from completed work. Keep important communications with the relevant task or engagement context rather than relying only on a total hour count.

The seller departure contingency guide focuses on continuity if support becomes unavailable. Preserve the operational response as well as the request to the seller. A later review may need to distinguish the effect of unavailable support from an independent staffing gap or the buyer’s own change in service delivery.

How should versions and changes be preserved?

Keep original source records and separately dated analyses. Identify the author, purpose, inputs, and calculation version. If data are exported from a system, record the period, relevant filters, and export date. A later export may differ after credits, corrections, or reclassification, so its timing is part of the evidence.

Do not overwrite the earlier file merely because the newer calculation seems more accurate. Preserve the correction and its reason through the appropriate process. System logs or controlled version history can help explain changes, but their availability and reliability should be tested rather than assumed.

What limits apply to client information?

The AICPA Code of Professional Conduct addresses member confidentiality and other responsibilities within its scope. The IRS Section 7216 information center explains restrictions relating to certain tax return information uses and disclosures. Evaluate the actual information and proposed access with qualified advisors.

Use only the information needed for the legitimate review, under appropriate permissions and controls. Aggregated or redacted evidence may answer some questions, while others require a properly authorized detailed review. A transaction file should not become an unrestricted archive accessible to every employee, buyer contact, lender, or advisor.

How should notice and resolution records be retained?

Keep the notice, supporting calculation, delivery evidence, response, and any applicable determination or settlement. Identify the actual contractual deadlines and required delivery method with counsel. A useful chronology distinguishes when an event occurred, when it was discovered, when notice was sent, and when the amount was resolved.

Reconcile the resolved treatment to the payment ledger. Show what was originally due, what was paid, and any authorized adjustment. Preserve disputed amounts as disputed until resolved. Do not describe a proposed credit as an agreed outcome or present a claim as a proven breach.

How do financing and tax records connect?

The lender findings guide explains how evidence relates to the acquisition’s cash-flow and financing analysis. Preserve material changes to assumptions and any communications required under the actual financing documents. A claim that affects payment timing can also affect liquidity without having the same accounting treatment as lost revenue.

IRS Form 8594 information describes asset acquisition reporting for transactions within its scope. Keep the agreed allocation, relevant reporting records, and later changes with the commercial resolution. Have tax advisors assess the actual consequences rather than assuming every settlement is simply a reduction in goodwill.

Who should own the preservation process?

Assign an authorized custodian and obtain qualified advice on retention, access, routine deletion, and any dispute-related preservation instruction. Different records can have different obligations; there is no single universal retention period established by this guide. Document the instruction and ensure the relevant systems and people can follow it.

The useful outcome is a traceable, controlled record set. It should support an accurate explanation of the transaction while preserving context, confidentiality, and the difference between facts, calculations, allegations, and resolved outcomes.