Statute of Limitations for Written Contract in New Zealand

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In New Zealand, claims based on a written contract are time-limited by the Limitation Act 2010. If you wait too long, your claim may become statute-barred, meaning the court can refuse to hear it even if the contract was breached.

For anyone tracking deadlines, the key question is usually this:

  • When did the limitation clock start?
  • How long do you have to bring a claim based on a written contract?
  • Are there exceptions that pause or reset the timeline?

DocketMath’s statute-of-limitations tool helps you run that timing analysis quickly. You input the relevant dates (and, where applicable, information about knowledge or hardship), then DocketMath calculates the likely end date for bringing the claim under New Zealand limitation rules.

Note: This page focuses on the Limitation Act 2010 framework for written contracts. It’s not legal advice, and it can’t replace case-specific review—especially where unusual facts affect the start date or whether an exception applies.

Limitation period

Baseline rule for written contracts

Under the Limitation Act 2010, a typical claim founded on a simple contract (including many written contractual claims) generally runs for a set period measured from the date the cause of action accrues.

For a “written contract” claim, the practical approach is to identify the accrual date—often the date the breach occurred or the date performance was due and not performed.

A common scenario:

  • A contract requires payment by 1 April 2024
  • The payer fails to pay by that date
  • The claimant’s cause of action usually accrues around then (subject to contractual terms and how the law characterizes the claim)

How DocketMath turns dates into an output

When you use DocketMath’s /tools/statute-of-limitations, the inputs typically affect two things:

  1. **Start date (accrual/trigger date)
    • Earlier start dates move the “last day” earlier.
  2. Whether an exception changes the clock
    • If an exception pauses, extends, or changes the computation, the “last day” moves later.

Because accrual can be fact-sensitive, DocketMath is designed to let you model timing scenarios. For example, you might compare:

  • accrual at the due date of payment, vs.
  • accrual at the date the breach was discovered (where a knowledge-based rule is relevant).

Practical checklist for timeline accuracy

Before calculating, gather these items:

Key exceptions

New Zealand limitation law includes situations where the limitation period can be affected. The exact outcome depends on the legal basis of the claim and the relevant facts, but common categories include:

1) Disability, incapacity, or special protected circumstances

Where a claimant is under a relevant disability, limitation may be suspended or treated differently. This can significantly change the last date.

Practical impact:
Even if the breach happened years ago, the end date may be later where the Limitation Act 2010 allows a delay or extension because of incapacity/disability.

2) Postponement rules tied to knowledge

Some claims can involve rules that take account of when a claimant knew (or should have known) of the relevant facts. Knowledge-based postponement is often more relevant in claims beyond “simple contract,” but it can still matter depending on how the claim is framed.

Practical impact:
A later “knowledge” date can push the limitation end date forward.

3) Conduct affecting limitation (for example, acknowledgments)

If the debtor acknowledges the debt or makes representations that can legally be treated as affecting limitation, the clock may reset or be otherwise impacted.

Practical impact:
A written acknowledgement—sometimes including correspondence, signed statements, or payments—can alter timing outcomes compared with a straightforward “breach date” start.

4) Claims against certain public bodies or special regimes

Some proceedings have distinct limitation considerations. If a claim involves a public body or a specialised legal regime, the limitation analysis may require separate attention.

Practical impact:
The written-contract rule may not be the whole story if another statutory framework overlays the claim.

Warning: Exceptions are highly fact-dependent. Two cases with the same breach date can still have different limitation outcomes based on acknowledgement, knowledge, or disability issues. Always confirm which exception (if any) is actually engaged before relying on a computed deadline.

Statute citation

The governing statute is the Limitation Act 2010 (NZ).

The relevant provisions include, among other sections:

  • Limitation Act 2010, s 11 — general limitation rules (including time limits for actions founded on simple contracts).
  • Limitation Act 2010, s 12 — when the limitation period runs (accrual / when a cause of action is treated as having accrued).
  • Limitation Act 2010, ss 14–15 — postponement/extension scenarios (including knowledge-related postponement in circumstances covered by the Act).
  • Limitation Act 2010, ss 24–26 — extension/special circumstances provisions (including disability and certain other protected cases).
  • Limitation Act 2010, ss 27–28 — acknowledgement and similar doctrines affecting limitation periods (where applicable).

Because the Limitation Act 2010 structures time limits through multiple sections, DocketMath’s calculation logic follows the statute’s framework: it models accrual, then applies the governing limitation period, and finally checks whether any statutory exception inputs are provided.

Use the calculator

DocketMath’s statute-of-limitations tool is built to turn limitation analysis into a clear “last date” output for New Zealand.

What you typically input

Check your situation and provide the dates that match the facts:

  • Breach / due date (start date candidate)
    Example: “Payment was due on 1 April 2024.”
  • Knowledge / discovery date (if applicable)
    Example: “The issue was discovered on 10 May 2024.”
  • Disability/incapacity information (if applicable)
    Example: “Claimant was under a relevant disability during part of the period.”
  • Acknowledgement or other trigger (if applicable)
    Example: “Written acknowledgement received on 20 June 2024.”
  • Claim type focus
    Example: “Claim founded on a written contract.”

How the output changes

Use DocketMath to compare scenarios:

  • Earlier start date → earlier limitation expiry
  • Later start date → later limitation expiry
  • If an exception/extension applies → DocketMath will extend the expiry date
  • If no exception applies → DocketMath will compute using the baseline limitation period

Interpreting the result safely

When you get a “calculated expiry date,” treat it as a timing indicator, not a guarantee. Two reasons:

  • accrual can depend on contract wording and how the breach is legally characterized;
  • exceptions require that the facts meet statutory thresholds.

To reduce error, cross-check that your chosen start date matches the contract’s performance obligations (and not merely a later complaint or negotiation date, unless the law links limitation to that later event in your scenario).

Related reading