Customer Reconciliation

By Nupur Mittal

Co-founder at OCTA — works with accounting firms on month-end close and reconciliation automation.

A customer reconciliation matches the accounts receivable (AR) subledger balance for a specific customer to that customer's own remittances and statement of account, then explains every difference. It confirms the AR balance in the books is accurate and collectible by resolving unapplied cash, disputed invoices, and unmatched items — not just tallying what's overdue. This page walks through the full process and format step by step, the red flags a careful reviewer watches for, and how accounting firms run customer reconciliations faster with OCTA Flow while a human approves every entry.

Why customer reconciliation matters, and where it goes wrong

Every dollar sitting in accounts receivable is a promise that hasn't been collected yet, and the AR subledger is only as trustworthy as the reconciliation behind it. Customers pay against invoice numbers that don't match the ones in your system, deduct amounts for disputes without telling anyone, and send remittances that arrive weeks after the cash hits the bank. Left alone, those gaps compound: a customer's own statement of account can end up materially different from what your subledger says they owe, and nobody notices until the customer refuses to pay an invoice they believe is already settled.

For a firm or an AR team, the work is genuinely tedious — matching hundreds of invoices to payments one by one, tracking down why a $6,000 receipt never got applied, chasing a sales rep for the backup on a disputed deduction. But the cost of skipping it is real: unapplied cash overstates open AR and can misstate revenue recognition, unresolved disputes erode the customer relationship, and balances that drift past 90 days without a plan quietly become bad debt. A properly run customer reconciliation turns "we think they owe us about that much" into a number the CFO, the auditor, and the customer all agree on.

The customer reconciliation process, step by step

A rigorous customer reconciliation follows a consistent sequence. The steps below are the full procedure OCTA Flow executes; they also stand alone as a best-practice process any AR team can follow.

1. Confirm the opening balance. Compare the AR subledger's opening balance for the customer to the customer's own statement, if one is available. A difference here usually means a prior-period item was never resolved — flag it before moving forward.

2. Match invoices to payments. For every payment the customer has remitted, identify which invoice(s) it was applied to. Match on remittance advice reference numbers, invoice numbers, and amounts. Fully matched pairs are cleared; partial payments carry forward the remaining balance on that invoice.

3. Categorize everything that doesn't match. Sort each unmatched item into one of five buckets:

• Open invoices — recorded in AR, not yet paid.
• Unapplied cash — a payment the customer sent and the bank received, but that hasn't been matched to an invoice in the subledger yet.
• Disputed invoices — the customer deducted an amount from their payment, usually pending a credit note or resolution with sales.
• Unapplied credit notes — credits issued to the customer that are sitting in their account without being applied to an invoice.
• Overpayments — the customer paid more than the invoice amount.

4. Age the open receivables. Bucket every open invoice by age from the invoice date: current (0–30 days), 31–60 days, 61–90 days, and over 90 days. Balances over 90 days carry the highest collection risk and should be flagged for credit review.

5. Check credit notes. For any outstanding credit note, confirm it's either applied against an open invoice or sitting as an acknowledged open credit the customer has confirmed. A credit note the customer doesn't know about is a discrepancy waiting to surface on their next statement.

6. Verify against the customer's own statement. If the customer provides a statement of account, compare their view of what they owe to the subledger line by line. Any difference — timing, dispute, or genuine error — needs an assigned reason, not a shrug.

7. Assess collectibility on aged balances. For anything over 90 days, confirm: has the customer been contacted? Is a payment plan in place? Should a bad debt reserve be recorded against the balance?

8. Compute the closing position. Compare the AR subledger closing balance to the customer statement closing balance (where available). Whatever is left after accounting for every reconciling item is the unreconciled difference — and it should be zero, or explained.

9. Propose the adjusting entries. Draft the entries that clear what the reconciliation found: applying matched cash to the right invoice, and recording a bad debt reserve where collectibility is in doubt. These go to a person for review before anything posts.

The customer reconciliation format (worked example)

The two-sided format brings the AR subledger and the customer's statement to the same number. Here's a worked example for a wholesale customer at period-end:

Both sides tie to $118,850. The story behind the two adjustments: the customer remitted $6,200 against Invoice INV-2041, and the bank received it, but the payment hasn't been applied to that invoice in the subledger yet — so the subledger still shows the invoice open even though the customer's statement already treats it as paid. Separately, the customer deducted $3,400 from a payment against Invoice INV-2058, disputing a portion of the invoice for a shipping-damage claim, and is waiting on a credit note before they'll consider the invoice fully settled. Once the $6,200 is applied and the dispute is resolved with either a credit note or a documented override, both balances will agree without an adjustment.

Key controls and red flags

The difference between matching invoices and a reliable reconciliation is what you watch for. A careful reviewer flags:

• Unapplied cash sitting for more than 30 days — risk of a revenue recognition error and an overstated open AR balance
• Invoices over 90 days without a documented payment arrangement — bad debt risk
• Customer deductions with no approved credit note behind them — an unauthorized deduction that needs resolution, not a write-off
• Duplicate invoice numbers in the AR subledger — a data or system error worth tracing before it recurs
• Payments applied to the wrong invoice — a misapplication that will surface as a false discrepancy next period
• Customer-acknowledged balance differing from the AR subledger by more than $1 — a statement-of-account (SOA) discrepancy that needs an assigned reason
• Credit notes issued but not applied within 60 days — sitting exposure the customer may not even know about
• Overpayments not refunded or applied within 30 days — cash that should either go back to the customer or reduce their next invoice

Catching these consistently, every customer and every period, is what keeps AR aging honest and collections focused on the accounts that actually need attention.

What a completed reconciliation produces

A finished customer reconciliation isn't just a matched spreadsheet — it's a documented workpaper the AR manager can sign off on and an auditor can follow. A complete package includes:

How OCTA Flow automates customer reconciliation

OCTA Flow does the mechanical matching for you and leaves the judgment — and the sign-off — with your team. The workflow mirrors the process above:

1. Pick the Customer Reconciliation Skill. Flow already knows the full procedure: match invoices to remittances, categorize unapplied cash and disputes, age open AR, and reconcile against the customer's own statement.
2. Connect your data. Point Flow at the AR module in your accounting system, or upload the period's files — the AR subledger, the customer's remittances, and their statement of account if they provide one.
3. Run. Flow matches every invoice it can to a payment, sorts what's left into unapplied cash, disputed invoices, unapplied credits, and overpayments, then builds the aging and reconciliation schedules.
4. Review findings by severity. Instead of a wall of matched line items, Flow surfaces only the exceptions — ranked by severity, each with a plain-English explanation and a recommended action: apply a matched payment, email the customer, request approval on a dispute, or escalate a balance that's gone quiet. Your team works the exceptions, not every invoice.
5. Sign off. Once the reconciliation ties and the proposed entries are approved, Flow assembles the workpaper with the full audit trail intact.

The result: the repetitive invoice-to-payment matching is done in a fraction of the time, and your AR team spends its hours on the customers and items that actually need a conversation.

Control and trust: Flow proposes, you approve

This is what matters most to a firm or AR team putting its name on the numbers: OCTA Flow never writes to your books on its own. Every application of cash, every credit note, and every adjusting entry is a proposal that a human reviews and confirms before anything is posted. Flow does the matching and shows its reasoning; a person makes the call — especially on a dispute, where the wrong call can cost a customer relationship.

That control model runs through the whole reconciliation:

• Findings, not silent changes. Flow raises what it found and what it recommends — you decide whether to apply the cash, credit the customer, or escalate.
• Severity and escalation built in. A large unapplied receipt or a stale dispute is flagged prominently and can be escalated to a manager rather than quietly aging another 30 days.
• A complete audit trail. Every match, proposed application, approval, and override is logged, so the reconciliation is fully traceable end to end.

You get the speed of automation with the accountability of human sign-off — exactly what a customer-facing balance like AR requires.

What the reconciliation draws on

To run a customer reconciliation, Flow uses the same sources a preparer already works from:

• AR subledger — the company's accounts receivable transactions for the customer (required)
• Customer remittances — the customer's payment remittances and payment advice (required)
• Customer statement of account — the customer's own view of what they owe, if they provide one (optional)
• Open sales orders — for a completeness check against what's been invoiced (optional)
• Credit notes — credit notes issued to the customer, to verify they're applied or acknowledged (optional)

Flow works from whatever your client has connected — it matches each input by its purpose, so it doesn't matter what the files are named or which accounting system they came from.

Related skills and terms

Frequently Asked Questions

What is a customer reconciliation? It's the process of matching a company's accounts receivable subledger for a specific customer to that customer's remittances and statement of account, so both sides agree on what's owed. It confirms the AR balance is accurate and identifies unapplied cash, disputed invoices, and unmatched items.

How is customer reconciliation different from bank reconciliation? Bank reconciliation ties the cash balance in the books to the bank statement. Customer reconciliation ties the AR subledger — what a specific customer owes — to that customer's own remittances and statement. The mechanics are similar (match, categorize, explain the difference), but the source documents and the reconciling items are different: unapplied cash and disputed invoices instead of outstanding checks and deposits in transit.

What is unapplied cash? Unapplied cash is a payment a customer has sent — and the company has received and deposited — that hasn't yet been matched to a specific open invoice in the AR subledger. Until it's applied, the subledger overstates how much the customer actually still owes. Cash unapplied for more than 30 days is a standard red flag.

How do you handle a disputed invoice in a customer reconciliation? Record the disputed amount as a reconciling item rather than writing it off. Confirm whether the dispute is supported by an approved credit note; if not, it's flagged as an unauthorized deduction that needs resolution with sales or operations before the invoice can be considered settled.

What causes a customer statement to not match the AR subledger? The most common causes are unapplied cash, a disputed or partially paid invoice, a credit note the customer hasn't acknowledged, an invoice posted for the wrong amount, or a payment applied to the wrong invoice. Any difference between the two should be assigned a specific reason — a gap over roughly $1 is generally treated as a discrepancy worth investigating.

Can customer reconciliation be automated? The invoice-to-payment matching, aging, and exception-flagging can be automated and reviewed, while judgment calls — especially on disputes and collectibility — stay with your team. That's the model OCTA Flow uses.

Does OCTA Flow post entries or credit notes directly to my accounting system? No. Flow proposes every cash application, credit note, and adjusting entry; a person on your team reviews and approves before anything is posted to the books. Nothing is written automatically.

See how firms run faster, fully-explained customer reconciliations with human sign-off → start a 30-day OCTA Flow trial.