An invoice reminder should help a customer pay the right amount through the right route. It does not need to sound like a threat. Before you write, check the invoice status, the agreed terms, and the person who handles accounts payable. Then send a short message that names the invoice, balance, due date, and next action. The examples below cover a reminder before the due date, on the due date, after a missed date, after a partial payment, and when an account needs a personal conversation. Adapt the timing to your contract and client relationship.
Key takeaways
- Reconcile payments and credits before sending any reminder.
- Give the invoice number, outstanding balance, due date, and a safe payment route.
- Use a lighter message before the due date and a direct request once it passes.
- Pause automation when a payment is disputed or a client has agreed to a plan.
- Log replies and promised dates so a new reminder does not contradict a conversation.
Check the account before following up
A reminder sent after the customer has paid can make a careful business look disorganized. Review the invoice record first. Check whether the invoice was actually sent, the contact received it, a payment is pending settlement, a credit note has been applied, or a partial payment changed the balance. If the customer pays by bank transfer, allow for the delay between their initiation and your reconciliation. Do not send a “past due” message based only on a dashboard badge when the ledger is stale.
Check the agreed due date and payment terms against the signed proposal or contract. Some customers require a purchase order number or a specific billing address before their accounts-payable team can process an invoice. If the original invoice missed that requirement, fix the invoice rather than treating the delay as a customer failure. Confirm the right recipient. The buyer who approved the work may not be the person who pays; copy the project sponsor only when needed and appropriate.
Use a consistent record for each invoice: number, issue date, due date, original amount, credits, payments received, remaining balance, customer billing contact, payment method, and the last conversation. This record can live in accounting software, provided the team actually updates it. A second spreadsheet with different balances creates more errors than it solves. Intuit’s current QuickBooks guidance distinguishes invoices that have been emailed and remain unpaid when it describes automatic reminders; check the rules of your own invoicing system before assuming every draft or imported invoice will be handled the same way.
Choose a sequence that fits the relationship
There is no universal reminder schedule. A common sequence is a courtesy note a few business days before the due date, a clear reminder on or soon after that date, then a personal follow-up if the balance remains open. Some clients have fixed payment runs, so a message one day after the due date may be unhelpful when the next scheduled run is known. Others need a prompt before a card expires. The timing should follow the contract, transaction size, and what you have learned about the payer.
Define which events stop the sequence. A cleared payment should stop it. A payment in transit may call for a temporary pause. A formal dispute, an agreed installment plan, a credit review, or a customer who has given a specific payment date should move to a human-owned path. Do not allow a generic automated “final notice” to run while an account manager is resolving the underlying issue. If you use a tool with automatic reminders, test those conditions with sample invoices.
Keep the tone proportionate. Before a bill is due, assume the client is organizing payment. Shortly after it is due, ask whether the invoice reached the right person and whether anything is missing. Later, say plainly that the balance remains open, request a payment date, and offer a way to resolve a problem. If an account needs escalation under your agreement, have the owner review the record and applicable terms first. A stronger message should be accurate and documented, not theatrical.
Template: a courtesy note before the due date
Subject: Invoice [number] due [date]
Message: Hi [name], a quick note that invoice [number] for [service or period] is due on [date]. The outstanding balance is [amount and currency]. You can view the invoice and available payment options at [secure invoice link]. If your team needs a purchase order, a different billing contact, or another detail to process it, please reply and I’ll help. Thank you, [sender].
This note works best when the invoice was sent earlier and the payer already knows what it covers. The link should lead to your actual invoicing portal or an approved payment route, not to a newly invented address in a template. If you attach a PDF, check that it is the current version and that the email does not expose unnecessary customer information. A courtesy note should never imply the customer is late before the due date.
Template: on the due date
Subject: Payment due today for invoice [number]
Message: Hi [name], invoice [number] for [service or period] is due today, [date], with [amount and currency] outstanding. Here is the invoice and payment route: [secure invoice link]. If payment is already in progress, please ignore this note or send the reference so we can reconcile it. If something on the invoice needs correction, reply here and I’ll look into it. Thank you, [sender].
Do not send both the pre-due and due-date messages if they would land within a day of each other for the same customer without adding value. The due-date note is useful when the account has a regular payment rhythm and the customer expects a reminder. It can be excessive if a person has just confirmed that payment was queued. The account record, not a rigid calendar, should decide.
Template: a first overdue follow-up
Subject: Follow-up on invoice [number], due [date]
Message: Hi [name], our records show [amount and currency] outstanding on invoice [number], which was due [date]. The invoice is here: [secure invoice link]. Could you confirm when payment is scheduled? If the payment has been sent, please share the date or reference so we can check it. If there is an issue with the invoice or the work covered, let me know and I’ll route it to the right person. Thank you, [sender].
“Our records show” leaves room for a reconciliation error while still stating the facts. Ask one clear question rather than stacking several demands. The message should come from an address that can receive replies and reach someone who can resolve them. A no-reply sender undermines the offer to help. If you manage a service project, coordinate with the account owner before contacting a senior sponsor about a small late balance.
Template: a partial payment or credit
Subject: Remaining balance on invoice [number]
Message: Hi [name], thank you for the payment of [amount] received on [date]. After applying it to invoice [number], the remaining balance is [amount and currency]. The original due date was [date]. You can review the current invoice record at [secure link]. If another payment or credit is in progress, please send the reference so we can reconcile it before sending another reminder. Thank you, [sender].
Partial payments can be intentional, a bank limit, a milestone agreement, or an accounting error. Do not claim the client failed to pay the whole invoice until you know which. If a credit is due, issue and apply it correctly, then send the adjusted balance. The template should use the current amount, not the original invoice total. Test the merge fields in your software because this is where careless automation most often produces a visibly wrong demand.
Template: a personal follow-up after repeated reminders
Subject: Can we resolve invoice [number] this week?
Message: Hi [name], I’m following up personally because invoice [number] still shows [amount and currency] outstanding after its [date] due date. I’d like to understand whether there is a billing issue, an approval delay, or a payment date we should record. Could you reply by [reasonable date] with the next step? The invoice is here: [secure link]. If it is easier to discuss, I can speak with you or your accounts-payable contact. Thank you, [sender].
Use this after a human has checked the record and earlier messages. The goal is to get an answer and resolve the issue. If your agreement allows late fees, service pauses, or collection steps, do not threaten them in an unreviewed template. Have the appropriate business and legal owners check the contract and the applicable rules before such a message is sent. A service relationship can be damaged by an escalation that is not supported by the facts.
Template: when the client has already promised a date
Subject: Confirming the plan for invoice [number]
Message: Hi [name], thank you for confirming that invoice [number] is scheduled for payment on [date]. I have noted that date against the [amount and currency] balance and paused the standard reminders until we can reconcile the payment. If anything changes, please let me know. I’ll follow up after [date] only if the balance is still open. Thank you, [sender].
This confirmation gives both sides one record of the plan. It also tells the client they will not receive contradictory automatic messages tomorrow. If the promised date passes, check settlement and contact the same person with the earlier agreement in view. Do not restart the whole generic sequence as if no conversation took place.
Write the message in your own voice
Templates are useful because they prevent omissions, not because every client should get identical wording. Keep the invoice facts fixed and adapt the opening to the relationship. A long-standing customer may appreciate a short direct note. A new buyer may need more explanation about what the invoice covers and how to reach billing. Use a real sender name or a monitored billing address. Avoid slogans, jokes about debt, or language that suggests the customer is acting in bad faith.
Make the subject easy to find later. Invoice number and due date are usually more useful than “Friendly reminder.” In the body, put the action near the top. A customer should not need to read three paragraphs to find the secure invoice link. If the invoice is disputed, ask for the specific item in question and route it to the project owner. Do not ask the payer to repeat information already in their reply or to send a copy of the entire agreement when your team has it.
Be careful with payment links. Use the link generated by your invoicing provider or a route already agreed with the customer. Do not paste bank details into a mass template. If payment instructions change, confirm them through a separate trusted channel and follow your business’s fraud controls. A reminder should never train clients to trust a surprise change of account details inside an email.
Use automation with a human exception path
Invoicing software can send scheduled reminders, but you need to understand its eligibility rules. Intuit’s QuickBooks Online instructions describe how to choose days before or after the due date, customize the subject and message, and send a manual reminder. They also say its automatic reminders apply to invoices already emailed through the product. Other systems have different rules. Test a sent invoice, draft invoice, partial payment, credit, disputed invoice, and payment recorded just before a scheduled send.
Decide who can change the automation. A marketer writing a friendlier message should not silently change the due-date trigger. A bookkeeper correcting a balance should know whether a queued reminder will use the new amount. Document the sender address, reply routing, templates, schedule, stop conditions, and owner. Review the list of reminders sent during the first week. Then sample it monthly or after a billing-process change.
Do not over-automate escalation. The first courtesy note can be routine; a later message about a large overdue balance may need an account owner’s approval. If the client reports a problem with the delivered work, pause collection automation and connect billing with the service team. Keep the payment record accurate while the issue is resolved. A good workflow preserves the relationship and the accounting trail at the same time.
Measure whether the sequence helps
Track days from due date to payment and the share of invoices paid on time, separated by customer type or service when useful. Look at the number of reminders sent per invoice, reply rate, disputes surfaced, and cases where a reminder went out after payment. The last measure is a quality check: even if collections improve, a high false-reminder rate is a warning. Do not claim the sequence increased cash flow unless you compare periods carefully and account for changes in client mix and invoice terms.
Review messages that get a reply. A request for a purchase order number suggests an intake problem. A complaint about the amount suggests the invoice was unclear. A client who wants a different billing contact suggests your CRM handoff is incomplete. Fix those upstream issues instead of sending more reminders. If repeated reminders rarely get a response, check deliverability, recipient accuracy, and whether the account manager has a better channel.
Keep a small sample of successful resolutions. Note the situation, the message, the reply, and the outcome, without turning private client details into a public case study. Use those examples to improve the wording and exception rules. The measure of a good reminder system is not how many emails it sends; it is whether accurate invoices get resolved with less avoidable friction.
A 30-day setup plan
Week 1: Review recent open invoices and map how payments, credits, and disputes are recorded. Identify the true billing contact and where the contract terms live. Pick a small set of invoice states for a pilot. Correct existing records before automation sends any message.
Week 2: Write the pre-due, due, and first overdue messages in your brand voice. Add fields for invoice number, service, outstanding balance, due date, and secure link. Test each merge field with sample data. Write the rules that pause reminders when a payment, dispute, or personal arrangement is recorded.
Week 3: Send or preview the messages for a small group under human review. Check the actual email received, sender and reply address, link destination, and balance. Watch for duplicate messages when an invoice moves between states. Ask the account owner whether the tone fits the clients involved.
Week 4: Enable only the parts that passed the pilot. Assign someone to monitor replies and reconcile payments. Review false sends, reply themes, and time to resolution. Keep personal escalation under a named owner and set a date to revisit timing after you have enough invoices to judge it fairly.
Watch: tracking an invoice and sending a reminder
Accounting Stuff’s August 2026 QuickBooks Online walkthrough shows where to see an invoice’s status, check the outstanding balance, send a manual reminder, and review the message before it goes out. It is a product demonstration, so confirm the menu labels in your own account. The video includes a paid-promotion notice; AdNxt did not make or sponsor it. Watch the original on YouTube.
Related AdNxt guides
- Compare invoicing software if you need a clearer billing and reminder workflow.
- Compare accounting software if reconciliation is the main bottleneck.
- Review CRM setup if billing contacts and project contacts are being mixed together.
Frequently asked questions
How many invoice reminders should I send?
Use the smallest sequence that helps customers act, often a courtesy note and a clear follow-up after the due date. The right number depends on the agreement, payment cycle, invoice size, and replies. Stop routine reminders when payment or a dispute changes the situation.
What should an overdue invoice reminder include?
Name the invoice number, service or period, due date, remaining balance, secure invoice link, and a clear request for a payment date or a billing question. Use a monitored reply address so the customer can resolve an error.
Should I send reminders automatically?
Automation can handle routine timing after the invoice data is reliable. Test partial payments, credits, disputes, and payments in transit. Keep later escalations and unusual cases under human review.