Remittance reconciliation. Every leg, every rate, every partner.

Remittance reconciliation, in short

Remittance reconciliation is the process of proving that each cross-border transfer was collected from the sender, converted at the booked rate, paid to the recipient once, and settled with the payout partner, and that your balances with every partner still add up. A remittance is not one payment but several connected legs, each with its own evidence, and every leg has to agree before the transfer can be treated as finished.

It is harder than domestic payment reconciliation because the legs happen in different currencies, time zones, and organisations, and because money often sits with partners in prefunded accounts between transfers.

Why is a remittance harder to reconcile?

A typical transfer has five parts that each need their own proof.

The sender cares about one status. Your operations and finance teams need to know which of these legs is complete and which is still waiting for evidence.

Where do FX and fee differences come from?

Most remittance breaks that are not missing records are differences in rate or fee.

• Rate applied versus rate booked: the partner converts at a different rate from the one quoted to the sender, or applies its own rounding.
• Fees netted at source: a partner deducts its fee from the prefunded balance when the contract says it will invoice monthly, or the reverse.
• Intermediary charges: a bank leg arrives short because a correspondent bank took a charge on the way.
• Rounding across currencies: small differences accumulate when amounts are rounded in each currency separately.

Each difference needs an agreed tolerance and an owner. A difference beyond tolerance becomes a FEE_FX_MISMATCH exception with the quote and the partner’s record attached, rather than being absorbed into a suspense account.

How do you reconcile prefunded partner balances?

Many remittance operators prefund payout partners in the destination currency. The check for each partner and currency is simple to state and easy to lose track of:

Opening balance, plus top-ups received, minus payouts, minus fees, plus returns, equals the closing balance on the partner’s statement.

• Top-ups in transit: a top-up that has left your bank but not yet reached the partner belongs in neither balance, so it needs its own in-transit record.
• Cut-offs across time zones: a payout made just after midnight in the partner’s time zone belongs to the next business day there, even if it was the same day for the sender.
• Returns: a failed or returned payout should come back to the prefund, and the sender’s refund should be evidenced separately.

When the balance differs and no single transfer explains it, the difference is raised as POSITION_UNEXPLAINED until it is traced.

What changes from corridor to corridor?

Illustrative corridors to show how the checks differ. This is not a list of supported corridors; coverage is agreed for each deployment.

A worked example

A sender in the UK sends GBP 200.00 to a mobile wallet in Ghana. The quoted rate is 1 GBP = 15.60 GHS and the fee is GBP 1.50, so the sender pays GBP 201.50 and the recipient should receive GHS 3,120.00.

1. Collection: GBP 201.50 is collected and appears in your PSP’s settlement and then on your GBP bank statement.
2. FX: the conversion record shows GBP 200.00 converted at 15.60, giving GHS 3,120.00, matching the booked quote.
3. Payout: the partner reports the payout as paid through its API and a signed webhook, with its own reference.
4. Partner settlement: the partner’s next-day transaction report lists the payout at GHS 3,120.00, drawn from your GHS prefund.
5. Position: at the end of the day, the GHS prefund is GHS 10.00 lower than your ledger expects. The statement shows a GHS 10.00 fee deducted per payout, while the contract says partner fees are invoiced monthly.

The transfer itself is matched: the sender paid, the rate was right, and the recipient was paid once. The GHS 10.00 is raised as FEE_FX_MISMATCH against the partner’s settlement, with the contract terms and statement line attached. The recipient’s payout is not touched, and the difference stays open until the partner credits it or a person records a decision.

Illustrative example. The amounts, rate, and fee are invented to show the method.

A daily remittance reconciliation routine

1. Ingest each PSP settlement, partner report, partner statement, and bank statement as it arrives, and list any that are missing at cut-off.
2. Match each transfer leg by leg, using your transfer reference and each partner’s reference.
3. Check booked rates and fees against the rates and fees applied.
4. Reconcile each partner prefund, in each currency, including top-ups in transit.
5. Raise an owned exception for every difference, and keep the evidence with it.
6. Close each transfer only when every leg agrees, and close the day only when every file is present or listed as missing.

How Flominzo applies this

Flominzo Send keeps one payment reference across the collection, FX, payout, and settlement legs of a transfer, so each leg is reconciled against its own evidence without losing the link to the sender. Flominzo Recon reconciles those legs and your partner positions, raises typed exceptions for rate, fee, and balance differences, and keeps the original records behind every decision. It can start read-only alongside your existing remittance platform.

Questions

Sources

• ISO 20022 message definitions (camt.052, camt.053, camt.054)