- A complete reconciliation has three checks; most guides stop at subledger to GL.
- Run the aging and the GL at one cutoff date, and look first for journal entries posted straight to the control account.
- Payment plans booked as one invoice can tie out perfectly while the aging shows a current customer as months past due.
- Reconcile each payment plan to its signed schedule every month, and hand missed installments to collections the day you find them.
- The structural fix is installment billing: give each installment its own amount and due date in the system.
Accounts receivable reconciliation looks routine until customers start paying in installments. Take a typical settlement at a customer we worked with, a contingency-fee employment law firm: a settlement of about $24,000, paid at roughly $2,000 a month for a year. The case management system generates one invoice and sends it with the settlement letter, and the payment plan lives in the letter. The accounting software receives that one invoice, for the full amount, with a single due date at the end of the month. The real schedule, with twelve due dates, what has come in and what is still owed, sits in a shared spreadsheet that someone updates by hand. When the finance team tries to pull an aging report it can trust, it can't.
Here's the uncomfortable part: receivables like these can tie out perfectly. The subledger can match the general ledger to the cent, and the aging can still be wrong.
Accounts receivable reconciliation is the process of proving your receivables are right: the AR subledger agrees with the GL control account, cash in the bank has been applied to the right invoices, and open balances match what customers actually owe under their agreements. Most guides stop at the first of those checks. With payment plans, the third is where the numbers break. This guide covers the steps, a worked example, and how to fix the structure with installment billing. If you collect settlements from the other side of a case, our guide to law firm collections covers the wider process.
What Accounts Receivable Reconciliation Is (and the Three Checks It Should Include)
AR reconciliation compares what your receivables records say with independent evidence and explains every difference. Most teams do it monthly as part of the close. The more often you do it, the smaller and fresher the differences you have to explain.
A complete reconciliation covers three checks:
| Check | Compares | Catches |
|---|---|---|
| 1. Subledger to GL | AR aging total vs. the receivables control account in the general ledger | Journal entries posted straight to the control account, cutoff differences, duplicate or missing postings |
| 2. Ledger to bank | Bank deposits vs. receipts applied in the subledger | Unapplied cash, payments applied to the wrong customer or invoice, deposits never recorded |
| 3. Ledger to agreement | Each customer's open balance and due dates vs. the signed terms | Wrong amounts, wrong due dates, missed installments nobody flagged |
The second check overlaps with cash application, the day-to-day work of matching each payment to the invoices it pays; reconciliation is the month-end proof that it was done right. For how that matching works, see our guide to cash application automation. It's also different from bank reconciliation, which ties the GL cash account to the bank statement (covered in our guide to building a bank reconciliation skill).
The third check is the one most teams skip, because for an invoice with one due date and one payment it adds nothing. For payment plans, it's the check that matters most.
How to Reconcile Accounts Receivable, Step by Step
- Finish posting and pick one cutoff date. Make sure every invoice, credit memo and receipt for the period has been posted, then choose a single cutoff, usually the last day of the month. Reports run on different dates are one of the most common reasons totals don't agree.
- Pull the aging and the GL balance at that cutoff. Run the detailed AR aging, by customer and invoice, and the GL receivables control balance as of the same date. Keep customer statements, invoices and bank deposit records at hand for the steps that follow.
- Compare totals and investigate differences. If the aging total and the GL balance differ, look first for manual journal entries posted directly to the control account. They change the GL without touching any customer account, and they're often the most common cause. Then check cutoff (an invoice or receipt in one report but not the other), duplicates, and postings to the wrong customer.
- Tie cash to receipts. Match the period's bank deposits against receipts applied in the subledger. A deposit nobody can identify goes into unapplied cash, with an owner and a plan to get the remittance details. A payment applied to the wrong invoice gets moved.
- Tie balances to agreements. For every customer on a payment plan or special terms, compare the ledger balance and due dates with the signed schedule: what should have been paid by now, what was paid, and what's due next. This step catches installment problems, and it's the one most process guides leave out.
- Adjust, document and sign off. Post corrections with support (a credit memo, a reclassification, an approved write-off), write a short note for each reconciling item you carry forward, and have someone other than the preparer review the package. File it where your auditors can find it.
Common Reasons the Numbers Don't Match
| Cause | Where it shows up | Fix |
|---|---|---|
| Journal entry posted straight to the AR control account | GL differs from subledger | Reverse it and post through the subledger, or document why it belongs at GL level |
| Reports run on different dates | GL differs from subledger | Rerun both at the same cutoff |
| Unapplied cash | Customer balances overstated | Park it, get remittance details, apply it |
| Payment applied to the wrong invoice or customer | Customer balance wrong, total right | Reapply; check how the payment was identified |
| Duplicate invoice | Subledger overstated | Void or credit the duplicate |
| Unsupported credit memo or unapproved write-off | Balance reduced without backing | Get approval and support, or reverse |
| Installments booked as one invoice | Totals tie; aging and due dates wrong | Reconcile to the schedule, then fix the billing structure |
Short payments and deductions also cause mismatches, but they belong in a dispute workflow rather than in the reconciliation itself; see invoice dispute management.
The last row is the one no total-to-total comparison will catch. Here's what it looks like.
Worked Example: A $24,000 Payment Plan Booked as One Invoice
The numbers below are illustrative, built on the scenario described above.
A $24,000 settlement is payable in 12 monthly installments of $2,000, due on the last day of each month from January through December. The accounting software holds one invoice for $24,000, due January 31. By the April 30 close, all four installments due so far have arrived: $8,000 paid, $16,000 open.
| View | Open balance | How it ages on April 30 |
|---|---|---|
| AR subledger (aging) | $16,000 | All $16,000 is 89 days past due (61–90 bucket) |
| GL control account | $16,000 | Not aged |
| Agreement (true position) | $16,000 | $0 past due; $16,000 not yet due (May–December) |
Check 1 passes: subledger and GL agree. Check 2 passes too, since every payment was applied. Check 3 fails. The customer is fully current, and the aging reports $16,000 as seriously overdue.
That error spreads. Collectors working from the aging chase money that isn't due, and a counterparty who is paying on time gets a call it shouldn't. Past-due reports to leadership overstate the problem. And if your allowance for doubtful accounts is estimated from aging buckets, it reserves against balances that aren't late.
Now suppose March's $2,000 never arrived. The open balance would be $18,000, still all in the 61–90 bucket. In the aging, a customer who is fully current and one who has missed a payment look almost the same. Only the spreadsheet shows the miss, and only if someone checks it. A missed installment needs attention within days, not at month-end; here's what to do after a broken promise to pay.
The distortion can also run the other way. If a single invoice were set to fall due at the end of the plan, the whole balance would show as current, and a real miss would stay hidden for months.
How do you record it? If the subledger and GL agree, the gap is in due dates, not the balance. Under standard practice, that means there's nothing to correct in the totals, though how teams handle it varies. Document it as a reconciling note, attach the schedule, and ask your accountant whether aging-based estimates such as the allowance need adjusting.
Installment Billing: How to Make the Ledger Match the Payment Plan
Reconciling to a spreadsheet every month treats the symptom. The structural fix is installment billing: each installment gets its own amount and due date in the system. There are three ways to get there.
| Approach | Report accuracy | Manual work | Fits when |
|---|---|---|---|
| One invoice plus a side schedule | Totals right; aging and due dates wrong | Spreadsheet upkeep every month; depends on whoever maintains it | Few plans, short terms |
| Invoice the full amount, then credit it and issue one invoice per installment | Aging right, by installment | More invoices to create; may not import automatically from upstream systems | Moderate volume; a tool with one due date per invoice |
| Native installment terms, or an AR tool that tracks each installment | Aging right; only the late installment shows past due | Set up once per plan | Growing volume of plans |
The first approach is where the firm started. The second is what its finance team planned: keep the integration that creates one invoice per case, then reverse it and replace it with installment invoices. They expected the reports to become accurate and the invoicing to become more manual, and harder to keep up with as volume grows. That's the honest trade-off of credit-and-split: you buy accurate aging with clerical work.
The constraint behind it is common. Some small-business accounting tools allow only one due date per invoice; the usual workaround is separate or recurring invoices. Some ERPs support installment terms that age each installment separately, so a missed payment shows up as one late $2,000 line instead of disappearing inside a large overdue invoice. If you're choosing or replacing an accounting system, ask early how it handles payment plans.
Whichever route you take, decide who owns the schedule. When a plan changes, say a customer skips a month or pays two installments at once, the invoices or terms have to change with it. Otherwise you're back to reconciling against a spreadsheet.
One caution: when the full settlement amount should be recorded as a receivable is an accounting question, not a reconciliation one, so ask your accountant.
Installment tracking in Daylit is coming soon.
A Month-End Reconciliation Checklist
- All invoices, credit memos and receipts for the period posted
- One cutoff date; aging and GL run as of that date
- Aging total agrees with the GL control balance, or every difference explained
- Manual journal entries to the control account reviewed
- Bank deposits tied to applied receipts; unapplied cash listed with owners
- Open payment plans listed with the next due date
- Installments due this period compared with installments received
- Missed installments handed to collections the day they're found
- Adjustments posted with support; reconciling items carried forward with an owner
- Package reviewed and signed off by someone other than the preparer
Accounts Receivable Reconciliation Is Three Checks, Not One
Accounts receivable reconciliation means checking subledger to GL, ledger to bank, and ledger to agreement. The first two keep your totals honest. The third keeps your aging honest, and it's the one that breaks when customers pay in installments. Reconcile to the schedule every month, then fix the billing structure so the ledger shows each installment on its own. That's when the aging, the collections queue and the reports start telling the same story.
How often should you reconcile accounts receivable?
Monthly, as part of the close, at minimum. Teams with many payment plans benefit from comparing installments due with installments received more often, because a miss found at month-end may already be weeks old.
What's the difference between AR reconciliation and cash application?
Cash application applies each incoming payment to the invoices it pays, usually daily. AR reconciliation proves, usually monthly, that the totals, the cash and the due dates are right. See cash application automation for the first.
Why does my AR aging look worse than it is?
The usual suspects are unapplied cash, which leaves paid invoices open, and payment plans booked as one invoice, which age the whole balance from the first due date.



