A repeating template that stopped
Xero has no paused state, so the only way to stop a repeating invoice is to delete it, and once deleted it leaves nothing behind. Nobody gets an alert. I notice the run that quietly stopped being billed.
I read your Xero file and tell you which of your regulars are still on the rate you set them years ago, what they would be on if you had moved with the award, and I write the letters. Read-only, and it never touches an invoice you have already sent.
No sign-in and nothing stored on the free check. It asks for one figure you already know.
Your accounting software chases what you sent. Your job software tracks what you scheduled. Neither answers the backward question: what was agreed, and is it still being billed at the price you agreed it at? On a book of recurring customers that question has no report behind it, in Xero or anywhere else.
Chaser, Paidnice and the rest automate collection on invoices that were raised. Good tools, and none of them look backwards.
Who your regulars are, what each is meant to pay, when that price last moved, and the day the ledger stops agreeing with the deal.
ServiceM8, Tradify, simPRO and friends know the job happened. They do not reconcile it to a recurring price.
Price rises do not usually fail for commercial reasons. They fail because the trigger lives in somebody's memory, and memory does not survive a busy June. That is a systems problem, not a discipline problem, and it is the kind of problem you can actually fix.
| A price you last raised in | Is behind the award by |
|---|---|
| June 2022 | 25.1% |
| June 2023 | 18.9% |
| June 2024 | 12.5% |
| June 2025 | 8.4% |
AN ESTIMATE FROM PUBLISHED AWARD RISES. NOBODY OWES YOU THIS.
Compounded from the Fair Work Commission annual wage review determinations, ex GST. Modern award rates, which are not the same figure as the National Minimum Wage. This year also carried a structural change to the lowest classifications, so a price pinned to entry-level labour moved by more than 4.75%. Whether you can raise a given customer, and how much notice you owe first, is a question about your agreement rather than about the award, and that is the part I read your file for.
Two of these read money straight off a document you already have. The other four are worked out from your own billing history and are labelled as estimates wherever they appear, because a figure that does not say what it rests on is a figure you cannot check.
Xero has no paused state, so the only way to stop a repeating invoice is to delete it, and once deleted it leaves nothing behind. Nobody gets an alert. I notice the run that quietly stopped being billed.
The relationship carried on and the invoices did not. Irregular billers are never called silent, and anyone you have archived in Xero never surfaces at all.
Every regular, with the month their price last changed and what the award has done since. This is the one that compounds, and the one nobody has a report for.
Remembering on 1 July is remembering too late if the agreement wants thirty days. I count backwards from the date and tell you before the window shuts.
They said yes, the work happened, and nothing was ever raised against it. Read from the quote and the invoice, not modelled.
Written up, never sent. Sitting in Xero where nobody looks at it. Also read, not modelled.
Every finding was opened in Xero and checked by hand. The confirmed recoverable money was zero, and the things it had flagged turned out to be customers who had left and were never archived. I fixed the guard and I am telling you about it, because a tool that finds leaks in a messy book and invents them in a clean one is worse than no tool at all: you cannot tell which one you are holding.
So the promise is not that I will find you money. On a well-kept book I will not, and I will say so plainly. What I can promise is that you will never again not know that a recurring template stopped, or that a customer is still on the rate you last set them.
There is one thing I cannot see, and it is worth knowing before you connect anything: a customer who left but was never archived in Xero looks exactly like one who is still with you and stopped being billed. I will not guess between those. Archive them and I stop counting them.
Per Xero organisation. You connect your own file. $468 a year against what a single 4.75% rise is worth on the work you already bill.
Ten client minimum. You hold the connections and the digests, and you get a quarterly statement you can put in front of a client with your own name on it.
There is no job-management tier and there will not be one advertised until that half actually ships.
I am not going to promise that. The first real book I ran this against came back with zero recoverable money once every finding was opened in Xero and checked by hand, and I would rather tell you that than have you find out on your own file. What it will do is tell you which of your regulars have not had a price rise, and that is a fact about your ledger rather than a claim about my software.
No. Those chase invoices that exist and they do it well. This looks at the invoice that was never raised and the rate that never moved. If you already run a chaser, this sits behind it rather than beside it.
Xero OAuth with four read-only scopes, and four collections: Contacts, Invoices, RepeatingInvoices and Quotes. No bank transactions, no payroll, no reports, no attachments. It cannot create, edit, send or delete anything in your Xero. That is enforced in the code rather than promised in a sentence: an authorise URL containing any scope outside that set will not build.
Sydney. Every read is logged, including mine, and you can see all of it. You can disconnect or delete everything yourself at any time without emailing me.
No, and it will not email your customers as you either. It tells you who is due, works out what the award has done since their rate last moved, and writes the letters. You read them, you decide, you send them.
Not yet. The request for a repeating-invoice report was raised in April 2022, carries 266 votes, and Xero currently has it marked as not in the pipeline. The underlying data is readable through the API, which is how this works at all.