Payment Reconciliation for Forex Brokers: Matching Deposits to Accounts

Header image: conceptual illustration.

A broker can have a perfect payment integration and still lose money through reconciliation gaps: a deposit credited twice, a reversed payment left credited, or a settlement shortfall nobody noticed. Reconciliation is the routine that catches these. This guide focuses on the brokerage case, where the final destination of a deposit is a trading account rather than a shipped order. For general principles, see our payment reconciliation guide.

Three-way matching

Brokers should reconcile three sources, not two:

1. Provider records — transaction reports and settlement files.
2. Payment records — your internal payment table with statuses and provider IDs.
3. Trading-account ledger — balance adjustments in the trading platform or back office.

Every successful deposit should appear once in all three, with the same amount and currency.

Identifiers that make matching possible

• Your internal payment ID, sent to the provider as the merchant reference.
• The provider's transaction ID, stored when returned.
• The trading-account adjustment ID, stored on the payment record when crediting.

If any link is missing, matching falls back to amount-and-time guessing, which fails at volume.

Exception types

• Provider success, not credited. The client paid but has no balance. Highest priority for client experience.
• Credited, not in provider report. Possible duplicate credit or fraud. Highest priority for financial risk.
• Amount mismatch. Often fees or currency conversion; confirm which.
• Credited, later reversed. Requires a documented procedure to adjust the account under the broker's policies.
• Duplicate credit. Same provider ID credited twice; prevent with a unique constraint on provider transaction ID.
• Settlement shortfall. Settlement total differs from expected net of fees.

A daily routine

1. Import yesterday's provider reports automatically.
2. Run matching and produce an exception list.
3. Assign each exception an owner and a due time.
4. Resolve client-facing exceptions first, financial-risk exceptions in parallel.
5. Record the resolution and keep the evidence.

Hypothetical example

*Invented for illustration.* Daily matching finds 1,204 provider successes, 1,203 credits, and one credit with no provider record. The unmatched credit shares an amount with a deposit credited a minute earlier; logs show the webhook was processed twice before a uniqueness check existed. The team reverses the duplicate under its policy, adds a database constraint, and notes the root cause.

Controls that reduce exceptions

• Unique constraint on provider transaction ID.
• Idempotent webhook processing (how idempotency helps).
• Crediting only from a verified status.
• Automated status checks for pending items.

Frequently asked questions

How often should brokers reconcile?

Daily for transactions; per settlement for settlement files. High-volume brokers often run intraday checks too.

Can reconciliation be fully automated?

Matching can; resolving exceptions usually needs a person and a documented decision.

Related: forex payment processing for operations teams.