Guides & Resources

Guides & Resources

โ€ข

โ€ข

โ€ข

โ€ข

10

10

Read

Read

How to Prioritize Collections Accounts: A Weekly Worklist for AR Teams

A practical scoring model and weekly worklist that tells a 3 to 5 person AR team which past-due accounts to work first, and how to make sure none are skipped.

Pratheek Adi

Pratheek Adi

Co-Founder & CTO

Collections Prioritization
AR Worklist
Accounts Receivable
Collections Prioritization
AR Worklist
Accounts Receivable
Collections Prioritization
AR Worklist
Accounts Receivable
Laptop computer on glass-top table

Table of contents

Share

To prioritize collections accounts, rank every past-due account by a few signals you already have (days past due, open balance, broken promises, dispute status and customer risk), work the list from the top each week, and make sure the bottom of the list still gets a routine contact. The goal is not only to call the biggest balances first. It is to make sure the right person works the right account at the right time, and that no account goes a month without hearing from you.

Short answer: score each past-due account on age, balance, promise history and risk; sort the list; send the top tier to people, the disputed tier to your disputes owner, and the long tail to a fixed routine cadence; then measure coverage every week so nothing falls off the bottom.

Prioritization matters because the clock works against you. Atradius reports that 43% of credit-based B2B sales in the US were overdue in 2025, and that bad debts now affect 5% of long overdue invoices. NACM, citing Commercial Law League of America data, notes that the probability of recovering a commercial account falls from 94% at 30 days outstanding to 74% at 90 days, and to 27% at one year. Every week an account sits unworked costs you some of its value.

Why Do Collections Teams Need a Prioritization Model?

Collections teams need a prioritization model because a three to five person team cannot give every account the same attention, and without a rule the team's attention goes to whoever is loudest. The largest customers and the angriest disputes take every available hour, and mid-size balances drift from 30 to 60 to 90 days without a single call.

The aging report is not a worklist

An aging report tells you what is owed and how old it is. It does not tell you which account to call at 9am on Tuesday. Sorting by balance ignores age; sorting by age ignores balance; and neither shows that a customer broke a promise last Friday.

Gut feel does not scale

Experienced collectors carry a mental list of "accounts I am worried about." That list is often right, but it lives in one person's head, it skips accounts nobody has looked at in a while, and it disappears when that person is out.

A written scoring model turns judgment into a list the whole team can share, check and improve. It also makes the weekly review faster, because the manager is approving a ranked list instead of building one from scratch.

Which Signals Should Decide Collections Priority?

Five signals carry most of the information you need, and all of them already live in your accounting system or your collectors' notes.

Days past due

Age is the strongest single signal because recoverability falls as invoices get older. Score by aging bucket rather than exact days so the model stays simple: current, 1 to 30, 31 to 60, 61 to 90 and over 90.

Open balance

A large balance deserves attention sooner. Score the total past-due balance on the account, not each invoice, so a customer with twelve small invoices is not treated as twelve small problems.

Promise history

A broken promise to pay is one of the clearest signs an account needs a person. Track promises with a date and amount; an account that broke one last week should rise to the top this week.

Dispute or deduction status

A disputed invoice will not be paid by another reminder. Flag it, route it to whoever owns disputes and take it off the routine call list until it is resolved. If short payments are a big part of your volume, our guide to customer deductions and short payments explains how to work them as a process.

Customer risk and concentration

Risk covers how the customer has paid in the past, any credit concerns you noted at onboarding and how much of your total receivables the customer represents. Our guides to assessing customer credit risk and AR concentration risk cover how to judge both.

How Do You Build a Simple Collections Priority Score?

Build the score by giving each signal a few points, adding them up and sorting the list from highest to lowest. Keep it simple enough that any collector can explain why an account is where it is. Here is a starting model you can adjust to your own customers.

Signal

0 points

1 point

2 points

3 points

Days past due (oldest invoice)

Current

1 to 30 days

31 to 60 days

Over 60 days

Past-due balance on the account

Bottom half of your past-due accounts

Top half

Top 20%

Top 5%

Promise history

No promises yet, or all kept

One promise slipped by a few days

One broken promise

Two or more broken promises

Contact history

Contacted this week

No contact in 1 to 2 weeks

No contact in 3 to 4 weeks

No contact in over a month

Risk notes

No concerns

Slow payer history

Credit concern or large share of total AR

Both

Disputes sit outside the score. An account with an open dispute goes straight to the disputes owner, whatever its score. Everything else gets ranked.

Why the contact history row matters

Most scoring models stop at age and balance. Adding "days since last meaningful contact" is what protects the long tail: a small, quiet account that nobody has called in five weeks gains points every week until it reaches someone's list. Contact history is the row that turns a priority score into a coverage tool.

Where to get the data

Start from your aging report. If you are on NetSuite, our guide to exporting the AR aging report from NetSuite shows how; the steps are similar in most ERPs. Promise and contact history usually live in collector notes, so the first version of the model may need a shared spreadsheet column until your process captures them consistently.

How Should You Split the Ranked List Into a Weekly Worklist?

Split the ranked list into tiers, and give each tier a different owner and a different kind of work. A three tier split works for most teams.

Tier 1: people work these first

The top scoring accounts (often the top 10% to 20% of the list) go to named collectors or the AR manager for a personal call this week. These are large, old or repeatedly broken promises, where a real conversation is the only thing likely to move them.

Tier 2: disputes and deductions

Every account with an open dispute goes to one owner, with a target resolution date. These accounts need research and coordination with sales or operations, not another reminder.

Tier 3: routine cadence for everyone else

The rest of the list still gets contacted every week through a fixed cadence of calls, texts and emails. This is where most teams fall behind: the work is repetitive, it is never urgent on any single day, and it is the first thing to slip in close week. Our guide to the ideal follow-up cadence after the due date sets out the touches and timing.

The tier 3 contacts are what keep tomorrow's tier 1 list short. An account that hears from you every week rarely becomes a large, 90 day problem.

What Does a Prioritized Collections Week Look Like?

A prioritized week has a fixed start, a protected middle and a clear finish. Here is a version for a three to five person team.

Monday: score and assign

  • Refresh the aging report and recalculate the scores.

  • Review the top of the list with the AR manager and confirm owners for tier 1 and tier 2.

  • Decide escalations for any account above your threshold. Our guide on when to escalate an invoice (and when to let it go) covers the ladder.

Tuesday to Thursday: work the tiers

  • Collectors work tier 1 from the top, logging every outcome: promise with date and amount, dispute opened, contact updated or no response.

  • The disputes owner works tier 2 against target dates.

  • Tier 3 contacts go out on schedule, without waiting for a collector to have a free hour.

Friday: check promises and coverage

  • Check every promise due this week; broken ones get a call the same day and move up next Monday.

  • Report coverage (the share of past-due accounts with a meaningful contact this week), promises kept, dispute age and cash collected.

When a customer pushes back during these calls, our guide to the top excuses for late payments and how to handle each one has responses your collectors can use.

How Do You Know Your Prioritization Is Working?

You know it is working when coverage stays high, broken promises get worked within days and the share of receivables in the oldest buckets shrinks. Track a short list every week; our list of 9 accounts receivable KPIs worth tracking goes deeper.

  • Coverage: the share of past-due accounts with a meaningful contact this week. If it drops, tier 3 is slipping.

  • Share of AR past 60 days: Credit Pulse treats more than 20% of receivables aged past 60 days as a warning sign.

  • Promises kept: the share of promises to pay that arrived on the promised date.

  • Days to work a broken promise: how long it takes for a broken promise to get a call.

  • DSO: the headline result, which moves after the others.

Earlier contact also pays off. Credit Pulse found that reminders that begin before the due date outperform post-due follow-up by 12 to 18 days on average, which is a good reason to put current invoices with a large balance on the routine cadence before they ever reach the past-due list.

How Does Abivo Help a Team Prioritize Collections?

Abivo takes tier 3 off your team's plate so your people can spend their week on tiers 1 and 2. Kate, Abivo's AI collections agent, calls, texts and emails customers about overdue invoices from your accounting system or ERP, logs every promise to pay and hands disputes and sensitive conversations to the right person on your team.

That fits the worklist above:

  • Every past-due account gets contacted on its cadence, so coverage no longer depends on how busy the week is.

  • Cadence can differ by account or segment, so key accounts, long-term customers and accounts near a credit limit each follow their own rhythm.

  • Sensitive accounts can be flagged to a named owner, so tier 1 accounts stay with the collector or manager who owns the relationship.

  • One invoice can be paused while a dispute is worked, and the rest of the account keeps moving.

  • One message can cover all open invoices on an account, with the details customers need, such as job, site, PO or billing period.

OFS Group, a fire protection company, went from four collectors to one with Abivo, recovered $842,518 in four months and cut DSO by more than 30 days; the full story is in the OFS Group case study. If you are comparing tools for a team your size, see our roundup of collections software for AR teams with 3 or more collectors.

Practical Takeaways for AR Managers

  • Turn the aging report into a ranked worklist with a simple score: age, balance, promises, contact history and risk.

  • Take disputed accounts out of the score and give them to one owner with target dates.

  • Send the top tier to people, and put everything else on a fixed weekly cadence.

  • Add "days since last contact" to the score so small, quiet accounts rise until someone works them.

  • Rescore every Monday, check promises every Friday and track coverage next to DSO.

  • Automate the routine tier first, so your collectors' hours go to the accounts that need judgment.

Related guides for AR teams: how to structure a collections team of 3 to 5 people and how to resolve invoice disputes.

FAQ

How do you decide which past-due accounts to call first?

Rank accounts by a simple score that combines days past due, past-due balance, promise history, days since last contact and risk notes. Call the highest scores first, route disputed accounts to your disputes owner and keep the rest on a routine weekly cadence.

Should collectors prioritize the largest balances or the oldest invoices?

Both, which is why a combined score works better than sorting by one column. A large invoice that is only a few days late may need less attention this week than a mid-size balance that is 75 days past due with a broken promise.

How often should a collections priority list be updated?

Weekly at minimum, ideally every Monday, with broken promises checked every Friday. Scores change quickly as invoices age, payments arrive and promises are kept or missed.

What should happen to small past-due balances?

They should stay on a routine cadence of reminders and follow-up, not wait until they grow. Adding days since last contact to the score makes sure small accounts that nobody has called in weeks move up the list.

Can AI help prioritize collections work?

Yes. An AI collections agent like Abivo's Kate can handle the routine contacts for every past-due account on its own cadence and hand disputes and sensitive conversations to the account's owner, so your team spends its time on the accounts at the top of the list.

Want every past-due account worked every week, without adding headcount? Get Started with Abivo.

Looking for more? Dive into our other articles, updates, and strategies