Overdue Invoice: How to Follow Up Without Losing the Customer

What Is an Overdue Invoice?

An overdue invoice is any invoice that has passed its payment due date without payment received. Issue a Net 30 invoice on May 1, and it becomes overdue on June 1. That definition is simple. What happens next requires judgment.

Most B2B credit teams treat overdue invoices as a collections problem to route and resolve. The more accurate frame: a relationship-management problem with a cash dimension. The goal is payment. The constraint is keeping the account in good standing after the check clears.

Days Past Due: Why the Number Matters More Than the Label

"Overdue" is a binary status. "Days past due" is the number your follow-up strategy should actually run on. A 3-day-late payment from a customer who has paid in 27 days for two years is not the same situation as a 3-day-late payment from a new account on their second invoice. The calendar is the same. The credit context is completely different.

Build your follow-up cadence around days-past-due buckets, not a single "overdue" flag. The tone, channel, and escalation threshold should scale with the clock.

The Follow-Up Cadence, Stage by Stage

1-7 days past due: Administrative reminder

Assume an internal processing delay, not a payment problem. Keep the message brief. State the invoice number, the amount, and the original due date. Ask if they need anything from your side to release the payment.

Avoid "overdue" or "delinquent" language. Do not include late fees in the first message if your terms include a grace period. The goal here is frictionless resolution, not escalation.

8-20 days past due: Direct follow-up

Name the amount. Name the date. Ask for a payment date. Subject lines that work: "Invoice #1042, $14,500, 12 Days Past Due." Vague subject lines get filed or ignored.

If you run AR automation software like HighRadius or Bectran, this is typically where their automated dunning sequences start. These tools handle scheduling well. They do not read the account history before sending the next message. A customer who paid in 25 days for two years and is now 18 days late deserves a different message than a new account already stretching terms. AR automation does not make that distinction without configuration. Your credit team does.

21-45 days past due: Escalate channel and tone

Move from email to a phone call. Reference the prior messages. Be direct about needing a payment date or a written payment arrangement. Do not leave the call without one of those two things confirmed.

At this stage, check the account's full payment history for pattern changes. A customer who has never been this late is sending a signal. Cross-check external sources: any news about their business, changes to their trade credit profile, public signals of financial stress. An overdue invoice from a financially healthy customer is a collections task. The same invoice from a customer whose finances are deteriorating is an early warning sign.

45+ days past due: Formal demand and credit review

Issue a formal demand letter with the outstanding balance, original terms, and a specific deadline before escalation to collections or delivery pause. Align with your collections team and legal counsel as needed.

Review the customer's credit limit and whether continued delivery is appropriate given the outstanding balance. Your credit policy should specify the trigger threshold for a credit hold. If it does not, this gap is where losses accumulate.

DSO Is the Wrong Number to Watch for Early Warning

Days Sales Outstanding is a portfolio-level trailing metric. It tells you what has already happened to your receivables. It does not tell you which individual accounts are trending toward payment problems before they go overdue.

The accounts that generate your worst collection outcomes are rarely the ones with obvious risk at onboarding. They are customers who paid reliably for 12 to 18 months and then slowed down. By the time DSO moves at the portfolio level, you may have multiple invoices at risk across several accounts.

The fix: monitor payment behavior trajectory per account, not just current overdue status. A customer whose average payment time has stretched from 22 days to 38 days over six months is worth a proactive credit review before the first invoice hits 30 days past due. DSO industry benchmarks tell you where you stand relative to your sector. Account-level trend data tells you which customers to watch before they surface in your collections queue.

The Delivery Pause Decision

Waiting too long to pause delivery while a balance grows is the most common credit management mistake. Credit teams that defer the pause decision often end up with four invoices outstanding instead of one, which compounds both the financial exposure and the difficulty of the eventual conversation.

Set the delivery pause threshold in your credit policy, not in the moment. Common triggers: the outstanding balance exceeds the customer's approved credit limit, an invoice is 45-plus days past due, or multiple invoices are outstanding with no agreed payment plan. Apply the threshold consistently. Exceptions based on account history or sales team pressure are how overdue balances compound into bad debt.

Frame the delivery pause to the customer as protecting the relationship, not ending it. You are pausing new orders to avoid creating a larger outstanding balance that becomes harder to resolve. Most customers understand that framing.

Overdue Data as a Growth Signal

Most credit teams treat overdue follow-up as cost control. The same data that surfaces payment problems also surfaces growth signals, and most teams leave that unused.

Customers with consistent early payment and credit limits set several years ago are candidates for a proactive limit increase. A limit increase unlocks more purchasing capacity and often correlates with higher spend from accounts that were previously credit-constrained. HighRadius and Bectran surface payment timing data. Neither tool prompts you to act on that data for limit expansion. The initiative has to come from a credit team that looks at its portfolio as a revenue asset, not just a risk ledger.

The practical question for every credit review cycle: which customers in your portfolio have earned a higher limit and have not received one?

Related Resources

• Days Sales Outstanding (DSO) Formula and Calculation Guide
• DSO by Industry: 2025 Benchmarks
• Dunning Letters: What They Are, How They Work, and When They Stop Working
• Demand Letter Template and Best Practices
• Accounts Receivable Management: A Guide for B2B Finance Teams
• Days Sales Outstanding (DSO): Formula and Calculation Guide

Frequently Asked Questions

What is an overdue invoice?

An overdue invoice is an invoice that has passed its agreed payment due date without payment received. For a Net 30 invoice issued May 1, the invoice is overdue on June 1.

How long before an invoice is overdue?

An invoice is overdue the day after its payment due date passes. Most B2B credit teams allow a short administrative grace period of 1-5 days before sending the first reminder, but the invoice is technically overdue as soon as the deadline passes without payment.

How do you follow up on an overdue invoice without damaging the relationship?

Keep early follow-ups administrative in tone: state the invoice number, amount, and due date, and ask if they need anything to process payment. Reserve escalating language for invoices 20-plus days past due. Most late payments in B2B result from internal processing delays, not deliberate avoidance.

When should you pause delivery on a customer with overdue invoices?

The threshold should be defined in your credit policy. Common triggers: the outstanding balance exceeds the customer's approved credit limit, an invoice is 45-plus days past due, or multiple invoices are outstanding with no agreed payment plan.

What is the difference between an overdue invoice and a past due invoice?

The terms mean the same thing. An invoice is both past due and overdue once its payment deadline has passed without payment. "Past due" is more common in US B2B contexts; both terms appear interchangeably in credit management workflows.