The Job That Reinvents Itself Every Year: Templating Recurring Work
Compliance work repeats on a schedule you already know. Here's how to turn that predictability into recurring jobs that generate themselves — steps, fees and all.
Most compliance work is not new work. It is the same work, again. The BAS you lodge for a client this quarter looks almost identical to the one you lodged last quarter. The individual return you prepare in November is the same shape as the one you'll prepare next November. The FBT return, the year-end financials, the ASIC annual review — every one of them arrives on a schedule you can see coming from months away.
And yet in a lot of practices, each of these jobs is created from scratch when someone remembers it exists. A partner glances at a list, thinks "we should probably start the Smith return," and opens a blank job. The checklist is rebuilt or copied from a half-remembered version. The fee is guessed at. The due date is looked up. Multiply that by a few hundred clients and you have a practice spending real hours re-creating work it has already designed.
Recurring work is a template problem, not a memory problem
The instinct in a busy firm is to solve this with reminders. Put a note in the calendar. Set a task for the third week of the month. Keep a spreadsheet of who's due when. But reminders only tell you a job should exist — they don't create it, scope it, or attach the steps to it. You still do all of that by hand, every cycle.
The better frame is to treat each type of compliance job as a product you've already built once. A quarterly BAS is a defined thing: it has a set of steps, a known fee band, a predictable turnaround and a due date that follows a formula. Once you've described that job properly, there's no reason to describe it again. The job should regenerate itself on its schedule — pre-loaded with everything it needs to start.
This is where recurring jobs earn their place in good account practice management software. Rather than a reminder pointing at empty space, you define the template once — the steps, the assignee, the estimated time, the fee — and set the cadence. Each quarter, each year, the next instance appears on the board ready to work, with the due date already calculated against the correct lodgment date.
What a good recurring template actually carries
A reminder carries a date. A proper recurring job carries the whole shape of the work:
- The steps. The checklist that turns "do the BAS" into a repeatable sequence anyone can pick up — request records, reconcile, review, lodge, invoice. Same steps every time means consistent quality regardless of who's holding it.
- The owner. Who does it, and who reviews it. Assigned before the job even appears, not decided in a scramble.
- The fee. The price you already agreed for this recurring service, so nobody re-quotes a job you've done fifty times. Priced compliance, not a round-number guess at invoice time.
- The due date. Calculated from the obligation itself — the correct BAS or lodgment date — not typed in from memory and not quietly wrong.
When all four travel with the job automatically, the act of "starting" the work becomes trivial. The thinking was done once. Everything after is execution.
Productising follows naturally
Once your recurring work is templated, you're most of the way to productising it — and productising compliance is where the margin lives. If a quarterly BAS is a defined job with defined steps and a defined fee, you can offer it as a package with a clear price. Clients understand what they're buying. Staff understand what they're delivering. And you understand your capacity, because you can count the instances rather than guess at the hours.
This is a very different way to run client accounting than treating every engagement as bespoke. Some work genuinely is bespoke — the advisory conversation, the restructure, the one-off problem. But the compliance base is not, and pretending it is just costs you time. The firms that grow comfortably are usually the ones that have drawn a firm line between the two: they productise the repeatable work so it runs almost on its own, and they spend their scarce attention on the work that actually needs a human to think.
The connection to everything downstream
Recurring templates also quietly fix problems that show up much later. When the job carries its fee, you don't discover a write-off at invoice time — the price was set before the work started. When the steps are consistent, onboarding a new staff member is faster, because the checklist teaches them the process. When the due date is calculated from the real obligation, you don't find out about a deadline after it's passed.
And because good accounting client management software keeps the work, the client record, the invoice and the compliance calendar in one place, the recurring job doesn't sit in isolation. The BAS job that regenerates each quarter can pull the client's details, sit on the same board as everything else you owe them, and flow through to an invoice attached to the actual work — not re-keyed into a separate system afterwards.
Where to start
You don't need to template everything at once. Start with your highest-volume recurring job — usually quarterly BAS or annual individual returns — because that's where the wasted re-creation adds up fastest. Write the steps down properly, once. Agree the fee band. Confirm how the due date should be calculated. Then set it to recur, and let the next instance appear on its own.
The first cycle after you do this feels almost anticlimactic. The job simply shows up, ready, and someone picks it up and works it. No blank slate, no rebuilt checklist, no re-quote. That quiet is the point. The work you do a hundred times should cost you the design effort exactly once — and then repeat itself while you get on with the work that doesn't.
Compliance is predictable by nature. The systems around it should be too. When your recurring work regenerates itself with its steps, owner, fee and deadline intact, you stop re-inventing the job every year — and start running a practice that scales on process rather than memory.