NetSuite A/R or A/P Aging Mismatch

When a NetSuite A/R or A/P Aging report does not match the General Ledger, do not begin with a journal entry to force the difference away.

Begin by making sure you are comparing the same thing.

Use the same as-of date, subsidiary, accounting book, currency, account scope, and report filters. Then compare the Aging Detail to the control-account GL detail, not just a summary total.

A few common causes are specific:

• Journal entries or other transactions posted directly to A/R or A/P

• A control-account line without the appropriate customer or vendor

• A payment, credit, or application entered after the historical as-of date

• Transaction dates and posting periods that do not align

• Different treatment of subsidiaries, currencies, or accounting books

• Customized aging or financial reports using inconsistent filters

A useful control is a saved search that flags every posting to the A/R and A/P control accounts that does not come from an expected transaction type, or that lacks the required customer or vendor. That turns the reconciliation from a recurring scavenger hunt into an exception-review process.

Also remember that aging buckets are designed to organize unpaid subledger balances. The General Ledger is designed to report accounting postings. They should reconcile, but they reach the answer through different structures.

The goal is not merely to make two totals agree today. It is to identify the transaction or process that created the difference so it does not return next month.

If you are dealing with this, feel free to reach out. These differences are diagnosable once the comparison is framed: https://bit.ly/schedule-with-justin