The invoice is not the problem. The fourth reminder is.
Chasing unpaid invoices is unpleasant for a specific reason: the first reminder is easy, the second is awkward, and by the fourth you are managing a relationship rather than a payment. What actually helps is not automation that fires and forgets — it is having the message already written, dated, and correct, so the only thing left is deciding to send it.
The job itself
Eleven thousand outstanding across four clients, two of whom you will work with next month, and no appetite for the conversation.
Nobody knows what has been sent
The first reminder went from a mailbox, the second from a phone, and the third was a conversation. The invoice record shows none of it, so the fourth message repeats the second.
The tone is the hard part
Writing a chase that is firm, warm and specific takes ten minutes of drafting for a message that reads as if it took thirty seconds.
Late means different things
Fourteen days late from a client who always pays in twenty is not the same as fourteen days from one who has gone quiet. Treating both with the same template is how you lose the good one.
What this changes
Three specifics, rather than a feature list
It knows what is actually late
Invoices carry a due date and a status. Overdue is computed rather than remembered, per client, and it is what the operator acts on rather than a calendar reminder you set once.
The reminder is drafted, dated, and specific
It names the invoice, the amount, the date it was sent and the date it was due, addressed to the contact designated for that client. No template variables left in it, and no guessing.
Sending stays yours
An outbound message to a client is a write, and a write waits for approval. The database refuses to let email be sent unattended — not as a preference, as a constraint.
Why "automatic dunning" is the wrong shape here
Software that fires reminders on a schedule works for a business with ten thousand small customers and no relationships. An agency has fifteen clients and every one of them is a relationship: the difference between a good reminder and a bad one is knowing that this client’s finance person is away, or that the work in question is still being argued about.
So the operator does the part that has no judgement in it — noticing, gathering, drafting, dating — and hands you the part that does. What you get at nine in the morning is a message you can read in six seconds and send, not a decision you have to make from scratch.
What the drafted chase contains
- The invoice number, the amount and the currency, read from the invoice rather than retyped.
- When it was sent, when it was due, and how many days that is.
- What it was for, in the words used on the invoice itself.
- A next step that is specific — a date, a payment link, or a person to ask.
And a tone that stays yours: the draft is written against how you have written to that client before, not against a generic dunning template that arrives sounding like a bank.
The ceiling that cannot be turned off
External email has a hard ceiling in this product: it cannot run unattended. That rule is enforced where the autonomy settings are stored rather than in the screen that shows them, which means no plan, no setting and no clever workflow can raise it.
It is worth being explicit because the opposite is a common feature. A tool that can email your client on its own is one bad draft away from an incident you cannot recall, and a payment chase is exactly the message where a wrong one costs the relationship.
What happens after it is paid
The invoice settles against the record, the client’s balance moves, and the forecast updates — so "what are we owed" is a number you read rather than an exercise you perform. Retainers that recur produce the next invoice as a draft on their own cycle.
Questions people ask about this
Will it email a client without me?
No. External email is the one capability with a ceiling in the database: it cannot be set to run unattended by any plan or setting. Reminders are drafted and wait for a person.
How does it know an invoice is late?
From the due date on the invoice and its status. There is no separate calendar to maintain — an invoice with a due date in the past and no payment against it is what "late" means.
Can it handle a payment plan or a partial payment?
Invoices carry their own status and amount, and a part-paid invoice is not treated as settled. What it will not do is invent a schedule you have not recorded — if you agreed three instalments, that agreement has to exist as invoices.
Does it charge the card automatically?
No. Neoflow bills you for Neoflow; it does not take your clients’ money. Payment links point at your own arrangements, and nothing in the product moves a client’s funds.
Last reviewed on . Something out of date or wrong? Tell us and it gets fixed.
Sigue leyendo
Point it at one client and see what it prepares.
Connect a mailbox, designate the contacts for a single client, and read what the operator has drafted by tomorrow morning. Free to start, and nothing leaves without you.