Make the numbers traceable before uploading more files
A financial data room should let an authorized buyer follow the business's results into the records that support them. Start with reconciled statements, a clear index, and a named owner for questions. Hundreds of unlabelled exports create more work when the same period appears under different filenames or a supporting schedule cannot be tied to the accounts.
RSM describes financial diligence across earnings, working capital, margins, and customer analysis. BDO's exit guidance also examines revenue recognition, reserves, and supporting adjustments. This article focuses on organizing the evidence for that work. Legal, tax, employment, cybersecurity, and commercial diligence require their own scoped investigation and access decisions.
References: RSM: Financial due diligence scope; BDO: Financial preparation for a private equity exit
Agree the perimeter and the reporting periods
Write a scope note naming the entities, locations, business lines, currency, accounting basis, and periods represented. Identify acquisitions, disposals, reorganizations, or system migrations during that history. If the sale concerns only part of the business, explain what has been directly identified and what has been allocated. A consolidated report alone may not describe the assets and operations being offered.
Ask the deal team for the initial request list and proposed update cadence. Distinguish historical full years, the latest year-to-date period, monthly detail, and forecasts. Use the same cutoff in related schedules. Keep a visible list of records still being prepared, including who owns each item and when the next reliable version will be available.
Build an index around the questions reviewers ask
A useful index points to a final document or a controlled source folder, describes its period, and explains how it ties to other records. The following structure is a starting point for a finance workstream. Adapt it to the requested diligence scope and the business's material exposures rather than filling folders with irrelevant documents.
| Folder | Core evidence | Link to preserve |
|---|---|---|
| Financial statements and ledger | Issued statements, monthly trial balances, adjusting entries | Monthly totals to annual accounts |
| Revenue and customers | Revenue detail, material contracts, credits, customer analysis | Transaction detail to reported revenue |
| Costs and people | Vendor costs, payroll summaries, material commitments | Schedules to expense accounts and liabilities |
| Working capital | AR, inventory, AP, accruals, reserve support | Subledgers to balance-sheet accounts |
| Debt and cash | Facility agreements, balances, restrictions, bank reconciliations | Statements to financing and cash schedules |
| Adjustments and forecasts | Proposed EBITDA adjustments, assumptions, approved models | Reported figures to adjusted or forecast figures |
| Questions and updates | Request register, responses, superseded-file log | Each answer to the version reviewed |
Keep a reconciliation beside every important export
Suppose annual financial statements show $8 million of revenue while monthly sales exports total $8.2 million. Resolve the difference before a reviewer has to discover it. It may involve credits, deferred revenue, an excluded entity, a cutoff adjustment, or an error. Save a concise bridge identifying the exact amounts and source records.
Use a comparable approach for employee counts, payroll costs, inventory quantities, and customer balances. A report's commercial definition may differ from its accounting definition. State that difference in the index or accompanying note. Do not alter raw exports to make them appear consistent; retain the original and provide a controlled reconciliation that another person can reproduce.
Control access and versions as the deal progresses
Assign access according to the approved transaction process. Payroll, customer, bank, and tax records can contain personal or commercially sensitive information. Use redacted or aggregated material where it answers the current question, and obtain the appropriate authorization before sharing more detail. Keep an owner for access changes when advisers join or leave the process.
Give final files a clear period and version identifier. When a new month closes or an error is corrected, publish the replacement with an explanation and preserve the previous version under controlled access. Avoid silent overwrites. The request register should identify which version an answer relied on so later questions do not mix old assumptions with current data.
Make the request log a record of resolved questions
Record each request, the underlying business question, owner, deadline, source file, answer, and remaining limitation. Consolidate duplicate questions while retaining their recipients. If a buyer asks why gross margin changed, an unexplained spreadsheet is an incomplete answer. Provide the relevant calculation and a factual explanation of price, volume, mix, or cost movements supported by the records.
Before a major release, ask someone who did not assemble the folder to trace one revenue number, one working capital balance, and one proposed adjustment. Fix retrieval failures and unexplained differences. If external accounting support is needed, scope the missing reconciliations and record preparation directly so the company can distinguish production of evidence from the transaction adviser's independent evaluation.
Sources
Requirements and product details can change. Check the linked guidance for the facts that apply to your situation.
Related reading
Need help with this work?
General information, not personalized accounting, tax, legal, or investment advice. Have the appropriate qualified professional review decisions that depend on your circumstances.