The tax treatment of software expenditure in your business: Lost in the cloud, or just up in the air?

The way New Zealand’s tax system treats software expenditure was initially designed for a simpler time of boxed software and perpetual licences. Although the rules have evolved over time they haven’t always kept pace with cloud computing, agile development, Software as a Service (SaaS) and increasingly, AI. 

Legislative changes and administrative guidance have reduced the risk of expenditure falling into “black hole” territory. Inland Revenue has been clear black hole expenditure outcomes are not intended by businesses, and in practice they should be rare. That said, intangible property rules, particularly where certain software arrangements do not qualify as fixed life intangible property, means there’s still a residual risk of having expenditure which is neither capitalised and depreciated, or a claimed as a deductible expense. 

Inland Revenue issued a consultation paper about software expenditure which closed in January. It includes SaaS configuration and customisation costs, and may signal an important next step towards establishing the distinction between capital and revenue. 

For most taxpayers, software costs will ultimately be deductible. The real question is when and how those deductions arise: immediately or over time through depreciation? 

While SaaS sits at the centre of the current debate, the underlying issue is much broader and should also focus on how the tax system recognises and measures investment in all forms of software in a modern digital economy.

What this means for your business

Software, which is increasingly delivered through SaaS, is no longer a support function, it is the backbone of your operations. ERP, CRM, finance systems, and even core revenue platforms are now delivered via the cloud. Yet the tax treatment of these arrangements remains complex, particularly if you’re incurring configuration and customisation costs.

Historically, significant software implementation and acquisition costs have been generally treated as capital in nature, with deductions obtained over time through depreciation. More recent legislative and administrative developments have expanded opportunities for immediate deductibility in certain circumstances.

The result is a familiar mix: complexity, compliance cost, and inconsistent outcomes across taxpayers.

There is also a commercial impact. If your business has significant upfront implementation costs, spreading deductions over years can create a timing mismatch with revenue, particularly where value is realised early, but tax relief is deferred.

The challenge now facing IRD

Notably, IRD’s consultation does not propose specific legislative changes. Instead, it seeks to better understand where the existing framework is falling short and where complexity persists. This approach is telling, because rather than prescribing solutions, it highlights a number of emerging challenges:

• The existing rules were built for a different software paradigm
• Modern software arrangements, particularly SaaS, do not sit neatly within traditional tax concepts, particularly ownership of an “asset”
• The compliance burden associated with determining deductibility is often disproportionate

One of the more significant challenges is the treatment of SaaS as an “asset”. In practice, customers rarely acquire ownership, they receive access rights under a service contract. Yet the tax system still often applies asset-based logic to determine treatment. That disconnect is a key driver of all this complexity.

This is not unique to New Zealand. Internationally, tax systems are grappling with similar challenges as software shifts from owned products to hosted and service-based delivery models.

Capital vs revenue in a digital world

The consultation also brings renewed focus to a familiar issue in tax: the capital and revenue boundary.

Across software expenditure more broadly, and particularly for SaaS configuration and customisation costs, that boundary is increasingly blurred:

• Configuration may simply enable use of an existing platform
• Customisation may create enduring benefits resembling an intangible asset
• Integration and data migration often sit somewhere in between

Inland Revenue’s existing guidance already recognises this spectrum, requiring a case-by-case analysis and, in many circumstances, treating expenditure as capital but deductible over time.

However, the consultation suggests this framework, while technically workable, may no longer be fit for purpose in a cloud-first environment.

Future implications for your business

While no immediate changes have been put in place, the direction of travel is clear and businesses should take note.

1. Increased scrutiny of software costs

Inland Revenue is likely to continue focusing on whether costs are correctly characterised across software expenditure, particularly as SaaS and digital investment continue to grow.

2. Potential simplification ahead

There is a strong signal that reform could aim to reduce compliance burdens, potentially through more standardised or principle-based approaches, or closer alignment with accounting treatment.

3. Potential review of research and development rules

The consultation questions whether the existing research and development deduction rules remain fit for purpose in a modern software environment. For businesses developing software, any reform could have implications for how expenditure is characterised and when deductions become available.

Where to from here?

Submissions closed months ago, so our attention is turning to Inland Revenue’s next move.

While no immediate changes have been signalled, the consultation itself points to a broader reform agenda. Inland Revenue has acknowledged that, while the existing framework is broadly workable, it can produce unnecessary complexity and administrative burdens when applied to modern software arrangements. The next phase is likely to involve:

• further policy development focused on reducing complexity and compliance cost
• consideration of whether more standardised treatment for software expenditure is appropriate
• potential refinements to better align the tax system with modern software delivery models.

What you can do right now

For your business, this is less about immediate action and more about being prepared. Current approaches to software expenditure, particularly for large scale implementations, may come under increased scrutiny as tax policy starts to evolve. In the meantime, there is value in:

• reviewing the existing positions on your software costs
• understanding where judgement has been applied
• ensuring your documentation clearly supports the treatment adopted.

While the ultimate policy response remains uncertain, the consultation indicates a clear desire to reduce complexity and improve the operation of the current rules, as there is growing recognition they may not deliver outcomes in the most efficient or intuitive way. 

The eventual reform agenda will therefore be less about fixing a broken system, and more about making the treatment of software expenditure simpler, more consistent, and better aligned with how businesses actually invest in technology.