eInvoicing in New Zealand: the 2026 government rules and what comes next

New Zealand took a distinctive path to e-invoicing: rather than mandating businesses, it made eInvoicing the fastest way to get paid by the government. Since 1 January 2026, large government agencies must be able to send and receive Peppol eInvoices, and must pay 95% of the eInvoices they receive within 5 business days ^{[1] [2]} . From 2027, the largest suppliers to government will be required to invoice that way. The rules, dates, and thresholds below are sourced from New Zealand Government Procurement and the official eInvoicing programme in the Sources section.

The two dated mandates

Both obligations live in Rule 44 (eInvoicing capability) of the Government Procurement Rules ^[1] :

A large supplier is an entity whose total revenue, including subsidiaries, exceeded NZ$33 million in each of the two preceding accounting periods ^[1] . More than 100 agencies are covered by the mandates ^[2] .

So for the typical SMB, nothing is compulsory: the 2027 requirement bites suppliers at a scale most small businesses never reach. What matters to everyone else is the payment rule.

The prompt payment rule: 5 business days

From January 2026, mandated agencies must pay 95% of domestic trade eInvoices within 5 business days, against a 10-day standard for other domestic trade invoices ^[2] . Agencies report their payment times quarterly to MBIE, and the results are published ^[2] , which gives the rule teeth: slow payers are visible.

For any business that sells to government, this is a straightforward cash-flow arbitrage. The same invoice, sent as an eInvoice instead of a PDF, moves from a 10-day expectation to a 5-day one, and skips the inbox-to-AP-system retyping step where invoices stall and errors creep in.

Getting on the network

New Zealand runs on Peppol, the same international standard as Australia; the two governments committed to a joint trans-Tasman approach, and MBIE acts as New Zealand’s Peppol Authority ^[2] . For most SMBs, adoption is not a project: Peppol-connected accounting platforms, Xero among them, let a business register on the network and start sending eInvoices from the software it already uses. A sensible 2026 checklist for a bookkeeper:

1. Register clients on the Peppol network through their accounting software (minutes per client, typically free).
2. Switch government-facing invoices to eInvoices first to capture the 5-day payment standard.
3. Offer eInvoicing to B2B customers opportunistically; both sides save processing time, but nothing forces it.
4. For clients near the NZ$33 million revenue line who supply government, plan for the 1 January 2027 requirement now.

How this differs from Australia

Because the two countries share the trans-Tasman Peppol framework, a business registered on the network in New Zealand can exchange eInvoices with Australian counterparties on the same rails. The policy approaches differ, though: Australia mandated its federal agencies to be able to receive eInvoices and is now making eInvoicing the default in Commonwealth procurement, while New Zealand paired its agency capability mandate with the published 5-day payment standard and a dated requirement on large suppliers. For an SMB with customers on both sides of the Tasman, one network registration covers both markets, and the NZ payment incentive is currently the more concrete reason to switch.

The documents eInvoicing does not touch

eInvoicing covers invoices exchanged between Peppol-connected parties. It does not cover the expense side of a small business’s paperwork: EFTPOS receipts, fuel dockets, supplier bills emailed as PDFs, or invoices from overseas vendors outside the network. Those still need to be captured, coded with the right GST treatment, and filed against the ledger.

ExpenseFlow handles exactly that stream: it captures paper and PDF documents, extracts the data, codes each line, and syncs the transaction into the accounting platform with the source document attached. The result is one ledger where the eInvoiced revenue side and the messy expense side meet, with the evidence Inland Revenue expects attached to both. ExpenseFlow is not a Peppol Access Point and does not transmit eInvoices; it makes sure the other half of the books keeps up.