The Job You Rebuild Every Year: Templating Recurring Work
If your annual compliance jobs get reassembled from scratch each cycle, you're paying for the same setup 200 times. Here's how to build the job once and roll it.
Think about the last BAS you started. Someone created a job, listed the steps, worked out who does what, added the client's due date, wrote the request email, and set a reminder to chase the docs. Now multiply that by every client, every quarter, every year. If each of those jobs is being assembled by hand — even partly — you're rebuilding the same machine hundreds of times a year.
Recurring compliance work is, by definition, the same job repeated. A quarterly IAS is the same shape whether it's client 12 or client 212. The problem isn't the work itself; it's that most practices treat each instance as a one-off. The template lives in someone's head, or in last year's folder, and it gets reconstructed every cycle by whoever happens to pick it up.
Why rebuilding costs more than you think
The cost isn't just time. When the job is reassembled from memory, three things happen:
- Steps drift. One preparer's tax return checklist has nine steps; another's has six. The review point that catches a common error is in one version and not the other.
- Quality depends on the person. A new staff member can't see how the job is supposed to run, so they invent their own version — and now you have a third variant.
- Nothing improves. When you fix a mistake this quarter, the fix lives in one job. Next quarter it's gone, because the next job was built fresh.
Standardising recurring work is the single highest-leverage move in a compliance practice. It turns "how does Sarah do the SMSF jobs?" into "here's how we do SMSF jobs," and it means the tenth year of a job is better than the first — because the template carries every improvement forward.
What a good recurring job template actually contains
A useful template is more than a name and a due date. Build it once with everything the job needs to run without a person deciding each time:
The steps, in order
List every stage from start to lodgment-ready, including the review and sign-off points. If a step is skippable for some clients, note the condition. This is the checklist that would otherwise live in someone's head.
Who does what
Assign roles, not names, so the template survives staff changes. Preparer, reviewer, partner sign-off. When the job spins up, the right people are already on it.
The client request, pre-written
The information you need from the client is the same every cycle. Write the request once — the document list, the wording, the portal link — so it doesn't get retyped or forgotten.
The timing rules
The template should know the obligation it's tied to. A quarterly BAS job should generate itself off the lodgment cycle, not because someone remembered to create it. The due date should track the client's actual obligation, and the internal deadlines should sit far enough ahead that the work doesn't hit the wall.
Build once, roll forever
The point of a template is that it repeats itself. In good account practice management software, you define the recurring job once and it generates each instance automatically on schedule — a new BAS job every quarter, a new tax return every year, each landing on your board with the steps, assignments and client request already in place.
This is where recurring work and productising your services meet. When a compliance service is a repeatable, templated job rather than a bespoke effort each time, you can actually price it as a product. You know what goes into an "Annual Company Accounts & Tax" package because the template tells you: these steps, this much review time, this request to the client. The menu you offer clients and the job that runs behind it are the same thing.
Finye is built around this. Your recurring jobs are defined as templates and roll onto your boards automatically, tied to the ATO and ASIC obligations they belong to. The steps, the roles, the client request through the portal — all set once, all carried forward. It's not a tax-lodgment tool; it's the system that runs the practice around the lodgment, so the same job done 200 times is done the same way 200 times.
Getting from ad-hoc to templated
You don't need to template everything at once. Start where the volume is:
- Pick your highest-volume job. Usually BAS or individual tax returns. This is where standardisation pays back fastest.
- Document one good instance. Sit with your best preparer, watch them do it once, and write down every step — including the ones they do without thinking.
- Turn it into the template. Load the steps, roles, request wording and timing into your accounting client management software so it's the default, not a suggestion.
- Let it generate the next cycle. Don't hand-create the next round. Let the template roll and see what breaks — the gaps show you where the head-knowledge was.
- Improve the template, not the instance. When you find a better way, change it in one place. Every future job inherits it.
The version number nobody argues about
When work is templated, there's a single source of truth for how a job is done. New staff learn the template instead of learning a person. Reviews get faster because the reviewer knows exactly what should have happened. And you can finally answer the question that's hard to answer in a busy practice: are we doing this the same way every time?
Recurring compliance is the backbone of most Australian firms. Treating each cycle as a fresh build is quietly expensive — in time, in quality, in the improvements that never stick. Build the job once, tie it to the obligation, and let it roll. The client accounting work doesn't change from year to year, so the job that delivers it shouldn't have to be reinvented either.