The Payables Report That Aged the Orders
A payables ageing built from purchase orders measures when you ordered, not when you owe. It ages commitments as debt, misses every bill raised without an order, and throws away the one date your supplier actually agreed to. Ours did exactly that, until we rebuilt it on approved bills.
The month-end pack goes to the finance committee on a Thursday. On the payables page, the ninety-plus column is the largest on the sheet: 60,000 owed for more than three months. A committee member asks the obvious question — who are we three months late paying, and why has nobody called us? The finance lead does not know. She goes looking, and finds that the 60,000 is a single purchase order for shelving, raised in March for a warehouse fit-out, expected in April, still not delivered. Nobody has invoiced anything. Nothing is owed. The report aged an order.
Further down there is a second problem she does not notice that day. The landlord’s invoice for the quarter’s rent is two weeks overdue, and it is not on the report at all. Rent is never ordered. There was no purchase order for the report to age, so the one bill the business genuinely was late on did not exist as far as the ageing was concerned.
That was our payables ageing, for longer than we would like. It read open purchase orders and bucketed them by expected delivery date. It looked like a payables ageing, it had the right five columns, and it answered a different question from the one on its title.
Ordering is not owing
A purchase order is a promise you make. It says you intend to buy these things at this price, and it is the right document to control spending against — budgets, approvals and three-way matching all start there. But in almost every supplier relationship, nothing is owed on an order until the goods or service arrive and the supplier sends an invoice. The invoice is the claim. Its date and the terms behind it decide when payment falls due.
Build an ageing on the order and three things go wrong at once.
Aged from purchase orders
- The clock starts at an order or delivery date you chose, not one the supplier agreed to.
- An undelivered, uninvoiced order sits in the overdue columns as though you were in arrears.
- Rent, utilities, subscriptions and services bought without an order never appear.
- The amount is what you ordered, not what was delivered, billed and still unpaid.
- A partial payment or a returned delivery leaves the figure where it was.
Aged from approved supplier bills
- The clock starts at the due date on the supplier’s invoice.
- An order with nothing billed is shown as a commitment, beside the debt, not inside it.
- Every approved bill counts, whether or not an order sits behind it.
- The amount is the bill’s remaining balance after payments and credits.
- Each bill ages in its own currency.
The first column is not a lazy report. It is usually a report built before the system had supplier bills at all, when the order was the only payables-shaped record available. That is how ours came about. The trouble is that it keeps its title after the business it describes has moved on.
An ageing built on orders measures your purchasing calendar. An ageing built on bills measures your obligations. Only one of them should be in a finance pack.
What the report reads now
The payables half of the Aging Report — on the web, in the API and in the mobile app — is now built from one place, and it reads supplier bills. A bill counts when it is approved or partially paid and still has a balance. Drafts are left out, and so are bills a supplier has submitted through the portal and nobody has reviewed: until someone with the authority to approve has looked at an invoice, it is a claim, not an agreed debt. Rejected and cancelled bills are out for the obvious reason. Approval itself is a two-person act by default — the person who keyed a bill cannot approve it while someone else in the workspace can, which the post on keying and approving bills explains.
Each bill is placed by its own due date. A bill due today, or later, is current. One due yesterday is one day overdue and lands in the 1–30 column; then 31–60, 61–90, and ninety-plus. The figure placed is the remaining balance, which the system recomputes from the bill rather than trusting a running total: the bill’s total, less any withholding tax deducted on it (that part is owed to the tax authority, not the supplier), less payments that have actually completed, less debit notes applied to it. Pay half a bill and half of it stays in its column. Apply a debit note for a return and the balance drops by exactly that much.
Every currency gets its own row of buckets, and they are never added together. A bill in one currency and a bill in another are two separate obligations with two separate settlement risks; summing them gives a number that means nothing. The receivables half of the same report learned that lesson first, and the post on that total covers why we group rather than convert.
A worked month-end
Here is the same warehouse business at 30 June, once the report reads bills. Five items are open; only four of them are debts.
| Item | Due | Balance | Days overdue | Column |
|---|---|---|---|---|
| Packaging bill, 12,000, 5,000 paid | 1 June | 7,000 | 29 | 1–30 |
| Haulage bill, 8,400, 420 withheld | 9 April | 7,980 | 82 | 61–90 |
| Rent bill, no order behind it | 15 June | 4,500 | 15 | 1–30 |
| Cleaning bill, 9,000, 1,000 debit note applied | 20 July | 8,000 | 0 | Current |
| Shelving order, nothing delivered or billed | none | 60,000 | — | Ordered, not yet billed |
Payables at 30 June, one currency
Beside the buckets: 60,000 on one open order not yet billed — a commitment, not a debt.
Run the same month through the old logic and the committee sees a different business: 60,000 in the ninety-plus column for shelving nobody has delivered and the rent invoice absent. The one genuinely late payment — the haulier, 82 days past due — would be hidden behind the shelving.
Why commitments still belong on the page
Taking open orders out of the buckets does not mean pretending they are not there. Cash planning needs both numbers: what you owe, and what you have promised to spend. So the report keeps a line beside the payables buckets — open orders with no approved bill against them, counted and totalled, with a note that they are not owed until the supplier bills. An order that is paid or cancelled drops off. The moment an approved bill exists against an order, the bill takes over and the order leaves that line.
For older mobile app builds
The API used to return overdue purchase orders under a key of their own. Phones that have not updated still look for it, so the response keeps that key and sends it empty; current builds read the overdue bills and the unbilled-orders figure instead. A changed meaning under an old name would have been worse than an empty list: an old app would have shown bills labelled as orders.
Where the due date comes from
Everything above rests on the due date, so it is worth knowing how one gets onto a bill. When a bill is captured — by your team, or by the supplier through the portal — the due date is whatever is entered from the supplier’s invoice. If it is left blank, the system sets it thirty days after the bill date. A due date earlier than the bill date is refused.
That thirty-day default is the place to be careful. A supplier on seven-day terms whose bill is keyed without a due date will look comfortably current for three weeks after you are already late; one on sixty-day terms will look overdue a month early. Today the supplier record does not carry its own terms to fill the date in, so the habit that matters is typing the due date printed on the invoice. It takes four seconds at capture and decides which column the bill sits in for its whole life.
Before you trust a payables ageing — any system’s
- Pick the largest figure in the oldest column and trace it to a supplier invoice. If it traces to an order, the report is ageing commitments.
- Find a bill you paid half of last month. Its remaining half should be in one column, not the full amount.
- Find your rent or a utility bill. If it is not on the report, the report only sees ordered spend.
- Find a supplier on short terms and check the due date on its latest bill against the invoice itself.
- Look for a single total across currencies. If there is one and it does not say how it was converted, it is not a number.
- Ask what the report treats as approved. An unreviewed supplier submission is not yet a debt.
The ageing and the ledger will not always agree
One consequence of building on bills catches accountants out, so it is better said plainly. When goods arrive against a purchase order and the receipt is approved, the system books the liability then — inventory up, accounts payable up — because you owe for goods you have accepted whether or not the paperwork has followed. The bill, when it comes, posts nothing further for those goods; it becomes the document that is matched and paid. So between delivery and invoice, the payables account in the ledger includes goods received and not yet billed, and the ageing does not, because there is no due date to age them by.
That is the correct behaviour for both reports, and the difference between them is real information: it is roughly your received-not-invoiced position. But it means the ageing total and the payables account balance are not expected to match at month end, and anyone reconciling them should look at recent receipts against orders before looking for an error.
A large figure sits in an old column
Open the bill and check its due date
Most stale balances are bills keyed with the default date or a payment recorded against the wrong bill, not genuine arrears.
The commitments line is large
Chase the deliveries, not the payments
These are orders nobody has billed. The question for them is whether the goods are coming, and whether the order should be cancelled.
The ageing is lower than the ledger
Look at receipts not yet billed
Goods accepted against an order sit in the payables account before an invoice arrives. Ask the supplier for the bill.
A supplier has returned goods to credit
Apply the debit note to the bill
Until it is applied the bill shows its full balance. A payment run will net it at payment time, but the ageing reads the bill as it stands.
Where to find it, and who sees it
The payables section sits on the Aging Report in the accounting module, beside receivables, and in the mobile app’s accounting screens. Both are behind the same permission, view aging report, so someone who can see one can see the other. The overdue bills table lists the most overdue first and is paged; a bill number links through to the bill for anyone who can view supplier bills. The supplier bills list carries its own overdue filter if you would rather work from the bills themselves. The supplier bills and payables page covers capture, approval and payment runs in full.
An ageing you can date, file and reconcile
Bill-based ageing per currency, with commitments beside it, is in place on the web, the API and the mobile app. The next pieces build on the same bills and the same due dates.
Payables ageing as at a chosen date
The same buckets reconstructed for the last day of a past month, so the committee pack and the audit file show what was owed then, not what is owed on the morning you print it.
Ageing export to a spreadsheet
Every open bill with its supplier, due date, days overdue, column and currency, in one file for the reviewer.
Supplier payment terms on the supplier record
Seven, thirty or sixty days set once per supplier and used to fill a bill’s due date when the invoice is keyed.
Tell us how your month-end pack is put together and we will come back with a written scope and cost.
Scope payables reportingWhat AWRA OpsHub does today
- Payables ageing built from approved and partially paid supplier bills with a balance, on the web Aging Report, in the API and in the mobile app, from one shared calculation.
- Buckets by each bill’s own due date: current (due today or later), 1–30, 31–60, 61–90 and ninety-plus days overdue.
- Balances net of completed payments, applied debit notes and withholding tax deducted on the bill.
- One row of buckets per currency, never summed across currencies.
- Bills raised without a purchase order — rent, utilities, services — aged alongside bills against orders.
- Open purchase orders with no approved bill reported beside the buckets as a commitment, not as debt.
- An overdue bills list, most overdue first, linking to each bill for people who can view supplier bills.
- The old overdue-orders field kept, empty, in the API response for older app builds.
- Access through the view aging report permission on both web and API.
More we can add to your workspace
- Payables ageing as at a past date. The buckets rebuilt for a chosen month end rather than for today.
- Export of the payables ageing. A spreadsheet of every open bill with its column, currency and days overdue.
- Supplier payment terms on the supplier record. A due date filled from each supplier’s own terms in place of the thirty-day default.
- Open debit notes shown against a supplier’s aged balance. Credit already owed back to you set beside the bills before it is applied.
- Commitments split by currency. The ordered-not-billed figure grouped per currency, the way the buckets already are.
- The unbilled remainder of a partly billed order. An order billed in instalments kept on the commitments line for the part still to be invoiced.
- Every currency’s payables buckets in the mobile app. The per-currency rows the API already sends, drawn on the phone as they are on the web.
- A tie-out from the ageing total to the payables account. Goods received and not yet billed shown as the line that reconciles the two.
Where we point you to a specialist
- We do not add balances in different currencies into one figure without saying which rate and which date converted them. A total that hides that choice is a number nobody can check.
- Which supplier to pay first, and whether to pay early or hold to terms, is a treasury decision about cash and relationships. The report shows what is owed and when; the order of payment stays with you.
Our position
A payables ageing should age debts, and a debt starts with an approved supplier invoice and its due date. Keep orders on the page as commitments, because cash planning needs them, but never in the overdue columns. Type the due date from the invoice rather than trusting a default, apply credits to the bills they belong to, and expect the ageing and the ledger to differ by what you have received and not yet been billed for.
Age what you owe
Capture supplier bills with their due dates, approve them with a second pair of eyes, and the Aging Report shows what you owe, by currency, in the column the supplier’s terms put it.
Supplier bills and payablesFrequently asked questions
Why should a payables ageing use supplier bills rather than purchase orders?
Because nothing is owed on an order until the supplier delivers and invoices. An ageing built from orders puts undelivered, uninvoiced orders in the overdue columns, leaves out every bill raised without an order, and starts the clock on a date the supplier never agreed to.
Which bills does the AWRA OpsHub payables ageing include?
Supplier bills that are approved or partially paid and still have a balance. Drafts, unreviewed supplier submissions, rejected and cancelled bills are left out.
What are the ageing buckets?
Current for a bill due today or later, then 1 to 30, 31 to 60, 61 to 90 and more than 90 days past the bill’s due date.
What happens to purchase orders that have not been billed?
They are shown beside the buckets as orders not yet billed, with a count and a total. They are a commitment, not a debt, so they are kept out of the overdue columns. Once an approved bill exists against an order, the bill is aged instead.
What if a bill is entered without a due date?
The system sets the due date thirty days after the bill date. Typing the due date printed on the supplier’s invoice is the reliable habit, because the due date decides which column the bill sits in.
Why does the ageing total differ from the payables account in the ledger?
Goods received against a purchase order are booked as a liability when the receipt is approved, before the supplier’s invoice arrives. The ageing only includes approved bills, so the difference is broadly what has been received and not yet billed.
