The Invoice That Repeats Itself, and the Client It Forgets
A monthly retainer for forty clients used to be forty invoices somebody created by hand. It is now forty templates and a daily run. The failure mode of recurring billing is still not that one invoice is wrong. It is that one is missing — and the run can only bill the clients it was told about.
Some billing errors cost you accuracy. A missing invoice costs you revenue, and it does so silently, because nothing outside your own records notices an invoice that was never raised.
The position, up front
Recurring invoices are built: a template per client with its lines, a cadence, a start and an end, and a daily run that raises each period once, catches up periods it missed, and tells the template’s owner when one fails. What the run cannot know is a client who was never given a template. If a material part of your revenue is contracted and repeating, reconcile your templates against your client list monthly — because the system will not tell you that client thirty-seven was never set up, and neither will client thirty-seven.
The asymmetry that makes this expensive
Consider the two ways a manual invoicing process fails.
An invoice raised wrongly gets found. The client reads it, disagrees, and calls. The correction is annoying and it happens.
An invoice not raised at all is found by nobody. Your client does not chase an invoice they never received. Your ageing report cannot show a receivable that was never created. Your revenue for the month is simply smaller, and it looks like a smaller month.
Every other error in invoicing has somebody on the other side who wants it corrected. A missing invoice has nobody at all.
That asymmetry is why recurring billing exists as a feature category, and it is why a manual process for repeating revenue needs a control that a manual process for one-off revenue does not.
What the product gives you to work with
A recurring invoice template: a customer, lines, a cadence, a start date and an optional end date. A daily run raises the invoice for each period that has come due — once per template per period, ever, so a re-run, a crash or a button pressed twice cannot bill a client twice. Periods missed while the run was down are raised and dated to their own period. A period that fails is recorded as failed, retried the next day, and reported in the bell to whoever set the schedule up.
Each template chooses whether its invoices are issued and emailed straight away or left as drafts for review, and every template keeps a history of its runs. Numbering is handled properly underneath: a sequence per organisation, per document type, per prefix and per year, with no gaps and no collisions even when the run and a person invoice at once.
What stays yours is the list of who should be billed at all. A template that exists will not be forgotten; a client nobody set up has no template to forget.
Why a Canadian services business hits this hardest
Because so much of the market here runs on contracted recurring revenue rather than transactional sales — managed services, retainers, maintenance agreements, monthly support contracts, subscription arrangements of every kind.
For that shape of business the invoice run is the revenue process. It is not an administrative task that follows the work; it is the moment the work becomes money, and it happens on the same day every month for the same list of people.
It is also, precisely because it is routine, the task most likely to be done in a hurry by whoever is available. Which is where the missing one comes from.
The control that closes it
A monthly check around the billing run
- Make the active templates the recurring client list. Not a spreadsheet beside them. One template per contract, with its amount and its cadence, owned by one person.
- Reconcile count against count, not amount against amount. Compare the number of active templates to the number of clients under contract. A total that looks about right is exactly how a missing client survives.
- Start with drafts. Let the run raise drafts for review until you trust the templates, then switch a template to issue on its own. The first time an unattended run bills a cancelled client, it has cost more than it saved.
- Add, pause and end templates at the moment the contract changes. The commonest cause of a missed invoice is not forgetfulness; it is a client who started in the middle of a month and was never set up.
- Read the bell. A failed period is reported to the template’s owner and retried daily; somebody should be the owner of every template, and still be at the company.
More we can add on top of the run
The template, the daily run, the draft-or-issue choice and the failed-period alert are built. What sits beyond them are the contract-shaped decisions.
A contract with a term and a renewal
A template that knows when the agreement ends and asks whether to renew it, rather than an end date somebody types.
Proration for a mid-period start or stop
A first and last invoice for part of a period, computed rather than edited by hand.
Clients under contract with no template
A list of customers flagged as recurring who have no active template — the omission the run itself cannot see.
We put scope on a public page and dates in a written quote. Tell us how many recurring clients you bill and how often the amounts change, and we will come back with a written scope, timeline and cost.
Scope recurring billingFour questions about recurring billing, for any vendor
Show me a template that generated an invoice last month.
A good answer sounds like
A template, a history of runs, and the resulting invoices.
What it actually means
Ours keeps a run history per template. Asking to see the history rather than the feature separates a working recurrence from a duplicate button.
What happens if a run fails halfway?
A good answer sounds like
A recorded state and a resumable run.
What it actually means
Half a billing run is worse than none, because nobody can tell which half. Ours records each period per template, and a failed one is retried rather than skipped.
Are invoices posted automatically or created as drafts?
A good answer sounds like
A choice, or a clear default.
What it actually means
Unattended posting is the option everybody asks for and regrets the first time a cancelled client is billed. Ours is a choice per template.
What tells me a recurring invoice was missed?
A good answer sounds like
An exception list.
What it actually means
The part of the feature that addresses the actual risk. Ours alerts on a failed period; a client with no template at all is the omission to check by hand.
What AWRA OpsHub does today
- Invoices with lines, tax per line, a currency, a due date, terms, and a snapshot of the financial context at the time.
- Sequential document numbering per organisation, per type, per prefix and per year, safe when several people invoice at once.
- Credit limits enforced at invoice creation and update, with a real hold and a snapshotted record of the decision.
- Payments applied against invoices, with ageing on receivables.
- Recurring invoice templates — a customer, lines, a cadence, a start and an end — with a daily run that raises each period once, catches up missed periods and keeps a run history.
- A failed period recorded, retried daily and reported in the bell to the schedule’s owner, so a month cannot be skipped silently.
- A choice per template between drafts for review and invoices issued and emailed on their own.
- Sales quotes and sales orders, so a commitment has a document before it has an invoice.
More we can add to your workspace
- A contract check beside the templates. It lists every client flagged as recurring with its active template, so a client the run never sees shows up on a screen. Commission it
- Subscription or contract entities with a term and a renewal. Commission it
- Automatic proration for a client who starts or stops mid-period. Commission it
Where we point you to a specialist
- The numbering is genuinely well built and it is the part of a manual run most likely to go wrong elsewhere. It does not go wrong here.
- A client left off the run costs revenue rather than accuracy, and it does so invisibly. That is why the mitigation is a count rather than a review.
- This is market-neutral. It is what any billing run does to repeating revenue; this is a market where repeating revenue is the dominant model.
Count your templates against your client list this month
One comparison, five minutes, and most organisations moving recurring billing onto templates find something the first time they try it. We will set up the templates and the reconciliation with you.
Set up the checkFrequently asked questions
Can invoices repeat on a schedule?
Yes. A recurring invoice template holds the customer, the lines, the cadence and a start and end date, and a daily run raises each period once — as a draft for review or issued and emailed, as the template says. Missed periods are caught up, and a failed one is retried daily and reported to the template’s owner.
What does the run not catch?
A client who was never given a template. The run bills every template faithfully; it cannot know about a contract nobody entered. That is why the monthly check is templates against the client list rather than invoices against last month.
What is the single most valuable habit here?
Counting. Each month, compare the number of active templates against the number of clients on contract. Reviewing amounts finds errors; counting finds omissions, and omissions are the expensive half.