How to follow up on unpaid invoices: email and text templates

Before you send anything, check these six things

1. The right bill: invoice number, customer, service dates, and work description. An estimate awaiting approval is not an overdue invoice.
2. The current balance: subtract recorded payments and credits. Check for a pending payment before asking the customer to pay again.
3. The original terms: confirm when payment was actually due. Do not silently change that date when resending the invoice.
4. The recipient: make sure the bill reached the person who handles payment, not only the person who booked the job.
5. The conversation: look for a dispute, a promised payment date, or a question nobody answered.
6. The payment path: open the invoice link yourself and check the customer-facing amount and business identity.

Intuit’s past-due invoice guide similarly emphasizes checking invoice details and keeping communication records. If the document itself is unclear, fix that first; see our estimate-versus-invoice example.

Use a schedule you can actually manage

Here is an illustrative routine—not a legal deadline or a rule for every customer:

First working day after the due date

Verify the balance and send a friendly reminder through an appropriate, agreed channel.

About a week later, if there is no response

Check payment activity again. Ask the billing contact to confirm receipt or an expected payment date.

Still unresolved after another week

Put it in an owner-review list. Check delivery, scope questions, and prior agreements before choosing the next step.

Change the timing to fit your terms and relationship. A customer reply should interrupt the sequence. Do not stack automated emails, manual texts, and phone calls simply because each tool has its own reminder schedule.

Five payment follow-up templates

These are original examples to adapt, not notices of legal action. Replace every bracketed field and verify the balance before sending. Stripe’s payment-reminder guidance supports keeping the invoice reference, amount, due date, and payment instructions easy to find.

Only text the customer through a channel they have agreed to use. For automated messaging, confirm your provider permits the use case, retain the required consent, identify the sender, and honor opt-outs. Twilio’s policy, for example, requires consent and an opt-out instruction in the initial message. Having a phone number alone is not the same as permission. Do not send payment-card details or sensitive account information by text.

If a different payment schedule has already been agreed, reference that schedule instead of asking the customer to explain it again.

Only say reminders are paused after actually pausing them. This message acknowledges a concern; it does not resolve the balance or promise a credit.

Keep one follow-up record beside the invoice

Missouri State University’s Accounts Receivable office describes maintaining amounts owed, issuing statements, and communicating about account activity. That is an institutional example, not a small-business collection policy. The useful principle is to keep the money record and the communication history connected.

Fictional example: a $600 window-cleaning invoice has a confirmed $200 payment and $400 remaining. The customer questions one charge. The next action is “Trevor: review the disputed line item by Thursday,” not “send another $600 reminder.” Keep the $400 balance visible while the question is reviewed.

Track collected money separately from billed work. Missouri State’s efactory explains the distinction between income, cash flow, and cash on hand. A promise to pay should not make an invoice appear paid.

When should you stop the automatic reminders?

Pause and put a person in charge when a customer disputes the bill, a payment is processing, the recipient is wrong, or a payment arrangement needs review. Stop texts when the recipient opts out. A completed payment should close the reminder sequence; partial payments need an updated balance.

If repeated contact gets nowhere, review the agreement and records before deciding what happens next. Do not invent late fees, threaten legal action, or promise to suspend work based on a generic template. Formal collection steps and contract rights need advice appropriate to the situation.

The Pebble Creek approach: keep the next step visible

We built our own operating system around the lawn and property-care business because important information was getting scattered. Invoice follow-up has the same problem: the bill might be in one place and the customer’s explanation buried in a text.

A spreadsheet and your existing invoicing tool may be enough. If that handoff is breaking down, a custom business operating system can be scoped around the invoice, payment status, contact history, responsible person, and review queue. The goal is fewer missed steps—not more messages or a guarantee that every invoice gets paid.

For the customer-facing payment path, see how to accept online payments. To discuss your own follow-up workflow, start a conversation with Pebble Creek Media.