Terms and Conditions for New Zealand Accounting Software Businesses

If you run an accounting software business in New Zealand, your terms and conditions do much more than sit in the footer. They set the rules for subscriptions, user access, payment disputes, data handling, service outages and liability when something goes wrong. Founders often make the same mistakes here: they copy overseas SaaS terms that do not fit New Zealand law, they promise too much about uptime or accuracy, or they leave key issues buried in sales emails instead of the contract itself.

That creates risk fast. A customer may assume your platform guarantees compliance, prevents all accounting errors or will never go offline. If your contract does not clearly deal with those expectations, you can end up arguing about refunds, responsibility for incorrect reporting, or whether a customer can cancel mid-term. This guide explains what terms and conditions for accounting software business arrangements should cover in New Zealand, what to check before you sign or accept standard terms, and where software providers commonly get caught out.

Overview

For New Zealand accounting software businesses, well-drafted terms and conditions should clearly define the service, set realistic limits on responsibility, and deal with data, payment and termination in a way that matches how the product actually works. The right contract helps manage customer expectations and reduces disputes when a subscription, integration or support issue does not go to plan.

• Define exactly what the software does, and what it does not do
• Set clear rules for fees, renewals, upgrades and refunds
• Explain customer responsibilities for data accuracy, access credentials and lawful use
• Deal with outages, maintenance, support response times and service changes
• Address privacy, data storage, third-party integrations and security obligations
• Limit liability in a way that is fair, clear and more likely to be enforceable
• Set out termination rights, access to data after termination and transition steps
• Check whether any consumer law protections or unfair contract term risks affect your wording

What Terms and Conditions for Accounting Software Business Means For New Zealand Businesses

For a New Zealand accounting software provider, terms and conditions are the core contract that governs how customers use your platform and what happens when expectations do not line up with reality.

This usually covers SaaS subscription terms, licence conditions, support terms, acceptable use rules, payment terms and privacy-related commitments. Some businesses keep these in one master agreement. Others split them into an order form, platform terms, service level commitments and a privacy notice. Either way, they need to work together.

Accounting software creates some specific legal and commercial issues. Customers often rely on it for GST records, invoicing, payroll functions, reconciliations, reporting and integrations with banks or other systems. That means your contract should do more than state a monthly fee and basic licence.

It should answer practical questions such as:

• Is the software a tool to assist accounting processes, or are you making promises about legal or tax compliance?
• Who is responsible for checking the accuracy of data entered into the system?
• What happens if a bank feed, payroll function or integration fails?
• Can the customer rely on marketing statements about uptime, automation or reporting accuracy?
• How quickly can you suspend access for non-payment or security concerns?
• What happens to stored financial data when the subscription ends?

Why the wording matters

The main risk is mismatch. Your sales team may describe the software one way, your product team may operate it another way, and your standard terms may say something else again. When a dispute starts, customers usually point to the statement most favourable to them.

That is why your contract should align with your website copy, demos, onboarding materials and support practices. If you say the product is suitable for all New Zealand businesses, automatically compliant with all legal obligations, or guaranteed to prevent accounting mistakes, those claims can create problems under contract law and fair trading rules.

Business to business versus consumer issues

Many accounting software providers deal mainly with businesses, but that does not mean consumer law never matters. Sole traders, very small businesses and mixed-use customers can create grey areas, especially where standard form contracts are used at scale.

You should also think carefully before assuming every liability exclusion will stick. In some cases, New Zealand legislation can affect attempts to exclude statutory guarantees or impose one-sided terms. The safer approach is to use clear, commercially reasonable wording that reflects the real deal rather than relying on extreme disclaimers.

Common contract documents in this space

Depending on how your software is sold, your terms and conditions may need to sit alongside:

• enterprise order forms or negotiated MSAs
• implementation or onboarding statements of work
• data processing or privacy-related terms
• service level commitments for uptime and support
• partner or reseller agreements
• terms for add-ons, API access or marketplace integrations

If those documents overlap, make sure they do not contradict each other. A common example is where the order form promises custom support, but the standard terms allow broad service changes and disclaim support commitments. That tension often surfaces only after the customer has signed.

Legal Issues To Check Before You Sign

Before you sign a contract, or before you accept the provider's standard terms, make sure the document matches the product, sales process and risk profile of the business.

Scope of the software and licence

Your agreement should state what the customer is actually getting. Is it a non-exclusive, non-transferable subscription to access hosted software? Are there user caps, entity limits, transaction limits or feature-based plans?

If you offer payroll, invoicing, reporting or bank integrations, say whether those are standard features, optional modules or third-party services. Customers often assume everything shown in a demo is included in the base plan unless the contract says otherwise.

The licence and access section should usually cover:

• who may use the software
• whether contractors, bookkeepers or external accountants can access it
• restrictions on sharing logins
• prohibited uses, such as reverse engineering or misuse of the platform
• rights to suspend access for security, breach or non-payment

Service description and support commitments

If you offer support, implementation or migration help, spell out what is included and what falls outside the price. This is where founders often get caught. A sales conversation may refer to onboarding assistance, but the contract may stay silent.

For accounting software, support disputes often arise around:

• setup and data migration from another platform
• response times for technical issues
• help with reconciliations, payroll settings or integrations
• training for staff or advisers
• whether support includes accounting advice, tax advice or only software help

You should avoid blurring software support with professional advice. If your business is not providing accounting or tax advice, say so clearly and consistently. Businesses should speak with their accountant or tax adviser for advice of that kind.

Fees, renewals and cancellation

Payment terms should be easy to read and hard to misinterpret. Set out when fees are charged, whether pricing is per user or per entity, and when changes can be made.

Key points often include:

• monthly or annual billing cycles
• automatic renewals and notice periods
• price increase rights and when notice must be given
• refund position for early cancellation
• consequences of failed payments
• rights to downgrade, upgrade or pause plans

If there are minimum terms, put that front and centre. If implementation fees are non-refundable, say so expressly before the customer signs.

Data ownership, access and exit

For accounting software, data questions matter just as much as subscription pricing. Customers want to know whether their records remain theirs, how they can export them, and what happens after termination.

Your contract should clearly address:

• ownership of customer data
• your limited rights to host, process and back up that data
• whether aggregated or de-identified data can be used for analytics or service improvement
• how long data is retained after termination
• whether export tools are included or charged separately
• whether assistance with transition to another provider is available

Do not leave post-termination access vague. A customer who loses access to financial records at the wrong time may argue the process was unfair or not properly disclosed.

Privacy and information handling

If your platform handles personal information, which accounting software often does through payroll, invoicing and contact records, your terms should work with your privacy disclosures and internal processes. The Privacy Act 2020 may be relevant depending on the data you collect and how you use it.

Contract wording should reflect reality on issues such as:

• what personal information is collected through the software
• whether information is stored or accessed overseas
• use of subprocessors or cloud hosting providers
• security measures and incident response
• customer responsibilities for permissions, consents and user access controls

If you market your platform as secure, encrypted or compliant, be careful not to overstate those claims. Marketing statements should match your actual systems and contractual position.

Liability, warranties and disclaimers

Liability clauses are often the most negotiated part of accounting software contracts because customers depend on the platform for sensitive business records.

You usually want to address:

• whether the software is provided with general functionality rather than a guarantee of uninterrupted service
• limits on liability for indirect loss, data loss, profit loss or business interruption
• overall liability caps, often linked to fees paid over a set period
• carve-outs for non-excludable rights, wilful misconduct, confidentiality breaches or privacy breaches where appropriate
• any warranty that the provider has authority to license the software

Be realistic. A clause that tries to exclude everything, regardless of fault, can create enforceability and relationship issues. A balanced allocation of risk is usually more credible and more likely to hold up commercially.

Third-party integrations and dependencies

Many accounting platforms rely on external services such as payment gateways, banking feeds, e-commerce tools and payroll connections. If part of your product depends on third parties, your terms should say so.

This is especially important where an outage or regulatory change affects a connected service rather than your own code. Customers should understand whether you control that service, support it fully, or simply enable compatibility.

Dispute process and governing law

For New Zealand businesses, the contract should state the governing law and any dispute resolution process clearly. Even a basic escalation process can help contain a disagreement before it becomes expensive.

If you contract with overseas customers too, make sure your standard terms deal sensibly with cross-border issues and do not accidentally create conflicting legal obligations.

Common Mistakes With Terms and Conditions for Accounting Software Business

The most common mistakes happen when accounting software businesses use generic SaaS terms that do not match the product, the customer base or the promises made during the sale.

Copying overseas templates without localising them

US or UK software terms often use concepts, consumer law assumptions and dispute processes that do not fit New Zealand. They may also refer to legislation that does not apply here.

That can leave awkward gaps around privacy, statutory guarantees, fair trading obligations and local contracting practice. Local context matters, especially if you are dealing with New Zealand SMEs that expect plain language and practical processes.

Promising outcomes instead of supplying a tool

Accounting software can automate workflows, but it does not remove the need for businesses to review inputs, approve outputs and meet their own legal obligations. Terms should not imply that the software guarantees tax compliance, error-free bookkeeping or regulatory accuracy in every case.

Founders often create risk through marketing copy first, then try to pull it back with a disclaimer later. That is not a good fix. The contract and the sales message need to point in the same direction.

Leaving implementation and migration unclear

Data migration causes a lot of friction. A customer may assume old records will import cleanly, historical data will reconcile perfectly, or your team will fix legacy errors during setup.

If migration support is limited, say what you will and will not do. If timing depends on customer cooperation or source-system quality, include that too. Before you rely on a verbal promise made in a sales call, get it into the written terms.

Ignoring customer responsibilities

A good software agreement does not just list provider obligations. It also sets expectations for the customer.

For accounting software, customer obligations commonly include:

• keeping login credentials secure
• maintaining internet access and compatible systems
• reviewing reports and payroll outputs before submitting or relying on them
• ensuring authorised users have proper access rights
• complying with applicable accounting, employment and tax-related requirements

If those responsibilities are missing, customers may argue that any error linked to their inputs or approvals is still your fault.

Failing to deal with suspension and termination properly

Suspension rights are important for unpaid accounts, misuse, security concerns and legal compliance. But they should not come as a surprise to the customer.

Termination wording should also be practical. If the contract says you can terminate immediately for any breach, but your team usually allows a cure period, the mismatch can cause trouble. Use terms your business can actually follow in day-to-day operations.

Forgetting the records issue after termination

Accounting software stores information businesses may need for audits, reconciliations and internal reporting. If your contract is silent on exports and retention, the end of the relationship can become the start of a dispute.

Set a clear process for post-termination data access. That includes timing, format, fees if any, and when deletion occurs.

Using harsh limitation clauses in standard form contracts

A very one-sided contract can create negotiation friction and reputational damage, especially with SMEs who rely heavily on your product. The goal is not to make your terms aggressive. The goal is to allocate risk clearly and fairly.

That often means tailoring different terms for self-serve customers, small business subscriptions and enterprise deals instead of forcing every customer into the same wording.

FAQs

Do accounting software businesses in New Zealand need written terms and conditions?

In practice, yes. You can operate without formal written terms, but that leaves key issues open to argument. Written terms help define the licence, fees, support boundaries, liability limits and data position.

Can I just use a generic SaaS agreement for my accounting platform?

Usually not without changes. Accounting software raises specific issues around financial data, integrations, migration, reporting accuracy and customer reliance. Generic SaaS terms often miss those points or deal with them too lightly.

Do my terms need to cover privacy?

Yes, if your software handles personal information. Your contract should align with your privacy practices and explain the main responsibilities around information handling, security, storage and customer use of the platform.

Can I exclude all liability if the software makes an error?

No, you should not assume a blanket exclusion will work. Some liability may be limited, but the wording needs to be clear, reasonable and consistent with New Zealand law. Extreme disclaimers can be risky and may not reflect the real commercial bargain.

What should happen to customer data when a subscription ends?

Your terms should set out a clear exit process. That usually includes when access stops, whether data can be exported, how long it will be retained, and when it may be deleted from active systems.

Key Takeaways

• Terms and conditions for accounting software business arrangements should reflect how the software is sold, supported and used in real life.
• Your contract should clearly cover licence scope, fees, renewals, support, customer obligations, privacy, data ownership, integrations, suspension and termination.
• Accounting software businesses need to be careful with claims about accuracy, compliance, uptime and security, especially where customers may rely heavily on the platform.
• Generic overseas templates often miss New Zealand legal and commercial issues, including fair trading concerns and local privacy expectations.
• A clear post-termination data process is essential because financial records remain important after the subscription ends.
• Before you sign or before you accept the provider's standard terms, make sure the written contract matches the sales promises, onboarding process and actual product features.

If you want help with subscription terms, liability clauses, privacy wording, and data exit provisions, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.