How to Reconcile Accounts Receivable: Step-by-Step Process & Checklist

To reconcile accounts receivable, compare the total balance in the AR sub-ledger or aging report with the accounts receivable control account in the general ledger for the same cutoff date. If the balances differ, identify the cause, correct valid discrepancies, and document the reconciliation.

The basic process is:

This process helps finance teams verify that customer-level receivables are properly reflected in the general ledger and that differences such as timing issues, unapplied cash, incorrect postings, duplicate transactions, and manual adjustments are identified and resolved.

Organizations with high transaction volumes may use automated accounts receivable matching, cash application, exception management, and reconciliation platforms to reduce repetitive manual work while maintaining appropriate review and controls.

What Does It Mean to Reconcile Accounts Receivable?

Accounts receivable reconciliation is the process of verifying that the detailed balances recorded in the AR sub-ledger agree with the corresponding accounts receivable balance in the general ledger.

The AR sub-ledger contains customer-level details such as invoices, payments, credit memos, and adjustments. The AR control account in the general ledger contains the summarized accounting balance.

The reconciliation proves that the detailed customer receivable records support the balance reported in the general ledger.

The accounts receivable reconciliation process becomes especially important during month-end and year-end close, when finance teams need confidence that reported receivables are complete, accurate, and supported.

AR Sub-Ledger vs. AR Control Account

The total supported balance in the AR sub-ledger should agree with the AR control account after valid timing differences and approved adjustments are considered.

What Should an AR Reconciliation Prove?

A completed reconciliation should demonstrate that:

• The AR sub-ledger balance agrees with the general ledger control balance.
• Customer invoices and credits are appropriately recorded.
• Payments have been correctly recorded and applied.
• Unapplied cash and unresolved transactions are identified.
• Differences have been investigated and explained.
• Required adjustments have appropriate support and approval.
• The reconciliation has been reviewed and documented.

What Do You Need Before Reconciling Accounts Receivable?

Before starting an AR reconciliation, gather the reports and supporting records needed to compare the detailed receivable balance with the general ledger.

AR Aging or Sub-Ledger Report

Run the accounts receivable aging or equivalent sub-ledger report as of the reconciliation date. The report should include the customer-level balances that make up total receivables.

The accounts receivable aging report provides the detailed receivable balance used for comparison.

General Ledger AR Control Balance

Obtain the closing balance of the accounts receivable control account in the general ledger for the same period and cutoff date.

Using different dates, entities, currencies, locations, or account filters can create differences that are caused by reporting criteria rather than actual accounting errors.

Supporting Transaction Reports

Keep supporting information available for investigation, including:

• Customer invoice register
• Cash receipts and payment records
• Unapplied cash report
• Credit memo report
• Write-off records
• Adjustment and journal-entry reports
• Relevant bank or payment information
• Prior-period reconciliation documentation

How to Reconcile Accounts Receivable: 6 Steps

Step 1: Confirm the Reconciliation Period and Cutoff

Start by defining the accounting period and reconciliation date.

The AR aging or sub-ledger and the general ledger balance must represent the same cutoff. For a month-end reconciliation, both reports should reflect the same month-end date.

Also confirm the applicable entity, currency, business unit, AR account, and reporting filters before comparing the balances.

A mismatched cutoff can create a false variance even when the underlying accounting records are correct.

Step 2: Pull the AR Aging and General Ledger Balance

Generate the AR aging or sub-ledger report and record its total balance.

Then obtain the corresponding AR control account balance from the general ledger for the same date.

At this point, you should have two primary numbers:

• AR sub-ledger total
• AR general ledger control balance

Step 3: Compare the AR Sub-Ledger With the General Ledger

Place the two balances side by side and calculate the difference.

A matching total does not eliminate the need for appropriate review. Finance teams may still perform supporting checks on unusual transactions, significant balances, or known risk areas.

Step 4: Calculate and Investigate the Difference

If the balances do not agree, record the exact variance and investigate the likely causes.

Start with common reconciling items such as:

• Timing or cutoff differences
• Unapplied cash
• Incorrect payment application
• Missing invoices
• Duplicate invoices
• Credit memos
• Write-offs
• Incorrect customer postings
• Manual journal entries
• Unposted or failed transactions
• System integration issues

Document the root cause of each material or unresolved difference rather than simply posting an adjustment to force the balances to agree.

Step 5: Correct and Reconcile the Difference

Once the cause is established, take the appropriate corrective action.

Depending on the issue, this may involve:

• Applying an unapplied payment
• Correcting a customer posting
• Posting a missing transaction
• Reversing a duplicate transaction
• Recording an approved credit memo
• Correcting a journal entry
• Resolving an integration or posting failure
• Recording an approved write-off or adjustment

Corrections should be supported by appropriate evidence and follow the organization’s approval and financial-control requirements.

After corrections are completed, re-run or recheck the relevant reports to confirm that the discrepancy has been resolved.

Step 6: Review, Document, and Sign Off

The final step is to document the reconciliation and obtain the required review and approval.

A reconciliation package should normally identify:

• Reconciliation period
• Cutoff date
• AR sub-ledger balance
• General ledger balance
• Reconciling differences
• Supporting evidence
• Corrections or adjustments
• Outstanding items and owners
• Reviewer or approver
• Completion date

Maintaining this documentation provides an audit trail and makes the next reconciliation cycle easier to perform.

Common Accounts Receivable Reconciliation Differences

Timing and Cutoff Differences

A transaction may be recorded in one system or period before it appears in another. Differences in report dates can therefore create temporary variances.

Unapplied Cash

Unapplied cash occurs when a customer payment has been received but has not yet been correctly associated with a customer account or invoice.

Missing remittance information, incorrect references, unknown payers, partial payments, and consolidated payments can all make payment application more difficult.

Missing or Duplicate Transactions

Missing invoices, duplicate invoices, duplicate payments, or omitted receipts can cause the AR sub-ledger and general ledger to differ.

Credit Memos and Write-Offs

Credit memos, write-offs, and other approved adjustments change customer balances and therefore need to be reflected appropriately in the relevant accounting records.

Manual General Ledger Journal Entries

Manual journals posted directly to the AR control account can create differences if the corresponding detail does not exist in the AR sub-ledger.

When investigating a variance, review manual journals and other journal sources affecting the AR control account.

Unposted Transactions and Integration Problems

Transactions may be present in the AR system but not successfully transferred or posted to the general ledger. ERP and subledger reconciliation reports can help identify these situations.

Customer and Master-Data Issues

Incorrect customer mappings, account assignments, entity settings, or other master-data problems can also create inconsistencies between operational and accounting systems.

Detailed AR Reconciliation Workflow

A practical workflow moves from the overall balance to the individual transaction and then back to the final reconciled balance.

1. Freeze the period: Establish the exact reconciliation cutoff.
2. Gather reports: Obtain the AR aging/sub-ledger and GL control balance.
3. Compare totals: Calculate the difference between the two balances.
4. Analyze exceptions: Identify transactions or journal sources responsible for the variance.
5. Resolve issues: Apply corrections, adjustments, or other approved actions.
6. Recheck balances: Confirm that the correction resolved the variance.
7. Document: Record evidence, explanations, approvals, and outstanding items.

AR Reconciliation vs. Bank Reconciliation

Accounts receivable reconciliation and bank reconciliation are related but different financial controls.

The two processes intersect through accounts receivable cash application. Customer payments received through banks or payment channels need to be correctly identified and applied before the related AR records can be fully validated.

How to Do Accounts Receivable Reconciliation at Month-End

For a month-end reconciliation, use a consistent sequence so that the same controls are performed every period.

1. Confirm the prior-period reconciled balance.
2. Review open prior-period exceptions.
3. Confirm the current period cutoff.
4. Run the AR aging or sub-ledger report.
5. Run the GL AR control account balance.
6. Compare the two balances.
7. Review unapplied cash and significant adjustments.
8. Investigate differences.
9. Post approved corrections.
10. Re-run the reconciliation.
11. Document the final result.
12. Obtain review and sign-off.

A standardized monthly workflow makes it easier to identify recurring issues and prevents reconciliation activities from becoming an end-of-period catch-up exercise.

Accounts Receivable Reconciliation Checklist

Best Practices for Accounts Receivable Reconciliation

• Use the same cutoff: Run all primary reports for the same date and accounting period.
• Standardize the workflow: Follow the same sequence each reconciliation period.
• Investigate root causes: Do not use unexplained adjustments simply to make balances agree.
• Review unapplied cash regularly: Prevent payment backlogs from accumulating.
• Monitor manual journals: Review direct postings to the AR control account.
• Document exceptions: Assign ownership and a next action to unresolved items.
• Maintain an audit trail: Keep supporting evidence for reconciliation decisions and adjustments.
• Automate repeatable work: Use technology where transaction volumes make manual comparison inefficient.

AR automation solutions can help finance teams standardize recurring reconciliation and related accounts receivable processes.

How to Automate Accounts Receivable Reconciliation

Manual reconciliation can become difficult to scale when finance teams work across multiple entities, ERP systems, banks, currencies, payment channels, and high transaction volumes.

Automation can reduce repetitive work by bringing data together, applying matching logic, identifying exceptions, and providing structured workflows for investigation and approval.

Automated AR Matching

Automated matching compares transaction records across systems using defined rules and, where appropriate, intelligent matching techniques.

Modern accounts receivable platforms can support automated matching, monitoring, exception handling, and reporting.

Exception Management

Automation should not only identify unmatched transactions. A useful workflow should show the relevant transaction information, classify the exception, assign ownership, and track resolution.

ERP and GL Integration

Integration between the AR sub-ledger, general ledger, payment systems, and other financial applications reduces manual file movement and makes it easier to identify posting differences.

Oracle’s AR reconciliation guidance, for example, distinguishes internal reconciliation within receivables from external reconciliation between receivables and the general ledger and highlights unposted items, manual GL journals and other subledger sources as potential reconciling causes.

AI-Assisted Reconciliation

AI can assist with complex matching and exception analysis by identifying patterns across transaction and payment information.

The appropriate operating model is generally controlled automation: automate high-confidence and repeatable work while keeping transactions requiring judgment available for human review.

Accounts Receivable Reconciliation Platforms

When evaluating AR reconciliation software, finance teams should consider capabilities such as:

• AR and GL data integration
• Automated transaction matching
• Exception identification and routing
• Unapplied cash visibility
• Approval workflows
• Audit trails
• Reconciliation dashboards
• ERP integration
• Support for multiple entities and currencies
• Scalable transaction processing

The right technology should support the organization’s accounting controls rather than simply automate the act of comparing two numbers.

Metrics and KPIs for AR Reconciliation

Finance teams can monitor several metrics to understand how efficiently the reconciliation process operates.

Common Challenges in AR Reconciliation

High Transaction Volumes

Large organizations may need to reconcile thousands or millions of transactions across multiple systems, making spreadsheet-based processes difficult to scale.

Unapplied Cash

Payments without sufficient remittance information can remain unresolved and complicate both cash application and reconciliation.

Data Fragmentation

When invoice, payment, banking, and general ledger data reside in separate systems, finance teams may need to manually consolidate information before reconciliation.

Manual Errors

Manual data entry and spreadsheet manipulation can introduce errors and make it difficult to maintain a consistent audit trail.

Inconsistent Processes

Different teams or business units may use different reconciliation procedures, making it harder to compare results or identify recurring problems.

How Emagia Supports Accounts Receivable Reconciliation

Modern finance organizations need scalable ways to manage receivables across ERP systems, banking networks, payment channels, and customer transactions.

Emagia supports intelligent automation across the receivables lifecycle, including accounts receivable reconciliation, cash application, payment processing, and related AR workflows.

Key capabilities described for the platform include:

• Automated accounts receivable matching
• Integrated accounts receivable cash application workflows
• Reconciliation visibility and dashboards
• Exception management
• Integration with financial and payment systems
• Scalable automation for enterprise receivables

Organizations can use platforms such as Emagia to connect reconciliation with broader accounts receivable automation rather than treating reconciliation as an isolated spreadsheet activity.

The objective is to create a more connected workflow in which transaction data is captured, payments are applied, exceptions are resolved, and AR balances can be reviewed with greater visibility and control.

Frequently Asked Questions

How do I reconcile accounts receivable to the general ledger?

Run the AR aging or sub-ledger report and the general ledger AR control account for the same cutoff date. Compare the totals, identify any variance, investigate the underlying transactions, post approved corrections, and document the final reconciliation.

What are the steps to reconcile accounts receivable?

The main steps are to confirm the cutoff, gather the AR and GL reports, compare the balances, investigate differences, correct valid discrepancies, and complete review and documentation.

What reports are needed for AR reconciliation?

Common reports include the AR aging or sub-ledger report, general ledger AR control balance, customer invoice register, cash receipts, unapplied cash, credit memos, write-offs, and relevant adjustment or journal-entry reports.

What causes AR reconciliation differences?

Common causes include timing differences, unapplied cash, incorrect payment application, missing or duplicate invoices, credit memos, write-offs, manual GL journals, unposted transactions, and system or data issues.

What is the difference between AR reconciliation and bank reconciliation?

AR reconciliation compares the accounts receivable sub-ledger with the AR control account in the general ledger. Bank reconciliation compares accounting cash records with activity reported by the bank.

How does cash application affect AR reconciliation?

Accurate cash application ensures that customer payments are correctly associated with customer accounts and invoices. This reduces unresolved payment-related differences during AR reconciliation.

How often should accounts receivable be reconciled?

Many organizations perform formal AR reconciliation as part of the monthly close. Higher-volume or higher-risk processes may benefit from more frequent monitoring and exception resolution.

Can AR reconciliation be automated?

Yes. Automation can collect data, compare balances, match transactions, identify exceptions, route work for review, and provide reconciliation dashboards and audit documentation.

What is an AR control account?

The AR control account is the general ledger account that summarizes the organization’s accounts receivable balance. The detailed balances in the AR sub-ledger should support the amount reported in this control account.

What should you do when AR does not match the GL?

Record the variance, confirm that both reports use the same cutoff and filters, investigate timing differences and transaction-level exceptions, review unapplied cash and manual journals, correct valid errors, and rerun the reconciliation before final sign-off.

Conclusion

To reconcile accounts receivable effectively, finance teams need a consistent process that connects the AR sub-ledger with the general ledger and provides a clear method for investigating differences.

The essential workflow is simple: establish the cutoff, gather the reports, compare the balances, investigate differences, correct valid discrepancies, and document the result.

For organizations with high transaction volumes or complex receivables environments, automation can reduce repetitive matching and investigation work while improving visibility into exceptions and reconciliation status.

By combining standardized procedures, accurate data, appropriate controls, and intelligent automation, finance teams can make AR reconciliation a repeatable part of financial close and broader accounts receivable management.