How to Hand Off a Collector's Accounts Without Losing Cash: A Checklist for AR Teams

When a collector leaves, goes on extended time off or moves to another role, their accounts do not stop aging. Invoices keep coming due, promised payments keep arriving or not arriving, and customers who were in the middle of a dispute keep waiting for an answer from someone who is no longer there.

For a team of three to five people, one departure can leave a fifth or more of the open receivables without an owner. That is a real risk to cash. Atradius reports that 43% of credit-based B2B sales in the US are overdue (Atradius Payment Practices Barometer, US 2025), so a portfolio that goes quiet for two or three weeks is a portfolio that slips.

Turnover is also normal, not rare. The US Bureau of Labor Statistics counted 3.1 million quits in August 2026, a quits rate of 1.9% for the month (BLS Job Openings and Labor Turnover, August 2026). Every AR manager will run a handoff sooner or later. This guide is for the controller or AR manager who wants that handoff to cost nothing in cash.

How Do You Hand Off a Collector's Accounts?

You hand off a collector's accounts by freezing a snapshot of every open item, writing down the context that only the collector knows, and reassigning each account to a named owner before the collector's last day. The aging report tells you what is owed. The handoff has to capture why it is still owed and what was promised.

A good handoff covers five things:

• The open items: every invoice, credit, unapplied payment and dispute on the portfolio

• The commitments: every promise to pay, with a date and an amount

• The open questions: disputes, missing POs, wrong contacts, pending credits

• The relationships: who the real AP contact is at each customer and how they prefer to be reached

• The new owner: a named person for every account, with a first touch date

If any of these five lives only in the collector's head or personal inbox, the handoff is not done.

Why Do Collector Handoffs Lose Cash?

Handoffs lose cash because the context behind each account is usually stored in a person, not in a system. The ERP holds the invoice. The collector holds the story.

Promises that go untracked

A collector who heard "we will pay on the 15th" may have written it in a notebook, a spreadsheet or nowhere. When the 15th passes and the payment does not arrive, the new owner does not know a promise was broken. Our guide to promise to pay tracking explains how to store commitments so they survive a change of owner.

Disputes that restart from zero

A customer who already explained a billing error to one collector will not enjoy explaining it again. If the new owner opens with a standard reminder, the customer feels ignored, and the dispute drags.

Contacts that go stale

The collector often knows that the AP inbox on file is unmonitored and that the person who actually releases payment is a controller named in a reply from last spring. That detail rarely makes it into the customer record. See our guide to keeping AR billing contact data clean.

Accounts that simply go quiet

The most common loss is the simplest one: the account sits untouched for three weeks because everyone assumed someone else had it.

What Should Be in a Collector Handoff Checklist?

A collector handoff checklist should capture every open item, every commitment and every relationship detail, account by account, in a format the next owner can act on the same day. Use the table below as the minimum.

If your team keeps this information in the ERP or a collections system as a matter of habit, the handoff takes an afternoon. If it lives in personal inboxes, it takes a week of interviews, and some of it is lost anyway.

How Do You Run the Handoff Step by Step?

Run the handoff as a short project with a start date, an end date and a named owner, ideally the AR manager. Here is a sequence that works for a team of three to five.

Step 1: Pull a snapshot of the portfolio

Run the aging report for the departing collector's accounts on a fixed cutoff date. Tie it to the ledger. This snapshot is the list you will check off, account by account. Our guide to AR aging report analysis covers how to read it.

Step 2: Sort accounts by risk, not by name

Put the accounts in three groups:

• Act this week: broken promises, open disputes, large balances past 30 days

• Act this cycle: past due but quiet, with no open questions

• Routine: current invoices with a clean payment history

This is the same logic as a weekly collections worklist, applied to one portfolio.

Step 3: Interview the collector, account by account

Book two or three working sessions before the last day. Start with the "act this week" group. For each account, ask four questions:

• What was the last conversation, and what did the customer say?

• Is there a promise, a dispute or a missing document?

• Who actually pays at this customer?

• What would you do next if you were staying?

Write the answers into the customer record during the session, not afterward.

Step 4: Move every open question into a shared log

Disputes, missing POs, pending credits and unapplied payments go into a shared log with a new owner and a target date. Our invoice dispute workflow and the guide to clearing unapplied cash both assume this kind of log exists.

Step 5: Assign every account to a named owner

Every account gets a person, not a team. Split the portfolio by size and complexity, not alphabetically. Large and complex accounts go to your most experienced collector. If you are rethinking the split more broadly, see how to structure a collections team of 3 to 5 people.

Step 6: Introduce the new owner to each key customer

For the top accounts by balance, send a short introduction before the collector leaves, ideally from the collector. Name the new contact, confirm the open items, and restate any promise already made. This one email prevents most of the friction that follows a handoff.

Step 7: Check the portfolio at 30 days

Thirty days after the handoff, compare the portfolio to the snapshot. Look at past-due balance, broken promises and accounts with no touch since the handoff. Anything that slipped shows up here.

What Should the Introduction Email Say?

The introduction email should name the new owner, list the open items and restate any existing promise, so the customer does not have to repeat anything. Keep it short.

A simple structure:

• Subject: Your accounts receivable contact at [your company]

• Opening: "Starting [date], [new owner] will be your contact for invoices and payments. [Collector] is moving to a new role."

• Open items: a short list of open invoices, with any agreed payment date

• Open questions: "We are still working on the credit for invoice [number]. [New owner] will confirm by [date]."

• Close: the new owner's direct email and phone

Restating the promise matters most. It tells the customer the commitment still stands and that the new owner knows about it.

How Do You Cover Accounts During Time Off?

Cover accounts during time off with a lighter version of the same handoff: a snapshot, a short list of live commitments and a named backup for each account. A two-week absence does not need interviews, but it does need a list.

Before the time off starts:

• Flag every promise due during the absence and give it to the backup with the date

• Pause or reassign scheduled follow-up that would otherwise go out under the absent collector's name

• Set an out-of-office reply that names the backup and a direct contact

• Give the backup read access to notes and recent customer correspondence

When the collector returns, the backup hands back the same list with what happened on each item.

How Do You Make Future Handoffs Painless?

The best handoff is the one that is already done, because the context lives in the system every day, not in a person. If a collector could leave tomorrow without losing cash, the team is in good shape.

Habits that keep context in the system

• Log every customer touch on the account the same day, with what was said

• Record every promise with a date and an amount, and check it on that date

• Keep one dispute log for the whole team, not one per collector

• Update contact records whenever a reply comes from a new person

• Use shared mailboxes for collections correspondence rather than personal inboxes

Signs your team is exposed

• A single collector is the one person who knows how to work a top-ten account

• Promises are tracked in personal spreadsheets

• The aging report is clean but the notes field is empty

• A collector's time off means their accounts go untouched

These habits also make the KPIs you report to leadership more reliable, because the numbers no longer depend on who happened to be in the office that week.

How Does a Handoff Affect DSO?

A badly run handoff raises DSO for the departing collector's portfolio, because accounts go untouched and broken promises go unnoticed. A well-run one should leave DSO flat.

The effect is easy to measure. Compare the portfolio's past-due balance and average days past due at the snapshot date with the same numbers 30 and 60 days later. If they rose while the rest of the ledger held steady, the handoff leaked cash. Our guide to lowering DSO without hiring covers the wider levers.

There is also a people cost. Covering a departed colleague's accounts on top of a full workload is one of the fastest ways to wear out the people who stay. We wrote about that pattern in why finance teams burn out.

Where Does Abivo Fit?

Abivo keeps routine follow-up running on every account no matter who is on the team, so a departure or time off does not leave a portfolio silent. Kate, Abivo's AI collections agent, works from your ERP aging data, sends follow-up by email and phone on a set cadence, logs every touch and promise on the account, and hands disputes and exceptions to your collectors with the context attached.

For a handoff, that changes the job. The routine accounts are already covered, the history is already in the system, and your team spends its time on the disputes and key accounts that need a person. OFS, a trades client, recovered $842,518 in four months, cut DSO by more than 30 days and went from four collectors to one (read the OFS case study).

Practical Takeaways for AR Managers

• Start the handoff before the last day, with a snapshot of the portfolio on a fixed cutoff date.

• Sort by risk: broken promises, disputes and large past-due balances first.

• Interview the collector account by account and write answers into the customer record during the session.

• Give every account a named owner and every open question a date.

• Send an introduction email to key customers that restates any existing promise.

• Check the portfolio at 30 days against the snapshot.

• Keep context in the system every day, so the next handoff is a formality.

Frequently Asked Questions

What is a collector handoff in accounts receivable?

A collector handoff is the process of moving a collector's accounts, open items and customer context to a new owner when that collector leaves, changes roles or takes time off. It covers open invoices, promises to pay, disputes, contacts and the next planned action on each account.

How long should a collector handoff take?

For a portfolio of a few hundred accounts, plan on one to two weeks of overlap if the collector is leaving, with two or three working sessions to review the riskiest accounts. If notes and promises are already logged in the system, it can take an afternoon.

Should you tell customers their collector has changed?

Yes, for your largest and most active accounts. A short introduction that names the new contact and restates any agreed payment date prevents customers from having to repeat themselves and keeps existing promises on track.

How do you cover a collector's accounts during time off?

Give a named backup a short list of every promise due during the absence, pause or reassign scheduled follow-up sent under the absent collector's name, and set an out-of-office reply with the backup's contact details.

How do you know if a handoff lost cash?

Compare the portfolio's past-due balance, average days past due and broken promises at the handoff date with the same figures 30 and 60 days later. A rise that the rest of the ledger does not show points to accounts that slipped during the handoff.

If you want routine follow-up to keep running on every account no matter who is on the team, get started with Abivo.