Back to blog
ArticleBlog / Workflow Automation
Jun 23, 20265 min readWorkflow Automation

Polite overdue invoice reminders for agencies: wording, timing and a log

Three overdue invoice reminder emails that keep the client, a timing that works for agencies, a Sheets log, and how Tensor drafts each reminder for you to send.

Written by Tensor AutonomousThe Tensor Autonomous team builds approved AI Action and workflow automation systems for service businesses.

Chasing an unpaid invoice is the email agency owners put off longest, because the client is also the relationship. Your invoicing tool can send a reminder, but its reminder sounds like a robot and lands in a billing inbox nobody reads. A short note from you to the person who hired you works better, if you remember to send it.

Here are the three reminders, the timing, and the log, then how Tensor Autonomous drafts them for you so that remembering is no longer the job.

Timing

  • Due date + 3: a friendly check. Assume it slipped.
  • Due date + 10: a direct ask with the amount and a date.
  • Due date + 20: a formal notice: what happens next, still polite.

The second and third exist so the first can be gentle.

Day 3

Subject: Invoice 2041 for September

Hi Sam, a quick note that invoice 2041 for September's work ($4,200) was due on the 3rd. If it is already on its way, thank you and ignore this. If anything about it needs changing, let me know and I will sort it out today.

Day 10

Subject: Invoice 2041: $4,200 outstanding

Hi Sam, following up on invoice 2041 ($4,200), now ten days past due. Could you let me know when we can expect payment? If a different due date or a split payment would help this month, I am happy to arrange it. The invoice and payment link are below.

Day 20

Subject: Invoice 2041: final reminder before we pause work

Hi Sam, invoice 2041 ($4,200) is now twenty days past due and I have not heard back. Under our agreement we pause new work when an invoice passes thirty days, which would be the 3rd. I would much rather not; please pay or reply by the 1st so we can keep things on schedule.

Say the consequence once, in your agreement's words, with a date. Do not threaten in the first two emails.

The log

InvoiceClientAmountDue+3 sent+10 sent+20 sentPaidNotes
2041Harbor Street Co.$4,200Oct 3Oct 6Asked about split payment

The log is what lets you be gentle: you know exactly how many times you have asked.

Tensor drafts the reminders

There is no Library starter for overdue invoices yet, so this is a responsibility you describe in your own words, which is how any job without a starter begins: "Read the invoices sheet; for any invoice 3, 10 or 20 days past due with no payment recorded, draft the matching reminder to the client contact in my words, with the invoice number and amount, and note the date in the sheet." Then put it on a schedule: weekdays at 8am, in your time zone.

From then on:

  • Each scheduled run reads the sheet and finds the invoices that have crossed a reminder date.
  • It drafts each reminder in your Gmail, in your words, with the invoice's details filled in. Nothing is sent by Tensor. You read, soften or sharpen, and send, so the message to the person who hired you stays yours. Each run's drafts and sheet changes wait for your approval unless you have set limits that cover them; sending never runs without asking.
  • It fills in the sent date on the invoice's row.
  • Every run leaves a receipt: the sheet it read, the drafts it made and the rows it wrote, read back and compared.

Marking an invoice paid is yours (or your invoicing tool's); Tensor reads the sheet, it does not read your bank. It does not promise a payment plan either; where a client asks for one, the draft says you will come back to them, and the question is in front of you.

Today this works in Gmail and Google Sheets. Microsoft 365 comes later.

Where to start

See it in a demo

Watch Tensor do a sample task (log an order, book an appointment or answer a rental inquiry), wait for your approval and hand you the receipt.

Try it live

Tagged in#invoice exception handling#workflow automation