Analytics Catalog/Workday/Financials/Customer accounts/AR aging
Explore the catalogModulesCustomer accountsCollections worklistBad-debt reserve
Workday · Financials · Report

What to chase first, honestly

Every aging answers chase-what-first, and most answer on the wrong clock. This one ages 73 open invoices on the due date, totals to the roll-forward’s 5,700,000.00 exactly, and hands its past-due buckets straight to collections and the reserve.

RuleAge open receivables on the due date, as of a stated date, from stored open invoices, reconciling the total to the roll-forward’s closing.
Neverage on invoice date and call it collections priority. What matters for chasing is what is overdue, and invoice-date aging buries it.
Open invoices, stored as of 31 May Aged on due date the chasing clock One total the balance, bucketed
Aging answers chase-what-first. The due date is the clock, and the total must be the balance, always.
◆ Open receivables, 31 May73 invoices, aged on the due date.
BucketInvoicesAmount
Not yet due443,912,000.00
1 to 30 days past due181,243,500.00
31 to 60 days past due7386,300.00
Over 60 days past due4158,200.00
Open receivables735,700,000.00

The total is the roll-forward’s closing to the cent, on the stated due-date basis, and the past-due buckets feed the collections worklist directly. The reserve prices the same buckets; one table, three consumers, zero drift. Sample values are illustrative, never client data.

◆ The basis, stateddue date, for the same reason as payables.

Invoice-date aging measures how long paper existed; due-date aging measures what is actually late. The payables mirror states the same rule from the paying side. Both pages join the as-of family: stored open items, any past date, the same answer twice.

◆ The owned answeropen invoices stored daily, the total pinned.

Open invoices are stored per day on the customer star, so as-of aging is a filter, the basis is a visible column choice, and the total pins to the roll-forward nightly.

Use case
Problem
Aging reports age on invoice date, drift from the ledger, and answer only today, so collections chase the wrong accounts and the reserve argues with the aging.
What we build
Due-date aging over stored daily open invoices, as of any date, pinned to the roll-forward, feeding collections and the reserve from one table.
What you get
Chasing priority from the clock that matters, an aging the controller reconciles at a glance, and one bucket table that collections and the reserve both trust.
Does your aging match your receivables balance?
We build the due-date aging that pins to the balance every night.
Talk to us
Terms on this page
AR
Accounts receivable, the money customers owe.
due-date aging
Buckets by when payment was owed; the chasing clock.
open invoice
Billed, not yet fully collected, stored per day.
past due
The buckets that feed collections and the reserve.
the basis
Which date the buckets use; stated, never assumed.