New Zealand's 31 March year end concentrates a practice's entire annual workload into one quarter in a way Australian firms, with their staggered July-to-May lodgement program, never quite experience. Every client's balance date, every set of annual accounts, every terminal tax position arrives in the same season, and the extension-of-time regime spreads the filing but not the preparation. This is the workflow-by-workflow map of what AI now absorbs from that season, and what stays firmly with the chartered accountant.
The season, honestly described
February and March: year-end tax planning conversations, provisional tax true-ups, and the last clean shot at client decisions before balance date
April onward: the document collection grind begins across the whole client base at once
Winter: annual accounts and IR3, IR4 and IR6 preparation in bulk, working the EOT list
7 April the following year: terminal tax for EOT clients, closing the loop on the balance year
The structural problem is bunching. A firm with 300 annual engagements does not have 300 evenly spread jobs; it has one mountain with a 31 March summit, and the traditional answers, overtime and triage, both degrade the work.
What Claude absorbs, workflow by workflow
The document chase: a live outstanding-items list per engagement built from what is actually in the client folder, with reminder emails drafted for review; the single highest-payoff automation in a bunched season
Extraction: bank statements, loan summaries and supplier documents read into workpaper-ready schedules, GST treatment suggested
Reconciliation first pass: bank, GST and payroll positions checked continuously from April rather than discovered in August
Workpaper preparation: lead schedules, tie-outs and movement commentary built from the Xero file in the firm's own template, with an honest exceptions page
Provisional tax pulses: who is on standard uplift, whose estimates need a conversation, and the reminder letters drafted with each client's actual numbers
What stays with the CA
Terminal tax positions, provisional tax estimates that depart from uplift, structuring advice, anything IR-facing, and every signature. The model is review-not-build: the agent prepares and flags, the accountant decides and files. That boundary is what keeps the workflow inside professional standards, and it is also simply where the value of a CA lives. Nobody pays a chartered accountant to retype a bank statement.
NZ-specific settings
Three local details matter in setup. Privacy: the Privacy Act 2020 principles govern client data, with IPP 12 covering cross-border disclosure, so the deployment uses scoped per-engagement folders, named connectors only, and business Claude accounts that do not train on firm data by default. Dates: the skills encode the NZ calendar, balance dates, EOT filing windows and provisional instalments, rather than inheriting Australian assumptions. And rates: use-of-money interest and thresholds change often enough that skills are written to flag positions for review rather than assert current rates. Verify the current IR settings when you configure; the automation should inherit your firm's view, not invent one.
A season with the automation running
Picture the same 300-engagement firm a year in. Through February the provisional pulse has already drafted the pre-balance-date letters, so the planning conversations happen while decisions can still change outcomes. In April the chase loop goes out across the whole base in a week, not the six weeks it used to take admin staff working down a spreadsheet, and documents start arriving while the questions are still fresh in clients' minds. Workpapers begin building themselves as folders fill, so by June the preparers are working an exceptions queue instead of a backlog, and jobs finish in the order documents arrived rather than the order someone remembered them. The EOT list stops being a source of anxiety because the morning pulse tracks it, and the following April's terminal tax run works off reconciliations that were checked continuously instead of reconstructed. Nothing about the season's shape changed; the mountain is the same size. What changed is that the firm stopped carrying it by hand.
The maths for an NZ practice
The reported benchmark from NZ firms that built their own automation is around seven hours per staff member per week during the season. Take a conservative half of that across eight staff for a 20-week peak and you recover roughly 560 hours; at typical charge-out rates that is well over NZ$100,000 of capacity, against a setup cost of $3,500 AUD plus subscriptions. Run your own numbers with your own book; the arithmetic survives a heavy discount.
Starting before the season starts
The right time to deploy is the quiet stretch before balance date, so the chase loop and workpaper skills are tuned on live files before the mountain arrives. A fixed-fee Claude Cowork setup covers NZ practices with the same structure as Australian ones: folders, connectors, first skills and a staff walkthrough, typically live within a week. Book a brainstorm call and bring last season's worst bottleneck; that is where we start.
