Source of Funds vs Source of Wealth: Documentation Standards Explained
Source of Funds proves where the specific money entering an account came from. Source of Wealth proves how the customer's entire net worth was built. Both are required under Enhanced Due Diligence — but they are documented and verified differently, and confusing them is one of the most common findings in regulatory examinations.
The distinction between Source of Funds and Source of Wealth seems straightforward in theory but routinely breaks down in practice. Many firms treat the two interchangeably — collecting a single bank statement, declaring SoF and SoW both satisfied, and moving on. Regulators consistently identify this as a control failure, and for good reason: the two questions are testing different things, and answering only one of them leaves the assessment incomplete.
FATF Recommendation 12 and the EU AMLD frameworks both require source-of-wealth verification for PEPs. The EU's AMLD/AMLR framework, the UK's MLR 2017, MAS Notice 626, and FinCEN's CDD Rule each extend similar obligations to other high-risk relationships. The practical question for an MLRO is not whether to collect this information — it is how to collect it in a way that satisfies a supervisor reviewing the file two years later.
Defining the Two
A useful way to think about the distinction is in terms of time horizon and narrative scope. SoF is short-horizon and narrow: it concerns the funds the firm is seeing right now, or in a specific recent transaction. SoW is long-horizon and broad: it concerns the customer's economic story across years or decades.
An example illustrates the difference. A customer wires $2 million into their account. The SoF is the immediate origin of that wire: who sent it, from which institution, in payment for what. The SoW is the larger question of how the customer came to be in a position to receive a $2 million transfer at all — their career, their business interests, their inherited wealth, their investment history.
A complete EDD assessment answers both questions and tests them against each other. A customer whose declared SoW would not plausibly generate the observed SoF is the configuration that should drive a Suspicious Activity Report, not a closed file.
Where Each Sits in the AML Framework
Standard Customer Due Diligence typically does not require formal SoF or SoW documentation for low-risk customers — the customer's declared occupation and the platform's general understanding of expected activity are usually sufficient. The obligation crystallises when the relationship moves into Enhanced Due Diligence territory.
EDD triggers include any of the following situations:
- The customer is a foreign Politically Exposed Person — SoW verification is mandatory under FATF Recommendation 12. Domestic PEPs trigger SoW where additional risk indicators are present.
- The customer is connected to a high-risk jurisdiction — residence, nationality, ownership, or significant transactional exposure to a FATF black-list or grey-list country.
- The customer's activity is materially out of profile — incoming or outgoing transactions inconsistent with the declared occupation, business, or income.
- Complex ownership or trust structures — multi-layered corporate ownership, opaque jurisdictions, nominee arrangements, or beneficiaries whose role in the structure is not commercially obvious.
- Specific transactions above defined thresholds — many firms set internal thresholds (often in the $100K–$500K range) that automatically require SoF documentation regardless of customer rating.
SoF and SoW are not parallel one-time exercises — they are continuing obligations. The SoF for a new wire must be re-established for each material transaction. The SoW must be refreshed on periodic review and whenever the customer's circumstances materially change.
Acceptable Source of Funds Documentation
Source of Funds is transactional. The documentation should evidence the specific origin of the specific money. Acceptable evidence varies by the nature of the underlying transaction:
- Salary or employment income — recent payslips, an employment contract, or a bank statement showing regular salary credits from a verified employer.
- Sale of property — the completion statement from the conveyancing solicitor, the contract of sale, or a bank statement showing receipt of sale proceeds from the buyer's solicitor.
- Sale of a business or business interest — the sale and purchase agreement, the completion accounts, and the bank statement showing receipt of consideration.
- Investment income — broker or custodian statements showing the relevant dividend, interest, or capital-gain entries; for crypto, on-chain records combined with exchange withdrawal confirmations.
- Inheritance — a copy of the grant of probate, the executor's distribution statement, and ideally the bank record of receipt from the estate.
- Loan proceeds — the loan agreement, the drawdown notice, and the bank record of the lender's transfer.
- Gifts — a written gift letter from the donor, identification for the donor, and the bank record of the gift transfer. Gifts from non-immediate family members or from third parties typically warrant additional scrutiny.
Customer self-declarations are not, on their own, sufficient documentation. Every regulator that has issued specific guidance on this point — MAS, FCA, FinCEN, AUSTRAC, EU AMLA — has confirmed the same principle: SoF must be supported by independent documentary evidence, not by what the customer says about it.
Acceptable Source of Wealth Documentation
Source of Wealth is biographical rather than transactional. The objective is to corroborate a coherent narrative of how the customer's overall economic position was built. SoW evidence is rarely a single document — it is usually a constellation of reference points that together support the customer's story.
Typical SoW evidence includes:
- Employment history — LinkedIn profile, professional regulatory filings, employer references, or industry-publication coverage that confirms the customer's career trajectory and likely earnings range.
- Business ownership — corporate registry filings, financial statements of customer-owned businesses, public disclosures, news coverage of company sales or fundraising rounds.
- Inherited wealth — probate records, family trust documentation, public reporting on the deceased's estate.
- Investment portfolio history — historical custodian statements, broker statements, audited financial statements where the customer is a director or significant shareholder.
- Real estate — title records, mortgage records, valuation evidence at relevant historical points.
- Public-record corroboration — media coverage, regulatory disclosures, court filings, sanctions and PEP registers.
The narrative test is whether an analyst could read the file two years later and understand, without further explanation, how the customer's declared wealth was actually built. A single payslip showing a high salary does not satisfy SoW — it satisfies one component. A complete SoW file weaves multiple components into a documented economic biography.
Common Failures Regulators Identify
Across major supervisory reviews of EDD files, the same SoF/SoW failures recur. The most frequent findings:
- Conflating the two — collecting one bank statement and treating it as evidence of both SoF and SoW.
- Customer self-declarations accepted without corroboration — a written statement from the customer recorded as evidence with no supporting third-party documentation.
- No alignment test in the file — both SoF and SoW collected, but no written analysis of whether they are consistent with each other.
- Stale information not refreshed — SoW documented at onboarding three years ago and never updated despite material changes in the customer's circumstances or activity.
- Documents not actually reviewed — statements and contracts uploaded to the system but no analyst notes evidencing that anyone examined them critically. A document that nobody read is not evidence of due diligence.
- Plausibility ignored — accepting a SoW narrative that is internally inconsistent or implausible given other available information (for example, a customer claiming an inheritance from a person whose own public profile would not support the declared sum).
Operationalising SoF/SoW Collection at Scale
The operational challenge with SoF and SoW is that they are document-heavy, analyst-judgment-dependent, and difficult to automate fully. The right architecture combines structured data capture with workflow controls that ensure no file closes without the alignment test being performed.
A well-designed compliance platform supports SoF/SoW in three ways. First, by triggering the collection workflow automatically when EDD criteria are met — no analyst has to remember which customers need it. Second, by providing structured templates that prompt for both SoF and SoW separately, with checklists of acceptable evidence types for each scenario. Third, by requiring documented analyst reasoning before the case can close — the alignment test recorded in writing, not just inferred from the documents uploaded.
The One Constellation compliance portal implements this workflow end-to-end: automatic EDD triggers from the risk-rating engine, structured SoF/SoW templates per customer type, document capture with categorisation, and a required analyst-narrative field that must be completed before the case advances. The audit trail captures every document, every action, and every reviewer touchpoint — so that the file two years later remains defensible.
For the wider EDD framework, see our guide to when EDD is required and how to apply it. For periodic refresh and ongoing monitoring obligations that connect to SoF/SoW, see the CDD guide.
SoF and SoW, Documented to Audit Standard
One Constellation's compliance portal automates EDD triggers, structures SoF and SoW evidence capture, and produces audit-ready files that regulators can read end-to-end.
