Billing Contacts in Collections: How AR Teams Keep the Right AP Contact on Every Account
Many slow invoices are slow because the reminder reaches the wrong person. A practical system for a 3 to 5 person AR team to find, verify and maintain the right AP contact on every customer account.
Pratheek Adi
Co-Founder & CTO
Table of contents
Share
To keep the right AP contact on every account, an AR team needs three things: a defined set of contact fields per customer (who approves, who pays, where invoices go), a rule that every bounce, out-of-office or "I no longer handle this" reply updates the record the same day, and a verification step before any change to a contact or a payment detail is trusted. Most slow invoices are not slow because the customer refuses to pay. They are slow because the reminder is sitting in the inbox of someone who cannot act on it.
The numbers make the stakes plain. In the US, 43% of credit-based B2B sales in the US were overdue in the latest Atradius Payment Practices Barometer. At the same time, people move: the US Bureau of Labor Statistics reports that median tenure with a current employer was 4.1 years in January 2026. Over the life of a long customer relationship, the person who set up your account in their AP system is very likely to change at least once. If your records do not change with them, every reminder after that point is wasted.
This guide is for the controller or AR manager running a team of three to five collectors across hundreds of open invoices. It covers what a good contact record holds, where bad contact data comes from, how to clean it up without stopping collections, how to verify changes safely, and how to get the data ready before you automate follow-up.
Why Does Billing Contact Data Matter So Much in Collections?
Billing contact data decides whether a reminder reaches someone who can approve, schedule or release a payment. A perfect follow-up cadence sent to the wrong person collects nothing.
In most mid-market AR teams, contact problems show up as symptoms rather than as a named issue:
Invoices that age past 60 days with no reply at all, which looks like a ghosted customer but is often a dead address.
"We never received it" answers late in the cycle, after three reminders went to a shared inbox nobody reads.
Collectors who spend the first ten minutes of every call asking "who should I be talking to about this?"
Reminders addressed to a buyer or project manager who forwards them, slowly, to AP.
Each of these costs days on the invoice and minutes of collector time. Across a portfolio of hundreds of accounts, it adds up to a meaningful share of a collector's week spent finding people rather than collecting from them. Our piece on ghosted invoices covers silence as a risk signal; the first check on any silent account should be whether the contact is still valid.
The real cost is coverage
For a 3 to 5 person team, the goal is every open account touched every week. Bad contact data quietly breaks that goal, because an account with a dead contact looks "covered" in your activity log while nothing is actually happening on it.
What Should a Complete Billing Contact Record Include?
A complete record names the people and channels for each stage of getting paid, not just one email address. One contact per account is the single most common gap, and it is the one that breaks first when someone leaves.
Here is the record we recommend for each customer account in your ERP or accounting system:
Field | Why it matters | Where it usually lives | When to re-check |
|---|---|---|---|
Invoice delivery address (often an AP inbox) | Where invoices must land to enter the customer's AP process | Customer record, invoice delivery or email settings | On any bounce or "not received" reply |
AP contact (named person, email, direct phone) | The person who can tell you status and schedule payment | Customer contacts list | Every 6 months, and on any out-of-office or departure reply |
Approver or budget owner | The person who signs off when an invoice is stuck in approval | Contact notes or a secondary contact | When an invoice sits "in approval" past terms |
Escalation contact (controller or AP manager) | Who to reach when the AP contact cannot resolve it | Secondary contact | Before the first escalation, not during it |
Portal or submission method | Some customers only pay invoices submitted through their own system | Customer notes or a custom field | At onboarding and when invoices are rejected |
PO and reference requirements | Invoices without the right PO or reference stall in AP | Customer terms or notes | When a PO is renewed or changed |
Large customers with structured AP processes need the portal and PO fields most. Our guide to selling to big companies with slow pay systems covers those requirements in depth.
Separate the inbox from the person
Shared AP inboxes are good for invoice delivery and poor for follow-up. Keep both: send invoices to the AP inbox the customer asked for, and follow up with a named person who can answer. A reminder to "accountspayable@" gets queued; a call to a named AP specialist gets a date.
Where Does Bad Contact Data Come From?
Bad contact data almost always comes from one of five sources, and each has a simple fix.
1. Sales enters the buyer, not the payer
At account setup, the contact on file is often the person who signed the order or the project manager on the job. They are rarely the person who pays. Fix it at onboarding: the new-customer form asks for the AP contact and the invoice delivery address as required fields, separate from the buyer.
2. People leave and nobody tells you
Customers do not send notices when their AP specialist changes jobs. You find out from a bounce, an auto-reply, or a forwarded email weeks later. Every one of those signals should trigger a same-day update, which is a process rule rather than a technology problem.
3. Notes live in inboxes, not the system
A collector learns on a call that "Maria handles our invoices now," writes it in a personal note or an email thread, and the ERP record never changes. When that collector is out, the next person starts over. We wrote about this in why your ERP needs a memory: the conversation is only useful if it ends up in the record.
4. Acquisitions and restructures
When a customer is acquired or centralizes its AP function, invoice addresses, remit-to rules and contacts can all change at once. These events are worth a full contact review for that account, not a one-field patch.
5. Duplicate customer records
The same customer set up twice, once by sales and once by finance, means two contact lists and two sets of reminders. Merging duplicates is a one-time cleanup with lasting payoff.
How Do You Clean Up Billing Contacts Without Stopping Collections?
Clean up in priority order, starting with the accounts where wrong contacts cost the most cash, and fold the work into the normal weekly rhythm. Do not schedule a big-bang data project; fix the top of the aging report first.
Step 1: Pull the aging report with contact fields
Export your aging report with the customer's contact email and phone as columns. Our step-by-step guide to exporting an AR aging report from NetSuite shows how to add fields to the export; the same idea works in Sage Intacct, Business Central and QuickBooks.
Step 2: Flag the obvious gaps
Sort by balance and mark every account that has:
No named contact, only a generic inbox.
A contact whose email bounced in the last 90 days.
No phone number at all.
A contact who is clearly the buyer or project manager rather than AP.
Step 3: Fix the top 20 by balance this week
For each flagged account near the top of the list, call the customer's main line and ask a simple question: "Who handles payment of our invoices, and what is the best email and phone for them?" Update the record before you hang up.
Step 4: Make the fix a weekly habit
Add a line to the team's weekly review: "contacts fixed this week" and "accounts with no valid AP contact." Once the top of the list is clean, keep working down it a handful of accounts per collector per week.
Give the contact record one owner
Each account should have one collector responsible for keeping its contacts current. When everybody can edit a record, nobody feels responsible for it.
How Should AR Teams Verify Contact and Payment Detail Changes?
Verify every change through a channel you already trust, never through the message that announced the change. A new contact or a new payment instruction that arrives by email should be confirmed by a call to a number already on file before anyone acts on it.
This matters because payment fraud often starts with a convincing email. In the 2026 AFP Payments Fraud and Control Survey, 76% of US organizations reported attempted or actual payments fraud in 2025, and 74% were affected by business email compromise. A message that says "please update our AP contact to this new address" is exactly the kind of request a fraudster would send.
A simple verification routine
Confirm new contacts with a call to the customer's main number or a known contact, not the number in the new email.
Log who confirmed the change and when, in the customer record.
Treat any request to send statements or payment links to a personal or free email domain as a reason to double-check.
Tell customers, in your invoice footer and onboarding, that your own bank details will never change by email alone.
Our article on verified communication in accounts receivable explains why consistency in how you contact customers builds trust on both sides.
How Do You Turn Every Reply Into a Contact Update?
Every reply to a reminder carries contact information, and the team should capture it as a matter of routine. Out-of-office messages, bounces and forwards are free data; the only cost is the habit of recording them.
Replies worth capturing
Hard bounce: the address is dead. Flag the account and find the new contact the same day.
Out-of-office with an alternate: add the alternate as a secondary contact, and check back after the return date.
"I no longer handle this, please contact X": replace the primary contact after a quick verification.
Forward to a colleague who then replies: that colleague is very likely your real AP contact. Add them.
"Please submit through our portal": record the portal requirement so the next invoice goes there first.
Bounced emails move up the worklist
An account whose contact just bounced should jump to the top of a collector's list for the week, ahead of accounts that are simply slow. It is cheap to fix now and expensive to discover in 60 days. If an account still has no valid contact after several attempts, it is a candidate for the decision framework in when to escalate an invoice.
Why Clean Contact Data Comes Before Collections Automation
Automation sends more messages, more consistently, to whatever contacts you give it. If the contact data is wrong, automation repeats the wrong message faster.
That is why contact cleanup belongs at the front of any automation plan. Our roadmap for what to automate first in accounts receivable puts automated follow-up at stage one; the contact cleanup in this guide is the work that makes stage one pay off. The same applies to a well-built past-due invoice email sequence: the sequence only works if the first email reaches a person who can act.
Before you switch on automated follow-up, check:
Every account in the top half of the aging report has a named AP contact with a working email.
At least the larger accounts have a phone number for a person, not just a switchboard.
Portal-only customers are flagged, so their invoices are submitted the way they require.
Duplicate customer records are merged.
Many of the most common delays come from the invoice itself, so it is worth pairing this cleanup with a pass through the invoicing mistakes that slow down payments.
How Abivo Works With Your Contact Data
Abivo's AI collections agent, Kate, follows up by phone, text and email using the customer and contact records already in your accounting system, whether that is NetSuite, Sage Intacct, Microsoft Dynamics 365, QuickBooks or Xero. Because Kate uses the contacts you already maintain, clean contact data makes every reminder count.
A few practical points that matter for contact quality:
Reminders name the invoice details your customer's AP team needs to find it, such as the PO, job, site or billing period.
One message can cover all open invoices on an account, so a new AP contact gets a single clear picture rather than a pile of separate reminders.
Accounts can be set so that sensitive replies, such as a request to change who receives invoices, go to a named owner on your team to confirm.
Cadence can be set per account, so a customer with a portal requirement or a known slow approval cycle gets follow-up that fits it.
If you are comparing tools for a team of three or more collectors, our roundup of collections software for AR teams lays out the options. You can also read the OFS Group case study.
Practical Takeaways for AR Teams
Define the record. Every account gets an invoice delivery address, a named AP contact with email and phone, an approver and an escalation contact.
Separate buyer from payer at onboarding, with the AP contact as a required field.
Turn every bounce, out-of-office and forward into an update the same day.
Fix the top of the aging report first, about 20 accounts by balance, then a few per collector per week.
Verify every change through a number already on file, and log who confirmed it.
Give each account's contacts one owner on the team.
Clean the data before you automate, so automated follow-up reaches people who can pay.
Related guides for AR teams: how to structure a collections team of 3 to 5 people, how to prioritize collections accounts each week and how to track promises to pay.
Frequently Asked Questions
Who is the right contact for collecting an overdue invoice?
The right contact is the person in the customer's accounts payable team who can see the invoice's status and schedule payment, usually an AP specialist or AP manager. The buyer or project manager who placed the order can help with approvals, but is rarely the person who pays.
How often should AR teams update customer billing contacts?
Update contacts immediately whenever a bounce, out-of-office or "no longer handles this" reply arrives, and review the AP contact on every active account at least twice a year. Larger accounts are worth checking at each new contract, PO or renewal.
Should invoices go to a shared AP inbox or to a person?
Both. Send invoices to the AP inbox or portal the customer specifies, because that is how invoices enter their process, and send follow-up to a named AP person who can answer questions and give a payment date.
How do you find the right AP contact when nobody replies?
Call the customer's main line and ask who handles payment of your invoices. Ask your own sales or account manager who they speak to. Check the invoice approval history for names. Once you have a name, confirm the email and direct phone on the call and update the record before you hang up.
Why does clean contact data matter before automating collections?
Automated follow-up sends more reminders more consistently, so it multiplies whatever contact data it uses. With clean contacts, automation reaches people who can pay. With stale contacts, it sends more messages to dead addresses and the wrong people.
Ready to see how an AI collections agent works with the customer records you already keep? Get started with Abivo.
