Payment reconciliation: keeping AR and cash in sync

Payment reconciliation is the process of confirming that the payments recorded in your AR ledger match the money you actually received across your bank, payment processors, and gateways. It ties the applied cash on your books to the settled funds in your accounts, so the receivables picture reflects reality. When the two sides agree, you know cash is fully accounted for. When they do not, reconciliation finds the gap before it reaches the financial statements.

This matters because payments rarely move in a straight line. Funds settle on one day and post on another, processors take fees before depositing, and a single deposit can bundle dozens of payments. Reconciliation is what keeps all of that honest.

What payment reconciliation involves

At its core, reconciliation answers one question: does the money the ledger says we collected equal the money that actually arrived? To answer it, you compare three things for a given period:

• Recorded payments: the cash applied against invoices in your AR subledger.
• Settled funds: the deposits and settlements that hit your bank and processor accounts.
• The difference: every fee, timing gap, reversal, and unapplied item that explains why the two are not identical.

A clean reconciliation accounts for every dollar of difference with a reason. Nothing is left unexplained. This is the close cousin of cash application: where cash application decides which invoices a payment clears, reconciliation proves the totals tie out across every account the money touched.

Sources of payment data to reconcile

Modern AR collects cash through many channels, and each one reports differently. A full reconciliation pulls from:

• Bank statements: ACH, wires, and lockbox deposits.
• Card processors and gateways: Stripe, Adyen, or similar, which settle in batches net of fees.
• The AR subledger: applied payments and credits in your ERP.
• The general ledger: the cash and AR control accounts the subledger should tie to.
• Customer payment portals and remittance: the detail explaining what each payment covered.

The work is lining these up. A processor batch deposit of $48,200 might represent $50,000 of customer payments less $1,800 in fees, spread across 60 invoices applied two days earlier. Reconciliation connects those numbers.

Common reconciliation breaks

Most reconciliation time goes to a short list of recurring breaks:

• Timing differences. A payment settles at the bank on a different day than it posts to the ledger, so a period-end snapshot shows a gap that closes itself a day later.
• Processor fees. The gross payment and the net deposit differ by the fee, and that fee has to be booked, not treated as a short pay.
• Partial and combined payments. One deposit covers many invoices, or one invoice is paid across several deposits, so totals do not map one to one.
• Refunds and reversals. A chargeback or refund pulls money back out, and the reversal has to be matched to the original payment.
• Unapplied cash. Money received but not yet matched to invoices sits in a holding account, making the subledger and bank disagree until it clears.

Each break is explainable. The cost is the manual effort of finding and explaining it, item by item.

Manual vs automated reconciliation

Manual reconciliation is a spreadsheet exercise. Someone exports the bank file, exports the processor settlements, exports the subledger, and lines them up by hand, ticking off matches and hunting down the differences. It works, but it is slow, error-prone, and concentrated at month-end when everyone is already stretched. The bigger the volume, the longer the tie-out, and the later the close.

Automated reconciliation pulls each data source in continuously and matches it as money moves. Settlement files from each processor, bank deposits, and applied cash get matched on amount, date, and reference, with fees and timing differences accounted for automatically. Instead of building the reconciliation from scratch each period, the team reviews a short list of genuine breaks. Clean matching here is what keeps a cash application process and the books in agreement day to day rather than once a month.

How AI resolves mismatches

Agentic automation goes a step further than matching totals. It reasons through why a break exists and resolves it.

When a processor deposit does not equal the applied cash, the system identifies the fee and books it. When a payment settles in a different period than it posted, it flags the timing difference rather than calling it a discrepancy. When a refund appears, it traces it to the original payment and ties the reversal out. When cash is unapplied, it works to apply it, then reconciles the result. What remains is the small set of breaks where the cause is genuinely unclear, handed to a person with the supporting detail already gathered.

The effect is that AR and cash stay in sync continuously, not just at the end of a frantic close. This also feeds directly into bank reconciliation for AR, where deposits get matched back to applied cash.

Reconciliation controls and audit trails

Reconciliation is a control, so the trail matters as much as the result. Good practice means every match and every adjustment is logged: what was matched, on what basis, who or what approved it, and when. That record is what lets an auditor confirm the cash account is complete and accurate without re-performing the work.

Automation strengthens this. Because the system records each decision and its evidence as it goes, the audit trail is a byproduct of the reconciliation rather than a separate reconstruction. Segregation between who applies cash and who approves adjustments stays intact, and exceptions are documented at the moment they are resolved.

How Rex keeps payments reconciled

Rex reconciles payments across processors, banks, and the ledger continuously, without the spreadsheet tie-outs most teams run at month-end. It pulls settlement data from each source, matches it to applied cash and deposits, books fees, accounts for timing and reversals, and ties the totals out across the subledger and GL. The reconciliation is always current because the agent works it as money moves, not in a period-end batch.

When a break cannot be explained from the available data, Rex escalates it to an operator with the matched detail and the gap already isolated, so a person makes the call instead of hunting for it. AR and cash stay in agreement, and the close stops being a scramble.

See how Rex keeps your receivables and cash reconciled in real time.