Blog

Provisional and Terminal Tax: Automating the NZ Tax Agent's EOT Year

July 2026 · 5 min read · Industry Guide

Notebook illustration of a circular year dial with three instalment marks and a terracotta pointer
← Back to all posts

New Zealand's extension-of-time regime is a gift with a catch. Filing spreads across the year instead of bunching at a single deadline, but the price is a rolling memory problem: every client sits somewhere different in the cycle of provisional instalments, terminal tax true-ups and filing windows, and the agent carries the whole map. Standard-balance-date clients alone mean instalments in late August, mid-January and early May, terminal tax the following April for EOT clients, and a different overlay for every ratio-method or non-standard-balance-date engagement. Multiply by a few hundred clients and the map stops fitting in anyone's head.

Where the cycle actually bites

  • Instalment reminders sent generically, so clients pay wrong amounts or skip payments they misunderstood

  • Estimates that should have replaced uplift never revisited after a client's trading changed mid-year

  • Underpayment exposure accruing use-of-money interest quietly until the terminal tax wash-up surfaces it

  • The EOT list itself: who is filed, who is looming, who is about to lose extension status

None of these are knowledge failures. Every agent knows the dates. They are attention failures, and attention is exactly what a practice runs out of in season.

The automated cycle

Claude Cowork turns the map into a scheduled pulse. Reading the client list, each Xero file and the firm's records, it maintains the cycle continuously:

  • Ahead of each instalment date: the client-by-client list of who owes what under which method, with reminder letters drafted using each client's actual numbers

  • Continuously: trading-change flags, where a client's current-year figures have drifted far enough from the uplift assumption to deserve an estimate conversation

  • After payments: reconciliation against what was requested, so the underpayment conversation happens in weeks, not at wash-up

  • Always: the living EOT list, filed and unfiled, with the filing-window countdown per client

Every letter is a draft until a person approves it, and every number traces to the file it came from. Rates and thresholds move, use-of-money interest settings especially, so the skills are written to flag positions for review against current IR settings rather than assert them.

What stays with the agent

Estimates, method choices, anything that changes a client's tax position, and every interaction with Inland Revenue. The automation is the diary and the drafting hand, not the adviser. That split keeps the workflow inside professional obligations and, more practically, it is what clients are paying the agent for: the judgment about whether to estimate down is worth money precisely because the reminder about the date is not.

A tale of two Februaries

The difference shows sharpest in February, ahead of the year's most consequential decisions. In the manual practice, the second instalment has just passed, the admin team is still reconciling who paid what, and the clients whose trading collapsed in the spring are still sitting on uplift assumptions nobody has revisited, quietly building either an overpayment the client will resent or an underpayment accruing interest. In the automated practice, the pulse flagged those trading drifts months ago, the estimate conversations happened while they could still shape the third instalment, the payment reconciliation finished the week the money moved, and February's partner attention goes to the handful of clients whose situations genuinely need thought. Same clients, same law, same dates. The only variable is whether the cycle runs on software or on the memory of whoever has been at the firm longest, and one of those two resigns eventually.

Beyond the cycle: what the same setup carries

The provisional pulse rarely stays alone. The same deployment carries the 31 March year-end workflows, the document chase, workpaper preparation and reconciliation checks, because the cycle map and the compliance grind draw on the same folders and the same Xero files. Practices that start with the pulse usually add the chase loop within a month, at which point the two feed each other: documents arrive earlier, positions firm up sooner, and the instalment letters go out with numbers the agent actually trusts.

The arithmetic

Count the touches. Three instalment rounds across, say, 250 provisional taxpayers is 750 client contacts a year, each carrying ten to twenty minutes of look-up, drafting and sending when done by hand: roughly 190 hours of staff time, call it $30,000 AUD equivalent at charge-out, spent on contacts that are 90 per cent identical. The automated version reduces each to a review-and-approve. Add the avoided interest conversations, because underpayments surface early, and the avoided panic when the EOT list is questioned, and the pulse pays for the whole $3,500 setup several times over in its first cycle.

Setting it up between seasons

The natural deployment window is after terminal tax closes one year and before the first instalment round of the next. Configuration is mostly encoding what the firm already knows: which clients sit on which method, the reminder tone, the escalation point where a letter becomes a phone call. A fixed-fee Claude Cowork setup covers NZ tax practices with the same structure as the rest of our accounting deployments. Book a brainstorm call and bring your EOT list; if the pulse cannot make that list boring, it is not doing its job.

Ready to move from AI pilot to production?

We help mid-market Australian businesses deploy AI automations that actually reach production and deliver measurable ROI.