How to prioritize which overdue invoices to chase first
Not every overdue invoice deserves the same effort. A simple scoring method by amount, age, and customer risk to decide what your team chases first.
Part of the accounts receivable and collections guide.
Monday morning, 140 invoices are past due and your AR team has time to work about 30 of them properly. Working the list from oldest to newest feels fair, but it is rarely the best use of those hours. To prioritize which overdue invoices to chase first, score each invoice on three factors, amount, days past due, and customer risk, then work the highest scores first while routing disputes and promises to pay into their own queues. This post gives you a scoring matrix you can use this week, a worked example, and the rules that keep the score honest.
Key takeaways
• Chase by expected recovery, not by age alone. A large, recently overdue invoice from a slipping customer often deserves attention before a small, very old one.
• Score three factors from one to three: amount outstanding, days past due, and customer risk. Weight them, add them up, and sort.
• Pull disputes and promises to pay out of the queue. Disputes need resolution, not reminders; promises need a follow-up date, not a call today.
• Re-score daily after Cash Application, so the list reflects payments that arrived overnight.
• Loopfour, the deterministic finance workflow automation platform, calculates the score the same way every day and posts the ranked worklist to Slack with the context each collector needs.
Why chasing oldest-first is not enough
Oldest-first prioritization ignores size and risk, so collectors spend hours on invoices that barely move cash. Age matters, because recovery gets harder as invoices get older, but it is one factor among three.
The risk of waiting is real. Atradius's 2025 survey of US businesses found that 43% of credit-based B2B sales were overdue, and that bad debts affected 5% of long-overdue invoices. The goal of prioritization is to act on the invoices most likely to slide into that long-overdue group, while they are still worth the most.
Three common failures of an unscored list:
• Big invoices wait their turn. A $120,000 invoice at 12 days past due sits behind forty small invoices at 60-plus days.
• Risk signals are invisible. A customer who has started paying later every month looks the same as a reliable one on a single late invoice.
• Disputed invoices clog the queue. Collectors call about invoices the customer has already contested, and nothing moves.
What factors should decide which overdue invoice to chase first?
Three factors decide priority: how much is owed, how late it is, and how likely the customer is to pay without intervention. Everything else is either a modifier or a reason to route the invoice elsewhere.
| Factor | Why it matters | Where the data comes from |
|---|---|---|
| Amount outstanding | Larger balances move more cash per hour of effort | Open balance on the invoice in NetSuite or QuickBooks |
| Days past due | Recovery gets harder as invoices age | Due date and today's date; aging bucket |
| Customer risk | Slipping payment behavior predicts further delay | Days-beyond-terms trend, broken promises, credit limit use |
Keep the factors few and the data sources fixed. A score nobody can explain in one sentence is a score nobody trusts. Your ERP already supplies the age factor: NetSuite's A/R Aging Summary, for example, groups overdue balances into 1 to 30, 31 to 60, 61 to 90, and over-90-day columns, and lets you change the interval.
The overdue invoice scoring matrix
Score each factor from one to three, apply a weight, and sum to a priority score between 1.0 and 3.0. The thresholds below are a starting template. Set yours from your own invoice sizes and terms.
| Factor (weight) | Score 1 | Score 2 | Score 3 |
|---|---|---|---|
| Amount outstanding (40%) | Under $5,000 | $5,000 to $50,000 | Over $50,000 |
| Days past due (30%) | 1 to 15 days | 16 to 45 days | Over 45 days |
| Customer risk (30%) | Pays on time historically; no broken promises | Pays up to 15 days late, or payment trend slipping | Pays more than 15 days late, broken promise, or near credit limit |
Priority score = (amount × 0.4) + (days past due × 0.3) + (customer risk × 0.3).
Then sort into action tiers:
| Score | Tier | Action |
|---|---|---|
| 2.4 to 3.0 | Call today | Personal call or email from the collector or account owner |
| 1.7 to 2.3 | Work this week | Personal follow-up after the next automated reminder |
| 1.0 to 1.6 | Automated cadence | Leave to the dunning schedule and monitor |
Modifiers and routing rules
Some invoices should leave the scored queue entirely, because calling about them wastes time or damages the relationship.
• Open dispute: route to the dispute owner with a target resolution date. Do not chase.
• Valid promise to pay: hold until the promised date plus a short grace period, then return to the queue with risk raised if the promise breaks.
• Payment in flight: hold until it settles or fails.
• Strategic account: keep the score, but assign the account owner as the contact for any call.
Worked example: scoring six overdue invoices
Here is the matrix applied to six illustrative invoices. Customer names and figures are hypothetical.
| Invoice | Amount | Days past due | Risk signal | Amount score | Age score | Risk score | Priority | Tier |
|---|---|---|---|---|---|---|---|---|
| Customer A | $120,000 | 12 | Payments slipping | 3 | 1 | 2 | 2.1 | Work this week |
| Customer B | $64,000 | 52 | Broken promise | 3 | 3 | 3 | 3.0 | Call today |
| Customer C | $18,000 | 38 | Pays about 20 days late | 2 | 2 | 3 | 2.3 | Work this week |
| Customer D | $2,400 | 75 | Pays on time otherwise | 1 | 3 | 1 | 1.6 | Automated cadence |
| Customer E | $55,000 | 48 | Near credit limit | 3 | 3 | 3 | 3.0 | Call today |
| Customer F | $40,000 | 30 | Open dispute | n/a | n/a | n/a | Routed | Dispute owner |
Reading the result: Customers B and E get a call today, together worth $119,000. Customer D is the oldest invoice on the list, but at $2,400 from a reliable payer it stays on the automated cadence. Customer F never enters the queue, because a collector call would not resolve a disputed line item.
The oldest-first list would have started with Customer D. The scored list starts with the invoices that carry the most cash at the most risk.
How to make the score trustworthy
A priority score is only useful if the data under it is current and the rules do not change quietly. Four practices keep it honest.
• Re-score after Cash Application every day. A payment applied overnight should remove the invoice before anyone calls.
• Calculate risk from data, not memory. Use days-beyond-terms history and broken promises recorded against the customer, not a collector's impression.
• Version the thresholds. When you change a band or weight, record the date and the reason, so month-over-month comparisons stay valid.
• Review the output weekly. Check a sample of high and low scores with the team and adjust if the matrix consistently ranks the wrong invoices.
Clean data comes first. Duplicate customers and unapplied credits distort every factor. If your aging report looks off, see why your AR aging report is wrong after a customer record didn't sync.
How Loopfour builds the prioritized worklist
Loopfour runs the scoring matrix as a deterministic workflow, so the same invoice with the same data gets the same score every day. The ranked list lands in Slack each morning, with context attached.
The flow: Cash Application completes in NetSuite or QuickBooks → open overdue invoices pulled → disputes, promises, and in-flight payments routed out → amount, age, and risk scored → tiers assigned → worklist posted to Slack with invoice, balance, last touch, and customer history → collector marks the outcome, which feeds tomorrow's risk score.
AI has one scoped task here: reading customer replies. It classifies a reply as a promise to pay, dispute, or remittance and extracts the date. Below your confidence threshold, the reply goes to a person for review before it changes any routing. The scoring itself is rules, not a model, so you can explain every rank to your controller.
Book a workflow review to see your current overdue list scored with your own thresholds.
How to choose a prioritization approach
Choose the simplest approach your team will actually trust and maintain. A transparent rules-based score usually beats an opaque model for a finance team that has to explain its decisions.
| Approach | When it fits | Watch out for |
|---|---|---|
| Oldest-first aging list | Few overdue invoices, similar sizes | Ignores amount and risk |
| Spreadsheet scoring matrix | Small team, stable rules | Manual refresh, formula drift, stale data |
| Black-box predictive score | Very high volume with data science support | Hard to explain why an invoice ranks where it does |
| Loopfour deterministic scoring | Teams that want a daily, explainable, auditable worklist | Rules need an owner to tune thresholds over time |
A model that ranks invoices without an explanation leaves your collectors guessing. A rules-based score tells them why. Pair the worklist with a consistent reminder cadence, covered in our guide to automating dunning and collections reminders.
Frequently asked questions
How do I prioritize which overdue invoices to chase first? Score each overdue invoice on amount, days past due, and customer risk, weight the factors, and work the highest scores first. Remove disputed invoices and valid promises to pay from the queue, and re-score daily after payments are applied.
Should I always chase the oldest invoices first? No. Age matters because older invoices are harder to recover, but a small invoice from a reliable customer can wait on an automated reminder. A large, moderately overdue invoice from a customer whose payments are slipping usually deserves attention first.
How do I measure customer risk for collections? Use data you already have: the customer's average days beyond terms, whether that trend is worsening, broken promises to pay, and how close they are to their credit limit. Combine these into a simple one-to-three score so collectors can see why a customer is flagged.
What should I do with disputed overdue invoices? Take them out of the collections queue and assign an owner with a target resolution date. Chasing a disputed invoice rarely speeds payment, and it frustrates the customer. Once the dispute is resolved, the invoice returns to the queue with its corrected balance.
How often should I re-prioritize the overdue list? Daily, after Cash Application runs. A worklist built on yesterday's balances sends collectors after invoices that are already paid, which wastes time and annoys customers.
Conclusion
Prioritizing which overdue invoices to chase first is a scoring problem, not a willpower problem. Score amount, days past due, and customer risk, route disputes and promises out of the queue, and re-score every day on current data. Your team spends its limited hours where the most cash is most at risk, and every rank has a reason you can explain.
Tell us the one workflow your team dreads. We will show it running: deterministic, permissioned, and auditable.
Book a demo.
Sources
• Atradius, B2B payment practices trends in North America 2025
• Oracle NetSuite Help, A/R Aging Summary Report
Related reading
• The AR aging report: how to read it and forecast collections from it
• How to automate dunning and collections reminders without annoying good customers
• How to reduce days sales outstanding: the levers that actually move DSO
• How to automate accounts receivable without losing customer relationships
• Why your AR aging report is wrong after a customer record didn't sync
Sources
- Oracle NetSuite, A/R Aging Summary Report (opens in a new tab).