Most SOW files fail not because the wealth isn't real, but because the documentation doesn't say what the reviewer needs it to say. There's a difference between a file that tells a coherent story and a file that survives scrutiny. The gap between those two things is hierarchy.

Not all documents carry equal weight. An auditor looking at your SOW file is mentally assigning credibility to each piece of evidence — whether you've told them to or not. The question is whether your narrative is built around that credibility structure, or working against it.

The Five-Tier Framework

Think of SOW documentation as a hierarchy with five distinct levels. The higher the tier, the more weight it carries with an external reviewer. The strongest files lead with Tier 1 and 2 evidence, use Tier 3 to corroborate, and treat Tier 4 and 5 as context — not substance.

Tier Document Type Examiner Weight
T1 Official government / legal records Highest — independently verifiable, hardest to fabricate
T2 Regulated third-party statements High — bank statements, audited accounts, brokerage records
T3 Professional certifications Medium-high — lawyer letters, accountant sign-offs, valuation reports
T4 Self-generated client documents Medium-low — self-declarations, personal asset schedules
T5 RM-sourced narrative Low — call reports, relationship notes, verbal client confirmation

The problem in most files is that the narrative is built on T4 and T5 evidence with T1 and T2 documents used as decoration. An examiner reads the file and sees a call report as the primary source, supported by a self-declaration, referenced against a bank statement that doesn't actually confirm the figure claimed. That's a weak file even when the wealth is legitimate.

SOW vs SOF — The Distinction That Matters

These terms are used interchangeably in practice. They shouldn't be. Source of Wealth explains how the client accumulated their overall asset base over their lifetime. Source of Funds explains where the specific funds entering this account came from. Conflating them is one of the most common documentation errors in private banking KYC.

A client who made their money in manufacturing twenty years ago has a clear SOW. Whether the wire transfer last month came from a dividend, a property sale, or a personal loan is a SOF question. You need both, and they need to be consistent with each other.

When auditors find SOW-SOF misalignment, it doesn't mean the client is suspicious. It means the RM didn't understand the distinction. The file then requires remediation work that could have been avoided at onboarding. The governance cost is always higher after the fact.

The Five-Point Audit-Defensibility Test

Before signing off on a SOW narrative, run it against these five questions. If any answer is no, the file needs work before it goes to a reviewer.

The fifth question is the most important. Reviewers — whether internal compliance or external auditors — do not have the RM's relationship context. The file has to speak for itself. If it can't, the narrative has failed regardless of how well the RM knows the client.

What Auditors Are Actually Looking For

External reviewers like Deloitte, KPMG, or EY are not trying to catch criminals. They're trying to assess whether your institution has a defensible position if the client turns out to be problematic. That's a different test. It's not about guilt — it's about whether you did what a reasonable, compliant institution would have done given the information available.

That means they're looking for evidence of a process, not just a conclusion. A file that says "client is a successful businessman, SOW is from business income, confirmed by RM" fails this test. A file that documents what business, what income, over what period, corroborated by which specific documents, with the methodology for how the figures were assessed — that's a file that holds.

The hierarchy isn't about bureaucracy. It's about building a file that can be defended by someone who wasn't in the room when the client relationship was formed. Every piece of documentation you add at the right tier is insurance against the question you haven't been asked yet.