← Blog · Compliance

Source of Funds vs Source of Wealth: Documenting Money's Origin

PrivateKYCBot Team · September 25, 2026 · 3 min read

Source of Funds vs Source of Wealth: Documenting Money's Origin

Enhanced due diligence frequently turns on a question that sounds simple: where did the money come from? In practice, that question splits into two distinct inquiries with different scopes, different evidence, and different failure modes. Teams that treat them as interchangeable tend to over-collect from low-risk customers and under-document the high-risk ones.

Two Questions, Not One

Source of funds (SoF) concerns the specific origin of the money involved in a particular transaction or account activity — the salary payment, the property sale, the loan drawdown that produced the balance moving through your platform. It is transactional and near-term.

Source of wealth (SoW) concerns how the customer accumulated their total net worth over time — the business they built, the inheritance they received, the equity that vested across a decade. It is biographical and cumulative.

A customer wiring €40,000 for a car purchase can explain the source of funds (a bonus paid last month) while their source of wealth (twenty years as a salaried engineer) remains a separate story. Regulators such as the UK FCA and guidance echoing FATF Recommendation 10 expect firms to distinguish the two when applying enhanced due diligence to higher-risk relationships and PEPs.

What Evidence Actually Supports a Claim

Assertions are not evidence. A stated origin needs corroboration proportionate to the risk. Common documentary support includes:

  • Employment income: payslips, employment contracts, and bank statements showing regular credits from a named employer.
  • Business ownership: audited financial statements, dividend vouchers, sale-of-business agreements, and company registration records.
  • Property sales: completion statements, contracts of sale, and solicitor or notary confirmations.
  • Inheritance or gifts: grant of probate, a will, or a signed gift letter with the donor's own source documented.
  • Investment proceeds: brokerage statements, capital gains records, or dividend histories.

The principle is traceability: each figure should connect to an independent record, and large or unusual amounts warrant deeper corroboration than routine ones. A single document rarely settles both questions — a payslip evidences funds but says little about accumulated wealth.

Collecting Without Overreach

Source-of-wealth reviews are where data minimization is most often abandoned. Faced with uncertainty, teams request everything: five years of statements, full tax returns, entire portfolios. That creates a larger breach surface and a retention liability without proportionally improving the assessment.

A tighter approach starts from the risk that triggered the review and asks only for what resolves it. If the concern is a €200,000 inflow, the objective is explaining that inflow — not auditing the customer's life. Some practical constraints:

  • Scope the request to the trigger: name the transaction, threshold, or risk factor prompting the ask, and bound the documents accordingly.
  • Prefer targeted evidence: a completion statement for a property sale beats a full year of statements you then have to store and redact.
  • Redact at intake: unrelated line items on a statement rarely serve the file and should be minimized where the format allows.
  • Set retention deliberately: hold what supports the AML record for the period your jurisdiction requires, then delete on schedule rather than by default.

Chat-based collection can enforce this discipline structurally. A conversational flow asks for one document at a time, tied to a stated reason, and can apply per-field retention rather than warehousing an entire uploaded folder — turning the abstract principle of proportionality into a configurable rule.

Documenting the Reasoning

The evidence is only half the file. The other half is your rationale: why the stated origin is plausible given what you know about the customer, why the documents corroborate it, and why any residual gaps are acceptable or require escalation. A reviewer months later should understand not just what was collected but what conclusion it supported.

This narrative is what distinguishes a defensible file from a stack of PDFs. When an examiner or an internal audit revisits a high-risk relationship, a clear SoF and SoW analysis — dated, sourced, and reasoned — is the record that holds. This is general information, not legal advice; calibrate thresholds and documentation to your own regulatory obligations.

General information, not legal advice. Talk to your compliance counsel for guidance on your specific obligations.