The past-due email that works—and the four that don't

You've sent the friendly reminder. You've sent the firmer one. The invoice is still open, and the customer's inbox is a graveyard of well-meaning follow-ups. The problem isn't your tone. It's that most past-due emails are built to be ignored: they ask nothing, name no one, and set no date. Here's the version that gets answered.

The four that don't work

• "Just checking in on the invoice." Vague enough to mean anything, urgent enough to mean nothing. It trains the customer that your emails can wait.
• "Per my last email…" Passive-aggression is not a collections strategy. It reads as frustration, and frustrated vendors are easy to stall.
• The novel. Three paragraphs of history, context, and relationship nostalgia. AP teams skim it, file it, and pay you last.
• The threat with no date. "We will have to escalate this" means nothing without a trigger date. Debtors stall amateurs; they don't stall someone holding their own file.

What the working email does

The past-due email that works has four parts and stays under 120 words:

1. The fact: invoice number, amount, date past due—no adjectives
2. The ask: the name of the approver and a specific payment date
3. The consequence: what happens on a named date if there's no response
4. The easy out: a dispute or a problem gets handled if they say so now

A version you can use

Subject: Invoice #4821 — $38,400 — 45 days past due

Hi [Name],

Invoice #4821 for $38,400 is 45 days past due. Can you confirm who approves payment on your side, and a date we can expect the funds? If there's an issue with the invoice—a dispute, a missing PO, a budget question—tell me now and we'll work it out before this goes further.

If we haven't heard back by [date], we'll pause the account and turn it over to our collection partner, which we'd rather not do on a working relationship.

Why the working one works

Ask for the approver's name and contact information. A legitimate approval process has a real person attached to it. If the AP contact can't or won't provide a name, the approval isn't real—you've just learned the truth about the stall. Naming the date converts an open-ended promise into a deadline. And offering the dispute path up front means the customer who genuinely has a problem tells you now, while the account is still young enough to fix, instead of six months from now when the file has gone cold.

One more thing: send this by email, then pick up the phone. The written record matters for later, but the conversation is where the answer lives. If the email goes unanswered past your date, that's your placement trigger—not your cue to send a fifth reminder.