Standardize financial documents into a diligence pack
Organize submitted financial documents into a consistent review format. Preserve differences in periods and definitions so reviewers can identify what needs clarification.
How this works
Organize submitted financial documents into a consistent review format. Preserve differences in periods and definitions so reviewers can identify what needs clarification. Use this to make financial evidence from inconsistent files comparable for a transaction or investment review. Preserve the difference between reported figures, normalized mappings and calculated metrics.
Inventory statements and supporting schedules by entity and period. Build a source-linked normalized workbook, then explain gaps and inconsistencies in a diligence memo. Do not manufacture missing financial periods or treat a polished pack as verified financial assurance.
Before you start
Diligence scope
Confirm entities, periods, currencies and questions the reviewer needs answered.
Financial source files
Collect statements, trial balances and relevant schedules with version and approval status.
Mapping conventions
Agree account categories, sign conventions and any currency conversion basis.
Prepare the inputs
- source_manifest
- Required
document ID, entity, period, type and status
Identify missing and duplicate versions before extracting numbers.
- financial_tables
- Required
original rows and amounts
Retain page or cell references and units.
- normalization_map
- Required
source account to common category
Keep unmapped or ambiguous accounts separate.
- review_questions
- Required
prioritized diligence topics
Avoid expanding into unsupported valuations or assurances.
Implementation, step by step
Inventory the evidence
- Map documents to the requested entity-period grid.
- Choose the authoritative version with the finance owner and retain superseded references.
Checkpoint: The coverage grid exposes missing periods.
Extract and normalize
- Read financial tables into structured rows with units and currency.
- Apply the approved account mapping while preserving original labels and signs.
Checkpoint: Every normalized value can be traced to a source cell.
Reconcile the schedules
- Check totals, opening-to-closing movements and cross-document consistency using formulas.
- Separate genuine differences from unit, currency or timing mismatches.
Checkpoint: A reconciliation sheet records explained and unexplained differences.
Prepare the diligence narrative
- Answer the specified questions using supported figures and ratios.
- Label estimates, management-provided figures and unavailable evidence distinctly.
Checkpoint: The memo includes findings, caveats and evidence references.
Assemble the review pack
- Package the workbook, source index and unresolved-question list.
- Have finance verify mappings and calculations before sharing outside the authorized review group.
Checkpoint: The pack is complete for its declared scope.
Decisions along the way
Two statements disagree
Retain both versions and ask the owner which is authoritative.
Prior-year data missing
Show the comparison as unavailable, not zero growth.
Currencies differ
Keep separate totals unless an approved rate and date basis is supplied.
What you will produce
diligence-workbook.xlsx
SpreadsheetComparable financial tables with reversible mappings.
Include: entity · period · source_account · normalized_category · amount · currency · source_ref
diligence-memo.md
MarkdownAn evidence-linked brief for a qualified reviewer.
Include: question · finding · evidence · uncertainty · follow_up
source-index.csv
CSVA manifest defining what was and was not reviewed.
Include: document_id · entity · period · version · status · coverage
Check the result
- Reconcile normalized totals to each source statement.
- Check formulas across negative values and unit conversions.
- Verify ratios use comparable periods and definitions.
- Confirm missing schedules and provisional figures remain visible.
When something goes wrong
PDF table extraction merges columns
Re-extract the affected schedule and compare against page images.
Account mapping is disputed
Keep the original category and create a reviewer decision row.
Late document replaces a prior version
Recompute dependent tables and retain a change log.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: standardize two annual revenue statements.
Inputs
Document D1 reports 2024 revenue 1.2 in millions USD; D2 reports 2025 revenue 1,350 in thousands USD. No 2025 cash-flow statement is supplied.
Expected result
Synthetic result: normalized revenue is 1,200,000 and 1,350,000 USD, a calculated 12.5% increase. Mark 2025 cash-flow analysis unavailable and retain both original units.
Run a small pilot
Start small
Use one entity with two periods and a known set of reconciliation issues.
Record the baseline
Record manual normalization time and unresolved differences.
Agree success criteria
Agree traceability and reconciliation acceptance criteria before broadening scope.
Stop or revise
Stop comparative conclusions when units, versions or period definitions cannot be resolved.
Keep the scope clear
- Preparing a diligence pack does not establish an audit opinion or investment recommendation.
- Share only within the authorized review audience and preserve source access restrictions.
Check before using
A reviewer checks figures and comparability; funding decisions remain human.
Business activities
- Manage finances and accounting
- Raise capital or evaluate investments
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Submitted financial documents · Review criteria and metric definitions
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow