What to Do When a Customer Stops Responding to Invoice Emails
Stop sending more email to the same address. When a customer stops responding to invoice emails, the cause is usually mechanical rather than deliberate: the message is arriving in a mailbox nobody reads, the invoice never entered the system they pay from, or a question they asked three weeks ago is still sitting unanswered. Work through those three before you escalate. Monk's intelligent collections is built around that sequence, because most silence ends once the message reaches someone who can act on it.
This post covers why customers go quiet, the order to work through it, how long to wait before escalating, and when to bring in the account owner.
Why do customers stop responding to invoice emails?
Silence rarely means a refusal to pay. In our experience the common causes are narrow and repeatable: the contact left and their mailbox is unmonitored, invoices route to a shared AP address behind a ticketing system that never replies, your sending volume increased and your mail started filtering to spam, the invoice is parked in a portal queue instead of a person's inbox, or there is an open question your last three reminders did not address.
Each of those has a different fix, and none of them are fixed by a fourth reminder. That is the practical reason to diagnose before escalating: the escalation only works if the invoice has reached someone who can approve it.
What to do when a customer stops responding to invoice emails
Work the list in order. The first three steps are diagnostic and take about fifteen minutes per account. The last four are the escalation path, and they work better once the first three have ruled out a delivery problem.
- Confirm the emails are being delivered. Check your sent history for hard bounces, auto-replies, and out-of-office notices, and look for the date opens stopped abruptly. A contact who left the company generates a bounce that is easy to miss inside a shared AR mailbox, and every reminder you have sent since then went nowhere.
- Verify the invoice reached the system they pay from. Around 92% of enterprise invoices have to be submitted through a customer AP portal, so an invoice emailed as a PDF may never have entered an approval queue at all. Log into the portal, find the invoice, and note the exact status and any rejection or hold reason attached to it.
- Re-read the last reply you received. Silence frequently begins immediately after a question you did not answer: a purchase order number that does not match, a missing document, a line item they contest. Find the last substantive message from them and check whether it ended with something still outstanding on your side.
- Change the channel and the recipient. Call the AP main line, use the message function inside the portal, or contact a different person: the original buyer, the procurement contact, or whoever signed the contract. A portal message is logged against the invoice and routes to whoever is assigned to it, which an email to a personal address never does.
- Send one short message with a single question. Replace the reminder with a message that asks one thing someone can answer in a sentence: is invoice 1234 approved, and what date is it scheduled to pay. Drop the attachments and the thread history, because a long email to a busy AP clerk gets deferred rather than answered.
- Escalate with the history attached. After two weeks and two channels with no reply, bring in the account owner or your manager with a two-line summary: invoice number, amount, days outstanding, what you have tried, what you need from them. Escalating without that summary pushes your diagnostic work onto someone with less context than you have.
- Set a decision date and act on it. Decide in advance what happens at 90 or 120 days: a service hold, a credit hold, a formal demand from a manager, or handoff to an agency. Write the date on the account and act on it, because an account that drifts past your own deadline learns that the deadline is negotiable.
What is the silence telling you?
The pattern of the silence narrows the cause faster than any single check. The table below maps what you can observe to the most likely explanation and the move that follows from it.
| What you are seeing | Likely cause | Next move |
|---|---|---|
| Hard bounce or delivery failure | Your contact left, or their domain changed | Find a new contact through the portal directory or the account owner |
| Opens stopped on a specific date | Contact departed, or your mail is filtering to spam | Send from a different address and call the AP main line |
| No bounce, no opens, no reply | A shared inbox nobody monitors | Switch to the portal message function or the AP phone line |
| Replies stopped after your last message | An unanswered question or an open dispute | Re-read the thread and answer the outstanding item explicitly |
| Portal shows the invoice rejected or on hold | A submission or invoice data problem | Fix the named reason and resubmit rather than emailing again |
| Their other invoices from you are paying | Something specific to this invoice | Compare this invoice line by line against one that paid |
How long should you wait before escalating?
A workable default: diagnose at seven days past due, change channel at fourteen, escalate internally at twenty-one, and reach your decision date at ninety. Adjust for account size and the state of the relationship, then write the schedule down so it runs the same way every time without a debate.
Escalation timing does more for collection outcomes than message wording. An account contacted through three different channels over three weeks tends to resolve; an account that received nine near-identical emails over two months tends to keep aging, because nothing about the ninth email changed the reason the first eight failed.
When should you involve the account owner or sales?
Bring in the account owner once the AP path has produced nothing across two channels and two weeks, or whenever the relationship is worth more than the invoice. They hold contacts your AR team does not, and a message from them tends to get opened.
Give them a single ask rather than a task. "Can you find out who owns invoice 1234 in AP and get me a payment date" produces a result. Forwarding the aging report and asking them to help produces a reply saying they will look into it.
What if the customer is silent because something is wrong with the invoice?
This is the case worth ruling out early, because it looks identical from your side. A buyer who cannot find the invoice, whose portal rejected it, or whose purchase order does not match the amount will often say nothing at all rather than explain, particularly if the person receiving your email is not the person who noticed the problem.
Three checks cover most of it. Confirm the buyer has the invoice at all, covered in customer says the invoice was never received. Confirm your emails are reaching a live mailbox, covered in what to do when an AP contact's email bounces. Then confirm the invoice matches their purchase order, covered in how to resolve a PO mismatch on an invoice. If the portal itself is where things are dying, why invoices get rejected in AP portals lists the specific failure reasons.
How does Monk handle accounts that stop responding?
Monk's intelligent collections ingests the context of each customer conversation and responds accordingly, so an account that went quiet after raising a dispute is handled differently from one that never replied to anything. Follow-up reflects the state of the account instead of running a fixed reminder schedule against every open invoice at the same cadence.
Escalation rules stay with your team: how long to wait, who gets pulled in, and when automated outreach stops entirely. Monk resolves roughly 90% of collections without human intervention and reaches customers with about 24% higher response than standard dunning, and the accounts that need judgment arrive at a person with the full history attached. Across the $2B+ in receivables running on the platform, the average DSO reduction is 40%.
Our analysis shows around 39% of cash-flow slowdowns come from predictable, recurring exceptions, and an unresponsive account is usually one of them wearing a different label. If you are building a process around all of these at once, six strategies for reducing DSO covers where follow-up fits against the rest of the cycle. Monk goes live in 1 to 3 days, so a team stuck in a silent-account backlog can work through it in the same quarter.
Frequently asked questions
How many times should I email before escalating?
Two or three messages across at least two channels over roughly two weeks. Sending a fourth email to an address that has produced no reply adds nothing, and the escalation is more useful once you can say which channels you have already tried.
Is it worth calling the customer?
Yes, and the AP main line is usually more productive than your regular contact's direct number. Ask who owns the invoice and how to reach them, and you generally come away with a name, an extension, and the actual status of the invoice.
What if my contact left the company?
Find a replacement through the buyer's supplier portal directory, your own account owner, or the AP main line. Update the customer record the same day, because the next invoice will otherwise route to the same dead mailbox and repeat the cycle.
Should I stop work or put the account on credit hold?
That decision belongs to your leadership rather than to an AR analyst, and it should follow a written policy applied consistently across customers. Communicate the hold before it takes effect, since a surprise stoppage usually costs more relationship than it recovers cash.
When should an account go to a collections agency?
Most teams set the threshold at 90 to 120 days past due, after internal escalation has run its course. Setting that date in advance keeps the decision from being made emotionally in the middle of a bad quarter.
Does automation help with unresponsive accounts?
It helps when the follow-up changes based on the state of the account rather than sending more copies of the same reminder. Automation that fires a fixed schedule at an unmonitored mailbox reproduces the problem faster.
How do I tell ordinary silence from a dispute?
Look at exactly when the replies stopped. Silence that begins right after you sent an invoice usually means a delivery or portal problem, while silence that begins right after a question from them usually means an open item they are waiting on you to resolve.
.avif)