The 20-Minute Close: A Daily Client Money Reconciliation Checklist for Fast-Growing Brokers

Client money reconciliation gets harder exactly when your business is working: more deposits, more instruments, more bonus programs, more payout volume. The risk isn’t only “being off”—it’s being off and finding out too late, after withdrawals queue up or a regulator (or banking partner) asks for evidence.

Below is a practical daily checklist you can run in ~20–45 minutes once your reporting is wired correctly. It focuses on the four breakpoints that create most reconciliation incidents at scale: balances, open P&L, bonuses/credits, and pending withdrawals.

1) Start with a clean “as-of” timestamp (and freeze moving parts)

Before you reconcile numbers, reconcile time. Most breaks come from comparing reports generated at different cutoffs.

Set a daily “as-of” time (e.g., 23:59:59 platform time or 00:00 UTC) and make it explicit in every export and dashboard. If you operate multiple servers (MT4/MT5/cTrader) or multiple payment providers, align them to the same window.

Practical controls to apply each day:

• Confirm business day definition: trading day vs calendar day (especially around rollover, swaps, and weekend crypto trading).
• Freeze the queue: pause manual wallet adjustments during the reconciliation window (or log them separately as “post-cutoff”).
• Lock FX rates for valuation: if you report liabilities in a base currency, use a consistent rate source and timestamp.

Regulatory note: client money rules differ by jurisdiction and license type. If you’re under a regime that requires segregation and specific reconciliation frequency, check local regulations and document your methodology.

2) Reconcile client balances: platform equity vs wallet ledger vs bank/payment rails

This is the core “client money reconciliation” step: do your systems agree on what you owe clients?

At scale, you typically have three layers:

1. Trading platform (MT4/MT5/cTrader): balance/equity, credit, floating P&L, swaps/commissions.
2. Wallet/CRM ledger: deposits, withdrawals, transfers, adjustments, bonus credits, chargebacks.
3. External rails: bank accounts, PSP settlement accounts, crypto wallets, local payment methods.

Daily checklist:

• Platform total client balance (sum of balances by account group) matches CRM wallet liability (sum of client wallet balances), after mapping rules.
• Validate account mapping: one client ↔ multiple trading accounts; one wallet ↔ multiple currencies; sub-accounts for IB rebates.
• Bank/PSP settlement movement ties to deposits/withdrawals recognized in the ledger (net of fees, rolling reserves, and timing delays).

Common causes of breaks (and what to do):

• Unposted deposits: PSP shows “settled,” CRM shows “pending.” Fix: enforce webhook retries + an exception queue.
• Manual adjustments: back-office credits/debits not mirrored across systems. Fix: require reason codes and dual approval for manual entries.
• Currency conversion drift: wallet in USD, deposit in EUR, platform account in USD—rates differ. Fix: store both transaction currency and base currency equivalent with the rate timestamp.

3) Reconcile open P&L: floating exposure, valuation, and “who holds the risk”

Open P&L is where reconciliations quietly fail—especially when you aggregate across A-book/B-book, bridges, and liquidity providers.

You’re not only checking “does the number match,” you’re checking whether the liability recognition is correct:

• On the platform, clients have floating P&L (unrealized).
• In your risk/backoffice, you track exposure and possibly hedged positions.
• In finance, you need a view of client equity vs net broker exposure (and what’s realized vs unrealized).

Daily checklist:

• Total client equity = balance + floating P&L + credits (per platform rules). Confirm your CRM reporting uses the same definition.
• Compare platform floating P&L vs risk system floating P&L using the same pricing source and cutoff.
• Validate bridge/LP statements for hedged flow: mismatches often come from partial fills, rejected orders, or LP swaps/commissions.

Fast diagnostics when open P&L is off:

• Check symbol pricing differences (markups, last price vs bid/ask, stale quotes).
• Check rollover timing (swaps posted after cutoff).
• Check netting vs hedging mode (MT5 can behave differently depending on account type).

If you’re using a risk backoffice like Brokeret’s RiskBO, the goal is to have a single operational view: client-side P&L, broker-side exposure, and hedge-side P&L—all timestamped and explainable.

4) Reconcile bonuses and credits: treat them as liabilities with rules, not “marketing spend”

Bonuses, credits, and promotional balances create reconciliation noise because they’re often tracked inconsistently: some teams treat them as “non-withdrawable,” others treat them as “equity,” and the platform may treat them as Credit with special margin behavior.

Daily checklist:

• Break out cash balance vs credit/bonus in every report. Don’t reconcile a blended number.
• Confirm bonus lifecycle events are posted: issuance, partial release, cancellation, expiry.
• Validate withdrawal constraints: if a rule says “bonus removed on withdrawal,” ensure the ledger posts the reversal at the same cutoff.

Operational best practice:

• Define a bonus liability policy: what portion is recognized as client liability vs contingent promotional credit.
• Use reason codes for every bonus adjustment (campaign, retention, IB-funded, correction).

Compliance note: bonus treatment can be sensitive depending on jurisdiction and marketing rules. Consult your compliance team on how bonuses are disclosed and how client money is defined in your regulatory context.

5) Reconcile pending withdrawals: queue health, approval latency, and negative-balance prevention

Withdrawals are where reconciliation issues become client-facing. Your daily process should treat the withdrawal queue as a control surface: it tells you whether your ledgers, risk checks, and payment rails are aligned.

Daily checklist:

• Pending withdrawals total (by currency and method) matches what finance expects to settle within the next cycle.
• Verify status integrity: requested → approved → sent → settled → completed (and clear rules for rejected/returned).
• Check available-to-withdraw logic: equity, bonus restrictions, open positions, chargeback windows.

Exception handling you should run every day:

• Stuck withdrawals (pending > X hours): categorize by cause (KYC missing, risk review, PSP outage, bank cutoff).
• Duplicate requests: same client, same amount, close timestamps.
• Negative equity edge cases: client requests withdrawal after rapid drawdown; ensure your system re-checks eligibility at approval time, not only at request time.

A scalable pattern is to split the queue into two lanes:

• Straight-through payouts (low risk, fully verified, clear ledger)
• Manual review (flags: bonus constraints, unusual velocity, third-party payment method mismatch)

6) Build an “exceptions-first” dashboard: 10 checks that catch 90% of breaks

At scale, reconciliation is less about generating PDFs and more about surfacing breaks early with clear ownership.

Here are 10 daily checks worth automating into an exceptions dashboard (CRM + risk + payments):

• Top 20 largest balance deltas between platform and wallet ledger
• Unmatched transactions (PSP settled but not posted; posted but not settled)
• Manual adjustments in the last 24h (count, total value, approver)
• Credit/bonus liability movement (issued, reversed, expired)
• Pending withdrawals aging (0–4h, 4–24h, >24h)
• Chargeback/rollback events and whether wallet balances were corrected
• FX conversion outliers (rate deviation beyond threshold)
• Open P&L discrepancy by server/symbol group
• Hedge/LP statement breaks (fills, swaps, commissions)
• Dormant-account changes (sudden activity on long-idle accounts)

Assign each exception type an owner (payments ops, dealing, finance, compliance) and a target SLA. The reconciliation process becomes predictable when exceptions are triaged the same way every day.

The Bottom Line

Client money reconciliation at scale is a daily operational discipline, not a month-end scramble. Anchor everything to a single cutoff time, reconcile balances across platform/ledger/rails, and treat open P&L, bonuses, and pending withdrawals as first-class breakpoints.

If you want to automate exception detection across payments, CRM ledgers, and trading platforms, Brokeret can help—start here: /get-started.