FrontierERP
Sign inTalk to Frontier
Applied guide

Why A/R aging won't tie to the balance sheet

NetSuite's A/R aging lists open items; the balance sheet shows a ledger balance. Five reconciling lines between them, footed to zero on one example.

Frontier · November 12, 2026

An applied guide for the controller who has to tie the aging to the A/R account at month-end.

The short answer. In NetSuite, the A/R line on the balance sheet is a general-ledger balance by posting period. An A/R aging, whether NetSuite's own, a saved search or one an AI builds, is a list of the items still open on a date. The two part ways in four places. They select transactions differently: the balance sheet by posting period, an aging by transaction date. They count different things: a journal to the A/R account, an unapplied credit memo or an unapplied payment sits in the ledger, and a pull of invoices misses it. They measure "open" at different times: the ledger holds what was open on the as-of date, and a pull of each invoice's amount unpaid today drops whatever was paid since. And they carry a foreign-currency receivable at different rates: the ledger at the month-end revaluation, an aging at the rate on the invoice or not translated at all. Differ on any of these and the aging won't tie. Below, the four become five reconciling lines on one constructed set of receivables that ties to zero two ways: against NetSuite's own A/R Aging, and against a pull of invoice headers.

This is the third tie-out on this site. Why a saved search won't match NetSuite's P&L and Why a saved search won't match the balance sheet reconcile a pull to a whole statement. This one ties a subledger to a single line of the balance sheet, on the same Harbor group at 31 October 2026.

The five lines, in Oracle's words.

  • Period against date. "If you filter by date range, report records are selected by transaction date. If you filter by period, report records are selected by posting period" (Report by Period). The Report by Period preference decides which reports run by period. On Financials Only, the reports run by period are the "Income Statements, Balance Sheets, Cash Flow Statement, Trial Balance Report" and three graphs (Reporting Preferences). The A/R aging isn't on the list, so it runs by date. On All Reports, "All reports will be run by posting period" (Report by Period). A transaction can carry a date in one period and a posting period in another when the Allow Transaction Date Outside of Posting Period preference is set to Warn or Allow (General Accounting Preferences).
  • Journals to A/R. NetSuite's aging counts them: "Entries grouped under No Customer/Project are Journal Entries" (A/R Aging Detail), and the summary report puts an A/R entry with no customer on its No Customer/Project line (A/R Aging Summary). A pull of invoice headers never reads a journal.
  • Credit memos and payments. The detail report lists transaction types "such as invoice, customer credit, payment, and so on", and "This includes credit memos." An applied credit or payment reduces an invoice's own unpaid amount, so every list agrees on it. An unapplied one is a credit to A/R that only an invoice pull leaves out.
  • Open when. The ledger at 31 October holds every receivable posted through October, whatever happened in November. NetSuite's detail report "shows transactions based on the date they are closed, as opposed to the date they are applied." A pull that tests each invoice's amount unpaid when it runs reads today's state for a past date.
  • Rate. "Revaluations apply exchange rates as of the last day of the accounting period to calculate gain or loss" (Revaluation of Open Currency Balances), and "Accounts Receivable, Accounts Payable, and Unbilled Receivable accounts are always included on the Month End Currency Revaluation page" (Types of Accounts That Can Be Revalued). So the ledger carries an open foreign-currency invoice at the period-end rate. Entity balances and A/R reports don't: "NetSuite converts foreign currency balances to base currency using the exchange rates on the transactions", and "A/R and A/P reports also show transaction and balance amounts in the base currency" (Balance Information for Entities with Multiple Currencies).

None of this is a defect. Oracle describes the aging as a collections tool, a way "to identify where your collection efforts should be concentrated" (A/R Aging Detail). The balance sheet is the ledger. They answer different questions, and a month-end tie-out has to name the difference line by line.

Harbor's receivables at 31 October.

This is the group from the P&L and balance sheet pages, with its receivables broken out. Every amount and rate below is constructed for the example and labelled as such; nothing comes from a live account. A script committed beside this page generates the figures and re-foots them.

Harbor Inc. is the US parent and keeps its books in dollars. Its A/R account holds 212,000 of the 1,570,000 of assets on the balance sheet page. Harbor GmbH, the German subsidiary, holds EUR 64,000 of its EUR 542,000. On the consolidated balance sheet that is 282,400 of A/R: 212,000 plus EUR 64,000 at the current 1.1000. None of the five items below is on Harbor GmbH's books, so its aging and its ledger agree in euros. Harbor Inc. has all five, so tie one subsidiary at a time and start with it.

The report to match is the Balance Sheet for Harbor Inc., not consolidated, period Oct 2026, accounting book Primary: A/R 212,000. Two agings are set against it, each as of 31 October 2026 and run on 12 November:

  • NetSuite's A/R Aging for Harbor Inc. The Report by Period preference is Financials Only, so the balance sheet runs by period and the aging by date.
  • A header-only pull, the shape a saved search or an AI-built query over transaction headers usually takes: invoices and cash sales dated on or before 31 October, open when their amount unpaid is above zero when the pull runs, each amount in the invoice's own currency, summed as returned.
Item Date Posting period Ledger, 31 Oct NetSuite's A/R Aging Header-only pull
USD invoices still open today, one of them 2,500 from May to 31 Oct to Oct 2026 155,000 155,000 155,000
Invoice for a September delivery, entered 4 Nov 29 Sep Nov 2026 — 9,000 9,000
Journal: write-off against the bad-debt allowance, no customer 31 Oct Oct 2026 (2,500) (2,500), No Customer/Project —
Credit memo, unapplied 18 Sep Sep 2026 (3,000) (3,000) —
Customer payment, unapplied 28 Oct Oct 2026 (7,500) (7,500) —
Invoice, due 21 Oct, paid 5 Nov 21 Sep Sep 2026 26,000 26,000 —
Invoice, EUR 40,000 4 Sep Sep 2026 44,000 at 1.1000 44,600 at 1.1150 40,000 in EUR
Total 212,000 221,600 204,000

Constructed figures, Harbor Inc., USD unless marked. Harbor Inc.'s other assets are 1,358,000, so its total is still the balance sheet page's 1,570,000. The credit memo and the invoices with income behind them are dated in September, and the journal and the payment touch only balance-sheet accounts, so October's income is still the P&L page's 61,000. The pull's total adds the euro invoice's 40,000 to the dollars, as a sum of its amount column does.

Here is each line, in the order a reconciliation would take them.

1 · Date against period. A September delivery was invoiced on 4 November, dated 29 September, the delivery date, and posted to November, the open period. The Allow Transaction Date Outside of Posting Period preference permits that on Warn or Allow. The ledger for October doesn't hold it. Both agings select on the transaction date, the date on the record, not the day it was keyed, so both list it: 9,000 above the ledger. An aging run on 31 October didn't have it; one run on 12 November for the same day does. Set Report by Period to All Reports and Oracle says all reports then run by posting period, so NetSuite's aging would select by period and this line would leave its column; the pull, filtered on the date, keeps it. The reverse case, dated in November and posted to October, sits in the ledger and in neither aging.

2 · A journal to A/R. On 31 October a 2,500 invoice from May was written off against the bad-debt allowance by journal: credit A/R, debit the allowance, with no customer on the A/R line and nothing applied to the invoice. Oracle's write-off takes two more steps: the customer named on the A/R line, then a zero-amount customer payment that applies the journal to the invoice (Creating a Journal Entry to Write Off Bad Debt). The ledger fell by 2,500. NetSuite's aging still shows the May invoice open under its customer, and the journal's (2,500) on its No Customer/Project line, so the two cancel only in the total. The header-only pull has the invoice and not the journal: 2,500 above the ledger. Done Oracle's way, the invoice "is no longer included in the Open Invoices report or in A/R Aging reports" (Accepting a Customer Payment to Write Off Bad Debt), and the three agree without this line; so would they after a credit memo applied to the invoice.

3 · An unapplied credit memo and an unapplied payment. A 3,000 credit memo from 18 September and a 7,500 payment received on 28 October are not yet applied to any invoice. Both credit A/R, so the ledger is 10,500 lower. NetSuite's aging lists both. The pull reads invoice headers and misses both: 10,500 above the ledger.

4 · Open on 31 October, paid on 5 November. A 26,000 invoice from 21 September fell due on 21 October and was paid on 5 November. The ledger at 31 October holds it, and NetSuite's aging as of 31 October shows it, 10 days past due. The pull runs on 12 November, finds the amount unpaid is now zero, and drops it: 26,000 below the ledger. Run on 31 October it would have agreed on this line. Every day after the as-of date it drifts by whatever was collected.

5 · A euro invoice on dollar books. Harbor Inc. invoiced a German customer EUR 40,000 on 4 September at 1.1150, or 44,600 when it posted. The September revaluation restated it at 30 September's 1.1000, a 600 unrealized loss. That reversed on 1 October (reversals "post the first day of the period after the Unrealized Gain/Loss transaction", Currency Revaluation Transactions), and the October revaluation restated it at 31 October's 1.1000 again. So the ledger carries 44,000, and October's revaluation nets to nothing. NetSuite's aging carries 44,600, at the rate on the invoice: 600 above the ledger. The pull returns 40,000 in euros, and summed with the dollars it is 4,000 below.

Harbor Inc., 31 Oct 2026 NetSuite's A/R Aging Header-only pull
A/R per the balance sheet 212,000 212,000
1 · Date vs period: invoice dated 29 Sep, posted to Nov 2026 9,000 9,000
2 · Journal to A/R with no customer: a 2,500 write-off — 2,500
3 · Credit memo and customer payment, both unapplied — 10,500
4 · Open on 31 Oct, paid on 5 Nov — (26,000)
5 · Rate: EUR 40,000 invoice, revalued to 1.1000 in the ledger 600 (4,000)
Reconciled 221,600 204,000
The aging's own total 221,600 204,000
Difference 0 0

USD. Constructed figures; generated and re-footed by the packet script. Each line is the amount to add to the ledger to reach that aging.

Only two of the five lines touch NetSuite's own aging: the date and the rate. It already counts the journal, the unapplied credits and the paid-later invoice the way the ledger does. The header-only pull carries all five, and they don't cancel: it sits 8,000 below the ledger, while NetSuite's aging sits 9,600 above it. A pull that happens to land on the ledger's figure can still be wrong on every line, so tie it line by line, not on the total.

Check before you trust the number.

Run the aging and the balance sheet for the same subsidiary, the same date and the same book. Then work through five checks, one per line, each naming the setting, report line or field that decides it.

  1. Date against period. Read the Report by Period preference at Home > Set Preferences, on the Analytics subtab (Choosing a Date or Period Range for a Report; Oracle's Report by Period FAQ calls it the Reporting/Search subtab). It is one of the "individual user preferences that apply only to reports available with your current login" (Reporting Preferences), so read it for whoever ran or scheduled the aging; two users can get two answers. On Financials Only the balance sheet runs by period and the aging by date. Then read Allow Transaction Date Outside of Posting Period, on the General subtab of the Accounting Preferences page. On Disallow, users can't save a transaction unless its date falls within its posting period. On Warn or Allow, list the A/R transactions whose date and posting period fall in different months around the as-of date.
  2. Journals. Read the No Customer/Project line on NetSuite's A/R Aging. For a pull, add every journal line posted to the A/R account, or list them beside it. A write-off journal leaves its invoice open in every invoice list until a zero-amount customer payment applies the journal to it, Oracle's second step. Oracle notes one kind of journal that cancels itself: journals "against identical accounts for the same entity value don't impact the general ledger" (A/R Aging Detail), so neither side sees them.
  3. Credit memos and payments. On the A/R Aging Detail, read the Transaction Type column for customer credits and payments. For a pull, add unapplied credit memos and unapplied customer payments, or list them beside it.
  4. Open when. Did the pull run after the as-of date? Then add back every payment and credit applied after that date to an item dated on or before it, or run the pull on the as-of date itself. NetSuite's detail report keeps an item until the date it closed.
  5. Rate. On a subsidiary with foreign-currency receivables, open the period's revaluation (Transactions > Financial > Revalue Open Currency Balances > List) and its Details subtab. On Open Receivables, each row's Gain/Loss is "(Balance × Ending Exchange rate) - Base Currency Balance" (Revaluation Record Details): the gap between the ledger and an aging at the rate on the invoice. For a pull in transaction currency, translate each foreign amount at the period-end rate first. If revaluation didn't run, the ledger is still at the invoice's rate, and Oracle warns that "your monthly financial statements may be inaccurate due to missing currency revaluation transactions" (Revaluation of Open Currency Balances).

An aging that passes all five and still differs has a cause this page doesn't cover, and that one is worth a ticket. An aging that fails one of them has its answer.

What this means for an AI-built aging.

The same five lines apply to an aging an assistant builds from your account, whatever the tool. Frontier's A/R aging is one of nine standard statements: "which customer invoices are open, how late, in which bucket", from an as-of date and an optional subsidiary. Like the A/P aging, it reads transaction headers only and takes no book. The query and the rows come attached.

Read against this page, it is the header-only pull. It reads invoices and cash sales that post and are not voided, dated on or before the as-of date. An item is open when its amount unpaid, as the record stands when the query runs, is above 0.01. It ages by due date. Each amount comes back in the invoice's own currency, with a currency column beside it. Left without a subsidiary, it lists every subsidiary's items together, so on a multi-currency group run it one subsidiary at a time. For Harbor Inc. on 12 November its rows are the right-hand column of the first table.

So its limits are lines 2 to 5. It reads no journals to A/R. It reads no credit memos or customer payments, and its own documentation names credit memos as the piece to layer in. It reports what is open when it runs, which is not a historical balance for a past as-of date. And it reports in transaction currency. It is an open-item list for collections, as of the day you run it. It does not reproduce NetSuite's A/R Aging.

For the tie-out, pair it with the trial balance on the same list. Its A/R account line reads posting periods ending on or before the as-of date, posting lines only, in one book. Run for one subsidiary, it gives that subsidiary's ledger balance in its base currency: Harbor Inc.'s 212,000. Run the aging on the as-of date and translate its euro rows at the period-end rate the revaluation used, and lines 4 and 5 close. Lines 1 to 3 are the list the checks above produce.

On access: Frontier reads your NetSuite through one integration role that you create and can revoke at any time: web-services only, view-level record permissions. Every answer carries the query and the rows behind it, so your team can check any figure against the ledger.

One next step: take the aging you have and the balance sheet's A/R line for the same subsidiary, date and book. Walk the five checks in order. Each difference belongs to one of them, and the list you end up with is the reconciliation.

Sources and limits.

Every figure in this guide is constructed to show the mechanism. None comes from a customer account, and the page carries no query. Statements about NetSuite's behaviour are quoted or paraphrased from Oracle's documentation, linked where they appear: the A/R Aging Detail report, the A/R Aging Summary report, filtering reports by period or date, reporting preferences, choosing a date or period range, general accounting preferences, revaluation of open currency balances, accounts that can be revalued, currency revaluation transactions, revaluation record details, writing off bad debt by journal, the zero-amount payment that closes it and balances for entities with multiple currencies. Your account's Report by Period preference, its journals to A/R, how promptly credits and payments are applied, and its currencies decide which of the five lines apply to you, and the checklist is how to find out.

Questions this raises

Why doesn't my NetSuite A/R aging match the balance sheet?
Because the balance sheet's A/R is a general-ledger balance by posting period, and an aging is a list of the items still open on a date. The two select transactions differently (posting period against transaction date), count different things (journals to A/R, unapplied credit memos and payments), measure open at different times (open on the as-of date against open today) and carry foreign-currency receivables at different rates (the month-end revaluation against the rate on the invoice). Each difference is one reconciling line. The page ties one constructed set of receivables to zero both ways.
Where do journal entries to A/R show up on the aging?
On NetSuite's own A/R aging, journal entries to the A/R account with no customer are grouped on the No Customer/Project line. A saved search or query that reads only invoice headers never sees them, so it differs from the ledger by every journal posted to A/R. A write-off journal not yet applied to its invoice with a zero-amount customer payment, the second step of Oracle's write-off, also leaves that invoice open, so in NetSuite's aging the invoice and the journal cancel only in the total.
Why does an aging run for a past date change?
Two reasons. A transaction entered later with an earlier date joins every aging run by date for that past day; posted to a later period, which the Allow Transaction Date Outside of Posting Period preference can permit, it also stays out of that day's balance sheet. And an aging built from each invoice's amount unpaid today drops anything paid since the as-of date, so it shrinks every day collections come in. NetSuite's A/R Aging Detail report shows transactions based on the date they are closed, so it keeps an item paid after the as-of date.
Does currency revaluation change the aging?
It changes the ledger. Month-end revaluation restates each open foreign-currency receivable at the exchange rate on the last day of the period and posts the difference as unrealized gain or loss. Oracle's documentation says entity balances and A/R reports convert foreign-currency balances to base currency using the exchange rates on the transactions, so the aging still carries the invoice at its own rate. The gap is the Gain/Loss on that period's revaluation record, invoice by invoice.

← All notes

Push the Frontier

Work alongside our team to establish your first operational capabilities, built around the problems that matter most to your business.

Explore the platformTalk to Frontier
FrontierERP

Set a new standard for how businesses operate.

Platform
Solutions
Resources
Company
© 2026 Frontier ERP, Inc.PrivacyTerms