The 3-Stage Reminder Sequence

Across the invoicing and collections guidance published by Harvest, FieldPulse, and Emagia's AR automation research, the same basic sequence recurs with only minor timing variation: a courtesy reminder before the due date, a due date notice, and a series of escalating reminders afterward, typically at 7, 14, 30, and 60 days overdue. Yonovo's 2026 guide to invoice reminder timing notes that reminders sent before the due date consistently produce the highest response rates and set a professional tone for the rest of the relationship, and recommends 3 to 4 total reminder touches before escalating to a different channel or contact.

Stage	Timing	Tone	Purpose
Pre due courtesy notice	3 to 7 days before due date	Friendly, low pressure	Confirm the invoice was received and catch any dispute before it becomes an excuse for delay
Due date notice	On the due date	Neutral, informational	Restate the amount and payment link with no urgency language
First overdue reminder	7 days past due	Polite but direct	Confirm the invoice is now overdue and ask for a payment date
Second overdue reminder	14 to 30 days past due	Firm, still professional	Reference the earlier reminders and request a specific response
Partner escalation	30 to 60 days past due	Direct, relationship level	Move the conversation from email to a phone call or direct message from a partner

A structured reminder process matters because most late payment is not driven by a client's inability to pay. PYMNTS reporting on B2B payment delays found that a late invoice typically traces back to an operational cause, such as an invoice that does not match the engagement letter, a procurement dispute, or a slow internal approval chain, rather than the client being unwilling to pay. A well timed reminder sequence catches most of these causes before they turn into a 60 day overdue balance.

What to Say Before the Due Date

The pre due reminder should do exactly one job: confirm the invoice arrived and give the client an easy way to flag a problem before the due date passes. It should not apologize for sending it. Emagia's AR automation guidance recommends pre due reminders roughly 1 to 3 days before the due date, framed as a courtesy rather than a request.

A workable structure for a consulting firm's pre due email:

• Subject line that includes the invoice number and due date, not a vague phrase like "Following up"
• One sentence confirming the engagement or project the invoice relates to
• The amount, due date, and a direct payment link
• A single line inviting the client to flag any question about the invoice before the due date

This is also the point where a mismatch between the invoice and the engagement letter, one of the most common non client causes of delay covered in How Do Consulting Firms Reduce DSO Without Hiring an AR Person?, gets caught early instead of surfacing as a dispute after the due date.

What Changes After 30 and 60 Days

By the second overdue reminder, the tone should shift from a nudge to a direct request for a specific response. Invoicito's 2026 guide to unpaid invoice reminders makes a point worth taking seriously for consulting firms specifically: excessive apologizing in a reminder email trains clients to deprioritize it. A firm that has delivered the work is entitled to be paid on the terms it agreed to, and the email should read that way, polite but not tentative.

At 30 days, most receivables guidance, including Invoicito's and Yonovo's, converges on the same recommendation: if three or four email attempts have not produced payment or a response, it is time to change channel, not tone alone. That means a phone call or a direct message rather than a fifth email that repeats the same request.

At 60 days, the reminder should reference the contract terms directly, restate any late payment or interest provisions in the engagement letter, and set a firm expectation for resolution. This is also the point where firms typically reassess whether to continue extending open terms to that client on future engagements.

When to Involve the Partner Directly

Automated reminders should carry the sequence through the first 30 days. Beyond that, a message from the partner or engagement lead, not the AR system, tends to move the needle, because it signals the account has the firm's attention at a relationship level, not just a billing level.

A short, direct message from the partner at the 30 to 60 day mark should do three things: acknowledge the working relationship, state the outstanding amount plainly, and ask for a specific payment date rather than a general assurance. This is also a natural point to offer a payment plan if the client is facing a genuine cash constraint, since a structured plan collects more reliably than a series of ignored reminders.

Getting the reminder cadence right closes one part of the DSO equation. The other part is knowing whether your resulting DSO is actually healthy for a firm your size, which is covered in What Is a Healthy DSO for a Consulting Firm? Benchmarks by Firm Size, and how your billing structure itself contributes to collection speed, covered in Milestone Billing vs Retainer Billing: Which Gets Consulting Firms Paid Faster?

Frequently Asked Questions

What makes a payment reminder email effective for consulting clients?

Effective payment reminders for consulting clients are short, reference the specific invoice and engagement, and escalate in tone gradually across a pre-due, due-date, and overdue sequence rather than repeating the same message.

When should a consulting firm send the first payment reminder?

The first reminder should go out 3 to 7 days before the invoice due date as a courtesy notice, not after the invoice is already late. Reminders sent before the due date consistently get the best response and set a professional tone.

When should a partner get personally involved in collections?

Most receivables professionals recommend involving a partner or senior relationship owner once an invoice passes 30 days overdue, after the automated pre-due, due-date, and early overdue reminders have not produced payment or a response.