Fund-flow analysis

Turn transaction volume into a financial trail that can be tested.

Audit Corridor reconstructs material flows across accounts, entities and transaction layers, then links the movement to counterparties, documents, chronology, economic purpose and the question the analysis must answer.

Financial trailsTransaction layersCounterpartiesEvidence schedules

Updated: 25 August 2026

Direct answer

Fund-flow analysis reconstructs where money originated, how it moved, where it accumulated or ended and which records support each link. It is not only a diagram: a defensible trail preserves source provenance, transaction logic, scope limits and plausible alternatives.

Decision questions

What this work is designed to answer.

The analysis reduces large transaction sets into pathways relevant to a defined decision. It must remain possible to move from the summary back to the underlying statement, ledger or supporting record.

01

Where did the money move?

Normalise transactions, identify material inflows and outflows and reconstruct paths across accounts, entities, dates and instruments.

02

What patterns require testing?

Surface rapid movement, circularity, layering, concentration, pass-through behaviour, unusual timing and counterparties connected to the issue.

03

What does each path mean?

Corroborate transaction movement with invoices, contracts, ledgers, ownership information, communications and economic purpose before drawing a conclusion.

Evidence architecture

The conclusion is only as useful as the trail beneath it.

Transaction analysis is strongest when structured data and documentary evidence are connected. The workflow should preserve original files and record every transformation used to produce the analytical schedule.

Structured financial material

  • Bank statements and transaction exports
  • General ledgers and sub-ledgers
  • Payment registers and instrument details
  • Facility, escrow and settlement records
  • Opening balances and reconciliation material

Corroborating material

  • Invoices, purchase orders and contracts
  • Counterparty and ownership information
  • Related-party and control relationships
  • Communications and approval records
  • Business-purpose and delivery evidence

Engagement sequence

A controlled path from question to finding.

Scope, evidence handling, analytical challenge and reporting remain visible throughout the mandate.

01

Define materiality

At scoping

Set the accounts, entities, period, transaction classes, thresholds and questions the trail must answer.

02

Normalise with provenance

At intake

Standardise fields, retain source references, reconcile coverage and record exclusions or data-quality problems.

03

Reconstruct and test

During analysis

Build pathways, identify patterns, map counterparties and test each material interpretation against supporting evidence.

04

Deliver reviewable schedules

At conclusion

Provide transaction schedules, visual pathways, source references, gaps, limitations and a clear narrative of what is supported.

Decision-grade delivery

What a useful output contains.

A good fund-flow product can be challenged and reproduced. Summary visuals are useful only when the transaction schedule and source references remain available underneath them.

Core work product

  • Account and data coverage map
  • Normalised transaction schedule
  • Source-linked pathway analysis
  • Counterparty and entity map
  • Chronology of material movements

Reasoning and limits

  • Circularity and layering indicators
  • Concentration and end-point analysis
  • Documentary corroboration register
  • Unresolved breaks in the trail
  • Interpretive limits and alternatives

Scope boundary: Transaction patterns are indicators for examination, not automatic findings of misconduct. The analysis must be read with the governing documents, business context and evidence of knowledge or intent where those questions matter.

Common questions

Concise answers before a mandate begins.

These answers explain the usual architecture. The facts, access, jurisdiction and intended use determine the actual scope.

How is fund-flow analysis different from an accounting review?

An accounting review may test classification, balances, controls or reporting. Fund-flow analysis follows specific money movements across accounts and entities to answer a defined question about source, use, recipients, relationships or economic purpose. A mandate can require both disciplines.

How many transaction layers can be analysed?

There is no credible fixed number. Depth depends on data access, transaction continuity, identifiers, materiality and the decision being supported. The analysis should continue while additional layers remain relevant and supportable, then state where the trail breaks.

What happens when records are incomplete?

Coverage gaps are mapped explicitly. Available transactions can still be analysed, but missing periods, accounts, counterparties or supporting documents constrain the conclusion. Those constraints should appear in the output, not only in working notes.

Are diagrams enough for a fund-flow conclusion?

No. A diagram is a communication layer. It should be supported by a reviewable transaction schedule, source references, reconciliation, counterparty information and the documentary basis for any interpretation.

Connected work

Related capabilities.

A mandate may require more than one analytical lens. Boundaries and responsibilities are defined at scope.

Related capability

Bank fraud & fund diversion

Loan-lifecycle and end-use questions read alongside the financial trail.

Explore →
Related capability

Forensic investigations

Fact development where transactions form one part of a wider account.

Explore →
Related capability

Litigation & arbitration support

Reviewable financial schedules and chronologies developed with counsel.

Explore →

Start with the question the evidence must answer.

Discuss the mandate