What actually goes wrong
Nobody forgets a project invoice. The work ends, you send the bill. A retainer has no ending, so the trigger has to come from somewhere else — a note in a calendar, a reminder on a phone, a habit. All three fail the month you are busy, which is exactly the month you most needed the money.
The second failure is quieter. You remember, but you copy last month's invoice and forget one field: the period still says March, or the number repeats. A duplicated invoice number is not a cosmetic mistake — sequential numbering is what makes an invoice series auditable, and a repeat breaks it.
What a recurring invoice has to get right
Four things, and they are the four that hand-copying gets wrong:
- A new number, in sequence. Not the old one, not a gap.
- The right period. If the line says Retainer — September, September has to be generated, not typed.
- Dates that move together. Issue date and due date both shift; the due date is issue plus your terms, not last month's date plus thirty.
- VAT as it is today. If the client's status changed — they registered, they moved, reverse charge now applies — the copy carries the old treatment forward silently.
A worked example
A retainer of €1,200 a month, invoiced on the 1st, payable in 14 days. In Flowzivo you create the first invoice once, tick Recurring · monthly, and save. On 1 October the dashboard says the next one is due; one click issues it as INV-2026-0043 — the number after the last one you actually sent, not the one after the template — dated 1 October, due 15 October, with the line reading Retainer — October 2026.
Twelve months of that is €14,400. One forgotten month is 8.3% of the year's retainer revenue, and it is the cheapest 8.3% you will ever recover.
Automatic, but not silent
There is a design choice here worth naming. Some tools issue and email the recurring invoice on their own while you sleep. That sounds better than it is: the month the client paused, or the scope changed, or you were mid-negotiation on the rate, the invoice goes out anyway and you find out from an annoyed reply.
Flowzivo reminds instead of sending. The dashboard tells you a recurring invoice is due; issuing it is one click, and skipping it is doing nothing. You keep the thirty seconds of judgement that stops the awkward conversation.
Set one up
Create the invoice normally — client, line, amount, VAT treatment.
Monthly, quarterly or yearly. The period wording is generated from the date.
The dashboard raises it when it is due. One click issues it with the next number.
Send the invoice instead of reading about it
The demo is the real product with example data in it. No account, nothing to install, and anything you add you can keep when you sign up.
No account to look around. Example data, and anything you add is yours to keep.
Questions
Does the invoice number continue from my other invoices?
Yes. Recurring invoices draw from the same sequence as everything else, so the series stays unbroken even if you issue a one-off invoice in between.
What if the amount changes for one month only?
Edit that month's invoice before issuing it. The change applies to that invoice, not to the recurring setup, so the following month goes back to the agreed amount.
Can I pause a retainer for a month?
Yes — just do not issue it. Nothing is sent automatically, so a skipped cycle is simply a cycle you did not confirm. The next one appears as usual.
Does it handle quarterly and annual billing?
Monthly, quarterly and yearly. The period label on the line follows the cycle, so a quarterly invoice reads as a quarter, not as three months typed by hand.