Accounts Receivable Collections: A Complete Guide
Quick Summary
- Collections is the work of turning issued invoices into cash. It sits inside credit control and ends where third-party debt collection begins
- It rarely sits with one person. AR analysts, collections specialists, credit managers, controllers, and the CFO each own a piece, and accounts get dropped at the handoffs
- 43% of the value of US B2B invoices is overdue, with a further 5% written off as bad debt
- Refusal to pay isn't on the list of causes. Customers pay late because they can't pay right now, can't process the invoice, or are disputing it
- Most of what gets called collections is invoice delivery. Clearing the PO gate, the payment run, and the AP portal decides whether you get paid on time
- Fixed reminder calendars stop working. Customers learn the pattern, and a set schedule can't tell two accounts apart
Good collections is a system you run, not a chase you repeat.
What are accounts receivable collections?
Accounts receivable collections is the work of turning issued invoices into cash. It covers everything that happens after the invoice goes out: reminders, customer replies, payment promises, dispute handling, and escalation when an account goes quiet.
The goal is easy to state and hard to do. Get paid quickly, without damaging the relationship.
Collections vs credit control vs debt collection
These three terms get used interchangeably. They describe different things, and confusing them leads teams to apply the wrong playbook at the wrong moment.
Most of your accounts should never reach that third row.
One more piece of vocabulary worth having. Dunning is the industry term for the sequence of reminders you run against an unpaid invoice. You will find it in software, in job titles, and throughout this guide.
Where collections sits in order-to-cash
Order-to-cash is the full journey from a customer placing an order to the cash landing in your account.
It runs in six stages:
- Quote and order: terms agreed, credit extended
- Fulfillment: the goods ship or the work gets delivered
- Invoicing: the invoice is raised and sent
- Collections: the invoice is followed up until it's paid
- Cash application: the payment received is matched to the invoice it settles
- Reporting: the aging report, DSO, and the rest of the numbers
Collections is the stretch between sending the invoice and the money landing. It's where revenue you have already earned either becomes usable cash or sits stuck in your aging report.
Every other stage can run perfectly and you can still have a cash flow problem if this one falls short.
Cash application is worth flagging early, because collections carries on past the moment money arrives, until that money is matched to the right invoice. Chapter 4 covers why that distinction matters more than most teams expect.
Who actually runs collections
In most companies collections is a set of overlapping responsibilities that shift depending on how large the balance is and how far past due it has gone.
In smaller companies one person wears several of these hats. In a ten-person business, the founder wears all five.
The handoffs are where accounts get dropped. An invoice that needs a credit decision, a dispute resolution, and a write-off approval can touch three people, and each handoff is a chance for it to stall in someone's inbox.
Collections also reaches well outside finance. The people who own the relationship hold context and standing that the AR team doesn't have, and a clumsy chase can undo months of their work.
Collections is a team sport, and the seam between those teams should be invisible to the customer. Chapter 2 covers how to run that coordination in practice.
Why collections matters
Late payment sets your cash position, whatever line it sits on in the accounts.
The scale is larger than most teams assume. In its 2025 US Payment Practices Barometer, Atradius found that 43% of the value of B2B invoices in the US was overdue, with a further 5% written off as bad debt. Average payment terms sat at 45 days from invoicing.
At the small business end the picture is worsening. The 2026 Intuit QuickBooks Small Business Late Payments Report found that 59% of US small businesses carry invoices overdue by 30 days or more, up from 47% the year before, with an average of $17.7K outstanding per business.
The cash flow cost of late payment
Every day an invoice sits unpaid is a day you can't use that money. Payroll doesn't wait for your customers to get around to it, and neither do your suppliers.
The pressure compounds. QuickBooks found that small businesses with the most overdue invoices were roughly 1.4 times more likely to report cash flow problems, and leaned noticeably harder on loans, credit lines, and business credit cards to bridge the gap.
That's the quiet cost of weak collections: you end up borrowing money you have already earned.
Bad debt and write-offs
The longer an invoice ages, the less likely it is to be paid in full. Old receivables turn into losses gradually, and by the time one surfaces in a write-off report, the window to do anything about it has usually closed.
A steady follow-up process catches problems while they're still fixable. This is the argument for collecting early rather than collecting hard.
The cost to your team
There's a human cost as well. AR teams burn out chasing the same accounts by hand, and most of the work is copy-paste. A clear process lets your people spend their time on judgment calls instead of reminders.
Why customers don't pay on time
The instinct is to read a late customer as a customer who won't pay. That's usually wrong, and acting on it costs you both cash and goodwill.
Outright refusal is rare in B2B. Atradius asked US suppliers why their customers pay late. Refusal didn't make the list. Customer liquidity issues led at 45%, followed by delays in the payment process at 33%, supply chain disruption at 26%, and invoice disputes at 23%. Respondents could pick more than one, so the figures don't sum to 100.
Three causes cover almost all of it.
They can't pay right now
Cash is tight. A receivable of their own is late, or a weak quarter has them deciding which suppliers get paid this month and which wait.
This is the one cause you can't fix from the outside. What you can do is spot it early and tighten terms before it becomes a write-off, using the warning signs further down this page.
They can't process the invoice
Second on the list, and the cause where your effort returns the most. An invoice that can't be processed won't be paid, however willing the customer is.
Most of these trace back to a short list of problems:
- A missing or mismatched purchase order
- The invoice went to the wrong contact
- It was never uploaded to the customer's AP portal
- An error on the invoice itself: wrong amount, wrong entity, wrong terms
- No remittance advice, so the payment can't be matched when it lands
- The person who used to approve it has left, and nobody inherited the queue
All six are delivery and accuracy problems.
They're disputing the invoice
A query about the amount, the scope, the delivery, or the terms. Sometimes raised properly on receipt, and often surfacing only once you chase.
A disputed invoice isn't a collections problem until the dispute is resolved. It comes out of the dunning cadence entirely and goes to resolution instead. Chapter 2 covers the mechanics, including deductions, which behave differently again.
Lead with the assumption that something is in the way, and you'll collect faster than the team that treats every late payer as an outlaw.
How your customer's AP department actually works
It helps to understand the machine at the other end. Your invoice doesn't go straight to someone with a checkbook.
Three things shape whether it gets paid on time:
- The PO gate. Larger customers require your invoice to match an approved purchase order, often through a three-way match against the PO, the goods receipt, and the invoice. Anything that fails to line up gets parked, usually without anyone telling you
- The payment run. Most AP teams pay in batches, weekly or biweekly, rather than the moment your invoice arrives. An invoice that lands the day after a run waits for the next one
- The portal. Many customers mandate an AP portal such as Ariba, Coupa, or Tipalti as the only accepted channel. If your invoice isn't in the portal, their AP team can't action it, no matter how many reminders you send
An invoice that's not in the portal in the right shape was never payable in the first place, so chasing the customer for it won't help.
Knowing this reframes the job. A large share of what gets called collections is really just making sure your invoice clears these gates cleanly.
The early signals that a customer is actually at risk
Sometimes it really is the balance sheet. The signals tend to show up well before the write-off does.
Worth watching for:
- Payments slowing across the whole account, not just on one invoice
- A falling promise-kept rate, where commitments start arriving late or not at all
- Contacts going quiet or leaving with no replacement introduced
- A change in how they pay, part payments where there used to be full ones
- Public signals: layoffs, funding trouble, a bad quarter, a known industry crunch
- Disputes raised late, surfacing only after you chase rather than on receipt
One signal on its own is potentially just noise. Two or three together should change your credit terms before they change your dunning cadence.
Collections is a system, not a chase
The most common mistake in collections is treating it as a calendar of nags: fixed reminders on a set schedule, sent from a no-reply address, to every account alike.
Customers learn that pattern quickly. They notice that nothing happens when they ignore it, and they tune it out.
The deeper problem is that a fixed calendar can't tell two accounts apart. A strategic customer who always pays three days late after a friendly nudge needs nothing like a new account that has gone silent on a large balance, yet both sit at the same days past due.
Good collections is driven by customer behavior and risk. The same backbone for everyone, with individual judgment layered on top.
The teams that collect well build a system that adapts. Chapter 4 covers how to design one.
See how Lunos solves this
A fixed reminder calendar can't tell two accounts apart. The Lunos collections agent reads every reply, tracks every promise, and adjusts its follow-ups to each account's behavior, so the system adapts the way a good collector would.
Contents
This guide runs across 6 chapters. Work through it in order, or jump to what you need.
See Lunos work a real ledger
Lunos is an AI coworker for accounts receivable. It follows up on every invoice, understands what customers write back, and keeps your team in control of every send. Book a demo to see it run the chase for you.
