How to Handle Delayed Payments from Customers: A Recovery Playbook for B2B Teams
Late payments cost US small businesses $17,500 on average. A practical playbook for handling delayed payments: diagnose the cause, respond, and prevent it.
Sia Ghazvinian
Co-Founder & CEO
Table of contents
Share
A delayed payment is rarely an emergency on the day it happens. That is exactly what makes it dangerous. One invoice slides a week, then a month, then it is competing with newer invoices for your attention, and your cash flow is quietly financing your customer’s working capital. 56% of small business owners are owed money from unpaid invoices, with the average small business owed about $17,500, and invoices paid roughly 8.2 days late on average. Across B2B specifically, 43% of the total value of US B2B invoices was overdue in 2025.
Handling a delayed payment well means doing three things in order: diagnose why the payment is late, match your response to that cause rather than sending a generic reminder, and then fix the process gap that let the delay happen. Teams that follow up systematically collect meaningfully faster, and automated reminders alone have been shown to collect 12 to 18 days faster than manual follow-up.
This playbook walks through each step, with the exact questions to ask and the responses that fit each cause.
Why Do Customers Delay Payments?
Most payment delays trace back to one of five causes, and only one of them is what finance teams usually assume.
Process failure on their side
The invoice went to the wrong inbox, the approver was on vacation, the PO number was missing, or their AP system needs a vendor record you never completed. In our experience this is the largest single bucket in B2B. The customer intends to pay and simply has not processed the invoice.
Process failure on your side
The invoice went out late, went to a contact who left the company, or carried an error the customer is silently waiting for you to fix. Before treating a delay as the customer’s problem, confirm the invoice actually arrived, was accurate, and named the right terms.
Cash management strategy
Some customers pay late deliberately because holding your cash is cheaper than borrowing. The signal: the same customer is consistently 10 to 20 days late, on every invoice, with no dispute and no apology. This is a terms and enforcement problem, not a reminder problem.
Genuine cash shortage
The customer wants to pay and cannot, at least not in full. The signal: they stop responding, or they suddenly start disputing small details on invoices they never questioned before. Handled early, this becomes a payment plan. Handled late, it becomes a write-off.
A real dispute
Something about the work, the delivery, or the amount is actually contested. A disputed invoice is not a collections problem and reminders will not fix it. It needs a human conversation and a resolution path.
If you want the scripts for what customers actually say in each of these situations, we keep a full list of the most common excuses for late payments with a response for each one.
How Do You Diagnose the Cause of a Payment Delay?
You can usually identify the cause with one short, friendly contact. The goal of the first touch is information, not pressure.
Ask a question the customer can answer easily
“Can you confirm this invoice is in your approval queue, and whether anything is missing on our side?” works better than “this invoice is overdue.” It gives a cooperative customer an easy path to reveal a missing PO, a wrong contact, or an approval bottleneck, and it gives you a dated, written answer to compare against what happens next.
Check your own records first
Before any outreach, verify three things: the invoice was delivered to the current AP contact, the amount and PO details match the agreement, and the due date reflects the terms you actually agreed. A meaningful share of “late payments” are invoices the customer never correctly received.
Read the pattern, not the excuse
One late invoice from a good customer is noise. The same customer late three cycles running is a pattern. An abrupt change in a customer’s payment behavior, especially slower payment plus reduced communication, is the single most useful early warning sign of a cash problem on their side.
Match the Response to the Cause
Generic reminders treat every delay the same way. The faster path is to respond to the cause you diagnosed.
Process failure on their side: re-send the invoice to the confirmed contact, supply whatever their AP process needs, and ask for a specific payment date. Log that date and follow up on it, not before it.
Process failure on your side: fix the error, apologize once, re-issue with a fresh due date, and correct the underlying record so it does not repeat.
Cash management strategy: stop relying on politeness. Shorten terms on future work, require deposits, or hold new orders until the account is current. Consistent late payers respond to consequences, not to reminder number four.
Genuine cash shortage: get a partial payment now and a written plan for the balance. A customer paying something every month is an asset; a customer avoiding your calls is a risk. Keep the tone collaborative and the schedule specific.
Real dispute: route it out of the reminder sequence entirely, to someone empowered to resolve it. Every reminder sent on a disputed invoice damages the relationship and delays the actual fix.
Delay cause | What it looks like | The right response |
|---|---|---|
Process failure on their side | Wrong inbox, missing PO, absent approver, or vendor setup blocker. | Re-send to the confirmed contact, supply AP requirements, ask for a specific payment date, and follow up on that date. |
Process failure on your side | Late invoice, stale contact, incorrect amount, or terms that do not match the agreement. | Fix the error, apologize once, re-issue with a fresh due date, and correct the underlying record. |
Cash management strategy | Consistently 10 to 20 days late with no dispute and no apology. | Shorten terms, require deposits, or hold new orders until the account is current. |
Genuine cash shortage | Reduced communication, new small disputes, or inability to pay in full. | Get partial payment now and a written, specific plan for the balance. |
Real dispute | Work, delivery, or amount is actually contested. | Remove it from reminders and route it to someone empowered to resolve the issue. |
The other half of a good response is timing. A delayed payment should never wait for someone to notice it. Map an ideal follow-up cadence in advance, so day 1, day 7, day 14, and day 30 each have a planned touch with a planned tone.
When Should a Delayed Payment Escalate?
Two thresholds matter more than any calendar rule.
First, engagement. A customer who responds, even to say “we’re tight this month,” is worth patience and a plan. A customer who has gone silent through three touches has earned escalation: a phone call, then a senior-to-senior contact, then a decision about holding work. We keep a fuller framework in our guide on when to escalate an invoice.
Second, portfolio exposure. Benchmark data from Credit Pulse suggests treating more than 20% of A/R past 60 days as an action threshold for the whole book, not just one account. If delayed payments are that widespread, the problem is your process, not your customers.
How Do You Prevent Payment Delays from Repeating?
Recovery without prevention just schedules the next delay. Four fixes close most of the gap.
Invoice immediately and correctly
Every day between delivering work and issuing the invoice is a day added to your DSO before the clock even starts. Invoice on completion, with the PO, contact, and payment instructions verified.
Set terms deliberately
Net terms are a price you charge yourself. If your average customer pays 8 days late against net 30, your real terms are net 38. Understand how your payment terms set your DSO and set them as a decision, not a default.
Confirm receipt and approval before the due date
A five-second “did this land in your approval queue?” touch at day 7 before due converts the largest delay cause, their process failure, into a non-event. It is the cheapest tactic in collections.
Automate the follow-up, keep humans for judgment
The reason delays compound is that follow-up is manual, and manual follow-up loses to urgent work every day. In our experience about 86% of collections touches are routine, diagnose, remind, confirm, re-send, log, and can run automatically, while the remaining 14%, disputes, hardship plans, sensitive accounts, genuinely need a human. Splitting the work that way means no invoice waits for attention, and your team spends its time only where judgment matters.
Where Abivo Fits
Abivo’s AI agent runs this playbook automatically: it contacts customers by phone, email, and text when an invoice goes past due, identifies which delay cause it is dealing with, asks for and logs specific payment dates, follows up on the dates customers commit to, and escalates to your team the moment an account needs human judgment. Your team sees every touch and outcome in one dashboard, and steps in for the 14% that needs them.
Curious what this sounds like in practice? Here’s a 98-second sample call: https://arcollects.com/#live-demo
Practical Takeaways for Handling Delayed Payments
Diagnose before you pressure: most delays are process failures, and one friendly question usually reveals the cause.
Check your own side first: delivery, accuracy, and contact. A share of late invoices were never correctly received.
Respond to the cause: re-send and confirm for process failures, terms and consequences for strategic late payers, partial payment plus a written plan for cash shortages, human resolution for disputes.
Escalate on silence and on portfolio exposure, not just on age.
Prevent the repeat: invoice immediately, set terms deliberately, confirm receipt before due date, and automate the routine follow-up so nothing waits for attention.
FAQ
What should I do first when a customer payment is delayed?
Verify your own records, then send one friendly, specific question asking the customer to confirm the invoice is in their approval queue and whether anything is missing. The first touch is for diagnosis. The cause you find, process failure, strategic late payment, cash shortage, or dispute, determines everything you do next.
How long should I wait before following up on a late payment?
Do not wait. A planned touch on the day after the due date, framed as a routine confirmation, is standard practice in B2B and no reasonable customer resents it. From there, follow a pre-mapped cadence with touches around day 7, day 14, and day 30, escalating tone gradually.
What is a reasonable explanation for a delayed payment?
Approval queues, missing PO details, a changed AP contact, and banking cutoffs are all common and usually genuine, especially the first time. What separates a reasonable explanation from a stall is specificity and follow-through: a credible customer names a payment date and hits it.
When does a delayed payment become a serious risk?
Watch for the combination of slower payment and reduced communication, disputes appearing on previously clean invoices, or broken payment promises. At portfolio level, more than 20% of A/R past 60 days is a widely used action threshold.
Can payment delays be prevented entirely?
Not entirely, but most of the volume can. Immediate accurate invoicing, deliberate terms, a pre-due-date receipt confirmation, and automated post-due follow-up remove the process-failure delays, which are the largest cause, and surface the risky accounts earlier.
Ready to stop chasing delayed payments manually? Get Started at abivo.ai/sign-up/get-started and see what your team’s 14% actually looks like.
