Invoice aging explained: Current, 1–30, 31–60, 61–90 and 90+ days
Aging turns a long list of unpaid invoices into a simple question: how long has each remaining balance been past due? This guide shows how the common buckets work and how to use them without turning a spreadsheet into accounting software.
Published Sep 20, 2026 · Free guide · No signup required
What is invoice aging?
Invoice aging is a way to group unpaid receivables by how long they have been outstanding relative to the payment due date. Instead of reading every invoice one by one, you can scan a few buckets and see where older balances are accumulating.
For a simple operational tracker, the starting logic is:
If As-of Date ≤ Due Date → Current
If As-of Date > Due Date → calculate Days Overdue and assign an aging bucket
Why the due date matters more than the invoice date
An invoice can be 40 days old without being overdue if the agreed payment term has not expired. For example, an invoice issued September 1 with a due date of October 1 is still Current on September 25. Aging from the invoice date would incorrectly make it look late.
That is why an operational aging view normally compares the date you are reviewing the account with the invoice due date.
What the common aging buckets mean
Current
The invoice still has an unpaid balance, but the due date has not passed. In this guide, an invoice due today is also Current.
1–30 days overdue
The invoice is between 1 and 30 days past due. This is often the first overdue bucket a small business reviews for routine follow-up.
31–60 days overdue
The unpaid balance is more than 30 days past due. At this stage, it is useful to confirm previous communication, any payment promises and the next review date.
61–90 days overdue
The balance is between 61 and 90 days past due. The purpose of the bucket is visibility: it helps older unresolved balances stand out from newer ones.
90+ days overdue
The remaining balance is more than 90 days past due. This bucket says nothing by itself about what action is legally or commercially appropriate; it simply identifies the age of the unpaid balance.
Worked examples
How partial payments affect aging
A partial payment changes the amount still exposed, not automatically the age. Suppose an invoice was originally $1,200, the client has paid $700, and $500 remains. If that invoice is 18 days past due, the operational aging view is $500 in the 1–30 day bucket.
This is one reason a separate payment log is useful. The original invoice amount stays intact, each payment is recorded separately, and the remaining balance is what the aging view needs to classify.
What happens when an invoice is paid?
Once the remaining balance reaches zero, the invoice should no longer contribute to unpaid aging totals. You may keep it in the invoice history as Paid, but it should not continue appearing as overdue just because its old due date remains in the record.
Five common aging mistakes
- Aging from invoice date instead of due date. This can make valid payment terms look overdue.
- Aging the original invoice amount after partial payment. The remaining unpaid amount is the useful exposure for an operational aging view.
- Leaving paid invoices in overdue totals. Zero balance should override old due dates.
- Using today’s date in one place and a reporting date somewhere else. Pick one clear as-of date for a review.
- Treating the bucket as the action. Aging tells you age, not what message, fee or collection action is appropriate.
Turn aging into a weekly review
Aging becomes useful when it supports a repeatable routine. Once a week, update payments, review balances, sort by aging, check promised payment dates and assign the next follow-up date. The goal is to leave every open invoice with a clear status and next review point.
Try it with one invoice
Use the free Invoice Aging Calculator with a due date, as-of date and remaining balance. It returns the days overdue and common aging bucket without requiring an account.
Build the underlying system first
If your invoices and payments are still mixed together in one table, read How to Track Unpaid Invoices and Partial Payments in Excel. That guide explains the invoice log, payment log, remaining balance and next follow-up date before you add aging.
When a ready-made workbook can save time
If you already understand the workflow but do not want to build the formulas and views yourself, you can inspect the Invoice & Payment Follow-Up Tracker. The product page shows the real workbook preview, two included Excel files, seven tabs and the boundaries of what the workbook does and does not do.
Quick questions
Is 30 days overdue the same as the 31–60 bucket?
No. In this guide, 30 days overdue is still in 1–30. The 31–60 bucket begins at 31 days overdue.
Is 90 days overdue in the 90+ bucket?
In this guide, 90 days is still in 61–90. The 90+ bucket begins after 90 days. Your accounting system may use a different convention, so follow the rule used by your source of truth.
Can I use aging to decide when to charge a late fee?
No. Aging can identify how late an unpaid balance is, but fees and collection actions depend on agreements and applicable rules.
General operational guidance only. This page is not accounting, tax, legal, lending or collections advice.