Ops & Strategy

Ops & Strategy

โ€ข

โ€ข

โ€ข

โ€ข

9

9

Read

Read

How to Structure a Collections Team of 3 to 5 People

Roles, account splits, a weekly operating rhythm and the KPIs a controller or AR manager needs to run a small collections team that covers every account.

Sia Ghazvinian

Sia Ghazvinian

Co-Founder & CEO

Collections Team
AR Operations
Accounts Receivable
Collections Team
AR Operations
Accounts Receivable
Collections Team
AR Operations
Accounts Receivable
Accounts receivable team meeting around a table in an office

Table of contents

Share

A collections team of three to five people works best when each person owns a clear set of accounts, one person owns disputes and deductions, and routine follow-up runs on a fixed weekly rhythm that does not depend on who is busiest. The structure matters more than the headcount: most small teams fall behind on coverage, not effort, because the largest balances and the loudest disputes absorb every hour and the long tail of overdue invoices never gets a call.

Short answer: split accounts by owner (by balance tier, segment or entity), give disputes and deductions a single owner, run a fixed weekly cadence for everything else, measure coverage alongside DSO, and automate the routine follow-up so your people spend their week on the accounts that need judgment.

The stakes are real. 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. The QuickBooks 2025 late payments report found that 56% of small businesses were owed money from unpaid invoices, averaging about $17.5K each. For a mid-market company with hundreds of open invoices, those numbers add up to a workload that a small team cannot cover by working harder.

Why Do Small Collections Teams Fall Behind?

Small collections teams fall behind because the work is uneven and the team's attention follows the noise. A three to five person team usually shares collections with cash application, credit reviews, deductions and month-end close. When close week arrives or a large customer disputes an invoice, routine follow-up is the first thing to slip.

The coverage gap

The pattern is consistent across industries. Collectors work the top of the aging report and the active disputes. Mid-size and small balances get an email if they are lucky. The accounts that quietly slide from 30 to 60 to 90 days past due are usually the ones nobody was assigned to call.

The ownership gap

When accounts belong to "the team," nobody owns them. Two collectors call the same customer in one week, while another customer hears nothing for a month. Customers notice both.

The documentation gap

Promises to pay live in someone's inbox or notebook. When that person is out, the next collector starts from zero and the customer repeats the same story.

Each of these gaps has a structural fix, which is what the rest of this guide covers. If you want the cost side of the same problem first, our breakdown of the real cost of collections puts numbers on the hours involved.

What Roles Does a 3 to 5 Person Collections Team Need?

A small team does not need five job titles. It needs four responsibilities, each with one named owner, even when one person holds two of them.

Responsibility

What the owner does

Typical owner on a 3 person team

Typical owner on a 5 person team

Team lead / AR manager

Sets priorities, owns the weekly review, approves escalations and write-off recommendations, reports to the controller

AR manager, also owns key accounts

Dedicated AR manager

Key account owner

Personally manages the largest balances and most sensitive relationships

AR manager

One senior collector

Portfolio collectors

Own a defined book of accounts for routine follow-up, promises to pay and simple questions

One collector for all non-key accounts

Two collectors, split by tier, segment or entity

Disputes and deductions owner

Resolves billing disputes, short payments and deductions with sales, operations and the customer

Second collector, part time

One specialist

The key decision is making disputes and deductions a named job. Disputes need research, coordination with sales or operations and follow-through. When every collector handles their own disputes, routine follow-up stops whenever a dispute gets complicated. If deductions are a big part of your volume, our guide to customer deductions and short payments covers how to work them as a process.

How Should You Split Accounts Between Collectors?

Split accounts so that every customer has exactly one owner and every owner has a workload they can cover every week. There are three common ways to do it, and most teams combine two.

By balance tier

The simplest split. Key accounts (often the top 20 to 50 customers by open balance) go to the lead or a senior collector. The rest are divided among portfolio collectors. This protects your biggest relationships, but it can leave one collector with hundreds of small accounts.

By segment or industry

Useful when customer types behave differently. A distributor might split contractors, retailers and national accounts, because each group pays on a different rhythm and raises different questions. Collectors get to know the patterns and the people.

By entity or region

The natural split for multi-entity companies on NetSuite, Sage Intacct or Business Central. Each collector owns the customers of one or two subsidiaries, so customers always hear from the right company name and the collector knows that entity's billing quirks.

A simple rule for sizing a book

Before you assign books, pull your aging report and count accounts with any balance past due, not just total invoices. (If you are on Business Central, our guide to exporting the aged accounts receivable report shows how.) Then ask one question per collector: can this person make meaningful contact with every past-due account in their book at least once a week, with time left for the accounts that need a real conversation? If the honest answer is no, the book is too big, and either the split changes or routine follow-up needs another source of capacity.

What Does a Good Weekly Collections Rhythm Look Like?

A good weekly rhythm makes routine follow-up automatic and reserves fixed time for judgment work. Here is a structure that works for most three to five person teams.

Monday: review and assign

  • The AR manager reviews the aging report, new disputes and last week's broken promises.

  • Accounts that moved into a new aging bucket get a named next step and owner.

  • Any account above your escalation threshold gets a decision: keep working, escalate to sales leadership, or hold.

Tuesday to Thursday: work the books

  • Portfolio collectors contact every past-due account in their book, starting with the oldest and largest.

  • Every contact ends with a logged outcome: payment promised (with date and amount), dispute opened, contact updated, or no response.

  • The disputes owner works open disputes and deductions, with a target date for each.

Friday: follow through and report

  • Check every promise due that week. Kept promises close out; broken ones get a call the same day.

  • The AR manager reports coverage, promises, disputes and cash collected to the controller.

The rhythm only works if the routine contacts actually happen on Tuesday to Thursday. In weeks when close or a large dispute eats those days, coverage drops and the next Monday review starts behind.

Which KPIs Should a Small Collections Team Track?

Track a small set of numbers every week, and include at least one that measures coverage rather than outcome. Our list of 9 accounts receivable KPIs worth tracking goes deeper; for a team of three to five people, these five carry most of the signal:

  • DSO: the headline outcome your controller and CFO watch.

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

  • Coverage: the share of past-due accounts that had a meaningful contact this week. This is the number that tells you whether the structure is working.

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

  • Dispute age: how long open disputes have been open, by owner.

Coverage is the leading indicator; DSO is the lagging one. If coverage falls for two or three weeks in a row, DSO will follow a month or two later.

When Should an Account Leave the Normal Cadence?

An account should leave the routine cadence when routine follow-up has stopped working or when the relationship needs a different owner. Common triggers:

  • A promise to pay is broken twice.

  • The customer disputes the invoice or raises a quality, delivery or invoice amount issue.

  • The balance passes an internal threshold for its customer tier.

  • The customer goes silent across phone, text and email for several weeks.

Each trigger should map to one owner and one next step, decided in advance. Our guide on when to escalate an invoice (and when to let it go) walks through the escalation ladder in detail.

Should You Hire Another Collector or Automate Routine Follow-Up?

Hire when the work that is falling behind needs judgment; automate when the work that is falling behind is routine. Most small teams find that the overflow is routine: reminders, follow-up calls on mid-size and small balances, confirming that an invoice was received, chasing a promised payment date.

Gartner expects that one-third of finance staff will occupy "shared jobs" by 2029, roles where people and AI do one job together. Collections is a natural fit for that model: software handles the repeatable contacts, and collectors handle disputes, key accounts and the conversations that need a person.

We compare the two paths in AI collections vs in-house collectors, and explain the difference between tools that assist collectors and tools that do the follow-up themselves in autonomous vs assisted AR collections.

How Does Abivo Fit a 3 to 5 Person Collections Team?

Abivo gives a small collections team a fourth or fifth "collector" for routine follow-up without changing who owns each account. 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 maps directly onto the structure above:

  • Account ownership stays intact. Accounts can be flagged so anything sensitive goes to a named owner, such as the key account collector or the disputes owner.

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

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

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

  • Multi-entity teams stay separated by subsidiary, so each customer hears from the right company.

The result is that your collectors spend Tuesday to Thursday on disputes, key accounts and the conversations that need judgment, while routine coverage happens every week regardless. 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 and the broader best AI AR collections software guide.

Practical Takeaways for AR Managers Running a Small Team

  • Give every customer exactly one owner, and make disputes and deductions a named job.

  • Split accounts by balance tier, segment or entity, then check that each book can be covered every week.

  • Run a fixed weekly rhythm: review and assign Monday, work the books midweek, follow through and report Friday.

  • Track coverage every week next to DSO; coverage moves first.

  • Decide escalation triggers and owners in advance, not account by account.

  • Before hiring for routine follow-up, look at automating it, and keep your people on the work that needs judgment.

Related guides for AR teams: how to prioritize collections accounts each week and how to resolve invoice disputes.

FAQ

How many accounts can one collector handle?

It depends on invoice volume, account complexity and how much of the collector's week goes to disputes, cash application or close. A practical test is whether the collector can make meaningful contact with every past-due account in their book at least once a week. If not, the book is too large or routine follow-up needs another source of capacity.

Should collectors be split by customer size or by industry?

Most teams combine the two. Key accounts go to a senior owner by balance, and the remaining accounts are split by segment, industry or entity so collectors learn each group's payment patterns.

Who should handle billing disputes on a small AR team?

One named owner. Disputes need research and coordination with sales and operations, and when every collector handles their own, routine follow-up stalls whenever a dispute gets complicated.

What is the most important KPI for a small collections team?

DSO is the headline outcome, but weekly coverage (the share of past-due accounts that had a meaningful contact) is the best early signal. When coverage drops, DSO usually follows.

Can an AI agent work alongside a human collections team?

Yes. An AI collections agent like Abivo's Kate handles routine calls, texts and emails on overdue invoices and hands disputes and sensitive conversations to the account's owner, so the human team keeps its structure and focuses on judgment work.

Ready to give your collections team full coverage without adding headcount? Get Started with Abivo.

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