Receivables Operating-State Benchmark: measuring what an ageing view cannot see

An ageing view and an operating-state view are both descriptions of the same open invoice. They differ in which fields they hold, and therefore in which questions they can answer at all. Both are defined here before anything is counted, because a benchmark that defines its instruments after seeing the data is not measuring anything.

Across the 60 invoices the ageing view answers none of the four questions and the operating-state view answers all four. That is not a finding. It is a restatement of what each view contains, and it would hold for any ledger, real or constructed. It is stated here so it is not mistaken for a result later.

Each invoice was given an operating-state class: the four answers, in order, as a single label — for example committed / no / no / yes for an invoice with a committed date, nothing blocking it, no decision needed and a balance that is collectable as stated. The rubric permits 48 such labels, some of which are logically impossible; the ledger exhibits 9 distinct classes, which is a modest spread and is already enough to make the point.

Working: bucket = 0–30, 31–60, 61–90, 90+ by days past due. Class = Q1/Q2/Q3/Q4 as defined above. “Materially different” means the class labels differ, so at least one of the four answers differs. Near-twin means the same bucket and balances within 15% of the larger. Synthetic ledger — constructed data, not client data.

Selection rule, applied mechanically to the ledger: every invoice in the 31–60 bucket with a balance between USD 9,000 and USD 10,000. That returns 5 invoices, spread across just 6.5% of balance and 8 days of age. On any ageing report they are one row repeated 5 times. They require 5 different next actions, and four of the five would be actively wasted effort if the fifth were applied to all of them.

Synthetic ledger — constructed data, not client data.

The consequences of treating them alike are not symmetrical. A reminder sent on the invoice already committed for Friday costs a little goodwill. A reminder on the disputed invoice is worse than nothing, because it answers a commercial question with an administrative act. A reminder on the invoice already paid three weeks ago is the one that ends a customer relationship, and it is entirely self-inflicted: the money is in the bank and nobody allocated it.

Each invoice was assigned exactly one required next action by a published precedence: Decide if an owner decision is needed; otherwise Fix if the balance is not collectable as stated; otherwise Ask if something specific is blocking the customer; otherwise Wait if a date is credibly expected; otherwise Chase. The precedence is a convention, stated so it can be argued with, and it is applied identically to all 60 invoices.

Synthetic ledger — constructed data, not client data.

Three results follow from that table and the ageing sort:

Measure 5: what the stated total is worth. An ageing report totals USD 582,280. Reading down the reconciliation state changes that figure twice over, and in different ways.

Composition of the 37,350 not collectable as stated: Cash already received, never allocated — 4 invoices, 22,000 · Credit note agreed, never applied — 2 invoices, 1,960 · Duplicate raised for the same work — 2 invoices, 8,500 · Standing deduction never modelled — 3 invoices, 4,890. Disputed balances are held separately and deliberately: a dispute makes an amount undetermined, not uncollectable. Synthetic ledger — constructed data, not client data.

The disputed share is the honest one to sit with. In this constructed ledger 13.3% of the stated total is neither collectable nor written off — it is unresolved, and only the business can move it. An ageing view reports that money as simply late. It is the same boundary the month-end exception map codes as a contested balance — a category no volume of follow-up can clear.

Corpus. A synthetic ledger of 60 open invoices across 18 accounts, one notional currency, stated total USD 582,280, published in full below. Synthetic and constructed by the author. Not sampled, not anonymised, not derived from a real business, not a market study. At Par has no customers and no client data exists to draw on.

Rubric. Four questions (a credibly expected date, a blocker, an owner decision, collectability as stated), each with a fixed set of permitted answers, applied identically to every invoice from each view. One required next action per invoice, assigned by a published precedence: Decide, then Fix, then Ask, then Wait, then Chase. Ageing buckets are 0–30, 31–60, 61–90 and 90+ days past due.

What was measured. Informational difference only: how many distinct operating states each ageing bucket contains; how many invoices are indistinguishable under ageing and materially different in state, at bucket level and at bucket-plus-size level; the distribution of required next actions; the composition of the ten oldest balances; where owner decisions fall in an age-ranked list; and how much of the stated total is not collectable as stated or undetermined. Version 1, 29 July 2026.

Reproducibility. The complete ledger follows, with each invoice’s bucket, balance, operating-state class and required action as computed. Every number on this page is derived from these 60 rows by the rules above — nothing is typed in by hand.

Synthetic ledger — constructed data, not client data. Cite as: At Par, Receivables Operating-State Benchmark v1 (29 July 2026), synthetic corpus of 60 invoices.

At Par maintains the operating state described here as part of ordinary bookkeeping, not as a separate collections product: every open invoice carries an owner, a last and next action, any commitment with the person who gave it, whether that commitment held, dispute status kept apart from collection status, and a reconciliation state so a balance already settled in cash stops being chased. A qualified accountant (ACCA) is accountable for the work.

That sits inside bookkeeping and month-end close and feeds management reporting, so the receivables position in the report is the one being worked. The decision about which parts of a receivables process can be handed over at all is a separate question, covered in the guide to accounts receivable outsourcing. Why the ageing instrument itself cannot answer the arrival question is set out in why an ageing report does not tell you when cash will arrive, and the invoice follow-up health check runs the same diagnostic on your own process in the browser.

More on original research

All guides →