Get paid · Uniwor resources
Payment reminder emails that are clear, useful and human.
Make it easy for your customer to identify the invoice and tell you what happens next. Use these templates as a starting point, then adapt them to the actual payment status.
- 3 copyable templates
- Follow-up checklist
- Invoice context
By Uniwor · Updated

A clear starting point
How do you write a payment reminder email?
A useful payment reminder identifies the invoice, amount and due date, provides the agreed payment instructions and asks for a clear next step. Check whether payment has arrived before sending it. Keep the message factual and leave room for the customer to explain a processing issue or dispute.
The templates below are original examples for routine business correspondence. Replace every placeholder, verify payment details and choose timing that fits your agreement and relationship. They are not legal demands or automated Uniwor messages.
What to look out for
A reminder should remove uncertainty.
The message has no identifying details
“Please pay your invoice” makes the customer search for context. Include a recognizable reference, due date and outstanding amount so the recipient can check the record or forward it to the correct person.
The reminder arrives after payment
Check the latest payment information before contacting the customer. If there may be processing time, invite them to share the payment date or reference rather than assuming nothing has happened.
A real issue is treated as silence
A missing reference, billing query or disputed item needs a different response from an overlooked email. Ask whether anything is preventing payment and give the customer a straightforward way to raise a question.
Put it into practice
Choose the reminder for the situation
These stages are examples, not a fixed collection schedule. Use your agreed terms and current information.
| Situation | Purpose of the message | Check first |
|---|---|---|
| Before the due date | Make the upcoming payment easy to identify. | Invoice was sent correctly and terms are agreed. |
| On the due date | Confirm the amount due and invite any processing questions. | Payment has not already been received or confirmed. |
| After the due date | Ask for an expected payment date or an explanation. | The invoice is genuinely overdue and not under an unresolved dispute. |
| Customer reports a problem | Clarify the issue and agree a next step. | The message is routed to someone who can resolve the query. |
Do not add penalties, interest or legal threats unless you have confirmed the contractual and legal basis with an appropriate adviser.
A practical example
Example: follow up on an invoice without escalating the tone
Invoice INV-1042 is overdue and the business has not confirmed payment. A useful message creates a path to an answer.
Identify
State INV-1042, the outstanding amount and the agreed due date. Reference the original invoice or provide it through your approved process.
Ask
Request the expected payment date, or invite the customer to explain anything preventing payment.
Acknowledge
If payment has been made, ask for the date or reference so you can check your records.
The immediate objective is useful information and a clear next step. Repeating a stronger version of the same email may not resolve the underlying issue.
Before the due date
On the due date
After the due date
Your next steps
Build a payment follow-up routine you can sustain.
- 01
Review current status
Check the invoice, due date, outstanding amount and recent correspondence. Confirm the billing recipient before preparing the message.
- 02
Personalize the reminder
Choose the appropriate template and replace every placeholder. Use verified payment instructions and a factual tone. Have the responsible person review any unusual situation.
- 03
Record the response and next step
Keep the promised date, question or dispute visible in your collection process. Recheck status before the next contact rather than repeating the same message blindly.
From learning to doing
Support payment follow-up with Uniwor
Uniwor’s published features include payment tracking and reminders. Use them as part of an agreed invoice-review routine so outstanding payments receive consistent attention alongside the rest of your business administration.
- Invoicing and payment tracking
- Reminders to support customer follow-up
- Business records alongside expense tracking
Your questions, answered
Payment reminder email templates: FAQs
Practical answers to help you choose your next step.
How do I politely remind a customer to pay?
State the invoice reference, amount and due date, then ask for payment or an expected payment date. Offer help with any billing question and acknowledge that payment may already be processing.
What should a payment reminder subject line say?
Use a clear subject such as “Reminder: invoice [number] due [date]” or “Payment follow-up: invoice [number]”. Avoid misleading urgency or language that does not match the current status.
When should I send a payment reminder?
Choose timing around the agreed terms, customer relationship and current payment information. A pre-due reminder may be helpful in some workflows, while overdue follow-up should begin with a status check.
Can I copy and use these email templates?
Yes. Use the copy buttons or select the text, replace the placeholders and check every detail before sending. The examples are for routine correspondence and are not legal notices.
Can Uniwor send these exact emails automatically?
Uniwor describes payment reminders, but its public feature list does not confirm support for these exact templates or scheduling rules. Ask the team to demonstrate the available reminder settings.
Sources and further reading
General business guidance, with original examples from Uniwor. Product capabilities are based on Uniwor’s published features and plan comparison.
- Office of the Small Business Commissioner: payment process guidance
Background on improving payment processes. The templates on this page are original, not copied from this guidance.
- Uniwor features · Current plan comparison
