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.
◆ Open receivables, 31 May73 invoices, aged on the due date.
| Bucket | Invoices | Amount |
|---|---|---|
| Not yet due | 44 | 3,912,000.00 |
| 1 to 30 days past due | 18 | 1,243,500.00 |
| 31 to 60 days past due | 7 | 386,300.00 |
| Over 60 days past due | 4 | 158,200.00 |
| Open receivables | 73 | 5,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.
- 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.