Settlement reconciliation. Proving each settlement against the payments inside it.

Settlement reconciliation, in short

Settlement reconciliation proves that each settlement a provider makes to you, or you make to others, is complete, adds up, and arrived as cash. It checks that every payment appears in exactly one settlement, that the settlement’s lines add up to its net amount, and that the net matches a movement on the bank statement. Any difference becomes an exception with a reason and an owner.

It sits between payment-level reconciliation, which follows each payment’s own records, and bank reconciliation, which compares your ledger with your bank. Most of the money that goes missing in a payment business goes missing here, inside a batch that looked right in total.

Settlement vs reconciliation

The two words are often used together, but they describe different things.

Put simply, settlement is the event and reconciliation is the proof. A settlement you haven’t reconciled is a total you have chosen to trust.

What a settlement contains

A settlement report usually carries more than payments. Reconciling it means accounting for every line type:

• Payments captured or paid out in the settlement period.
• Fees, per transaction or per batch, sometimes invoiced separately instead of deducted.
• Refunds and chargebacks, including dispute fees and reversed chargebacks.
• Reserves held back from this settlement, and reserves released from earlier ones.
• FX where the settlement currency differs from the transaction currency.
• Adjustments and prior-period items: corrections to earlier settlements, which is where closed days reopen.

Three checks for every settlement

1. Completeness. Every payment that should settle is in exactly one settlement, and every line in the settlement is a payment you know about. Missing payments, duplicates and orphans all show up here.
2. Arithmetic. The lines add up to the stated net, and the fees and rates match what you agreed. A settlement can be complete and still wrong if a fee was misapplied.
3. Cash. The net arrived on the bank statement within the expected window, in the expected account and currency. Until it does, the settlement is a claim, not a fact.

Give each provider an expectation: which report arrives, by what time, and which bank account it settles into. A report that doesn’t arrive by its cut-off should raise an exception on its own, rather than being noticed when someone looks for it.

Cut-offs, value dates and T+n

Timing causes more false breaks than anything else. A payment captured at 23:30 in your time zone can fall on the next day in the provider’s. A T+2 settlement lands on a different business day from a T+1 one, and bank holidays move both. The bank’s booking date and value date can differ again.

Encode these as rules, not habits: each provider’s cut-off and time zone, its settlement cycle, and the timing tolerance you accept. Then a payment that is simply early or late is recognised as timing, and only a real difference becomes an exception.

Reserves and multi-currency settlements

Reserves are where settlement reconciliation most often goes quiet. A provider may hold a percentage of each settlement for a period, keep a fixed amount, or hold money back after a spike in disputes. Each hold should be recorded against the batch it came from, and each release matched to that hold, so your balance at the provider stays explained line by line. A reserve that is never released looks like nothing at all unless you track it.

Multi-currency settlements add another layer. Payments taken in one currency may settle in another, at a rate the provider sets. Record the rate the provider applied, compare it with any rate you agreed, and keep the conversion as its own line so an FX difference doesn’t hide inside a fee or a rounding tolerance.

A daily settlement routine

1. Check that every expected settlement report has arrived, by provider and currency.
2. Check each report’s arithmetic: lines add up to the stated net.
3. Match each payment to exactly one settlement line, and each line to a payment.
4. Match each settlement net to a bank movement within its timing window.
5. Update reserves held and released, and your position at each provider.
6. Give every difference an owner, and close the day only when nothing is unexplained.

Run it every business day, not at month end. A settlement that is a day old can still be queried with the provider while everyone remembers it; one that is a month old usually can’t.

Settlements you make to others

Settlement runs in both directions. If you settle to merchants, sellers or partners, each outbound settlement needs the same proof in reverse: the balances it is meant to pay off, the payout instruction or file that carried it, the provider’s or bank’s confirmation, and the debit on your statement.

Two checks matter most. First, the amount you settled to each counterparty should equal their balance for the period, less anything you are entitled to hold back, with each deduction explained. Second, the statement you send them should agree with what actually left your account. When a merchant disputes a settlement, you want to show the lines behind it, not re-run the calculation from memory.

Outbound settlements also fail in their own ways: a payout returned because the account details changed, a payment sent to the right account for the wrong period, or a settlement paid twice after a timeout. Each of those is an exception on the counterparty’s balance until it is resolved.

What settlement reconciliation software must do

If you are choosing settlement reconciliation software, check for these, and test them on your own files:

• Read every provider’s reports as evidence, keeping the original file and its provenance next to the mapped rows.
• Match many-to-one: thousands of payments to one settlement, and one settlement to one bank line.
• Hold an expectation for every file, and raise an exception when a file is missing.
• Track reserves held and released across batches, per provider and currency.
• Log every use of a tolerance, rather than hiding small differences.
• Turn every break into an owned exception with its evidence attached, not a red cell.
• Reopen a closed day when late evidence arrives, keeping the earlier decision on record.
• Start read-only, alongside your current process, so the results can be compared before anything changes.

The broader checklist for choosing payment reconciliation software covers the rest.

The settlement exceptions to expect

How Flominzo Recon applies this

Flominzo Recon reconciles at three levels: each payment against the evidence it should receive, each settlement against its lines, the bank movement and your ledger, and each position against the provider’s statements. The exception names above are the ones Recon uses. Rules, tolerances and expectations are versioned, so every match can be explained by the rule that produced it.

100% reconciliation means every payment is matched or explained, with evidence: it ends either matched against independent evidence - the provider’s records, the settlement file and the bank statement - or as an open exception with an owner and a reason. None is silently assumed paid. A settlement that is short is never silently accepted: accepting it, or writing off the difference, is a decision a person with the right permission records.

Questions

Related guides