Tracing findings back to their sources

Financial diligence depends on a chain of evidence. A reported metric may pass through an accounting export, a normalization step, a calculation, and an adjustment before appearing in a deliverable. Each step changes what a reviewer needs to understand.

Preserve the identity of the source file, the relevant row or document location, the entity, and the analysis period. Similar filenames or repeated exports are not enough to establish that two reviewers are looking at the same evidence.

Keep the original. A hash of the uploaded file, its size, and the time it was received are cheap to record and settle most later disputes about which version was analyzed. If the file is replaced, keep both and note the reason.

Normalization should make records easier to analyze without erasing their origin. Mapping a ledger account into a financial category is a transformation that should remain understandable to the person reviewing the result.

Distinguish source values from calculated values. A financial figure copied from an accounting export is not the same kind of evidence as a metric derived from several transactions or a proposed management adjustment.

What a traceable figure carries

• The source file and the row, cell, or page it came from.
• The mapping applied, such as the ledger account and the statement line it was assigned to.
• The calculation, with its inputs and the period it covers.
• The treatment of missing values and any exclusions.
• Who reviewed it, what they decided, and when.

For a material calculation, document the inputs, period, treatment of missing values, and relevant exclusions. A total that reconciles does not by itself establish that the selected inputs are appropriate.

A reproducible calculation can still support the wrong interpretation. Review the business context, accounting treatment, and economic substance separately from the arithmetic.

Candidate addbacks need both numerical support and a rationale. Retain the original expense, proposed adjustment, supporting documents, and reviewer decision rather than overwriting the historical record with an adjusted result.

Evidence gaps should remain visible through handoffs. If bank statements cover only part of the analysis period, a downstream summary should not imply that a full-period cash proof has been completed.

In practice this means a reviewer can click from a statement line in Finsider Platform to the ledger transactions behind it, and from a flagged adjustment to the rows and documents that produced the flag. Addback retains source hashes and row citations in its derived reports for the same reason.

Exports should communicate the material assumptions and limits of the work. A reader should be able to distinguish a screened question, a reviewed adjustment, and an unresolved item.

Keep the lineage in the export, not only in the tool. A workbook that shows adjusted EBITDA without the schedule, the sources, and the decisions behind it cannot be reviewed by the next reader, and the next reader is usually the one who matters: the lender, the investment committee, or the seller's accountant.

This note describes an evidence-lineage framework for discussion and implementation. It does not claim a measured error reduction, certification, or completed external validation.