Source of Funds sits underneath more decisions than most people acknowledge. Banks need it for onboarding. Exchanges need it to stay compliant. Law firms need it to show a court that assets are clean. In the majority of Source of Funds engagements that reach us, the analysis done beforehand is incomplete. It stopped one step too early.
The standard approach is to run a blockchain analytics tool, take the output, and treat it as the answer. For simple single-chain cases, that holds. The moment real complexity enters, and with crypto it almost always does, automated tools start missing things.
A risk score from Chainalysis or TRM Labs is not a Source of Funds report. That distinction matters enormously in a legal context. Here are the four places where automated analysis breaks down, and what it takes to close the gap.
Cross-chain bridges break the provenance chain
When funds move across chains via bridges like Wormhole, Stargate Finance, or Across Protocol, most analytical tools lose continuity. The transaction leaving the source chain and the transaction arriving on the destination chain appear as two unrelated events. Bridge-specific contract logic, whether lock-and-mint, burn-and-release, or liquidity pool swaps, varies enough that automated matching fails regularly.
Closing this gap requires manual transaction decoding: identifying the bridge contract calls, matching the lock or burn event on the source chain to the mint or release event on the destination, and confirming the movement with cryptographic certainty rather than probabilistic inference. Without that step, there’s a gap in the provenance chain, and that gap is exactly what a regulator or a court will focus on.
DeFi earnings require transaction-by-transaction reconstruction
Yield farming on Curve, liquidity provision on Uniswap, staking rewards via Lido, airdrops, and arbitrage strategies each create financial patterns that automated tools decode poorly. The problem isn’t that the transactions are hidden; they’re all on-chain. The problem is that tools misread them as opaque movement rather than legitimate income.
When a client earned through DeFi, that income has to be reconstructed transaction by transaction and documented precisely. Approximation is not acceptable. “Probably legitimate” is not a position you want to defend in front of a compliance officer or a judge. The reconstruction work turns an automated flag into documented evidence.
Privacy coins generate false positives that penalize legitimate clients
When Monero (XMR), Zcash shielded transactions, or interactions with protocols like Tornado Cash appear anywhere in a transaction history, automated systems raise the risk flag immediately. Sometimes that’s warranted. Often it isn’t. A client who used Zcash’s transparent pool for a documented purpose years ago faces the same flag as someone who used shielded transactions to obscure illicit funds. The tool makes no distinction.
The work is to document everything before and after the privacy coin interaction. Where direct tracing is genuinely impossible, the approach is to build an alternative evidence chain using behavioral analysis, timing patterns, and corroborating off-chain data. The automated flag is where the forensic work should begin, not where it ends.
Legacy holdings require investigative reconstruction, not a software scan
Early Bitcoin or Ethereum acquired before KYC was standard. Defunct exchanges with no surviving records. Wallet migrations without documentation. Clients who genuinely cannot account for a specific tranche of assets from eight years ago.
No software scan resolves this. FinCEN, FINMA, and the FCA each recognize that pre-KYC holdings present a documentation challenge that requires judgment alongside tool output. The investigative approach is to reconstruct the likely acquisition history from what the chain still records, then corroborate it against whatever off-chain traces survive: email archives, early forum posts, exchange records, tax filings. The result is a coherent narrative supported by evidence, which is what the institution reviewing it actually needs.
What court-ready Source of Funds documentation requires
All of this exists to serve the deliverable. A Source of Funds report is only as useful as it is defensible, and a defensible report looks different from a tool printout. It includes an executive summary, visual transaction flows, cryptographic proof preservation, and a documented methodology at every step, formatted for the specific context: a banking onboarding review, an insurance claim, a regulatory examination before the AMF or FCA, or a courtroom.
The standard Recoveris applies to Source of Funds documentation is the same standard applied to evidence in active fraud cases, material that has to survive cross-examination. That matters because a significant share of the Source of Funds assessments banks and institutions are relying on right now carry material gaps. Either they miss real risk, or they generate false positives that block legitimate clients from services they’re entitled to. Both outcomes are costly. One lets the wrong funds through; the other turns away the right client.
A report that properly handles cross-chain bridges, DeFi positions, privacy coin interactions, and legacy holdings prevents both.
If you commission or rely on Source of Funds reports for banking onboarding, regulatory examination, or legal proceedings, schedule a confidential consultation with Recoveris.
