How to Collect From Multi-Location Customers When Every Site Pays Differently
A playbook for a 3 to 5 person AR team collecting from customers with many locations: map who approves and pays at each site, choose a billing model, set up parent and child accounts, and run follow-up at two levels.
Pratheek Adi
Co-Founder & CTO
Table of contents
Share
A customer with twelve locations is one relationship and twelve sources of delay. One site approves invoices locally. Another sends everything to a regional office. Head office pays some invoices in a weekly batch and holds the rest until a store manager signs off. When your AR team treats that customer as a single account, invoices land on the wrong desk and sit there.
The wider pressure is real. In the 2026 Atradius Payment Practices Barometer for North America, overdue invoices made up an average of 23% of B2B receivables, and late payment affected seven in ten of the companies surveyed. Multi-location customers carry more than their share of that risk, because every extra site adds another approver, another address and another place for an invoice to go missing.
This guide is for controllers and AR managers running a 3 to 5 person collections team. It covers how to map a multi-location customer, choose a billing model, set up the account in your ERP and run follow-up so that every site pays, not only the ones that answer the phone.
What Makes Multi-Location Customers Hard to Collect From?
A multi-location customer is hard to collect from because the people who receive the work, approve the invoice and release the payment often sit in different places. Your invoice has to travel from the site to the approver to accounts payable, and it can stall at each step.
The core problem is that the account in your ERP rarely matches how the customer actually approves and pays. If you bill a store, the store forwards the invoice to head office, and head office pays from a different bank account, your aging report shows one late customer when the real issue is one broken hand-off.
Approval sits at the site, payment sits at head office
A site manager confirms the work was done or the goods arrived. Head office AP will not pay until that confirmation reaches them. Neither side is chasing the other, so the invoice waits until your team notices.
Remittances do not say which site they cover
A single payment from head office often covers invoices from several sites, with a remittance that lists only invoice numbers or nothing at all. That cash lands as unapplied, and sites look past due when they are not. Our guide to clearing unapplied cash covers the fix.
Contacts change by location
Each site has its own manager, and site staff turn over faster than head office staff. A contact list that was right in the spring is often wrong by the fall. Our guide to keeping AR billing contact data clean explains how to keep it current.
How Do You Map a Multi-Location Customer Before You Chase?
Map the customer before you chase it. For each location, record who receives the invoice, who approves it, who pays it and where the payment comes from. One short call with head office AP usually answers most of it.
The four questions for every site
Who should the invoice be addressed to at this site?
Who approves it, and how: email, portal or a signed delivery ticket?
Which AP team pays it, and on what payment run day?
Does a PO, job number or store number need to appear on the invoice?
Record the answers where the team works
Put the answers on the customer record in your ERP or AR system, not in one collector's inbox. When a collector is out or leaves, the next person needs the map on day one. Our collector handoff checklist covers what to capture.
Find out who really pays
If you are not sure which entity pays, look at the last three remittances. The remitter name and bank account show who actually releases the money, and that is the contact worth building a relationship with.
Which Billing Model Fits a Multi-Location Customer?
Pick the billing model that matches how the customer approves and pays, not the one that is easiest for your billing team. Most multi-location customers fit one of four models.
Billing model | How it works | Works best when | Watch out for |
|---|---|---|---|
Bill each site | Each location gets its own invoice and pays it | Sites have their own budgets and AP | More invoices to chase and more contacts to keep current |
Bill head office for all sites | One invoice per period covers every location | Head office approves and pays everything | One dispute can hold the whole invoice |
Site approves, head office pays | Each site approves its own invoice, head office pays in a batch | Approval is local and cash is central | Remittances that do not name the site |
Consolidated statement | Invoices stay per site, one statement shows the full balance | Head office wants one view of what it owes | Statements that list sites but not invoice numbers |
When in doubt, ask head office AP which format it pays fastest, and bill that way. A billing model the customer chose is one it is less likely to push back on.
How Should You Set Up Parent and Child Accounts in Your ERP?
Set up the customer as a parent account with a child account for each location, so you can see both the total balance and the balance by site. Most mid-market ERPs support this structure.
NetSuite
NetSuite lets you create subcustomers under a parent customer. With the Consolidated Payments feature turned on, the parent record shows a consolidated balance and consolidated aging for the whole hierarchy, you can print a consolidated statement, and a payment from the parent can be applied to any subcustomer's invoices. NetSuite's Consolidated Payments documentation also notes that a credit limit on the top-level customer applies to the entire hierarchy.
QuickBooks Online
QuickBooks Online supports sub-customers, and its bill parent option puts charges for the parent and its sub-customers on one invoice addressed to the parent. Intuit's guide to the bill parent customer option walks through the setup.
Business Central
Business Central separates the customer you sell to from the customer you bill. Setting a Bill-to Customer No. on a location's customer card sends that location's invoices to the account that pays them, while the sale still records against the site.
Whatever system you use
Keep the site name or store number on every invoice, even when head office pays. It is the detail that lets AP route the invoice and lets your team apply the cash. Check that your aging report can roll up to the parent; if it cannot, export it and group by parent. Our guides to exporting an AR aging report from NetSuite and from QuickBooks cover the steps.
How Do You Run Follow-Up Across Many Sites?
Run follow-up at two levels: the site, for approvals and paperwork, and head office, for payment. Chasing only head office leaves unapproved invoices sitting at sites. Chasing only sites never gets the money released.
Lead with the site for approvals
When an invoice is not approved, contact the site manager directly with the invoice, the delivery or job details and one clear ask: approve it or reply with what is missing. Keep it short, because site managers are busy and are not finance people. If the site approves through a portal, our guide to supplier portal invoicing covers submission.
Lead with head office for payment
Once invoices are approved, contact head office AP with one message per account, not one per invoice, listing every open item by site with invoice number, amount and due date. One clear list gets paid faster than twelve separate reminders.
Send one consolidated statement each month
A statement that shows the full balance by site gives head office one document to work from. Our guide to customer statements covers format and timing.
Log every promise by site
When head office promises to pay "the March invoices," write down exactly which invoices and which sites. Our guide to promise-to-pay tracking explains how to log promises so the next follow-up lands on the right day. When a site gives a reason for holding an invoice, our guide to late payment excuses has a response for each one.
How Do You Handle Disputes Without Holding Up Every Site?
Keep each dispute attached to its own invoice and site so the rest of the account keeps moving. A single short delivery at one store should not stop head office from paying the other eleven.
Ask head office to pay everything that is not in dispute while you resolve the one that is. Most AP teams will agree if you make the undisputed list easy to approve. Send the disputed item to the right owner with a fix date, and keep the customer updated. Our guides to resolving invoice disputes and to customer deductions and short payments cover the process.
Where a single dispute does hold a consolidated invoice, consider moving that customer to per-site invoices for the next period. It costs a few more invoices and can save weeks of waiting.
If an account stays stuck after both the site and head office have been contacted, our guide on when to escalate an invoice helps you decide the next step, and our guide on how to handle delayed payments from customers covers the conversation.
Who on a 3 to 5 Person AR Team Should Own Multi-Location Accounts?
Give each multi-location customer one owner across all its sites. Split the account by site and no single collector sees the whole picture. Split it by territory and head office hears from three people with three different totals.
One owner, a site map and a backup
The owner holds the site map, talks to head office AP and coordinates any site-level calls. A named backup covers time off. Our guide to structuring a 3 to 5 person collections team shows how to assign accounts this way.
Review the largest accounts every week
In the weekly AR review, look at the largest multi-location customers by parent balance first, then by site. A site with a growing balance while the other sites pay on time usually points to a local approval problem rather than a credit problem.
Where Does an AI Collections Agent Fit?
An AI collections agent helps most with the volume that multi-location customers create: many sites, many contacts and many small follow-ups that are easy to miss. Kate, Abivo's AI collections agent, follows up on every open invoice, sends one message per account, names the PO, job or site on each item, records promises and disputes, and hands disputes to your team. That leaves your collectors free for head office conversations and the accounts that need judgment. You can see how Kate works on the product page.
Practical Takeaways for Multi-Location Customer Collections
Map who receives, approves and pays at every site before you chase.
Pick the billing model the customer pays fastest, not the one easiest to send.
Set up a parent account with a child account per site, and keep the site name on every invoice.
Chase approvals at the site and payment at head office.
Keep each dispute attached to its own invoice so the rest of the account keeps paying.
Give each multi-location customer one owner and a named backup.
Frequently Asked Questions
Should I invoice each location or the head office?
Invoice the way the customer approves and pays. If head office approves and pays everything, bill head office. If each site has its own budget and AP, bill each site. When you are unsure, ask head office AP which format it pays fastest.
How do I apply one payment that covers several sites?
Ask for a remittance that lists invoice numbers by site and apply the payment against those invoices. Log any unmatched amount as unapplied cash and clear it within the week. A parent account with child accounts lets you apply one payment across sites in most ERPs.
What should a statement for a multi-location customer show?
Every open invoice grouped by site, with invoice number, invoice date, amount, due date and days past due, plus a subtotal for each site and a total for the whole account.
How often should I update contacts for each site?
Confirm site contacts at least every three months, and right away whenever an email bounces or a site manager changes. Site staff usually turn over faster than head office staff.
If your team is chasing dozens of sites by hand, Get Started to see how Abivo can follow up on every open invoice while your collectors focus on the conversations that need them.
