Bank reconciliation for AR: closing the loop on incoming cash
How bank reconciliation ties deposits to applied cash, why it matters for AR accuracy, and how automation matches incoming receipts while handling fees, reversals, and timing.
Bank reconciliation for AR is the process of matching the deposits on your bank statement to the cash applied against invoices in your ledger. It confirms that every dollar received is recorded against the right receivable and that the bank balance and the book balance agree. For an AR team, it is the final check that the cash you collected actually landed and actually cleared the invoices it was meant to.
When this loop is closed, the aging report is trustworthy and DSO is accurate. When it is not, deposits sit unmatched, invoices stay open that customers already paid, and the month-end close drags.
Why bank reconciliation matters for AR
Bank reconciliation is usually framed as a treasury or general-ledger task, but it has a direct line to AR accuracy. The bank statement is the ground truth for cash received. If a deposit appears on the statement that has not been applied to invoices in the subledger, that is unapplied cash, and unapplied cash distorts everything downstream.
The consequences are concrete. Invoices that have been paid still show as open, so collectors send reminders to customers who already paid, which damages relationships and spawns disputes. DSO climbs because the ledger does not reflect the cash sitting in the bank. The receivables balance on the financial statements is overstated. Reconciling the bank closes that gap and keeps the AR picture honest.
The bank reconciliation process
The process compares the bank statement to the cash recorded in the books for a period, then explains every difference. The core steps:
- Pull the bank statement. Capture every deposit and receipt for the period, including ACH, wires, lockbox, and card settlements.
- Pull the applied cash. List the payments applied against invoices in the subledger over the same window.
- Match deposits to applied cash. Tie each deposit to the payments it represents, on amount and date.
- Identify reconciling items. Account for deposits in transit, processor fees, reversals, and unapplied cash.
- Resolve and post. Apply any cash the ledger missed, book fees, and document the explained differences.
- Confirm the balances agree. The adjusted bank balance and the book balance should tie out to the penny.
This is the receipts side of the close. It sits alongside payment reconciliation, which proves the totals tie across processors and the ledger, and it depends on a clean cash application process upstream.
Matching deposits to applied cash
The matching itself is where the work concentrates, because deposits and applied cash rarely map one to one. A lockbox deposit can bundle 40 customer checks into a single line on the statement, while the subledger has 40 separate applied payments. A card processor deposits one net batch that represents many gross payments less fees. A wire might arrive as a round number that covers part of one invoice and all of another.
Good matching works from the deposit down to the underlying payments, confirming that the sum of applied cash for a batch equals the deposit, net of any fee. A deposit that will not tie out points to one of three things: cash that was received but never applied, a fee that was not booked, or a timing difference where the deposit and the application fall in different periods.
Handling fees, reversals, and timing differences
Three categories cause most of the friction:
- Processor fees. Card and gateway deposits arrive net of fees. The gross payment clears the invoice and the fee is booked as an expense. Treating the fee as a short pay leaves a phantom balance on the invoice.
- Reversals and chargebacks. A refund or chargeback pulls money back out after the fact. The reversal has to be matched to the original deposit and the invoice reopened or adjusted accordingly.
- Timing differences. A deposit in transit at period-end appears on the books before it clears the bank, or vice versa. These are legitimate and self-correcting, but they have to be identified as timing items, not unexplained gaps.
Naming each difference correctly is what separates a real exception from noise. Most of what looks like a discrepancy is one of these three, fully explainable.
Automating bank reconciliation
Manual bank reconciliation means exporting the statement, exporting applied cash, and matching them in a spreadsheet line by line, then chasing every difference. It is slow and it clusters at month-end.
Automation imports the bank feed directly, matches deposits to applied cash on amount and date, and resolves the routine reconciling items on its own. It books processor fees, ties reversals back to their original deposits, and flags deposits in transit as timing differences rather than breaks. Lockbox and batch deposits get decomposed into their underlying payments and matched at that level. Instead of building the reconciliation from nothing each period, the team reviews a short list of genuine exceptions.
Reducing month-end reconciliation load
The payoff is a lighter, faster close. When deposits are matched to applied cash continuously rather than in a period-end batch, the bank and the books stay in agreement day to day. Unapplied cash gets caught and cleared while the trail is fresh, so it never accumulates into a month-end backlog. The reconciliation that used to take days becomes a review of a handful of items.
That also means cleaner numbers earlier: DSO reflects real collections, the aging report is reliable, and the receivables balance on the statements is right without a last-minute scramble.
How Rex closes the loop on incoming cash
Rex reconciles the bank to AR continuously. It matches each deposit to the cash applied against invoices, decomposes lockbox and processor batches into their underlying payments, books fees, ties out reversals, and flags timing differences, all as the money moves. Because Rex also applies the cash in the first place, the deposit and the application stay connected, and unapplied cash gets caught the moment it appears instead of at quarter-end.
The true exceptions, the deposits that genuinely will not tie out, go to an operator with the matched detail and the gap already isolated. The month-end close stops being a reconstruction, and the AR picture stays accurate every day.
See how Rex keeps incoming cash matched and reconciled across the ledger.
Frequently asked questions
- What is bank reconciliation in accounts receivable?
- Bank reconciliation for AR is the process of matching the deposits on your bank statement to the cash applied against invoices in your ledger. It confirms that every incoming receipt is recorded and that the bank balance and book balance agree.
- Why does bank reconciliation matter for AR?
- It matters because unmatched deposits and unapplied cash make the aging report and DSO wrong. If the bank shows money the ledger has not applied, invoices stay open that customers have already paid, and collections chase the wrong accounts.
- How do you match deposits to applied cash?
- Tie each bank deposit to the payments applied against invoices for the same amount and date, accounting for lockbox batches, combined payments, and processor fees. A deposit that does not match points to unapplied cash, a fee, or a timing difference.
- Can bank reconciliation be automated?
- Yes. Automation imports the bank feed, matches deposits to applied cash, books fees, handles reversals and timing differences, and surfaces only the true exceptions, replacing the manual statement tie-out at month-end.