Aged Payables
What you owe suppliers, bucketed by how late it is.
Details
aged payablesUploads
Your logo
A photo or picture
Goes on this page only. Drag it anywhere and pull its corner to resize it.
Your signature
Draw it with a finger, a mouse or a trackpad, and it goes on the page like a picture.
Pictures and signatures stay on this device. Nothing is uploaded to a server.
Red highlights mark what is still blank. Click anything on the page to change it. Your draft is kept on this device as you work.
This sheet is a working document. If you are redoing it every month, ledger software does the reconciliation for you and keeps the audit trail — that is the part a template cannot do.
As at [date]. Ageing is measured from each due date.
| Supplier | Bill | Amount | Due | Overdue by |
|---|---|---|---|---|
| [add one line per invoice] | ||||
| Total you owe | $ 0.00 |
| Ageing bucket | Amount | % of total |
|---|---|---|
| Not yet due | $ 0.00 | — |
| 1-30 days | $ 0.00 | — |
| 31-60 days | $ 0.00 | — |
| 61-90 days | $ 0.00 | — |
| Over 90 days | $ 0.00 | — |
| Total | $ 0.00 | — |
Nothing on this list is more than ninety days past due.
What is an Aged Payables?
An aged payables report lists every unpaid supplier invoice grouped by how long it has been outstanding — current, thirty days, sixty, ninety and beyond. It matters because without it, payment decisions get made by whoever chased hardest that morning. The report turns a mailbox full of statements into a ranked position, so you can see what is genuinely overdue, what is disputed and what is about to stop a supplier delivering.
Bookkeepers and finance teams run it before every payment run. Owners run it weekly to decide what can be paid from the cash available. Accountants run it at period end to check the payables balance and to identify what needs accruing. Lenders and investors ask for it during due diligence, and auditors use it when testing whether liabilities are complete. In each case the question is the same: what do we owe, to whom, and how late is it?
The ageing buckets are a convention rather than a rule; what is regulated is the payment side. Large United Kingdom companies report on their payment practices and performance. The EU late payment directive, as implemented in each member state, sets default payment periods for commercial transactions. In India, the MSMED Act sets a payment window for registered micro and small enterprise suppliers and requires disclosure of amounts due to them. Public-sector contracts in several countries carry prompt payment terms. Check whether any of your suppliers sit in a protected category before letting them age.
The report shows posted invoices only. It does not include costs incurred but not yet invoiced, which is what accruals are for, and it does not include committed purchase orders not yet received. It is not a cash flow forecast — it tells you what is owed, not when you will be able to pay it, and turning one into the other is a separate exercise. If it does not agree to the payables control account, the difference is a bookkeeping problem to resolve rather than a rounding issue to ignore.
What to put in an Aged Payables
These are the details this template asks for. Anything left blank is marked in red on the preview so you can see what is still missing.
| Field | What goes in it |
|---|---|
| Business name | For example: Barton Supply Co. |
| Your address | For example: Unit 7, Barton Road, Columbus, OH 43212 |
| As at date | Free text |
| Appointments | One per line: Date | Time | Who | Where | What for |
How to write an Aged Payables
Fix the as-at date and the ageing basis
Decide whether you are ageing by invoice date or by due date, and label the report accordingly. Ageing by invoice date on sixty-day terms makes a perfectly current supplier look two buckets late; ageing by due date shows genuine lateness. Whichever you choose, keep it consistent between periods, or the comparison from one month to the next means nothing.
Post everything before you run it
Enter outstanding purchase invoices, apply credit notes, allocate payments on account and clear supplier deposits. A report run over an incomplete ledger understates what you owe and produces a payment run that misses invoices sitting in somebody's drawer. Set a cut-off for invoice entry and run the report after it, not alongside it.
Show suppliers, buckets and a reconciled total
One row per supplier with the total balance, the amount in each bucket and the date of the oldest open item. Then agree the report total to the payables control account in the general ledger. A report that does not reconcile is not a report, and the moment to find the difference is now rather than during the audit.
Flag the exceptions in their own column
Mark items that are disputed, on hold pending a credit note, part of an agreed payment plan, or subject to a supplier's protected payment terms. Without those flags the oldest bucket reads as neglect, and the team chases invoices that are deliberately unpaid while missing the ones that are simply overdue.
Build the payment run and record approval
Work down in a stated order — statutory and tax deadlines, suppliers who have placed you on stop, contractual due dates, then everything else — and record who approved the run and when. That record is what protects the person releasing the payments and what an auditor will ask for when testing authorisation.
Common mistakes
- Running the report before month-end postings are complete, which understates liabilities and produces a payment run that omits invoices already received.
- Ageing by invoice date when suppliers are on sixty-day terms, so everything appears overdue and the report loses the attention of the people who should act on it.
- Leaving credit notes and payments on account unallocated, which makes suppliers look overdue when they have already been paid.
- Having no dispute flag, so a genuinely disputed invoice is paid in the routine run and whatever leverage you had in the dispute disappears.
- Letting the report drift out of agreement with the payables control account, which expands audit testing and calls the completeness of liabilities into question.
Frequently asked questions
What are the standard aged payables buckets?
Current, one to thirty days, thirty-one to sixty, sixty-one to ninety and over ninety is the most common layout, and most accounting systems default to it. The buckets are convention, not regulation, so if your suppliers are mostly on sixty-day terms it can be more useful to age against the due date or to add a bucket. Label whichever you choose.
What is the difference between aged payables and accounts payable?
Accounts payable is the balance — a single figure in the general ledger for everything you owe suppliers. Aged payables is the analysis behind it, broken down by supplier and by how long each item has been outstanding. One tells you the size of the liability, the other tells you which parts of it are about to cause a problem.
How often should I run an aged payables report?
Weekly if you are managing cash closely, and always immediately before a payment run and at each period end. Running it only at month end means supplier problems surface after they have already escalated. The report costs nothing to produce once the ledger is up to date, which is the real constraint on how often you can run it.
Why does my aged payables report not match the balance sheet?
The usual causes are journals posted directly to the payables control account instead of through the purchase ledger, unallocated payments or credit notes, transactions dated after the report's as-at date, and foreign currency revaluation. Work through them in that order. A persistent difference usually means the control account has been used as a posting destination by something that should never have touched it.
Should ageing be based on invoice date or due date?
Due date tells you what is actually late and is the more useful basis for deciding what to pay. Invoice date tells you how long items have been sitting in the ledger, which is useful at period end and for spotting stale balances. Many teams run both. What causes confusion is running one of them and describing it as the other.
This page explains general practice and is not legal advice. Requirements differ between countries and, in some cases, between states — check what applies where the document will be used.