A difference between an accounts receivable aging report and the general ledger deserves an explanation before it deserves a journal. The reports may describe different populations, use different dates, or express balances in different currencies. Posting an adjustment too early can turn a reporting mismatch into an accounting error.
A useful NetSuite AR aging reconciliation starts by defining what should agree. Then it preserves every difference until a reviewer can trace it to a transaction, reporting choice, or approved correction. This guide gives an AR manager and controller a repeatable method for doing that without losing unexplained items inside a balancing figure.
Write a one-sentence reconciliation objective. For example: reconcile the subsidiary's trade receivables control accounts to customer open items at the close date, expressed in that subsidiary's base currency.
That sentence makes several decisions explicit. It identifies the legal entity, the account population, the cutoff, and the currency basis. A consolidated receivables balance requires a different comparison from a single-subsidiary ledger. A report containing one receivables account cannot establish agreement with a ledger total containing several.
Save both report definitions alongside the outputs. Record the run time, effective date or period, account filters, subsidiary context, currency presentation, customer filters, and any custom exclusions. Report availability and filter behaviour depend on the account's enabled features and configuration, so confirm the actual settings rather than relying on remembered defaults.
Use detail reports for the investigation. A customer subtotal can conceal an equal and opposite pair of errors. Keep transaction identifiers and the customer or project association wherever available.
Aging buckets answer a collection question: how old is an amount under the chosen aging basis? The total answers a balance question: which amounts are included at the selected cutoff? Changing bucket intervals will not necessarily resolve a difference in the total.
Start with a small sample around month end. Select an invoice, payment, credit, and journal from both sides of the cutoff. Inspect transaction dates, posting periods, and applications. Determine how the specific report treats them when run historically.
A payment entered today and applied to an older invoice can complicate a comparison of a historical ledger with a current open-item extract. A transaction dated in one month but posted in another can create another mismatch if the two reports use different bases. Document the behaviour you observe in your configuration; do not assume every report uses the same logic.
Repeat the same report after any late posting. A saved export represents the state when it was generated, not a permanent statement of the underlying records.
Use this sequence to reduce wasted effort:
Do not conclude that every journal to receivables is absent from aging. Its treatment can depend on the transaction and entity information, and unassigned amounts may appear separately. Inspect the report detail and underlying record before classifying the difference.
Likewise, unapplied cash is an investigation category rather than an automatic correction. Establish which account holds it, how the report presents it, and whether it belongs in the specific reconciliation objective.
Assume a subsidiary's ledger shows trade receivables of 126,400 currency units. The first aging export totals 120,000. The unexplained difference is therefore 6,400.
The reviewer identifies three reporting differences:
Adding these evidenced differences to the initial aging total produces 126,100. There is still a 300 difference against the 126,400 ledger balance.
That 300 remains explicitly unresolved. It is not relabelled as rounding, currency, or immaterial simply because the larger differences are explained. The controller may apply a documented materiality policy to decide the close response, but the worksheet should continue to show the amount, owner, and next investigation step.
This example assumes a common base-currency measurement and contains no exchange-rate adjustment. If currency measurement differs, construct a separate translation or revaluation bridge using the approved accounting basis. Mixing currency effects into the population bridge makes both harder to review.
Use one row for each difference, with these fields:
Define signs once. For example, a positive bridge item increases aging toward the ledger. Reversing the sign convention midway through a workbook can produce a superficially balanced result with incorrect explanations.
Keep the original exception row after resolution. Add the corrected report reference, transaction correction, or approved disposition. This creates a history that another reviewer can follow without recreating the investigation.
A report filter error usually calls for a report correction. A missing or incorrectly recorded transaction needs review of the underlying transaction. A currency presentation difference may require a comparable report rather than a ledger entry.
Where an accounting correction is warranted, the controller should approve its account, period, customer association, and supporting explanation. Closed-period implications and local accounting policies require separate review. Avoid a generic journal that makes the control account agree while leaving customer balances wrong.
After correction, rerun both sides on the agreed basis. Confirm the reconciled total and retest selected customer balances. Save the final bridge and the remaining exceptions, including any approved carry-forward items. A clean total with unexplained customer-level movements is incomplete evidence.
Investigate amounts without a customer or project association rather than assuming they disappear. Review how the selected aging report presents them and whether the transaction was recorded appropriately for the control account.
Only after making the populations and currency basis comparable. A subsidiary ledger and a consolidated report can differ because of entity scope and translation. Define the reconciliation at one level first.
Its size alone does not establish the cause. Follow the organisation's materiality and approval policies, retain the exception, and distinguish a justified accounting adjustment from a reporting correction.
Align the formal sign-off with the close cycle. More frequent checks can help where payment volumes, integrations, or late postings create recurring differences. Choose a cadence that allows exceptions to be investigated before close.
Use the same comparison definition each period and review repeat exception categories. If the cause remains unclear, ask CuriousRubik about a scoped NetSuite AR reconciliation diagnostic covering report settings, transaction evidence, and the unresolved bridge.