What counts as "current" on an invoice aging report?

Current means the invoice is within its payment terms, not yet due. If you sent a Net 10 invoice today, it is current for the next 10 days. On day 11, it moves to the 1-30 bucket. This distinction matters because many solo operators treat all unpaid invoices as a problem, which leads to premature collection follow-up that can irritate clients who are simply processing payment on a normal timeline. The aging report forces precision: only invoices past their due date require action. Current invoices require monitoring, not intervention. Knowing the difference prevents the uncomfortable experience of chasing a client who was planning to pay on time, and the relationship damage that kind of over-eagerness causes.

How is an invoice aging report different from just checking who owes me money?

Checking who owes you money tells you the total. An aging report tells you the urgency. Two invoices of equal dollar amounts, one 15 days past due, one 75 days past due, require completely different responses. The 15-day invoice needs a polite reminder. The 75-day invoice needs a direct conversation, a payment plan offer, or a collections decision. Without age-based grouping, both look the same in a simple balance view. The aging report also reveals trends that a balance view hides: a client who appears once in the 1-30 bucket is different from a client who has appeared in the 31-60 bucket for three consecutive months. One is a delay; the other is a pattern.

How often should I actually run this report?

Monthly is the minimum, ideally on the same date each month, such as the first or last business day. More frequent review (weekly) is worth the time if you carry more than 5 open invoices at a time, if your average invoice is above $3,000, or if you have had a collection problem in the past 12 months. The key is consistency over frequency. A monthly report run on the same date creates a rhythm that catches problems before they age into the 61-90 bucket. Most solo operators who run aging reports monthly report that they almost never have 90+ day invoices, not because clients pay faster, but because the regular review triggers intervention while the relationship is still healthy enough to fix it.

At what point should I stop internal collection and involve a third party?

The standard threshold is 90 days past due with no payment plan agreement and no credible communication from the client. Before reaching that point, you should have sent at least three escalating communications: a polite reminder at 1-15 days past due, a direct email at 30 days with payment plan offer, and a formal notice at 60 days stating the next steps. If a client has made zero contact and zero payment by day 90, a collections agency or small claims filing becomes a rational option. Collections agencies typically charge 25-50% of recovered amounts, so the calculus depends on invoice size. For invoices under $1,000, small claims is often more cost-effective. For larger amounts, an attorney's demand letter ($150-300) often prompts payment without full collections involvement.

The "Invoice Aging Report" Every Solo Should Run Monthly

The most expensive billing mistake a solo operator makes is treating all unpaid invoices the same. A 12-day-old invoice and a 75-day-old invoice look identical in a “money owed” summary, but they are completely different situations requiring completely different responses. The invoice aging report separates them and tells you exactly what to do with each.

The Five Buckets

The aging report divides all unpaid invoices into five age groups based on days past due date, not days since sent.

Current, Invoice is within its payment terms. No action required. Monitoring only.

1-30 days past due, Invoice missed its due date. Send a polite reminder. Most of these resolve without friction.

31-60 days past due, Invoice is significantly late. Direct communication required. Offer a payment plan if appropriate.

61-90 days past due, Invoice is at risk. Escalate tone. Pause new work if ongoing. Set a deadline for resolution.

90+ days past due, Invoice is in collections territory. Third-party involvement or legal options are on the table.

Each bucket has a different emotional register and a different script. The bucket tells you which script to use.

How to Build the Report in 15 Minutes

You do not need accounting software to run an aging report. A spreadsheet with six columns, client name, invoice number, invoice date, due date, amount, and days past due, is sufficient.

The setup:

List every open invoice (sent but unpaid)
Calculate days past due for each: =TODAY() - due_date
Add a bucket column: =IF(days<0,"Current",IF(days<=30,"1-30",IF(days<=60,"31-60",IF(days<=90,"61-90","90+"))))
Sort by bucket, then by amount descending within each bucket

Total build time for a new spreadsheet: 20 minutes. Monthly update time: 5-10 minutes.

Sort within each bucket by amount descending, your largest at-risk invoices surface first, which is where your collection effort should concentrate.

The Collection Action Matrix

The value of the aging report is the action it prescribes. Each bucket has a default action:

Current, No action. Add a note to check next cycle.

1-30, Send a one-line reminder email: “Hi [Name], following up on invoice [#] for [amount], due [date]. Let me know if you need anything to process this.” Friendly, zero accusation.

31-60, Email with a direct subject line: “Invoice [#], [amount], 30+ days past due.” Acknowledge that payment may have slipped. Offer a payment plan for amounts over $2,000. Ask for a payment date commitment.

61-90, Phone call or video message in addition to email. State plainly that the invoice needs to be resolved. Pause new work delivery until payment is confirmed. Give a specific deadline: “I need payment or a payment plan agreement by [date].”

90+, Formal notice of intent to escalate. Consider a collections agency, attorney demand letter, or small claims filing based on invoice size.

Reading the Patterns

A single late invoice is an event. A pattern is a diagnosis.

When you run the aging report monthly and add each client’s bucket to a simple history log, patterns emerge quickly. A client who has appeared in the 31-60 bucket for two consecutive months is not a cash flow anomaly, they are a slow-pay client, and your billing arrangement with them should change.

Patterns that require a conversation:

Any client who appears in 31-60 two months in a row
A retainer client whose payment date is drifting later each month
A project client who pays on delivery but disputes line items after 30 days

The aging report does not just tell you who owes you money. It tells you which client relationships have billing friction that will eventually become relationship friction if unaddressed.

Most collection problems are relationship problems that payment friction surfaced first. The aging report finds them when they are still fixable.

The Monthly Ritual

Pick one date, the 1st or last business day of the month, and make it your billing review date. The full ritual takes 30 minutes:

Update the aging report (10 minutes)
Send 1-30 bucket reminders (5 minutes)
Send 31-60 bucket direct emails (5 minutes)
Handle 61+ bucket personally (10 minutes)

Do this consistently for 3 months and you will have eliminated the experience of discovering a 90-day invoice by accident. The aging report is not a sophisticated system. It is a simple categorization discipline that solo operators skip because they assume they will remember who owes them what. Memory is not a collections strategy. The aging report is.

The Five Buckets

How to Build the Report in 15 Minutes

The Collection Action Matrix

Reading the Patterns

The Monthly Ritual

Keep reading

The "Annual Invoice Review" Conversation With Long-Term Clients

The "Invoice Audit": Quarterly Review of Days-to-Paid Per Client

The "Payment Plan" Offer: When to Restructure for a Struggling Client

The "Recurring Invoice" Workflow for Retainer Clients

How to Know When a Client Has Viewed Your Invoice (and What to Do Next)

The "Bilingual Invoice" Template for Cross-Border Service Work