How to Send eInvoices to New Zealand Government Agencies via Peppol

Sending an einvoice to a NZ agency in one sentence

To send an einvoice to a New Zealand government agency you connect to the Peppol network through an access point, register your participant identifier, produce a valid PINT A-NZ invoice, validate it, and let your access point deliver it to the agency. If the network model is new to you, what a Peppol Access Point is explains the four-corner exchange this all runs on.

New Zealand's programme is part of a joint trans-Tasman approach with Australia — background is in the full New Zealand e-invoicing guide.

Step 1 — Get onto the Peppol network

You do not connect to an agency directly. Peppol is a four-corner network: you (corner 1) send through your access point (corner 2), which routes to the agency's access point (corner 3) and on to the agency (corner 4). So the first step is engaging a Peppol access point — see how to choose a Peppol access point.

Step 2 — Register your participant identifier

Your access point registers you on the network and publishes a participant identifier — your address on Peppol, typically derived from your NZBN. This is what an agency's access point uses to route a document to you, and what lets you receive as well as send. Without it, the network cannot find you.

Step 3 — Produce a valid PINT A-NZ document

New Zealand and Australia jointly govern PINT A-NZ, the trans-Tasman specialisation of Peppol BIS Billing 3.0. Government agencies receive invoices as PINT A-NZ documents. Map your invoice data into that format:

Use the correct PINT A-NZ profile — not European BIS Billing, which is not interchangeable.
Populate all mandatory fields: correct identifiers, tax details, line items and totals.
Scope is domestic trade credit in NZD for goods or services delivered in New Zealand.

The distinction between the base standard and this specialisation is covered in Peppol vs PINT.

Step 4 — Validate before you send

Validate the document against the PINT A-NZ artefacts before delivery. A document that fails the business rules is rejected before it reaches the agency, so catching errors in your own system is far cheaper than a bounce. Wrong profile, missing mandatory data or a malformed identifier are the usual culprits.

Step 5 — Deliver to the agency

Once validated, your access point transmits the invoice to the agency's access point, which delivers it to the agency's finance system. Under New Zealand's government procurement rules, agencies aim to pay 95% of domestic e-invoices within 5 business days — confirm the current rule for your situation.

A readiness checklist

[ ] Engage a Peppol access point that supports PINT A-NZ.
[ ] Register your participant identifier (NZBN-based).
[ ] Map invoice data to the PINT A-NZ profile.
[ ] Validate against PINT A-NZ artefacts before sending.
[ ] Confirm the agency can receive Peppol invoices.
[ ] Archive each invoice for the statutory period.

If your customer base is large NZ suppliers rather than agencies, the 2027 large-supplier rule and the NZ$33 million threshold set out who is caught. The agency-side rules are in New Zealand government e-invoicing.

How GoRoute helps

GoRoute (POP000991) is a certified Peppol Access Point and SMP, and is now an ATO-accredited Australian Peppol Service Provider, ISO/IEC 27001:2022 and ISO 22301:2019 certified. You map your invoice data once, we validate against PINT A-NZ and deliver over the network through a single REST API — the same integration that reaches Australian agencies, since both countries share PINT A-NZ. We are also pursuing New Zealand mutual accreditation with MBIE. Book a demo.

Sources: New Zealand Government Procurement — eInvoicing; MBIE; Peppol / OpenPeppol.

Frequently asked questions

How do I send an e-invoice to a New Zealand government agency?

Get onto the Peppol network through an access point, register a participant identifier so the agency can find you, produce a valid PINT A-NZ invoice, validate it against the PINT A-NZ artefacts, and let your access point deliver it to the agency's access point. You do not email a PDF; you exchange a structured Peppol document over the four-corner network.

What invoice format does the NZ government require?

New Zealand and Australia jointly govern PINT A-NZ, the trans-Tasman specialisation of Peppol BIS Billing 3.0. Government agencies receive invoices as PINT A-NZ documents over Peppol. Validate against PINT A-NZ artefacts, not European BIS Billing, because the two are not interchangeable.

Do I need a Peppol access point to invoice NZ agencies?

In practice, yes. The Peppol network is four-corner, so you connect through an access point rather than directly. Your provider registers your participant identifier, validates each document and delivers it to the agency's access point. Many businesses use an access point that also exposes an API or portal.

How do I get a Peppol participant identifier in New Zealand?

Your access point registers you on the network and publishes your participant identifier, typically based on your NZBN, so other participants and agencies can look you up and route invoices to you. This registration also lets you receive invoices, not just send them.

What is a participant ID and why does it matter?

A participant identifier is your address on the Peppol network. When an agency sends or expects an invoice, its access point uses this identifier to route the document to the right recipient. Without a registered identifier, the network cannot find you.

What happens if my invoice fails validation?

A document that fails the PINT A-NZ business rules is rejected before delivery, so the agency never receives it. Common causes are a wrong profile, missing mandatory fields or a malformed identifier. Validate before sending so errors surface in your system rather than at the agency.

How fast do NZ agencies pay e-invoices?

Under New Zealand's government procurement rules, agencies aim to pay 95% of domestic e-invoices within 5 business days. Confirm the current rule for your agency and situation, as procurement policy is periodically updated.