AR Aging 60+ Days, Oracle ERP Cloud

AR Aging 60+ Days is the share of your total Accounts Receivable balance that is 60 or more days past due. The single cleanest collections-health gauge, sourced from Oracle Receivables.

Metrics type: Key Metrics • Category: Ecommerce Platform

The percentage of your total Accounts Receivable balance that is 60 or more days past due. The single cleanest collections-health gauge, and a rising 60+ band foreshadows write-offs.

At a glance

AR Aging 60+ Days expresses, as a single percentage, how much of your open Accounts Receivable sits 60 or more days past due relative to the whole AR balance. It is the one number a Finance Controller can glance at to judge collections health: the further money slips past 60 days, the lower the probability it is ever collected, and the closer it sits to a write-off. The figure is sourced from Oracle Receivables and recomputed against the live subledger across every in-scope Business Unit.

What it counts	The open Accounts Receivable amount whose aging (measured from invoice due date) is 60 days or greater past due, divided by the total open AR balance, across every in-scope Business Unit and ledger. Numerator and denominator both come from unpaid and partially-paid Receivables transactions in Oracle Fusion Receivables.
Currency	Computed as a ratio so the headline is currency-neutral, but the underlying numerator and denominator are consolidated in the reporting ledger’s functional currency (typically USD or the parent legal entity’s currency) using Oracle’s GL Translation cadence before the ratio is taken.
Business Unit scope	Respects the dashboard’s selected Business Unit filter. By default rolls up every Business Unit the connected role can see across all primary ledgers.
Time window	30D vsP (default 30D vs the prior 30D), so you watch the band trend rather than read a single static snapshot.
Alert trigger	Fires when AR Aging 60+ Days exceeds 15% of the total AR balance.
Roles	owner, finance

Calculation

Calculated automatically from your Oracle ERP Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A US Fortune 500 omnichannel speciality retailer running Oracle ERP Cloud across three Business Units (US Retail Inc, UK Retail Plc, EU DTC NV) under two primary ledgers. The 30-day window covers 23 May 26 to 21 Jun 26. The reporting ledger is the US ledger (USD), so all bands below are shown after translation.

AR aging band	Open balance (USD)	Share of total AR
Current (not yet due)	$22,500,000	50.0%
1 to 30 days past due	$9,000,000	20.0%
31 to 60 days past due	$5,400,000	12.0%
61 to 90 days past due	$4,950,000	11.0%
90+ days past due	$3,150,000	7.0%
Total open AR	$45,000,000	100%
AR Aging 60+ Days (this card)	$8,100,000	18.0%

Five things to notice:

1. The 60+ band is the last two rows combined. $4.95M (61 to 90) plus$3.15M (90+) gives $8.1M, which is 18.0$45M total. The card reports the percentage; Vortex Mind retains the dollar value for drill-down.
2. 18.0% is above the 15% alert threshold, so the Nerve Centre fires. Last period read 13.2%, so the band crossed the line inside the 30D vsP window. This is exactly the move a Key Metrics collections card is meant to catch early.
3. Concentration matters more than the average. Drilling in, a single B2B wholesale account holds $2.6M of the 90+ bucket. One stuck customer is dragging the whole percentage. Pair this card with High-Value Overdue Invoices to see who.
4. Rising 60+ AR is a write-off leading indicator. Collection probability falls steeply past 90 days. A growing 90+ slice is the early warning the credit team needs before the controller has to book a bad-debt provision.
5. The denominator moves too. A surge of fresh invoicing late in the window inflates total AR and mathematically lowers the 60+ percentage even though no old invoice was collected. Always read the ratio with the absolute balance and the DSO trend in mind.

Sibling cards merchants should reference together

AR Aging 60+ Days is the headline collections gauge. Pair it with these to find the cause and the cash impact.

Card	Why pair it with AR Aging 60+ Days
Days Sales Outstanding	The time-based twin. DSO tells you how long cash takes to arrive; this card tells you how much of it has slipped into the danger band.
High-Value Overdue Invoices	Pinpoints the specific large invoices driving the 60+ band, so collections can prioritise.
A/R Aging Detail	The full bucket-by-bucket, customer-by-customer breakdown behind this single percentage.
AR Balance (live, by Business Unit)	The absolute denominator, sliced by Business Unit, so you can see where the aging concentrates.
Cash Collected	What you actually banked against what is owed. Falling collections with rising 60+ AR is the classic squeeze.
AP Aging 60+ Days	The payables mirror. Compare the two to read your net working-capital position.
Oracle Fusion Health Score	The composite roll-up that AR aging feeds into alongside other integrity signals.

Reconciling against Oracle ERP Cloud

Where to look in Oracle ERP Cloud:

The closest native equivalents in the Oracle Fusion UI are:

Navigator → Receivables → Reports → Aging by General Ledger Account / Aging - 4 Bucket Report Navigator → Receivables → Billing → Manage Transactions (transaction-level view of open invoices) Reports and Analytics → OTBI → Financials → Receivables Aging Real Time Subject Area

The Receivables Aging report grouped into your standard buckets should reconcile to this card when you select the same as-of date and the same Business Unit scope. Sum the 61-to-90 and 90+ columns, divide by the report’s grand total, and you have the card’s percentage. Most Fortune 500 finance teams reproduce this in OTBI against the Receivables Aging Real Time Subject Area so they can pivot by customer and Business Unit.

Common mistakes when comparing against Oracle’s own reports:

• Aging by transaction date vs due date. Oracle’s aging reports can age from the transaction date or the due date. This card ages from the due date, so it reflects how far past due each invoice is, not how old it is.
• Disputed and on-account amounts. Invoices in dispute and unapplied on-account receipts can distort the open balance. A report that ignores on-account cash overstates net AR.
• Including or excluding credit memos. Open credit memos reduce net AR. A report listing only debit transactions overstates the denominator and skews the ratio downward.

Why our number may legitimately differ from Oracle’s reports:

Reason	Direction	Why
Aging basis (due date vs transaction date)	Either	The card ages from due date. An Oracle report run on transaction-date basis ages everything earlier and can inflate the 60+ band. Match the basis before comparing.
On-account and unapplied receipts	Card lower	Cash received but not yet applied reduces net AR in the card’s denominator. A report that ignores unapplied receipts shows a higher balance and a different ratio.
Business Unit and ledger scope	Either	A single-Business-Unit report will not match a consolidated card view. Always align scope with the dashboard filter.
FX translation timing	Small	The card translates foreign-currency invoices into the reporting currency before taking the ratio. A single-ledger-currency report can differ slightly on mixed-currency AR.
Subledger vs GL timing	Small	This card reads the Receivables subledger. A short backlog in Create Accounting can leave the GL trial balance momentarily out of step with the subledger aging.

Known limitations / merchant FAQs

Why is AR Aging 60+ Days a Key Metrics card when DSO already measures collections? Because they answer different questions. DSO is an average, and averages hide concentration. A healthy DSO can mask a single large customer slipping past 90 days. AR Aging 60+ Days exposes exactly that tail risk in one percentage, which is why it earns Key Metrics status as the cleanest single collections-health gauge.

Does the percentage age from the invoice date or the due date? From the due date, so the band reflects how far past due money is, not merely how old the invoice is. A Net-60 invoice is not “past due” until 60 days after its due date. Oracle’s aging reports can be set either way, so align the basis before reconciling.

Why did the percentage fall when collections did not improve? Because the denominator (total open AR) grew. A wave of fresh invoicing lowers the 60-plus share arithmetically even when no old invoice was collected. Read the ratio with the absolute AR balance and the DSO trend so you do not mistake dilution for improvement.

How does a rising 60+ band relate to bad-debt provisions? Collection probability drops sharply the longer an invoice sits past due. A growing 90+ slice is the leading indicator that auditors and the controller will soon expect a higher bad-debt provision. Catching the rise early, which the 30D vsP window is built for, gives the credit team time to act before a write-off is forced.

Are disputed invoices included? Yes, disputed invoices remain open AR and continue to age while the dispute is unresolved, so they sit in both the numerator and denominator. Resolving or crediting a long-running dispute is a common way a stubborn 90+ balance finally clears.

How fresh is the data? Vortex IQ reads the Oracle Fusion Receivables data through the Fusion REST API with a short cache, so the percentage reflects the AR state as of the last sync window. For a live intraday check, the native Receivables Aging report is always real-time.

Does this card tell me which customers are the problem? The headline is a single percentage, but Vortex Mind keeps the underlying detail. Pair this card with High-Value Overdue Invoices and A/R Aging Detail to drill from the percentage to the named accounts driving it.

---

Tracked live in Vortex IQ Nerve Centre

AR Aging 60+ Days is one of hundreds of KPI pulses Vortex IQ tracks across Oracle ERP Cloud and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.