Structuring a Source-of-Funds File Counterparties Will Actually Read

Compliance reviewers approach source-of-funds material with a defined set of questions: where did the wealth originate, what primary record proves it, how does the present holder connect to that record, and what is the timeline between accumulation and the proposed transaction. Vague narratives leave those questions unanswered, and unanswered questions are the default reason for rejection.

The file is structured around the reviewer's checklist rather than the user's preferred order of telling the story. Each item that the counterparty needs is matched to the document that supports it, in the column where they will look for it. The exercise is uncreative on purpose.

Primary records — tax returns, signed conveyances, dividend statements, payslips with employer attribution — carry the weight of source-of-funds work. Letters from accountants, informal declarations, and self-prepared spreadsheets are secondary. They are not useless, but they are not what the reviewer relies on, and they should not be placed where a primary record belongs.

Each primary artefact in the file links directly to the wealth event it evidences. Secondary documents are kept in a clearly labelled supporting section rather than mixed into the primary chain, so the reviewer never has to triage the file themselves.

Compliance teams read a lot of files and have limited patience for ones written in their own jargon back at them. A short, plain description next to each major record — what moved, from whom, to whom, when, and why — saves the reviewer from having to reconstruct the economic event from raw codes and abbreviations.

The descriptions are factual and short. They do not lobby, do not justify, and do not introduce intent the records cannot support. The aim is for the reviewer to finish reading and know exactly what occurred, not to be persuaded that it was acceptable.

A source-of-funds file fails when the wealth is well documented but the link to the current holder is not. Name variants, corporate vehicles, joint accounts and intermediate transfers all introduce points where the identity connection can drop, and reviewers stop reading when it does.

Identity documents, account ownership records and corporate registers are mapped alongside the financial artefacts. Where the same person appears under different name conventions, the variants are listed and tied together. Where capital passed through a corporate vehicle, the controller of that vehicle at the relevant time is documented from the register, not asserted.

Most long financial histories contain points where the primary record is not available. Pretending otherwise is the fastest way to damage the credibility of the entire file. Reviewers respond better to a clear acknowledgement of a gap than to a confident paragraph that turns out, on questioning, to be a guess.

Unresolved points are listed in their own section with the specific record that would close each one. The counterparty can then make a risk decision on actual information, instead of discovering the gap on the second read and treating the whole file as suspect.