Trust accounting: How NZ specific regulations favour NZ Legal Practice Solutions.
NZ trust accounting regulations are the core reason global PMS vendors find it hard to enter and support the NZ market. NZ-built systems focused on the NZ market have the edge.
When a NZ law firm evaluates practice management software, trust accounting compliance usually gets treated as a checklist item. Vendors confirm it handles trust accounting, confirm it meets NZLS requirements, and the conversation moves on.
The problem is that meeting NZ trust accounting requirements and being built for NZ trust accounting are two very different things. The reason that distinction matters comes down to the specific nature of NZ's regulatory regime.
What makes NZ trust accounting genuinely different
NZ's trust accounting obligations under the Lawyers and Conveyancers Act are specific in ways that trip up systems built for other markets.
Monthly TAS certificate. The trust account supervisor must file a monthly trust account statement certificate with NZLS by the 10th working day of the following month, under s115 and Regulation 17. This is not a general reconciliation report. It is a specific document with a specific structure required for NZLS submission. Software needs to produce it in the correct format — not an approximation of it.
Three-way reconciliation. Every month, three figures must agree: the bank statement balance, the trust cash book, and the total of all client matter ledger balances. This is structurally different from a standard bank reconciliation. Most systems built for other markets handle the bank reconciliation leg. The three-way structure is something else entirely, and it requires the system to be built around it, not adapted to produce it.
IBD handling under s114. Where it is practicable, client funds must earn interest, and that interest must be allocated per client. This requires tracking client funds in interest-bearing deposit accounts separately from the general trust account, with correct interest allocation across individual matters. This workflow was not in scope when most international systems were built.
Quarterly certificates. Firms must file quarterly certificates with NZLS covering IBD interest and related matters.
NZLS Inspectorate readiness. Since July 2024, the NZLS Inspectorate has been conducting reviews using Audit Assistant. The system needs to produce reports that map cleanly to what inspectors expect to see. If the underlying data is right but the reports are in the wrong format, inspections take longer and create friction that firms should not have to deal with.
Each one is tied directly to NZ legislation. A system built around them looks and feels different to one that was retro-fitted to produce them.
What a bolt-on approach looks like in practice: the Clio example
Clio is a large, well-resourced practice management platform that originated in the North American market. It only added NZ trust accounting capabilities in 2025. That is extremely late for a system that had been operating for years in other markets, and it reflects a commercial reality: the investment required to properly serve NZ trust accounting requirements was not a priority while bigger markets were available.
When Clio did enter the NZ market, the approach was a bolt-on report rather than a meaningful redesign of the user experience around NZ trust accounting workflows. The compliance requirement is met. The system produces the outputs NZLS needs. But the trust account supervisor's day-to-day experience is not built around NZ trust accounting. The reports live in a different part of the application, accessed through a different sequence of steps, and do not reflect how a NZ trust accountant thinks about their work.
And that is not a criticism of Clio specifically. Every large vendor serving multiple markets makes the same call. The development cost required to genuinely rebuild a product around NZ-specific trust accounting workflows is significant. The NZ legal market is small. The return on that investment does not stack up against what could be built for Australia, the UK, or the US with the same resources. So the bolt-on approach is what happens.
Why large vendors will almost always make this call
It is theoretically possible for a large international vendor to close the gap and build a genuinely NZ-native trust accounting experience. But it is not likely, and the commercial logic explains why.
For a for-profit company with operations across multiple markets, the decision about where to invest development resources will almost always favour the larger markets. Australia has a substantially bigger legal market than NZ. The US is larger again. Features and workflow improvements that serve those markets get built. NZ-specific requirements get met at a compliance level, and no further investment is made until market share demands it.
A NZ-built vendor like OneLaw operates differently because they have no other choice. NZ is their only market. Every regulatory change from NZLS, every shift in inspection methodology, every update to the TAS certificate format — these are existential concerns for a NZ-only vendor. They cannot deprioritise them in favour of a bigger market.
What this means when you are evaluating PMS vendors
International vendors are not a blanket bad choice. But you need to go in knowing what you are trading when you pick one.
If you are considering a system that was built for another market and adapted for NZ, the trust accounting experience will be more cumbersome for your TA team. That is not a hypothetical risk — it is the consistent experience of NZ firms that have made that choice. The question is whether the other features of that system — document automation, AI tools, integrations, time recording — deliver efficiencies significant enough to outweigh the friction in trust accounting.
For some firms, that trade-off is worth it. A firm doing high-volume conveyancing that benefits significantly from LEAP's document automation may judge that the workflow gains outweigh the trust accounting friction. A firm where the trust account is central to everything the firm does may reach the opposite conclusion. Our OneLaw vs LEAP comparison walks through how this trade-off plays out in practice across both systems.
The mistake is making that trade-off without knowing you are making it.
The hidden long-term cost nobody mentions in the sales process
Even when a firm selects a system that meets NZ trust accounting requirements, the transition carries a cost that is consistently underestimated: the time it takes for the trust accounting team to learn a system that was not built around their work.
Whatever system you choose, if it went through a proper due diligence process, it will be compliant. But compliance does not mean fast or intuitive. For a trust account supervisor who has spent years in a system where the TAS certificate process was second nature, learning to produce the same output in a system where it was bolted on rather than built in is a long road. Errors happen. Reconciliations need to be fixed. Interest on client money needs to be recalculated. Month-end processes that used to take an hour now take longer while the team adapts.
Factor the real cost of that learning curve into your timeline and implementation plan. Before you commit to a vendor, not after.
Getting independent advice
Valley IT works with NZ law firms on technology decisions, including practice management system selection.
To talk through your situation, book a free 30-minute consultation or call 0800 824 848.
This post reflects publicly available information and IT practitioner experience as at May 2026. It is not legal or compliance advice. Verify trust accounting requirements directly with NZLS and your trust account supervisor.