Why map your flows
Brokers often accumulate payment arrangements one at a time. A card acquirer is added for deposits, a bank account for the liquidity provider, a wallet for an introducing broker in Asia, a payroll service when the team grows. After a few years nobody has a single view of where money moves, who handles it and which account it comes from.
That causes problems. Flows end up on accounts that were never intended for them. Partners see transactions they did not expect and open reviews. Auditors struggle to trace corporate costs. And when a provider exits, the broker discovers that several unrelated flows depended on the same account.
A written flow map fixes this. It lists each type of payment, its direction, its source of funds, its counterparties, the account it uses and the provider responsible. It becomes the reference document for finance, compliance and every onboarding conversation with a new partner.
Two pools of money
Every flow in a brokerage starts from one of two pools. Client money is money held for clients, kept in segregated accounts under the broker's regulatory obligations. Corporate money is the broker's own: capital, earned revenue, borrowings and intra-group funding.
Keeping these pools separate is a regulatory requirement in most regimes and the single most important principle in the flow map. Each flow should be clearly tagged to one pool. A flow that seems to belong to both, such as a payment processor settlement that carries both client deposits and fee income, needs to be split at source or handled with extra care.
Client money flows
The client side of the map usually contains:
- Client deposits: card payments, bank transfers, local payment methods and, at some brokers, digital asset deposits. They arrive through acquirers and payment service providers and settle into segregated accounts.
- Client withdrawals: payouts to clients, usually back to the original payment method where possible, as an AML and anti-fraud control.
- Chargebacks and refunds: reversals initiated by card schemes or the broker.
- Transfers to corporate: earned revenue moved from client accounts to corporate accounts after reconciliation.
- Shortfall top-ups: corporate funds moved into client accounts when reconciliation shows a deficit.
These flows involve members of the public, high transaction counts and specific regulatory rules. They need providers that are set up for retail payment methods and client money accounts, often with acknowledgement letters confirming the status of the funds.
Corporate flows
The corporate side is broader and more varied:
- Liquidity provider margin: initial deposits, top-ups, margin calls and excess returns, funded from corporate money in most setups.
- Technology vendors: trading platform licences, bridge and aggregator fees, CRM, hosting, market data and security services.
- Introducing broker rebates: periodic payouts to IBs, often in batches across many countries and currencies.
- Affiliate and marketing costs: payments to affiliates, agencies and media owners.
- Professional services: legal, audit, tax and compliance consultants.
- Payroll and contractors: salaries, social contributions and contractor invoices, usually in the service company.
- Intra-group treasury: service fees, licence fees, loans, capital contributions and dividends between group entities.
- Regulatory and tax payments: regulator fees, compensation scheme contributions and taxes.
Corporate flows involve known business counterparties, contracts and invoices. They suit providers that focus on business-to-business payments, foreign exchange and batch processing, and that understand the brokerage sector well enough to recognise normal patterns.
The flow map at a glance
The table below summarises a typical map. It is illustrative and will differ between brokers.
| Flow | Direction | Pool | Typical counterparty | Suited provider |
|---|---|---|---|---|
| Client deposits | Inbound | Client | Retail clients | Card acquirer, local payment method provider, client money bank |
| Client withdrawals | Outbound | Client | Retail clients | Client money bank or payment service provider |
| Revenue transfer | Client to corporate | Both | Broker's own accounts | Client money bank to corporate account |
| LP margin and fees | Both ways | Corporate | Liquidity providers, prime brokers | Corporate payments and FX provider |
| Technology vendors | Outbound | Corporate | Platform, bridge, CRM, hosting vendors | Corporate payments and FX provider |
| IB rebates | Outbound | Corporate | Introducing brokers | Corporate provider with batch payouts |
| Marketing and affiliates | Outbound | Corporate | Agencies, affiliates, media | Corporate payments provider |
| Payroll | Outbound | Corporate | Employees, tax authorities | Local bank or payroll provider |
| Intra-group treasury | Between entities | Corporate | Group companies | Corporate payments and FX provider |
| Taxes and regulator fees | Outbound | Corporate | Tax authorities, regulators | Local bank |
Matching flows to providers
The table shows a pattern. Client flows need providers built for retail payments and client money. Payroll and local taxes usually need a domestic bank in the country where the employing company sits, because local tax and social security systems expect domestic payments. The remaining corporate flows, which are often cross-border and multi-currency, suit a specialist corporate payments provider.
Splitting flows this way has several benefits. Each provider sees only what it expects, so monitoring alerts drop. Each account has a clear purpose, which helps segregation and audit. And if one provider exits, the impact is limited to the flows it handled, so the broker can replace it without disrupting everything else.
The common mistake is to push everything through whichever account is easiest to open. A corporate account receiving client deposits, or a client account paying a software licence, creates exactly the mixed picture that partners and regulators dislike.
The currency layer
On top of the flow map sits a currency map. A broker may receive client deposits in a dozen currencies, hold corporate funds in euros or dollars, pay its liquidity provider in dollars, pay vendors in euros and pounds, and pay introducing brokers in local currencies across Asia, Latin America and Africa.
For each corporate flow, note the currency the counterparty expects and the currency the broker holds. Where they differ, a conversion is needed, and the timing and cost of that conversion become part of the process. Consolidating conversions, for example converting once for a whole IB payout batch instead of payment by payment, often reduces both cost and effort.
Building your own map
A practical way to build the map is to start from twelve months of bank and provider statements. List every payment category, the accounts it touched and the counterparties involved. Then draw the intended state: which accounts and providers should handle each category going forward. The gap between the two is the work plan.
Useful columns for the map include flow name, entity, direction, pool, frequency, typical size, currencies, counterparties, account used, provider, supporting documents and internal owner. Review the map whenever a new flow appears, a provider changes or a new entity joins the group.
Share a summary with each payments partner. A partner that has seen the map understands what will pass through its account and why, which shortens onboarding and reduces queries later.
Flows that do not fit neatly
Every map has awkward cases, and they are usually where problems start. A few come up at most brokers:
- Payment processor settlements: some processors deduct their fees before settling deposits into the client account. The fee is a corporate cost, but it has been taken from client money in transit. Many brokers resolve this by topping up the client account with the fee amount from corporate funds each day, or by arranging gross settlement with fees invoiced separately.
- Bonuses and promotions: where permitted, credits given to clients are funded by the broker. The money moves from corporate to client, and the transfer needs to be recorded as such.
- Negative balance write-offs: when a client account goes negative and the broker absorbs the loss, the client money calculation changes. The reconciliation, not an ad hoc transfer, should drive any movement.
- Digital asset deposits: brokers that accept digital assets from clients face a client money flow in a different form, with wallet, screening and conversion questions of its own.
- Refunds to vendors or from vendors: a platform vendor that refunds an overpayment should pay the corporate account it was paid from, never the client account.
Writing down how each awkward case is handled, and who decided it, prevents individual staff from improvising under pressure.
Who owns the map and its controls
The map also drives controls. Payment approval rules can check that each outbound payment uses the right account for its category. Beneficiary lists can be maintained per flow, so a vendor account cannot be used for an IB payout. Monitoring reports can flag any transaction on an account that does not match its mapped purpose.
A flow map only stays useful if someone owns it. In most brokers that is the head of finance, with compliance reviewing it at least annually and whenever a new flow, entity or provider is proposed. Linking the map to the onboarding process for new vendors and introducing brokers means every new payee is assigned to a mapped flow before the first payment. Linking it to the board's annual review of client money arrangements gives directors a clear view of how money moves through the business they are responsible for.
General information only
This article is general information about mapping payment flows in a brokerage. It is not legal, regulatory or accounting advice, and the right arrangement depends on each broker's licences, structure and regulator.
Where CCYFX works with brokers, it is on corporate payments only, subject to onboarding and review. It does not handle client deposits or withdrawals. See our Collections and payouts or CFD brokers page for details.
