Accounts Receivable Automation

How to Write a Past Due Invoice Email to Someone You'll Work With Again

How to write a past due invoice email to a client or counterparty you'll deal with again: who to address, tone by recipient, three examples, a final check.

Jared Shulman
November 21, 2026
Operations lead re-reading an email draft on her laptop in an office lounge armchair
When you'll work with the recipient again, a past due invoice email should take its tone from the reader and the relationship, not the number of days late. Pick the reader (relationship owner, AP processor or approver), lead with their reference, ask for one thing, and have someone check the email before it goes.
  • The same invoice can have three readers: the relationship owner, the AP processor and an approver. Each needs a different email.
  • Lead with the reference the recipient files under, and include a line asking who should receive it if you've reached the wrong person.
  • Mention fees or next steps only if your contract allows them and you'll follow through.
  • Switch to a call after two unanswered emails, a bounce or a reply from someone who doesn't handle payments.
  • Review emails to relationship owners and approvers before they go out, whether a person or an AI tool drafted them.

A customer we worked with, a contingency-fee employment law firm, collects most of its receivables from people it will meet again: defendants and opposing lawyers who show up on the next case and the one after. As the firm's operations lead put it, these are never one-off collections, and the relationships have been worth protecting. Its reminder emails worked for some recipients and not for others.

Most past due invoice email templates set the tone by the calendar: friendly at 15 days, firmer at 30, stern at 60. That works for a one-time buyer. When you'll work with the recipient again, the reader and the relationship should set the tone instead. This guide covers who to write to, what to include, how to match the tone to the recipient, three example emails, and a quick check before you send.

What Changes When You'll Work With Them Again

With a one-off customer, a past-due email is a transaction. With a repeat counterparty (a long-term client, a partner, or the lawyer across the table on your next matter), it's one exchange in a relationship that continues after the invoice is paid. An email that's too sharp costs goodwill you'll need later. One that's too apologetic teaches the recipient that your due dates are soft.

There's a second complication: the same invoice can have three different readers. The person who owns the relationship decides whether it gets paid. Someone in accounts payable processes it. And sometimes an approver, such as a controller or managing partner, has to sign off. Each needs a different email. A warm note to the relationship owner gives AP nothing to pay from; a purely transactional note to the relationship owner reads as if you've handed them to a collector.

This guide is about writing that single email well. For timing, frequency and how emails fit with calls in a sequence, see our guide to automated payment reminders.

Decide Who the Email Is For

Before you write a word, pick the reader.

Recipient Who they are What they need to act What to avoid
Relationship owner Client lead, partner, the other side's lawyer A short, specific ask from someone they know Threats, form-letter language, over-apologizing
Processor AP clerk, shared AP inbox, billing contact Everything needed to match and pay, up front Relationship talk, missing invoice details
Approver Controller, CFO, managing partner The decision needed and what's been tried Long history, emotional tone

Then make the email recognizable to that reader. People file payables under their own identifiers (their PO number, vendor ID, matter or client name), so lead with that reference, not just your invoice number. An email nobody can match to their records tends to sit unanswered.

Also give the email a way back if it reaches the wrong person: "If this should go to someone else on your team, could you let me know who?" That one line turns a misdirected email into a routing answer instead of silence.

One rule for law firms: if the paying party has a lawyer in the matter, send payment emails to that lawyer, not the party; ethics rules treat staff emails as the firm's. Our guide to law firm collections covers this and the other ground rules.

What to Put in a Past Due Invoice Email

Keep the structure compact:

  • Subject line: their reference, your invoice number and "past due," for example "[Their PO or matter]: Invoice 1042 past due."
  • First line: what the email is about, in one sentence.
  • The facts: invoice number, amount, original due date and their reference; for an installment, which one.
  • One ask with a date: a payment date, or a reply by a specific day.
  • How to pay: payment methods or a link, plus remittance details.
  • The invoice, attached, so nobody has to search for it.
  • A reply path: how to tell you if it should go elsewhere.
  • The right sender: the person who owns the relationship, or someone writing for them with them copied.

Mention late fees, interest or next steps only if your contract provides for them, and only if you intend to follow through. Our guide on how to write a collection letter covers fees, consequences and wording in more depth.

Set the Tone by Recipient, Not by Days Late

Days late still matter: a third email is firmer than a first. But the starting point comes from who's reading.

Relationship owner: collegial and direct. Write as one professional to another. Acknowledge the ongoing relationship without apologizing for asking; you're entitled to be paid.

  • Sounds like: "Wanted to flag that invoice 1042 for [matter] is now past due. Could you check where it stands?"
  • Not like: "Sorry to bother you again, I know you're very busy…" or "Failure to pay will result in…"

Processor: transactional and complete. They want to match, approve and pay. Put everything in the first three lines and keep pleasantries to a greeting.

  • Sounds like: "Invoice 1042, PO 7781, $4,800, due October 15, is showing as unpaid on our side. A copy is attached. Could you confirm the payment date?"
  • Not like: "Hope the project's going well! Just circling back…"

Approver: short and factual. By the time you write to a controller or managing partner, you've usually tried the relationship owner and AP. Say so, state the amount and age, and name the decision you need.

  • Sounds like: "We've emailed [Name] twice and AP once about invoice 1042 ($4,800, 45 days past due) without getting a payment date. Could you confirm whether it's approved, or who can?"
  • Not like: a forwarded chain of every earlier email with "see below."

Writing to an approver is a deliberate step. Agree internally on who decides when to copy someone senior, because the relationship owner will notice.

Three Past Due Invoice Email Examples

Placeholders are in brackets. None is tied to a day count; pick the one that fits the reader and the situation.

Example 1: To a contact you'll work with again

In some industries this reader is very specific. In legal, for instance, you'll often be writing to the other side's lawyer.

— Start of template —

Subject: [Their reference]: Invoice [number] past due

Hi [First name],

Quick note on [their reference]: invoice [number] for [amount] was due on [date], and I don't see a payment on our side yet. A copy is attached.

Could you let me know when it's scheduled to go out? If it's waiting on something from us, tell me and I'll sort it out this week.

And if someone else on your team handles payments for this one, I'm happy to send it to them directly. Just let me know who.

Thanks, and talk soon on [shared project or next matter].

[Your name]
[Title] · [Direct line]

— End of template —

Example 2: To an AP inbox that may not recognize the invoice

— Start of template —

Subject: Past due: Invoice [number], [their PO, vendor ID or matter], [amount]

Hello,

We haven't received payment for the invoice below and want to make sure it reached the right place.

  • Your reference: [PO, vendor ID, or matter or client name]
  • Our invoice: [number], dated [date]
  • Amount: [amount]
  • Original due date: [date]
  • Requested by: [the person on your side who engaged us]

The invoice is attached. You can pay by [methods or link]; remittance details are on the first page.

Could you confirm a payment date? If this isn't in your system, could you let me know who should receive it?

Thank you,
[Your name] · [Company] · [Email] · [Phone]

— End of template —

Example 3: When you haven't heard back

— Start of template —

Subject: Re: [Their reference]: Invoice [number] past due

Hi [First name],

Following up on my note from [day]. Is invoice [number] ([amount]) with you, or should I send it to someone else?

If it's easier to talk it through, I'm free for a 10-minute call [two time options].

Thanks,
[Your name]

— End of template —

The short follow-up is deliberate: one that repeats everything reads like a form letter, while a two-line question is easy to answer.

When Email Isn't the Next Step

Email works for some recipients and not others, as the firm in our example found. Signs it's time to switch: two notes without a reply, a bounce or a generic auto-reply, or a response from someone who doesn't handle payments. Then pick up the phone; our collections call script has lines for the switchboard, the wrong person and voicemail. If the account needs a formal step instead, see collection letter vs. dunning email.

Review Before You Send, Especially If AI Drafted It

The firm in our example wanted to collect faster but keep people in the loop in the right places. For past-due emails, that means a quick human check before anything goes to someone you'll work with again, whether a person or an AI tool wrote the draft:

  • Recipient and role: is this the relationship owner, the processor or the approver, and does the tone fit them?
  • Numbers: amount, dates and installment match your ledger and any payment plan.
  • Their reference: the one they actually use.
  • Promises and consequences: nothing you won't follow through on, and nothing your contract doesn't allow.
  • Confidential detail: nothing about one client or matter going to another party.

Which emails always get a person's review? First contact with a relationship owner, anything to an approver, and anything after a dispute or a broken promise to pay. Routine notes to an AP inbox can get a lighter check.

In Daylit, collection emails are drafted for your team to review, edit and confirm before they go out. Tone and sentiment detection on replies, and confidence checks before anything sends, are coming soon.

Putting It Together

Write for the person who'll read the email, lead with the reference they recognize, ask for one thing, and give them an easy way to tell you if you've reached the wrong person. Set the tone by the relationship, not the calendar, and have someone check the email before it goes. The invoice gets paid once; the relationship has to outlast it.

When should I send a past due invoice email?

Shortly after the due date, while the invoice is still easy to find on their side. How often to follow up after that depends on the account and your other channels; our guide to automated payment reminders covers cadence.

Who should a past due invoice email come from?

The person who owns the relationship, or someone writing for them with them copied. A sudden change of sender sends a message of its own, so make that change on purpose.

Should I add late fees to a past due invoice email?

Only if your contract or terms provide for them, and only if you'll actually apply them. See our collection letter guide for how to word fees and consequences.

Is a past due invoice email subject to CAN-SPAM?

A past-due email with no promotional content is generally a "transactional or relationship" message under CAN-SPAM: most rules don't apply, but sender and routing details must not be misleading. Adding promotions can change that, and B2B email is not exempt. This isn't legal advice.

Insights

You might also like...

VP of Finance pinning blank cards into three columns on a cork board
Credit Policy Template With Customer Risk Tiers: Criteria, Limits and Collection Rules per Tier
A credit policy template you can copy, plus a simple way to sort customers into risk tiers and set limits, terms and collection rules for each tier.
Read more
Credit Policy Template With Customer Risk Tiers: Criteria, Limits and Collection Rules per Tier
Accounts Receivable Automation
Controller holding a desk phone to his ear while waiting on hold at an office counter
Collections Call Script: What to Say When You Reach the Switchboard, Not the Payer
Most collection calls reach a main line, not the payer. Word-for-word scripts for the switchboard, wrong person, voicemail and payer, plus finding AP.
Read more
Collections Call Script: What to Say When You Reach the Switchboard, Not the Payer
Accounts Receivable Automation
AR specialist checking her phone at an office kitchen counter beside her laptop
Broken Promise to Pay: What to Do in the First 72 Hours (and When to Escalate)
A customer missed a promised payment. A 72-hour playbook to confirm, diagnose, re-commit and set escalation triggers — plus how to track every installment.
Read more
Broken Promise to Pay: What to Do in the First 72 Hours (and When to Escalate)
Accounts Receivable Automation
Book a free consultation with Daylit

Learn how to shorten your cash conversion cycle by reducing inventory levels, extending vendor payment terms, and accelerating customer collections.

Button
Button