Invoice aging reports: buckets, partial payments and a worked example
Build and read an accounts receivable aging report using due dates, unpaid balances and an as-of date. Understand aging buckets, partial payments, credits and follow-up priorities.
THE IDEA TO TAKE WITH YOU
An aging report groups the unpaid balance of each invoice by days past its due date at a specific point in time. Correct dates and correctly allocated payments matter more than the size of a bucket.
An invoice aging report answers two connected questions: how much remains unpaid, and how long has that amount been past its due date? It is a snapshot of outstanding invoices at a chosen date, not a history of every payment event.
For a freelancer, it can turn a folder of unpaid invoices into a manageable follow-up list. For an agency, it can show whether a cash shortfall is linked to one large overdue balance or many smaller invoices.
Use the invoice aging calculator to enter invoices or import a CSV, then export the bucket summary and invoice detail. The method below explains exactly how that report is constructed.
Choose the report date before entering balances
An aging report is always “as of” a date. A balance due on 15 September is 12 days overdue as of 27 September and 16 days overdue as of 1 October.
The payments and credits must refer to the same snapshot. If a client pays on 3 October, that payment should not reduce a report describing the balance on 30 September.
Our calculator takes cumulative payments and credits as inputs. It does not store their event dates or reconstruct a historical ledger. To create an earlier report, supply the figures as they stood on that earlier date.
Calculate the remaining balance for each invoice
Outstanding balance = original invoice total − allocated payments − allocated credits.
For an invoice of 1,200, payments of 500 and an agreed credit of 100 leave 600 outstanding. Age the 600 that remains, not the original 1,200.
Allocation is important. A payment on the customer’s account is not necessarily a payment against the invoice you are reviewing. Match references and records before subtracting it. A single payment covering multiple invoices must be allocated without counting the same money twice.
Keep each client and invoice-reference combination unique in the report. Duplicate rows can otherwise double the reported balance while still producing plausible-looking totals.
Age from the due date, not the issue date
The Ostro tool uses:
Days overdue = report date − due date, with a minimum of zero.
An invoice issued on 1 September and due on 1 October is not overdue on 27 September. It has existed for 26 days, but that is invoice age rather than days past due.
Some accounting reports use different conventions. Label the basis of your report so the reader understands which date starts the count. If the deadline is not yet clear, check the agreement and use the invoice due-date calculator to work through its date arithmetic.
Understand the bucket boundaries
| Bucket | Rule used by the calculator |
|---|---|
| Current / due today | Due date is today or later |
| 1–30 days | Between 1 and 30 days past due |
| 31–60 days | Between 31 and 60 days past due |
| 61–90 days | Between 61 and 90 days past due |
| 90+ days | 91 or more days past due |
The “90+” label is shorthand; the previous bucket includes day 90, so the last bucket begins on day 91. The calculation uses whole calendar dates, without daylight-saving adjustments or partial-day counts.
A positive unpaid invoice moves into a bucket based on its due date. A zero balance is settled. A negative balance is handled separately rather than being used to reduce the total of unrelated overdue invoices.
Follow a worked example
Consider this illustrative report as of 27 September 2026, with all invoices in USD:
| Invoice | Due date | Total | Payments | Credits | Remaining | Bucket |
|---|---|---|---|---|---|---|
| INV-001 | 15 June 2026 | 1,000 | 250 | 0 | 750 | 90+ days |
| INV-002 | 28 August 2026 | 600 | 100 | 50 | 450 | 1–30 days |
| INV-003 | 1 October 2026 | 800 | 0 | 0 | 800 | Current |
The total outstanding is USD 2,000. Of that, USD 1,200 is overdue. The 31–60 and 61–90 buckets are empty; the current bucket contains USD 800.
The report does not imply that the oldest invoice is uncollectible or that the current invoice will be paid on time. It gives a consistent starting point for checking the circumstances of each balance.
Investigate negative balances separately
An invoice of 400 with recorded payments of 450 produces a negative balance of 50. Possible explanations include an overpayment, a payment allocated to the wrong invoice or a duplicate entry.
Automatically subtracting that 50 from another customer’s overdue invoice would obscure both issues. The calculator reports it as an overapplied amount for review and leaves positive outstanding balances intact.
Likewise, do not treat an aging bucket as an automatic credit-loss provision or write-off instruction. Accounting treatment and collection decisions require information that the bucket alone does not contain.
Keep currencies separate
USD 1,000 and EUR 1,000 cannot be added into a meaningful “2,000 outstanding” balance without a defined conversion basis. The calculator therefore accepts one currency per report and rejects imported rows in another currency.
Prepare separate reports for each currency. If you need a consolidated financial view, translate using an explicit rate, date and accounting method appropriate to that purpose. Retain the original currency amounts so the client’s obligation remains clear.
The currency selector in a browser tool changes formatting and decimal precision. It does not convert money. Our guide to foreign-currency invoice accounting explains why invoice values and converted reporting values need separate records.
Turn the report into a practical follow-up list
Before contacting a client, check whether the invoice reached the correct contact, the due date is agreed, a purchase-order reference is missing, work is disputed or a payment has arrived without being matched.
Then send a message that names the invoice, remaining balance and due date, and asks for a payment date or clarification. The payment reminder template and generator prepares wording for upcoming, due-today and overdue invoices. It does not send messages on your behalf.
For repeated follow-up, keep an action note alongside the report: person contacted, response, promised payment date and next review date. Download the unpaid-invoice tracker if an editable spreadsheet better fits that ongoing workflow.
Finally, distinguish the report from a statement of account. A statement shows account activity and a balance over a period; an aging report groups the remaining invoice balances by time past due. They answer complementary questions and should reconcile when they use the same underlying records.
Explore the linked sources, practical tools and related guides for more on this topic.
Explore more payment guides ↗