Manual vs automated invoice follow-ups
Automating accounts receivable is usually pitched as a time saving. The more interesting question is what happens when the customer replies.
There is a point at which chasing invoices by hand stops being reasonable. It is later than most software vendors suggest and earlier than most owners admit.
Doing it by hand is fine for a while
With five or ten invoices outstanding, a person doing this properly beats any tool. You know the customers. You remember who said what. You can tell from the phrasing of a reply whether someone is stalling or genuinely waiting on their own approval chain. None of that is easy to encode.
The manual approach breaks down for a specific reason, and it is not volume exactly — it is context. It stops working when the answer to "should I chase this one?" requires going and reading a thread you have forgotten.
What most invoice automation actually does
The standard implementation is a reminder schedule. Day 7, day 14, day 30. Set the cadence, write the templates, and messages go out on time regardless of what else is happening.
That solves the wrong half of the problem. Sending on time was never the hard part. And a schedule that runs regardless of what else is happening is precisely the failure mode:
- It sends a day-14 reminder to a customer who replied on day 9 promising to pay on day 20.
- It sends a payment chase to someone who is disputing the invoice, turning a solvable disagreement into a fight.
- It nags a customer who paid yesterday, because the payment has not synced yet.
- It repeats itself, in slightly firmer language, at a person who already explained the delay.
The question that separates the two
When you are comparing approaches, the useful question is not "does it send reminders automatically?" Almost everything does. It is: what happens when the customer replies?
- Does the reply stop the sequence, or does the schedule keep running?
- Does anything read the reply, or does it just note that one arrived?
- If the customer promised a date, does the next message know that — and reference it?
- If the customer is disputing the invoice, does the tool refuse to send a payment reminder, or does it need you to remember to switch it off?
A tool that cannot answer those is a scheduler. That can still be worth having, but be clear about what you are buying: it saves you the typing, not the deciding, and the deciding was the expensive part.
A reasonable middle position
The arrangement most small businesses actually want is neither fully manual nor fully automatic. Something reads everything and keeps track. It proposes what to do. A person approves before anything is sent — at least until they trust it, and probably permanently for anything unusual.
That way you keep the judgement, which is the part you are good at, and hand over the remembering, which is the part you are not. And the tool should have hard limits it will not cross regardless of settings: never chase a paid invoice, never chase a disputed one, never write while a promise is still good.
When to bother at all
Honestly: not yet, if you have a handful of invoices and you are on top of them. The overhead of setting anything up will exceed the benefit.
It starts being worth it when you notice one of these — you have stopped being able to say from memory who owes you what, you have sent a reminder to somebody who had already paid, or you have realised an invoice went quiet two months ago and nobody noticed. Those are the symptoms of context exceeding what one person can hold, and no amount of discipline fixes them.
Common questions
- Should I automate invoice reminders?
- Automate the routine part, the first polite reminder on an invoice nobody has replied about, and keep a person on anything where the customer has said something. A reminder that ignores a reply is worse than no reminder.
- What's the risk with automated payment reminders?
- Sending the next reminder on a timer after the customer has already answered: chasing someone who paid, who disputed the amount, or who promised to pay on Friday. That is the failure that damages relationships, and it is why Collectly reads replies before drafting anything.
Keep reading
- How to follow up on an unpaid invoiceA practical sequence for chasing an overdue invoice without damaging the relationship: what to say at each stage, and what to do when they reply.Read
- Why small businesses struggle with late paymentsMost late invoices are not refusals. They are stuck in approval chains, payment runs or the wrong inbox, and each cause needs a different response.Read