Explainer Finance, Accounting, Banking, Insurance & Compliance · Accounting for Business · Issue 2026-W46

New Zealand's IFRS 20 announcement: identify timing differences before implementation

New Zealand's standard setter has announced adoption of a standard on regulatory assets and liabilities. Reporting teams should separate issuance, announcement and mandatory application. We propose an initial applicability file and an evidence map that can precede a software implementation project or accounting-policy change, while leaving technical accounting judgments to the applicable text and qualified specialists.

By ARPS Editorial Team Last reviewed 11 November 2026 About 5 min read (estimate)

Source date 2026-10-29

Blank calendars at separate heights, an evidence folder and a valve separated from an accounting ledger.

New Zealand's standard setter has announced adoption of a standard on regulatory assets and liabilities. Reporting teams should separate issuance, announcement and mandatory application. We propose an initial applicability file and an evidence map that can precede a software implementation project or accounting-policy change, while leaving technical accounting judgments to the applicable text and qualified specialists.

Dates with different functions

New Zealand's External Reporting Board, XRB, published its NZ IFRS 20 announcement on 6 November 2026. The standard's record gives October 2026 as its issuance month and states application for periods beginning on or after 1 January 2029. This week's development is the local adoption announcement. We do not suggest that the international standard originated this week or that reading the announcement triggers immediate mandatory implementation. [1][2]

The official text also separates taking legal effect on 26 November 2026 from mandatory application to accounting periods. These concepts are distinct, rather than contradictory dates. The announcement concerns rate regulation for for-profit entities within two local reporting tiers. We read the announcement, record and opening date/scope provisions, not the full standard or restricted materials. We offer no measurement judgments or illustrative entries. [1][2][3]

The text connects regulatory assets and liabilities to enforceable agreements and timing differences in charging allowed compensation through regulated rates. Not every revenue timing difference qualifies: it distinguishes differences arising under the revenue standard that create no regulatory asset or liability. [3] The assessment question becomes whether the company retains the reason for a difference and the supporting right, beyond holding a numerical discrepancy.

Establish an applicability file before an implementation plan

We propose a short decision record for one reporting entity, rather than assuming that the whole group has identical requirements. Identify the jurisdiction of its financial statements, accounting framework, entity status, nature of any arrangement regulating its rates and start of its financial year. For each item, record the internal evidence and person responsible for checking it.

The appearance of regulation in a business description is insufficient for this exercise. The purpose is to understand the arrangement a specialist will assess against the adopted text. Merely collecting a contract also does not establish its accounting consequences. The file should make a professional assessment easier to perform and explain, without anticipating its conclusion.

This preliminary work sorts the question before answering it. A company may operate in a regulated sector while the relevant accounting question is narrower. A subsidiary may need a separate assessment from a parent in another country. Neither observation establishes inclusion or exclusion from the standard. Acceptable preliminary outcomes are likely applicability requiring a documented professional conclusion, documented non-applicability, or missing information that prevents a conclusion.

For a Saudi or Gulf headquarters, the New Zealand announcement cannot establish a local application requirement. Check the framework adopted by the competent authority and requirements for the actual financial statements being prepared. The news can prompt an internal readiness question, while applicable texts and qualified specialists determine legal and accounting conclusions. This reduces the risk of funding a project based only on a familiar title.

Connect each difference to evidence before connecting it to software

Once the professional need is established, we suggest an evidence index that begins with a real regulatory agreement or decision and connects it to the record describing the transaction and its timing. Who owns the document? Where is its approved version? What event changes it? Who checks its connection to the data? These questions concern input quality, rather than instructions to recognize an asset or liability.

Keep the specialist's treatment decision separate from the existence of a digital record. A system can contain a complete field for an amount whose basis has not been approved. Equally, a sound technical conclusion can be difficult to implement if the relevant agreements have never been connected to transaction records. Those are different gaps and need different owners.

Consider a hypothetical group with two companies using the same software. One keeps rate decisions and agreement versions with its regulatory affairs team; the other has correspondence scattered across employees' email. Buying a new field for both companies does not resolve the difference in evidence readiness. The second might begin by retrieving documents and assigning ownership, while the first tests connections to transactions. This example establishes no conclusion about either company's inclusion in the standard's scope.

Assess the index by following a test case from document to data and back again. If reporting staff cannot explain which version they used, repair that issue before relying on an automated report. If the exercise requires an unresolved accounting decision, record the question and refer it to a specialist. Do not insert an unsupported estimate simply to make the software demonstration run. The source of an accounting judgment remains distinct from the source of its data.

Two project choices and the cost of acting too early

A company may choose a full implementation once applicability and materiality are established. Alternatively, it may choose limited discovery while scope or evidence remains incomplete. Discovery is a purposeful stage when it has an owner, output and review date. Buying software does not establish readiness if the documents remain unknown.

Compare the cost of discovering a gap early with the cost of redesigning a treatment later. We make no numerical estimate without company data. Before meeting a supplier, describe what is being purchased: a scope assessment, evidence organization, data changes or implementation of an approved policy. The answer changes who should attend and what acceptance means.

Stop where work would require copying restricted material without permission or where nobody has authority to approve the conclusion. A public announcement is useful for understanding a development; professional implementation needs a broader foundation.

Begin by putting issuance, announcement and application dates in one record, then choose a reporting entity for the applicability exercise. Which missing fact could change your next step from implementation to discovery? To follow the discussion, choose an appropriate community through ARPS communities; its public page describes ordinary membership as free.

This content is for professional education and does not replace advice from a licensed professional.

References

  1. A new international accounting standard comes to New Zealand — XRB · 2026-11-06
  2. NZ IFRS20 Regulatory Assets and Regulatory Liabilities, standard record — XRB · 2026-10
  3. NZ IFRS20 Official Standard, opening date and scope provisions — XRB · 2026-10-29

References open in a new tab.

Discuss this with practitioners

Create a free account to save articles and join the Specialists community discussion.

Create a free account

Discussion 0 published comments

No published comments yet. Be the first to share your experience.