What it means
A company has 500 unpaid invoices. One large invoice is two days late because the customer requested a missing purchase order, while another smaller invoice is 90 days late and disputed, so different causes call for different owners and next steps.
Start with a reliable accounts receivable aging report, since Stripe describes aging buckets that organise unpaid invoices by how long they have been outstanding, and check due dates and credit memos before calling an amount overdue. Separate accounts already paid but unapplied, because a reminder sent after cash arrived can embarrass the business and the customer.
Reconcile receipts, remittances and customer balances first. Then segment by cause, since an administrative document gap, service dispute, financial difficulty and forgotten invoice should not receive the same script, and the next step may be sending evidence, fixing a service problem or agreeing a lawful plan.
Prioritise by exposure and urgency. A large balance nearing a contractual deadline may need fast review, but repeated small overdue invoices can also create material cash strain, so look at both amount and probability of resolution.
Avoid ranking by age alone, because a fresh but large disputed invoice may need immediate technical help while a very old balance may already be in a formal process with a different owner. Zuora's guide to aging invoices discusses using aging information and automation to manage overdue balances.
Product capabilities vary; the general practice is to make aged items visible and assign timely follow-up. Use a clear queue that records invoice ID, due date, amount, owner, last contact, promised action and next date, keeping customer notes accurate and access-limited.
An illustrative high-priority share is overdue value assigned to the defined priority queue divided by all overdue value. If $200,000 of $500,000 is assigned, the share is 40%, which is a workload measure and not a recovery forecast.
Check customer commitments too, so the team does not send a second reminder while it has promised to investigate a billing error, and respect contract terms and applicable law because collection notices, fees and escalation steps can be regulated. Use automation for routine reminders only after checking the balance and timing, with a human route for disputed or vulnerable cases, because a wrong automated send can cost more than it collects.
Measure cash collected, dispute resolution time, broken promises and customer complaints, not only the number of messages sent, and keep forecast assumptions separate since a high-priority invoice is not necessarily collectible this month. For an owner, prioritisation makes collections more thoughtful, not louder, linking each overdue balance to a verified cause, an appropriate next action and an honest cash expectation.
In practice
Real-world examples.
Example
A large late invoice is cleared after the team supplies a purchase-order reference. The customer pays within days because the real obstacle was a missing document, not unwillingness.
Example
A disputed amount is sent to service resolution rather than repeated reminders. The collector keeps the undisputed part of the balance on the normal schedule.
Example
Unapplied cash is reconciled before a customer receives a late notice. The finance team matches a lump-sum transfer to three invoices and removes them from the queue.
Formula
Calculation
Illustrative priority-queue share = overdue value assigned high priority / all overdue value x 100. $200,000 / $500,000 x 100 = 40%.
A workload view builds on this. If the 40% share is made up of 25 invoices and the team can work 5 priority accounts a day, the queue needs 25 / 5 = 5 working days to clear once, which shows whether the threshold is realistic. If one invoice is $50,000 and disputed, it may be worth moving it to a service specialist rather than keeping it in the daily call list.Case study
Seen in the real world.
In this entirely fictional example, Elm Services reviews 500 open invoices. It discovers a major customer payment was received but not applied, and another invoice awaits a missing document. The team corrects the first balance and sends the document for the second. It does not send an automatic demand on either account. The case does not guarantee collection.
Elm Services then builds a short weekly queue of the 20 invoices where a specific action is open, each with an owner and a next date. Sales is told which accounts have unresolved service complaints. After a month the team compares disputes closed and promises kept with the old message-count report. The company and its figures are invented for illustration.
Watch out
Common mistakes.
- Sending reminders without checking whether cash was already received.
- Treating a customer dispute as ordinary unwillingness to pay.
- Assuming queue priority means certain or immediate cash collection.
Questions
People also ask.
Does the oldest invoice always come first?
No. Value, cause, risk and timing also matter.
Is prioritization a collection permission?
No. Follow agreed terms and applicable law for any contact or fee.
What data should a queue hold?
Verified balance, due date, cause, owner, last action and next step.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%