Skip to content

PAYMENT REMINDERS

Payment reminder emails that leave room for a reply

Copy seven payment reminder emails for B2B service invoices, including overdue payments, AP routing, payment promises, disputes and receipt checks.

By Published 8 min read

THE SHORT ANSWER

What should a payment reminder email include?

A useful payment reminder states the invoice number, outstanding amount and currency, original due date, and one clear next action. Match the message to the client’s latest reply. A payment promise, a disputed milestone and an unanswered invoice each need a different response.

Link to this answer
HUNT’s fictional character in red reviewing a paper invoice beside a laptop.
HUNT marketing illustration. The character and scene are fictional.

Choose by situation, then check the facts

These are original templates for agencies, consultancies and other businesses invoicing clients. Replace every bracketed field, confirm the balance and use the payment instructions already agreed with the client. Only say an invoice is attached if you actually attach it.

Which payment reminder should you send?
SituationUse this templateBefore sending
Due date is approaching1. Before the due dateCheck receipt and the client’s AP requirements.
Invoice is late, with no known issue2. First overdue reminderRecheck payments and credits.
Your contact cannot arrange payment3. Find the AP ownerCheck the existing vendor or portal instructions.
Client has promised a payment4. Confirm a payment dateConfirm amount and an unambiguous date.
Client says they paid5. Check a reported paymentPause the normal chase and check receipt.
Client disputes part of the work6. Acknowledge a disputeRoute the issue to the project owner.
A follow-up or promised date was missed7. Firm request for a next stepVerify there is no new reply or payment.

Keep one thread where practical so AP can see the history. Put the invoice number in the subject, use a recognisable sender and ask one answerable question. Square’s payment-reminder guide also emphasises clear invoice details, the due date and easy access to the invoice. The templates here add specific responses to common service-business blockers.

1. Before the due date: remove an administrative blocker

Send this when an invoice has already been issued and the due date is approaching. A few business days ahead can give AP time to identify a missing purchase order or approval. The timing is a starting suggestion, not a universal rule.

the pre-due reminder

Subject: Invoice [number] — due [date]

Hi [name],

A quick check ahead of the [date] due date for invoice [number]: [currency and amount] for [service period or milestone].

The invoice is attached, with the agreed payment instructions. Is there anything your accounts-payable team needs from us to include it in the scheduled payment run?

If it is already approved and scheduled to arrive by [due date], no reply is needed.

Thank you,
[name]
[role and business]

For a monthly retainer, first confirm the agreed billing dates and payment terms, then use the service period, such as “September design retainer.” For project work, use the agreed milestone reference. Do not introduce new conditions or call a not-yet-due invoice overdue.

2. First overdue reminder: ask for a payment date

Use this after confirming the invoice is overdue under the agreed terms and no payment, promise or dispute is awaiting review. It is direct without guessing why the client is late.

the first overdue reminder

Subject: Payment date for invoice [number]

Hi [name],

Our records show an outstanding balance of [currency and amount] on invoice [number] for [service period or milestone], due [original due date]. I have attached the invoice for reference.

Could you confirm the date this balance is scheduled for payment? If an approval or invoice detail is holding it up, please let me know what is needed and who we should coordinate with.

If payment has already been sent, please share the payment date and reference so we can match it to the invoice.

Thank you,
[name]
[role and business]

An illustrative example: “Our records show an outstanding balance of USD 4,800 on invoice ST-104 for the August website support retainer, due 14 September.” Use the remaining balance after allocated payments and credits, not the original total.

3. Wrong contact: find the person who can move it forward

A client sponsor may love your work and still be unable to schedule payment. Ask for the correct AP route without blaming them or adding unrelated executives to the thread.

the AP routing request

Subject: Accounts-payable contact for invoice [number]

Hi [name],

I’m checking the payment route for invoice [number], [currency and outstanding amount], due [date], for [project or service period].

Could you introduce me to the person or AP team handling this invoice? If it needs a purchase-order reference, vendor setup or portal submission, please point me to the required process.

I can supply the invoice and supporting milestone details through the agreed channel. Please let me know if you would like to remain copied on the payment thread.

Thanks,
[name]
[role and business]

If the invoice has been rejected by a portal, log the rejection reason and fix that item. Sending another reminder to a project manager does not substitute for a required submission. Confirm any unexpected change to payment details through a known contact channel.

4. Payment promised: agree the next check

Use this after a client offers a payment date. Record the exact calendar date, amount and any condition. If the promise changes contractual terms, get internal approval before describing it as an accepted arrangement.

the payment-promise confirmation

Subject: Confirming payment timing — invoice [number]

Hi [name],

Thank you for the update. I understand that [currency and amount] against invoice [number] is scheduled to be sent on [full date]. Please confirm that I have the amount and date right.

We’ll check for receipt on [agreed check date], allowing for the payment method’s processing time. If the timing changes, please reply here so we can review the next step together.

Please share the remittance reference once payment is sent.

Thank you,
[name]
[role and business]

Pause routine reminders until the agreed check. If a client says “next Friday,” confirm the date rather than interpreting it silently. A promise is useful forecast context; it is not cash in the bank.

5. Payment reported: check receipt without chasing twice

Use this if the client reports payment but you cannot yet match it. Check your bank or payment records before requesting information they have already supplied.

the payment receipt check

Subject: Matching your payment to invoice [number]

Hi [name],

Thanks for letting us know payment has been sent. We’re checking receipt against invoice [number].

Could you share the payment date, currency, amount and remittance or transaction reference? Please do not send full bank account details.

We’ll pause the standard reminders while we check and update you by [date]. If we match the payment before then, we’ll confirm the remaining balance, if any.

Thank you,
[name]
[role and business]

Assign the check to a named person so the pause does not become indefinite. Once funds are verified, allocate them to the correct invoices and acknowledge any remaining balance. Do not keep asking for the full amount after a partial payment.

6. Scope disputed: acknowledge and route the issue

A disputed deliverable needs a project conversation as well as an accounting record. Use this to clarify the issue without conceding a credit, accepting liability or insisting that the whole balance is undisputed.

the dispute acknowledgement

Subject: Reviewing your question about invoice [number]

Hi [name],

Thank you for raising the issue with [specific milestone or line item]. I’ve asked [project owner] to review it against [agreed scope or approval record].

Could you confirm which line items and amounts you are querying, and the specific point we need to resolve? We’ll pause routine reminders on the disputed amount while the review is open and update you by [date].

If you consider any part of the invoice undisputed, please confirm that amount and its expected payment date separately.

Thank you,
[name]
[role and business]

Only promise the pause and review date if your team can honour them. Record the disputed amount separately from the outstanding balance. Use the overdue-invoice triage guide to assign evidence, ownership and a resolution step.

7. No progress: request a specific next step

A firm reminder can ask for a clear response without becoming a threat. Send this after checking the previous promise or reminder and allowing for agreed processing time. Replace the first sentence with the accurate history.

the firm payment follow-up

Subject: Response requested by [date] — invoice [number]

Hi [name],

Following [our message on date / the payment date you confirmed], our records still show [currency and amount] outstanding on invoice [number], originally due [date].

Please confirm by [response date] when this balance will be paid, or identify the specific issue preventing payment and who is handling it. The invoice and agreed payment instructions are attached.

If we do not hear from you, [account owner] will contact you to discuss the account and next steps under our agreement.

We would like to resolve this promptly and keep the project relationship clear.

Regards,
[name]
[role and business]

This is an operational follow-up, not a legal demand. Do not insert automatic late fees, suspension or legal consequences without checking the agreement, applicable rules and internal authority. An invoice being 30 days overdue does not, by itself, authorise every escalation.

Use a cadence with stop conditions

For an undisputed invoice with no reply, a reasonable starting workflow is a check a few business days before the due date, a first overdue reminder after reconciliation, then another contact after several business days if needed. Adjust it for agreed terms, local business days, payment runs and the client relationship. Sending all seven templates as a sequence would be a mistake.

  • Stop the regular sequence when a reply arrives; choose the next action from the reply.
  • Pause for a promised date, reported payment or dispute, and record who will check it and when.
  • Change the channel or contact when delivery fails or the recipient cannot help.
  • After a call, write down the agreed amount, owner and next date in the same record.
  • Before every send, recheck the balance and the latest conversation so two people do not chase the same invoice.

For a repeatable team process, use the agency accounts-receivable guide. If you are evaluating software to assist with this work, the AI invoice follow-up checklist covers reply handling and human controls.

Sources & editorial notes

Published by . Examples and workflows are illustrative, not customer results. Sources checked on .

Read our editorial standards and current product status. Have a correction? Contact HUNT.

THE NEXT STEP

Keep a consistent voice as the conversation changes.

Explore HUNT’s AI personas, invoice context and human controls through early access. The public demo is scripted; live outreach and reply delivery are still in development.

Request early access