How to remind a client about overdue payment after the due date passes

This page starts after the due date, when you need a real reminder sequence instead of a first invoice follow-up.

This guide owns the stage after the due date has passed. Once payment is late, your job changes from asking for status to running a controlled reminder sequence with stronger wording and clearer next-step pressure.

Core takeaways

• This page owns overdue reminders, not the first unpaid-invoice check-in.
• Overdue reminders should state the late status plainly and ask for a date.
• Each reminder stage should become firmer while staying commercially clean.

Start this page only after the due date has passed

This guide is not for the first unpaid-invoice follow-up. It starts when the payment is late and the reminder needs stronger structure.

• If the invoice is still open but not overdue, go back to the unpaid-invoice guide.
• If the due date has passed, say so directly instead of writing another status check.
• Once you are in overdue territory, each reminder should clarify the next consequence or next step.

Use a real overdue reminder sequence

The message should change with the stage of lateness, not stay stuck in the same tone.

• First overdue reminder: name the late status and ask for the payment date.
• Second reminder: ask for a confirmed date today and make the thread harder to ignore.
• Later-stage reminder: make the next action or boundary explicit instead of sending another generic nudge.

Use wording that fits the overdue stage

Overdue reminder wording should sound firmer than the first follow-up because the commercial fact has changed.

• First overdue version: "Invoice [number] is now past due, so I wanted to follow up directly on the payment date."
• Second reminder version: "Please confirm the payment date today so I can plan the next step clearly on my side."
• Avoid slipping back into soft check-in language that belongs to the earlier unpaid-invoice stage.

Move from reminder logic into execution

Once the payment is overdue, the cluster path should get more specific rather than more repetitive.

• Use the payment reminder template when you want copy-ready overdue reminder versions.
• Use the overdue invoice no-response scenario when the thread has gone quiet or prior reminders failed.
• Move sideways to the unpaid invoice guide only if you realize the invoice is not actually overdue yet.

Recommended scenarios

FAQ