ChaseAI

Past Due Invoice Notice (Formal Email Template)

Use this past due invoice notice template for 30+ day overdue balances when you need a clear, formal message with documented details.

Alex Morgan

Invoice & payments writer at ChaseAI

A formal past due notice email should read like a clean account summary plus required next step. Keep it factual, short, and easy for AP or finance to process.

The formal template (with invoice summary table)

Subject: "Past due notice: invoice #[number] - action required"

"Hi [Name/AP team], this is a formal notice that invoice #[number] remains unpaid. Please review the invoice summary and complete payment by [deadline/timezone]."

Field Value
Invoice Number#[number]
Invoice Date[date]
Original Due Date[date]
Days Overdue[X]
Amount Due[amount]
Payment Link/Details[link/details]

"If payment has already been made, please share remittance details so I can update records. If there is any processing issue, reply today with the blocker and expected resolution date. Thank you, [Your Name]"

"Not received" / dispute wording

If the client says "not received" or raises a dispute, keep wording neutral and evidence-based:

  • Not received: "Resending invoice #[number] and attachments for confirmation."
  • Missing PO: "Please share PO reference so I can update and reissue if needed."
  • Amount dispute: "Please specify disputed line item so we can resolve quickly."
  • Vendor details issue: "Sharing legal entity and remittance details again for setup."

This keeps your overdue invoice notice professional while moving the thread toward concrete resolution.

Documentation checklist

  • Invoice PDF (current and correct version).
  • PO number or written no-PO confirmation.
  • Delivery/milestone proof if services were delivered.
  • Payment terms excerpt (late fee, due date, escalation terms).
  • Remittance details and pay-now link.
  • Previous reminder trail in the same thread.

Formal notices work best when AP can process the payment from one email without asking for missing docs.

What to do next (AP, final notice)

After this notice, use a strict decision path:

  • If AP confirms payment date, monitor and follow up only if missed.
  • If AP requests missing data, send full packet same day.
  • If no progress, escalate to final notice by your set deadline.

For AP-specific language use email to accounts payable overdue invoice. For end-stage escalation use final notice unpaid invoice email.

Quick tips

  • Use "formal notice" wording only after earlier reminders.
  • Include summary table for faster AP handling.
  • Set one deadline with timezone.
  • Keep all communication in a single thread.

Timeline: formal notice to escalation

gantt
    title Past Due Notice Escalation
    dateFormat  YYYY-MM-DD
    axisFormat  %d %b
    section Sequence
    Friendly reminders        :d1, 2026-04-01, 13d
    Firm reminder             :d14, 2026-04-14, 16d
    Past due formal notice    :d30, 2026-04-30, 10d
    Final notice window       :d40, 2026-05-10, 5d
    Post-final escalation     :d45, 2026-05-15, 1d

Automate

Generate first reminder through formal notice and final escalation from one invoice using the overdue invoice sequence generator.

  1. Upload invoice details once.
  2. Generate staged reminders with tone progression.
  3. Set timing, deadlines, and escalation rules.
  4. Track replies and payment completion.

Automate formal past-due notices

Build a complete reminder sequence from first nudge to final escalation in minutes.

Frequently asked questions

Most teams send a formal notice once an invoice passes 30 days overdue or after repeated reminders are ignored.