Field guide / Evidence & organization

Preparing a financial data room for quality of earnings diligence.

A good data room makes the financial story traceable. The goal is to help a reviewer follow a number from the source record to the explanation.

Start by agreeing the scope with your transaction advisers: entities, periods, reporting currencies, acquisitions, accounting basis and expected update cadence. Grant Thornton emphasizes monthly financial normalization and a performance narrative supported by underlying data during M&A preparation.1 The folder structure below is an organizational starting point, not a complete diligence request list.

Build five evidence folders.

Suggested financial diligence folder structure
FolderCore supportControl question
01 · Financial tie-outsMonthly trial balances, financial statements, chart of accounts, consolidation and mapping files.Can the reviewer reproduce the bridge from ledger to the reported results?
02 · Revenue qualityCustomer-level sales, relevant contracts, credits, revenue policies and concentration analysis.Do the detailed records reconcile, and are material movements explained?
03 · EBITDA normalizationAdjustment log, monthly impact, original entries and support for proposed treatment.Can the reviewer distinguish reported amounts, proposals and agreed conclusions?
04 · Working capitalMonthly balance sheets, aging, inventory if applicable, accruals and seasonality analysis.Do definitions, cutoffs and balances remain consistent across periods?
05 · Debt-like itemsDebt and cash schedules, leases, accrued interest and potential transaction obligations.Which items require discussion under the actual transaction definitions?

These areas are consistent with the earnings, customer, working capital and debt topics in RSM's financial diligence description.2 Tax, legal, commercial, operational and other specialist workstreams may require separate material; BDO describes diligence as broader than a traditional QoE analysis.3

Use a single index as the control point.

Give each request a stable identifier, an owner and a clear status. The index should answer what was requested, where the current evidence is, what period it covers, when it was updated, and what remains unresolved. Do not rely on an upload timestamp to communicate whether a file is final.

A practical file convention is RequestID_Subject_Period_Version. For example, REV02_CustomerRevenue_2025-01_to_2026-06_v03.xlsx. This fictional name identifies the topic and coverage without revealing a customer's name. Preserve superseded files according to your company's approved process, and point reviewers to one current version.

Reconcile before distributing.

For each material schedule, include a short control block: source system, extraction date, filters, included entities, currency, totals and the reference used for reconciliation. Then document the reconciling items. A difference is more useful when explicitly explained than hidden inside a plug.

For example, a sales export may differ from ledger revenue because of manual journals, unbilled revenue, deferred revenue movements or scope differences. Investigate the actual cause. Do not assume one generic bridge is appropriate for every business model.

Keep adjustments reviewable.

Each proposed EBITDA adjustment should have a unique ID and a monthly impact schedule. Include the explanation, original account references and relevant evidence. Link supporting files rather than repeatedly pasting different versions of the same calculation. Capture possible offsets and recurring replacement costs so the proposal is visible in full.

Keep the adjustment assessment distinct from the issue register. A schedule can be complete even when the economic treatment remains disputed; record that disagreement plainly rather than marking the entire topic resolved.

Turn open questions into actions.

Choose access deliberately.

Use the organization's approved data-room platform and sharing controls for sensitive evidence. Agree access with the deal team, minimize personal data and preserve an appropriate record of changes. QoE Kit's browser workspace holds status notes only; it is not a document repository or a substitute for a secure transaction data room.

Maintain the work after diligence.

Carry repeatable reconciliations into the monthly close. Transfer unresolved operational actions into an acquisition integration plan with owners and dependencies.

Further reading

  1. Grant Thornton — M&A readiness: Prepare for value achievement. Monthly normalization and evidence supporting the performance narrative.
  2. RSM — Financial due diligence. Typical financial analysis areas.
  3. BDO — Due diligence. Coordination of financial and wider diligence workstreams.

Sources reviewed October 11, 2026. The folder and control suggestions are an original practical framework, not a professional standard or exhaustive request list. Referenced firms have not endorsed this tool.

Give every evidence gap an owner.

Use the free checklist to track your preparation and export a working copy.

Open the readiness checklist →