Executive Read
A bank does not need to understand every onchain move you ever made. It needs a reviewable explanation of where the wealth came from, how it moved, who controlled it, and why the current transaction makes sense.
A strong file is built before the banker, lawyer, accountant, or residency team asks for it. It should connect identity, wallets, exchanges, entities, tax positions, and major transactions into one calm version of the truth.
- Separate source of wealth from source of funds. Reviewers often ask both, and confusing them makes the file feel weaker.
- Build a transaction timeline around material events, not every insignificant wallet movement.
- Prepare supporting evidence in layers so a reviewer can go deeper without receiving a chaotic document dump.
What Reviewers Actually Need to See
Most blocked crypto cash-outs are not rejected because the wealth is illegitimate. They get stuck because the story arrives in a format the institution cannot defend internally. A reviewer has to explain the file to compliance, risk, tax, legal, or management. If your evidence is scattered across screenshots, explorer links, old exchange exports, and half-remembered token events, the safest institutional answer is delay.
The file should make four points obvious: how the wealth was originally created, how control of the assets can be proven, how the assets moved into the current position, and why the requested banking or relocation step is consistent with that history.
- Origin: founder allocation, investment gains, employment, mining, staking, trading, token sale, or business revenue.
- Control: wallets, exchange accounts, multisigs, entities, signatory rights, and beneficial ownership.
- Movement: major transfers, bridges, OTC trades, liquidations, redemptions, and conversions into fiat.
- Purpose: the reason for the current cash-out, bank account, residency move, or advisor introduction.
Build Evidence in Layers
A boutique source-of-wealth file should not begin as a giant archive. Start with an executive narrative that a non-crypto reviewer can read in minutes, then back it with appendices that prove each major claim. This lets an institution review the file without feeling buried, while still giving them enough detail to escalate internally.
The best format is usually a short memorandum, a transaction timeline, a wallet and exchange register, an entity and ownership map, tax or accounting notes, and a clean evidence index. Each document should point to the same facts and use the same names, dates, wallet labels, and amounts.
- Memo: one coherent explanation of the wealth story and the current request.
- Timeline: material events in chronological order with dates, values, counterparties, and evidence references.
- Register: wallets, exchanges, custodians, entities, and who controlled them.
- Index: explorer links, exchange reports, tax records, contracts, invoices, employment records, and advisor letters.
Mistakes That Make a Legitimate File Look Risky
The most common mistake is treating compliance like a technical audit. Sending hundreds of transaction hashes without a human explanation rarely helps. The second mistake is waiting until after funds are frozen, a bank asks urgent questions, or a relocation deadline is close. Once the file is under pressure, every missing record looks more suspicious.
The third mistake is allowing different advisors to work from different versions of the story. If a banker hears one explanation, a tax advisor hears another, and a residency lawyer receives a third, the file becomes harder to trust even when the facts are harmless.
- Do not lead with raw blockchain data unless it is translated into a clear narrative.
- Do not mix personal, corporate, and treasury assets without explaining ownership and control.
- Do not approach institutions before deciding what you are asking them to approve.
- Do not let old exchange gaps or DeFi complexity remain unexplained until the final review.
Questions Clients Ask
Is an explorer link enough to prove source of wealth?
No. Explorer links can support a file, but a bank usually needs a plain-language explanation, ownership context, account records, tax or accounting support, and a reason the funds are moving now.
When should a crypto source-of-wealth file be prepared?
Prepare it before contacting banks, executing a large cash-out, relocating, or asking regulated advisors to support the move. Early preparation gives time to resolve gaps without urgency.
Does every wallet transaction need to be documented?
Usually no. The file should prioritize material events and explain the logic of the flows. Minor movements can be retained in backup records unless a reviewer asks for deeper support.