Separate the two reasons an invoice goes unpaid before you write anything. A declined card is a technical failure and needs a link, not a reminder. Silence is an attention failure and needs a short message at a predictable interval, each one carrying the invoice and a way to pay it. Three well-timed messages recover more than ten anxious ones, and the difference between a chase that works and one that costs you the customer is almost always tone and stopping on time.
The instinct when an invoice ages past due is to assume something is wrong: the client is unhappy, the work is being questioned, the money is not there. That is occasionally true and it is rarely the reason.
The common reasons are duller. The card on file expired. The invoice landed on the day someone was travelling. It went to a person who does not pay bills, or into an accounts inbox that only gets opened on Fridays. In each of those cases the customer is not refusing you. They have simply not been reminded at a moment when paying was easy.
This matters because it changes what you send. A message written for a dispute opens with an apology and an offer to talk. A message written for an oversight opens with the amount, the invoice, and a button. The second one gets paid.
If you take card payments, a meaningful share of what looks like late payment is a card that declined. Expired cards, changed banks, a limit hit on the wrong day, a bank declining a recurring charge it does not recognise.
Those need a retry and a link to update the card. They do not need a reminder about the invoice, because the customer already agreed to pay it and believes they have. Sending a chasing email for a technical decline reads as an accusation for something that was not their doing.
Sort the list before you write to anyone. Failed charge on one side, genuinely unpaid on the other. They get different messages, and the failed-charge side is usually the faster money.
None of this is difficult. That is the problem with it.
Chasing works when it is relentless and it stops being relentless in the second week you are busy. The invoice ages, the message you would have sent on day three now needs an apology in front of it, and by the time you write it the conversation has become awkward enough that you put it off again. Debt does not get harder to collect because the customer changed their mind. It gets harder because the follow-up got late and then the lateness became the subject.
This is exactly the shape of work nobody gets hired for. It is not enough hours to justify a person and it is too consequential to keep dropping.
Pull your outstanding invoices into two groups: charges that failed for a technical reason, and invoices that were never paid. Everything after this depends on knowing which is which.
Retry a declined charge a few days later rather than immediately — many declines are temporary limits that clear. If it fails again, send a one-line message with a link to update the card and nothing else in it.
A short note a few days after the due date, a firmer one at two weeks, and a clear final one at thirty days that states what happens next. More than three trains people to ignore you; fewer leaves money on the table.
Every message should let the person pay from where they are reading it. A reminder that requires the customer to go and find the original invoice is a reminder that gets postponed.
If email is not landing, move to a text or a phone call. Keep the wording as neutral at day thirty as it was at day three. Changing channel signals seriousness; changing tone starts an argument you will have to climb back out of.
Write down now what happens at sixty days: pause the account, hand it to a collections service, or write it off. Deciding while you are annoyed is how a customer relationship ends over an amount that was not worth it.
The single worst outcome is a reminder that goes out after the money arrived. Whatever system you use has to check the payment status immediately before it sends, not when the sequence was scheduled.
Three scheduled messages covers most of what is recoverable without help: a few days after the due date, at two weeks, and a final one around thirty days. Past that, more emails rarely change the outcome and a phone call or a formal step usually does.
Only if the fee was in the agreement before the work started, and only if you will actually apply it every time. A late fee announced after the fact reads as a penalty invented to win an argument, and one you apply selectively is one nobody believes.
When two written messages have gone unanswered. Silence after two attempts usually means the messages are not reaching the person who can pay, and a two-minute call finds that out faster than a third email will.
Yes, provided the sequence reads the payment status before every send, uses the customer's name and the real invoice details, and stops on any reply. What makes automated chasing feel robotic is not that it is automated, it is that it keeps going after the situation has changed.
We're onboarding our first companies by hand. A person reads what you write and answers within a day.