Flow-of-funds is the business translated into money movement.
A payment business can describe itself in a hundred ways, but flow-of-funds cuts through all of it. It answers the real question: what actually happens to money inside the model?
That is why this document matters so much. It does not only help explain the model to reviewers. It forces the business itself to become more precise about what it is doing. When the flow-of-funds document is weak, that usually means the operation is weakly understood internally too.
1. Start by identifying the exact starting point of money.
Every flow-of-funds document should begin with a plain question: where does the money first enter the system?
The answer might be:
- a merchant payment initiated by a customer,
- a sender funding a remittance transfer,
- a user topping up a wallet,
- a platform receiving settlement from a processor or banking partner.
What matters is precision. “Funds enter the platform” is too vague. Through what account, through which channel, under whose control, and in whose name?
2. Name every party in the chain.
This is where many flow-of-funds documents go bad. They show boxes and arrows, but the boxes say things like “processor,” “partner,” “settlement account,” or “third party.” That is not enough.
The document should name the role each party plays:
- customer or sender,
- merchant or recipient,
- platform operator,
- payment processor,
- banking partner,
- safeguarding account provider,
- agent, payout partner, or exchange counterparty.
If a counterparty cannot be named because the model is still fuzzy, then the problem is not the diagram. The problem is the model.
3. Show where funds pause, not just where they move.
Money does not only move. Sometimes it sits. That matters a lot.
Your document should clearly show:
- where funds are temporarily held,
- how long they may remain there,
- whether they are operational funds or user-related funds,
- what account type is used,
- who has authority over that account.
Pauses are one of the most important parts of the money path because that is where safeguarding, reconciliation, liquidity, and misuse risk begin to matter.
4. Explain what any balance actually represents.
If a balance appears in the model, describe it properly. Is it:
- a merchant receivable pending settlement,
- a customer-funded value balance,
- a temporary operational holding amount,
- a safeguarded pool linked to user claims,
- a settlement reserve,
- an internal ledger entry only?
The worst thing you can do is show balances in the model without explaining what they are or what legal / operational logic sits behind them.
Weak flow-of-funds
Generic boxes, anonymous counterparties, no account logic, no timing explanation, no controls, and no distinction between user funds and business funds.
Strong flow-of-funds
Named parties, account structure, timing, pauses, controls, reconciliation points, exception logic, and clear explanation of what each balance means.
5. Add the control points, not just the arrows.
A flow diagram that shows movement but not control is incomplete. The document should also explain:
- who authorizes release of funds,
- who approves payouts or settlements,
- how reconciliations are performed,
- what happens if amounts do not match,
- what monitoring applies before and after movement,
- how refunds, reversals, chargebacks, or failed transfers are handled.
This is the part that changes the document from “money movement sketch” into operational evidence.
6. Always show the exception cases.
A lot of founders only document the happy path. That is cute. Banks and reviewers care just as much about the ugly path:
- failed payout,
- refund request,
- rejected transfer,
- merchant suspension,
- blocked transaction,
- reconciliation break,
- stuck settlement.
If the business cannot explain how it behaves when something goes wrong, the flow-of-funds is not done.
7. Use plain language around the diagram.
The best flow-of-funds documents combine a visual map with short written explanations. The diagram alone is rarely enough. Each stage should have a short operational note that answers:
- what happens,
- who is involved,
- what account or ledger is used,
- what control applies,
- what the next stage is.
Do not make people reverse-engineer your business from arrows and abbreviations.
Common mistakes to avoid.
- Using vague labels instead of real counterparties or roles
- Skipping the point where funds pause or sit
- Failing to separate operational funds from user-related funds
- Showing only the happy path and ignoring exceptions
- Not explaining reconciliation and approval controls
- Using diagrams that look polished but communicate almost nothing
Bottom line.
Documenting flow-of-funds correctly means showing the real money path with no mystery left inside it. Every entry point, every holder, every pause, every balance, every counterparty, every control, and every exception should be visible and explainable.
When done properly, flow-of-funds does more than satisfy a reviewer. It makes the business itself sharper. And that is usually the difference between a payment company that looks bankable and one that looks like it still lives in slides.
