What to Do When a Customer Stops Responding to Invoice Emails

Stop sending more email to the same address and work out which of three silences you are dealing with: the message never arrived, it arrived at someone with no authority to act, or the recipient can act and is choosing not to. Each has a different fix and only the third one needs pressure. Monk runs invoice to cash as one system, covering invoice delivery, AP portal submission, cash application and collections, which means an account that goes quiet arrives with its history attached rather than as a row on an ageing report. Most silence ends the moment the message reaches somebody who can do something about it, and almost none of it ends because the ninth reminder was more strongly worded than the eighth.

The account looks the same in all three cases. An invoice ages, replies stop, and the file contains eleven outbound emails and nothing inbound. The work below separates them within a couple of days and gives you an escalation path that changes the recipient rather than the temperature.

Is the silence a delivery problem, a capability problem or avoidance?

Test in that order, because the diagnostics are quick and the wrong assumption sends you up an escalation ladder for a problem that a corrected email address would have solved.

Delivery silence leaves evidence. Look for a hard bounce, an out-of-office that never ended, or a date after which opens and replies both stopped abruptly. Check whether the invoice is even in their system, since 92% of enterprise invoices must be submitted through a vendor portal or network rather than paid from an emailed invoice, and an emailed PDF at a large buyer often never entered an approval queue. The three companion diagnostics are in customer says the invoice was never received, what to do when an AP contact's email bounces and how to resolve a PO mismatch on an invoice.

Capability silence is the commonest and the least understood. An AP clerk who cannot tell you when the invoice will pay, because it sits with an approver or waits on a goods receipt they cannot post, has nothing to say and no incentive to say it. The tell is that the invoice has a visible status somewhere and that status has not moved. Reframe the request as something within their control, such as naming the approver, and the reply usually comes back within a day.

Avoidance is real and rarer than AR teams assume. The signals are specific: other invoices at the same customer are paying while this one is not, replies stopped immediately after you asked for a date, promises have been made and missed more than once, or a dispute has been raised late and vaguely about work completed months ago. Where the portal shows the invoice approved and scheduled and payment still does not arrive, that is a liquidity or policy decision on their side rather than a communications failure on yours.

Why does changing the recipient and the channel work when changing the tone does not?

Because none of the three causes of silence are sensitive to wording, and all three are sensitive to who receives the message and through which queue.

The instinct after four unanswered emails is escalation by adjective. The message becomes urgent, then final, then formal, while the recipient, the address and the medium stay the same. If the mailbox is dead, the tone reaches nobody. If the clerk has no authority, the tone makes an uncomfortable exchange out of a task they still cannot complete. If the customer is deliberately stretching you, they have already decided how to handle firmly worded email. A harder tone helps only where you are prepared to follow it with an action, and the action does the work.

What does change outcomes is a different queue. Email to a personal address is the weakest channel available, depending on one person, one inbox and one filter. A phone call to the AP main line published on the customer's own website reaches a team with a rota. A case raised inside their supplier portal lands in a worked queue with an owner and a service level. A message from a different sender inside your company arrives with a different reputation. Each is a real change of route, and any one is worth more than another reminder.

Design the message for the new channel rather than pasting the old one into it. One invoice, one question answerable in a single sentence, the invoice number and PO number in the subject line, no attachments and no thread history. Ask who owns the invoice and what its status is before you ask when it will pay, since the first two are answerable and the third often is not.

Who do you escalate to, and in what order?

Work upwards one rung at a time, using the lowest rung that can perform the action you need, because each step above that spends goodwill you will want later.

The rung that gets skipped most often is the requisitioner. When an invoice is blocked on a missing goods receipt or an unapproved service entry sheet, no amount of AP correspondence moves it, because the person who can act sits in operations and never sees supplier email. Finding that name and asking for one action inside their own system resolves a large share of accounts that look unresponsive. The mechanics of that block are in why AP portals reject your invoices.

Keep the ladder written down per account, with names, extensions and the date each was last useful. An escalation path rebuilt from scratch every quarter is why the same customer produces the same crisis twice a year.

When should you bring in your own account manager?

After two channels and about two weeks of genuine attempts, or immediately where the relationship is worth substantially more than the invoice and you need a name nobody in AR can find.

Account managers hold a real advantage: their email gets opened, they know who cares about the delivered work, and they can ask a favour AR cannot. That advantage is finite. Spending it on an invoice a phone call to the AP main line would have released is waste, and doing it repeatedly teaches your commercial team that AR escalates reflexively.

There are three specific risks in going early. The customer learns that ignoring AR produces a friendlier interlocutor, which trains exactly the behaviour you are trying to stop. The account manager, wanting to be helpful, may offer a concession on terms or a discount that converts an administrative delay into a permanent revenue reduction. And the report that comes back is often "they said it is in process", which is not information and cannot be actioned.

Brief them properly. Give a single ask with a deadline rather than a task: the invoice number, the amount, the days outstanding, the channels tried, the exact thing you need and the date. Agree in advance that any concession on terms or value comes back to finance before it is offered. Forwarding an ageing report and asking for help produces a reply promising to look into it, and nothing else.

Does the portal case system reach anyone?

Yes, and at most large buyers it is the strongest channel available to a supplier, because a case enters a queue with an owner and a service level while an email enters an inbox.

Coupa, Ariba, SAP Business Network, Tungsten and Taulia all expose some form of supplier case, message or dispute function attached to the invoice record. A case raised there is logged against the invoice, visible to AP management as a metric they are measured on, routed to whoever holds the queue, and unaffected by an individual's holiday. None of that is true of a message to a personal address.

Write cases narrowly. One invoice per case, the invoice and PO number in the title, the status you can see, the action you need, and the date. Vague cases collect template replies. A case saying "invoice 4471 has shown pending receipt since 12 August, please confirm who can post the receipt against PO 98765" comes back with a name, and a name is a rung.

Two practical notes. Check your own portal message centre while you are in there, since rejections and requests frequently sit unread on the supplier side and explain the silence completely. Where a case is closed with an answer that resolves nothing, reopen it or raise a new one quoting the closed case number rather than reverting to email, because you lose the audit trail the moment you leave the portal.

When is a credit hold the right lever, and when does this stop being a collections problem?

A credit hold is right when the customer can pay and is choosing not to, and the situation stops being a collections problem the moment your exposure is growing faster than your recoveries.

Holds belong to a written policy applied consistently across customers, and the decision sits with the controller or CFO rather than with an analyst under pressure. Use one when the balance is growing, when commitments have been broken more than once, and when you keep delivering, which increases the amount at risk every week. Do not use one where the block is administrative, where a dispute you have not answered is the cause, or where your own delivery documentation is incomplete, since all three make the hold look arbitrary.

Communicate it in a way that leaves the relationship intact. Give notice before it takes effect rather than after, state the date, state the exact amount or action that lifts it, address the message to the commercial stakeholder as well as to AP, and offer the route back in the same paragraph. A hold that a customer learns about when a shipment stops or a login is disabled costs more relationship than the cash it recovers. A hold announced ten days ahead, with a clear way to avoid it, frequently gets the invoice paid before it ever applies.

Then recognise the point where the question changes. Persistent silence, a growing balance and deteriorating payment behaviour together are a credit event rather than a collections one. That means re-running the credit review, reducing the limit, tightening terms on new orders, asking for a deposit, and shortening the review cycle. Most teams set an agency or legal threshold at 90 to 120 days past due in advance. Where you are rebuilding the whole cycle rather than one account, six strategies for reducing DSO covers where follow-up sits against the rest of it.

How does Monk handle this?

Monk treats a silent account as a state with a cause attached rather than as an invoice that needs another reminder.

Monk's Intelligent Collections ingests the context of each customer conversation, so an account that went quiet after raising a dispute is handled differently from one that never replied to anything, and follow-up reflects the state of the account rather than a fixed schedule applied to every open invoice. Julia, Monk's AI agent for Intelligent Collections, earns a 24% higher response rate than standard dunning, and 90% of collections resolve with zero human intervention, so the accounts that reach a person are the ones that need judgement.

Escalation rules stay with your team: how long to wait, who gets involved, and when automated outreach stops. Around 39% of cash flow slowdown is caused by edge cases, and an unresponsive account is usually one of them wearing a different label. Across $2B+ in receivables under management customers see a 40% average reduction in DSO and save 26 hours a month. AI cash application matches 80% of receipts automatically and 95% with suggested matching rules, Monk is SOC 2 Type II compliant and integrates with QuickBooks, NetSuite, Salesforce, HubSpot and Stripe, and onboarding takes less than one week.

Where should you start?

Take every account that has not replied in thirty days and sort it into the three silences before sending anything else.

For each one, answer four questions. Has anything from this customer bounced or gone unopened since a specific date? Does the invoice appear in their portal, and in what status? Did their last reply contain a question you never answered? Are their other invoices from you paying normally? Those answers place nearly every account into delivery, capability or avoidance.

Then write the escalation ladder for your ten largest customers: the AP queue, the AP manager, the requisitioner, the procurement contact and the commercial stakeholder, with names and numbers. To see conversation context, portal status and escalation history sitting on the same invoice record, book a demo.

Frequently Asked Questions

How many times should I email before escalating?

Two or three messages across at least two channels over roughly two weeks. A fourth email to an address that has produced no reply adds nothing and delays the diagnosis. The escalation is also more effective once you can state which channels you tried and what each produced.

Is it worth calling the customer?

Yes, and the AP main line published on their website is usually more productive than your contact's direct number, because it reaches a team rather than one desk. Ask what the invoice status is and who owns it before asking when it will pay.

What if my contact has left the company?

Find a replacement through the supplier portal directory, the AP main line or your account owner, then update the customer record the same day. Set the shared AP alias as the primary recipient with individuals copied, so the next departure does not break delivery. Also check whether invoices sent since they left need re-delivering.

Should I put the account on credit hold?

Only under a written policy, decided by your controller or CFO and applied consistently. A hold suits a customer who can pay and is choosing not to, and suits an account where your exposure grows every week you keep delivering. Give notice before it applies, state what lifts it, and tell the commercial stakeholder rather than only AP.

When does this become a credit decision rather than a collections one?

When the balance is growing, commitments have been broken more than once, and payment behaviour is deteriorating across the account. At that point the question is how much more you are willing to let them owe rather than how to collect what is already there. Re-run the credit review, adjust the limit and tighten terms on new orders.

Does automation help with unresponsive accounts?

It helps when the follow-up changes according to the state of the account rather than repeating a fixed schedule. Automation that fires identical reminders at an unmonitored mailbox reproduces the original failure at greater volume. The useful version identifies which of the three silences applies and routes the account accordingly.

How do I tell ordinary silence from a dispute?

Look at when the replies stopped. Silence beginning right after you issued the invoice points to a delivery or portal problem. Silence beginning right after a message from them usually means an open item they are waiting on you to resolve, and re-reading their last substantive reply is faster than any escalation.