Balance reconciliation matches what a business recorded as earned against the money that actually arrived, line by line, until every difference has a name. In payments that means tying orders to transactions, transactions to the provider's settlement file, and the settlement file to the credit on the bank statement.
How does payment reconciliation work: three files that must agree
Two-way checking is where most teams stop, and it is not enough. The first source is the internal order or invoice record. The second is the provider's settlement file, listing each transaction with its fees and deductions. The third is the bank statement.
Matching the first to the second proves the payments processed as expected. Matching the second to the third proves the provider actually paid what its own file promised. Skip the middle step and underpaid payouts or misapplied pricing can run for months without anyone seeing them.
Unpacking one bank credit
A single Wednesday credit might contain Monday's card sales less processing and scheme fees, minus two refunds, minus a chargeback for a transaction from three months ago, plus a reserve release, less a fresh reserve withholding, with one group of sales missing entirely because it fell after the cut-off and went into the next file.
Every one of those movements has a different source. The sales come from a batch processing run, the reserve lines from the reserve account, the chargeback from a case opened long before this file existed. Reconciliation is the exercise of naming each of them.
Picking a join key that survives the trip
Use the provider's transaction ID as the key across every system, and store it on the order at the moment of capture. Order numbers get truncated, bank references get rewritten by intermediary banks, and customer-entered narratives are close to useless. Choosing the right key removes more manual matching work than any amount of process discipline.
Incoming bank transfers are the harder half, because the payer controls the reference. Giving each customer its own virtual account makes the payer identify itself and turns that matching problem into a lookup.
Breaks that come back every month
The same handful recur: a partial refund posted as a full one, rounding on multi-currency settlement, a duplicate capture, a chargeback debited with no case reference attached, a payout split across two bank credits, and any batch that crosses a month-end boundary.
Marketplaces face a harder version, since one incoming payment may be divided between several sellers, a platform commission and a tax withholding before anything leaves the account.
Daily, not monthly
Reconcile every day so a break is investigated while the underlying transaction is still fresh and the provider will still discuss it. Automate the exact matches and route only exceptions to a person. For firms holding client money the daily match is a supervisory expectation rather than good housekeeping, which is why it is usually built alongside treasury management reporting.