To do accounts receivable reconciliation each month, pull the AR aging and the GL control account at the same cutoff date, compare totals, and trace every difference to a transaction. Fix each one at its source, get it approved, and file the support.
If you’re a US controller, you know the pain. The subledger says one number, the ledger says another, and close slips while someone hunts. Our accounts receivable services team sees the same few causes again and again, so this post gives you the routine and the five differences you’ll meet most.
Quick Answer Accounts receivable reconciliation is the check that your customer-level AR subledger agrees with the AR control account in the general ledger. Run it monthly at a shared cutoff date, explain every difference, and clear it at the source. Weekly checks on unapplied cash and direct journals keep the month-end number clean.
Accounts receivable reconciliation confirms that the detail by customer (the subledger or aging) adds up to the AR balance on the balance sheet. Accounts receivable postings normally update the control account automatically. So a difference usually means something reached the GL outside the subledger, or the two reports were run on different dates.
We use one model throughout this post, and we reuse its stage names below.
The QServices Framework Reconcile = Cutoff → Compare → Trace → Fix → Repeat
Order matters: if the cutoff differs, every later stage chases differences that aren’t real.
A preparer, usually in AR or general accounting, does the work. A reviewer, usually the controller or an accounting manager, approves it. One university policy (UA Little Rock, LR 303.8) sets a good pattern: reconcile monthly by the 15th, and have preparer and approver sign within 7 days.
This is the accounts receivable reconciliation process in its plainest form. It’s also the heart of month-end AR reconciliation.
Start with the Cutoff stage. Run both reports as of the same date, on the same basis, and combine balances if you have more than one AR account (domestic, foreign, affiliates). To reconcile AR aging report to general ledger, compare the aging total with the control account balance, and write down the amount and direction of the gap.
Business Central has a built-in check for this: the Reconcile Cust. and Vend. Accs. report, which totals net change in the GL and in customer ledgers and splits entries by posting group.
Key Insight A signature and date no longer satisfies auditors on its own. CFGI recommends a coversheet per balance sheet account that shows the evidence, starting with your most material accounts.
Standards & References
- PCAOB AS 2201: auditing internal control over financial reporting
- COSO internal control guidance: the framework most US control programs follow
These are the common accounts receivable reconciliation differences. They come from our reading of vendor and documentation sources, not a ranked study, so treat the order as a rule of thumb.
A transaction lands in the subledger in one period and the GL in another, or a batch sits unposted. This is also the biggest source of AR reconciliation differences in ERP systems, because reports often run on document date in one place and posting date in another.
The bank deposit is in the GL, but there’s no remittance detail, so invoices still look open. Unapplied payments reconciliation is its own task because these items rarely clear on their own. See why unapplied cash piles up.
Someone posts straight to the AR control account. The GL moves and the subledger never knows.
They’re entered in the wrong period or left unapplied. Sage Intacct’s documentation also lists advances or overpayments mapped to non-AR accounts and payments dated before the invoice.
Duplicates, wrong-customer applications, and short-pays or deductions nobody approved. Our guide to tracking each short pay covers the last one.
Real-World Scenario A typical case we see: a controller’s GL shows AR of $2,396,200 while the aging totals $2,418,500, a $22,300 gap. Trace finds $18,000 of unapplied cash credited to the control account and a $4,300 manual journal that never reached a customer. Both lower the GL only. Naive hunting through 400 invoices takes days. The Trace stage splits the gap by posting type first and finds both items in under an hour.
A fix in the Fix stage should change the cause, not just the balance. For AR aging reconciliation, a few settings matter most:
Get remittance detail first, apply the payment, then clear the suspense entry. If the detail never arrives, escalate by customer after a set number of days. Our cash application services take this on directly, and the cash application process shows where it usually breaks.
A weekly accounts receivable reconciliation routine moves the Trace stage out of close week. Review unapplied cash daily or weekly, then check unposted batches and direct GL journals before the period ends. Teams that wait often spend close week on reconciliation: in Ledge’s 2025 vendor survey (n=100), 27% needed more than 7 business days to close, and account reconciliation was the most time-consuming activity. That’s a vendor survey, so read it as directional. Our month end close checklist shows why unapplied cash slows it, and the AR aging buckets guide helps you read what’s left.
| Month-end only | Weekly routine | |
|---|---|---|
| Differences found | After they’ve aged | While still fresh |
| Close-week workload | Heavy | Lighter |
| Audit evidence | One big file | Dated trail |
| Calendar cost | One crunch | A recurring slot each week (the downside) |
| Best for | Very low volume | Most US controller teams |
We start at Cutoff, because a shared date removes the false differences. Then we run these steps:
The same team builds and runs it, and we start with a two-week fixed-price assessment.
Implementation Checklist
- Aging and GL pulled as of the same cutoff date
- All AR control accounts combined in the comparison
- Difference amount and direction recorded
- Unapplied cash listed by deposit date
- Manual journals to the control account reviewed
- Preparer and approver signed and dated within 7 days
Pilot weekly accounts receivable reconciliation on one entity’s AR control account for a month, and measure days to complete the reconciliation, open unapplied cash, and unexplained differences at month-end. Your team approves every item that posts. Book the AR Cash Assessment and we’ll review your current routine with you.
Written by Rohit Dabra
Co-Founder and CTO, QServices IT Solutions Pvt Ltd
Rohit Dabra is the Co-Founder and Chief Technology Officer at QServices, a software development company focused on building practical digital solutions for businesses. At QServices, Rohit works closely with startups and growing businesses to design and develop web platforms, mobile applications, and scalable cloud systems. He is particularly interested in automation and artificial intelligence, building systems that automate routine tasks for teams and organizations.
Accounts receivable reconciliation is the check that the AR subledger (customer-level detail or aging) agrees with the AR control account in the general ledger. Any difference is investigated, corrected with approval, and documented.
Monthly at minimum, as part of the month-end close. Accounts receivable reconciliation frequency works best weekly for unapplied cash and direct journals, so month-end holds fewer surprises.
Usually one of five causes: timing and cutoff, unapplied cash, manual journals posted straight to the control account, credit memos or write-offs in the wrong period, or application errors. Start by confirming both reports use the same date.
Start by running one entity’s aging and GL balance at the same cutoff date and recording the gap. We begin with a two-week fixed-price assessment that maps your control accounts and sets up the weekly routine.
The AR subledger holds invoices and payments by customer. The general ledger holds the AR control account total. AR subledger vs general ledger should agree at every cutoff date.
Accounts receivable reconciliation made simple: follow a step-by-step monthly routine, spot the five most common differences and fix them at the source.
Collection effectiveness index shows what DSO hides. See the CEI formula, a worked example and how to use it to manage collectors in your AR team.
Process mining vs process discovery: see what each needs and delivers, and how your ERP and CRM logs can pick your first automation in two weeks.
Use this dunning letter sequence with templates for day 1, 7, 15, 30 and 45 to collect overdue invoices faster and keep the customer relationship intact.
Compare SYSPRO integration options for bank files, CRM and e-commerce, and learn how to connect them without touching your ERP core. Built for IT Directors.
ERP upgrade, cloud move, Power Apps extension or replacement? Compare costs and risks in one decision table and pick the right path for your on-prem ERP.
Accounts receivable reconciliation made simple: follow a step-by-step monthly routine, spot the five most common differences and fix them at the source.
Collection effectiveness index shows what DSO hides. See the CEI formula, a worked example and how to use it to manage collectors in your AR team.
Process mining vs process discovery: see what each needs and delivers, and how your ERP and CRM logs can pick your first automation in two weeks.
Use this dunning letter sequence with templates for day 1, 7, 15, 30 and 45 to collect overdue invoices faster and keep the customer relationship intact.
Compare SYSPRO integration options for bank files, CRM and e-commerce, and learn how to connect them without touching your ERP core. Built for IT Directors.
ERP upgrade, cloud move, Power Apps extension or replacement? Compare costs and risks in one decision table and pick the right path for your on-prem ERP.
Earning Global Recognition: A Testament to Quality Work and Client Satisfaction. Our Business Thrives on Customer Partnership
Every quote comes from a published review on GoodFirms, Clutch or our own site. Click a source to read the full review.
Trustpilot5.0★★★★★See reviewsGoodFirms5.0★★★★★45 verified reviews
G25.0★★★★★See reviewsClutch5.0★★★★★Quality 5.0 · Schedule 4.8
Google4.7★★★★★Mohali office“QServices was highly professional, knowledgeable, and approachable. We continue to work with them on other projects.”
“Quality assurance is often overlooked, but these guys take that very seriously. … their team of experienced, dedicated developers and highly skilled engineers quickly dissected and decomposed every problem and presented solutions and options that directly met my needs”
Erik BrownBusiness owner and software engineerClient review“The supplier delivered the application on time and was responsive to our needs. He was also flexible, which allowed us to make changes on the fly.”
Zoltan BodnarCFO, Yusen LogisticsGoodFirms“Thank you Sahil and team for wonderful collaboration right from day 0. … Highly recommend the developers.”
Ranbeer MakinClientClient review“They are always looking for new ways to improve their products and services and to deliver value to their customers.”
“I have had an excellent experience working with QServices. We have a highly collaborative relationship and I value them not just as contractors but as partners.”
Alex VanderElsClientClient review“Sahil undertakes every project with a high degree of professionalism. His communication style is unmatched and he is always available to resolve issues or just discuss the project.”
Philmore J.ClientClient review“Responsive, patient and professional. Consistent weekly attention to our project, and new ideas we hadn't asked for.”
Michael WilliamsonPresident and CEO, United Way of Southeast LouisianaGoodFirms“I have been working with them on a project for a year now … They have been able to solve problems that come up with bugs or development and able to communicate well with me.”
Steven LewisClientClient review“We had been working on the app for two years. QServices built it in two months.”
Brian WallerPresident, Technology Association of IowaGoodFirms“All projects were delivered on time and were fully completed upon delivery.”
“They had excellent quality. The hypercare they provided after the project went live is exceptional.”
Founder and CEO
Chief Sales Officer
Thanks, we’ve got your details. A named member of our team will reply within one business day.
