Skip to main content
Metrics type: Supporting MetricsCategory: Ecommerce Platform
A/R balance bucketed by 0-30 / 31-60 / 61-90 / 91-120 / 120+ days. Cash-flow telemetry.

At a glance

AR balance bucketed by Customer Ledger Entry due-date age: 0-30 / 31-60 / 61-90 / 91-120 / 120+ days. Cash-flow telemetry, aggregated headline alongside the AR Aging Buckets per-customer card.

Calculation

Calculated automatically from your Microsoft Dynamics 365 data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

US wholesale electronics distributor, $90M revenue, snapshot 14 Apr 26. Three observations:
  1. 18% of AR is past 60 days. Just below the 30% alert threshold, but trending up from 14% three months ago.
  2. 120+ bucket ($360K) needs write-down review. UK FRS 102 / US GAAP allowance for doubtful debts policies typically require provisions on AR > 120 days.
  3. Concentration check: 3 customers carry $940K of the 60+ buckets. Pair with AR Aging Buckets for the per-customer drill.

Sibling cards merchants should reference together

Reconciling against the vendor’s own dashboard

Where to look in Business Central:
Reports > Finance > Customer > Aged Accounts Receivable (definitive) Power BI > Cash Flow content pack > Receivables Aging tile Customer List > Statistics FlowFields
The Aged Accounts Receivable report matches this card to within rounding when run for the same Aging Periods (1M, 2M, 3M default). Why our buckets may legitimately differ: Cross-connector reconciliation: This card has no commerce-side counterpart. AR aging is BC-internal.

Known limitations / merchant FAQs

What is healthy aging distribution? Net-30 B2B: 70% in current, 20% in 31-60, < 10% in 61+. Net-60: shifted right by 30 days. Anything > 30% in 60+ is a collection problem. Aging by Due Date vs Posting Date: which does the card use? Due Date by default, since that is what determines whether an invoice is overdue. Configurable to Posting Date for merchants who track invoice issuance pace separately. Does the card include unposted Sales Invoices? No. Only posted Invoices (Customer Ledger Entries) count. Draft / unposted Invoices are not yet AR. How does this interact with DSO? DSO blends all buckets into one number; this card shows the distribution. Two merchants can have the same DSO with different aging shapes; the shape matters for action. Power BI parity? Power BI’s Aging Receivables tile uses the same buckets per Company. Multi-Company consolidation requires custom DAX. Sales Credit Memos: how are they handled? SCMs that have not been applied against an invoice show as negative AR. The card excludes them from the buckets (they are not aged debts). Concentration risk: how to see which customers drive the buckets? Drill via AR Aging Buckets per-customer card. Does this card include intercompany invoices? By default yes; can be excluded by Customer No. range in field map. What about Payments on account? Unapplied Payments reduce the customer’s AR balance and net against the buckets. The card uses net Customer Ledger Entry remaining amount.

Tracked live in Vortex IQ Nerve Centre

Invoice Aging Summary is one of hundreds of KPI pulses Vortex IQ tracks across Microsoft Dynamics 365 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.