Introduction
E-invoicing in New Zealand is a direct business system-to-business system exchange of structured invoice data over the PEPPOL (Pan-European Public Procurement On-Line) network. Data is transferred automatically between the supplier system and the buyer system, instead of sending PDFs or paper invoices, the data is prepared to be accepted and paid.
This will remove the manual entry of data, minimize mistakes and make the processing quicker. The Ministry of Business, Innovation and Employment (MBIE) is the national PEPPOL authority governing the system.
In simple terms: It is system-to-system flows of invoice data, rather than document flows via email.
New Zealand is not imposing the use of e-invoicing, but it is guiding businesses to the direction of e-invoicing. The PEPPOL (Pan-European Public Procurement On-Line) structure, the approach to standardization, interoperability, and long-term efficiency, rather than regulatory pressure, underlies the country.
The Reason e-Invoicing Is Important at This Point
New Zealand government does not enforce the use of e-invoicing. However, PEPPOL compliant invoicing is getting demanded by government procurement departments, large businesses and international trading partners. Companies that overlook this trend face the risk of experiencing slow payables, increased compliance expenses, and even risk losing sales to digitally sensitive clients.
Quick Stat:
E-invoicing can reduce invoice processing costs by up to 60–80% compared to manual or PDF-based methods.
(Source: Billentis Report / European Commission studies – widely cited globally)
e-Invoicing Regulatory Framework in New Zealand
The IRD Position: Pro-Encouragement, Not Pro-Mandate.
New Zealand has a different approach to e-invoicing, unlike several jurisdictions where structured e-invoicing adoption is more prescriptive in government procurement or tax compliance frameworks.
The Inland Revenue Department doesn’t legally require e-invoicing. Rather, the IRD has promoted voluntary adoption and the IRD has supported voluntary digital adoption and encouraged businesses to maintain digitally auditable invoice records.
Such adaptability is a two-sided sword. On the one hand, companies can still issue paper invoices. Conversely, firms which adopt e-invoicing enjoy a lot of efficiency and compliance benefits- particularly in the process of IRD audit.
Current Adoption & Mandate Status
| Area | Status |
| B2G (Business to Government) | From 1 January 2027, government agencies must require large suppliers (entities with annual revenue exceeding NZD 33 million) to submit eInvoices under updated procurement rules. |
| Expanded government adoption | Required for more agencies by January 2026 |
| B2B (Business to Business) | Voluntary |
| Outlook | Likely expansion based on adoption |
What the IRD really wants?
The IRD does not stipulate the format of e-invoicing, but all companies should keep auditable records of invoices to facilitate the compliance with GST. Specifically:
| IRD Requirement | What This Means |
| Maintain auditable records | Every invoice must be retrievable and verifiable. E-invoicing systems maintain automated logs. |
| Match GST returns | Invoices must contain sufficient information to support GST reporting and input tax deduction requirements under New Zealand GST legislation. |
| 7-year retention | All invoices are preserved for seven years. Businesses must retain invoice and tax records for at least seven years in a retrievable format. |
| Vendor verification | Record supplier NZBN where available. Improves invoice authenticity and payment matching. |
| Timestamp compliance | All invoices must have clear issuance dates. E-invoicing systems auto-timestamp records. |
PEPPOL: The De Facto Global Standard (Even in NZ)
The following is something that not all businesses in New Zealand know:
While IRD does not mandate PEPPOL, many international trading partners and procurement ecosystems increasingly prefer PEPPOL-based invoicing. PEPPOL (Pan-European Public Procurement Online) is becoming more common as the standard of B2B invoicing in Europe, Australia, Singapore and other countries. This is vital to NZ exporters or companies that have foreign suppliers.
PEPPOL is important to NZ Businesses because:
• Automatic invoice ingestion (invoices sent to the customers via the ERP systems of the companies do not require entry of the data)
• Reduced payment cycles (Fewer manual processes = Reduced processing time)
• High rejection rates (structured data minimizes conflicts) Supply chain visibility (invoice status visible to trading partner in real-time)
• Competitive edge (PEPPOL-using businesses look contemporary and business-like).
Hypothetical Example:
A Wellington manufacturing company exports 40% of its products to Australia. Payment processes got much faster after changing to PEPPOL invoicing: from 45 to 28 days per cycle. Annual savings: NZD 180,000 (lower working capital needs). Illustrative example only. Actual savings depend on transaction volume, ERP maturity, and operational structure.
Technical Requirements for E-Invoicing in New Zealand
What Must All Invoices Contain?
The IRD doesn’t prescribe data format, but invoices whether printed or electronic must contain specific information. Here’s the checklist:
| Data Element | Required? | Notes |
| Supplier legal name | Yes | Must match GST registration |
| Supplier address | Yes | Full physical address required |
| Supplier NZBN | No | Recommended for B2B transactions |
| GST Registration Number | If GST-registered | Critical for GST-registered suppliers |
| Invoice number (unique) | Yes | Sequential numbering preferred |
| Invoice date | Yes | Must match actual issuance date |
| Customer name & address | Yes | Must match purchase order |
| Description of goods/services | Yes | Clear, itemized listing |
| Unit price & quantity | Yes | Enables verification |
Supported File types & Standards
The software supporting e-invoicing can transfer invoices in various formats. These work in New Zealand:
| Format | Best For | Limitations |
| UBL (Universal Business Language) | PEPPOL compliance, automation | Requires technical expertise to set up |
| XML (eXtensible Markup Language) | Custom integrations, flexibility | Not as standardized; integration varies |
| JSON | Modern SaaS platforms, APIs | Newer; less support from legacy systems |
| PDF with metadata (not considered fully structured e-invoices under PEPPOL frameworks.) | Audit readiness, human review | Not machine-readable; poor automation |
What Format to use?
When exporting goods or receiving international invoices: Use PEPPOL-compliant UBL. When you are a simple domestic SME with simple invoicing: XML or JSON through your accounting platform will do. In case you are still moving: Use the native e-invoicing format of your ERP (Xero,MYOB,Sage) and upgrade to UBL in the future.
Pro Tip: Don’t overthink this. Format conversion is automatically done on most cloud accounting platforms (Xero, MYOB, Sage NZ). Select according to your current software and not the format.
Application: What Companies Should Do Right?
The process of adopting e-invoicing in New Zealand is comparatively easy but only with the basic requirements met. Most of the implementation issues are not of regulatory nature, they are operational and technical.
ERP Readiness e-invoicing is based on your ERP system
It must: Support formatted invoices. Facilitate the smooth incorporation with an Access Point Service Provider (ASP).
Insight: A high number of delays in adoption are because of ERP constraints and not the complexity of PEPPOL.
Access Point Selection
Selecting the appropriate ASP is important since it serves as your gateway to PEPPOL network. Look for: PEPPOL-certified provider Well-developed regional compliance knowledge. Scalable cloud deployment options.
New Zealand Business Number (NZBN Accuracy)
The system has the New Zealand Business Number (NZBN) as the routing backbone.
Ensure it is: Active and valid Properly mapped on to your entity. Registered in the PEPPOL directory Even a slight misalignment may lead into unsuccessful delivery of invoices.
Data Standardization
PEPPOL uses standardized formats such as BIS Billing 3.0 that involves alignment of data. Possible traps to eschew: Inconsistent field mapping Lack of required data fields. System to system format discrepancies.
Explore PEPPOL E-invoicing Solutions
How it links between functions
- GST Compliance: E-invoicing produces clean and structured data of invoices which can be reconciled with reporting forms. This minimizes mistakes in submissions and improves consistency in tax submissions.
- Reconciliation: Invoices are standardized, and therefore, matching transactions is quicker and more precise. This greatly minimizes differences and human involvement in the reconciliation process.
- Vendor Portal: E-invoicing makes the process of supplier onboarding simplified, as it requires data to be of the same format. It also enhances communication and minimizes the back and forth on correcting the invoices.
- Accounts Payable and Accounts Receivable (AP and AR): Instantaneous exchange of invoices enhances accountability of the payables and receivables. This allows faster processing, enhanced tracking and streamlines the cash flow.
Adoption Journey: Manual to Automated
Implementation of E-invoicing in New Zealand is more of a gradual transformation than a revolution.
Manual Invoicing → PDF Exchange → PEPPOL Adoption → Full AP and AR Automation
Stage 1: Paper/manual processes
Stage 2: PDF-based electronic communication (remain manual-intensive)
Stage 3: Organised PEPPOL invoicing.
Stage 4: Complete AP/AR automated processes.
Most New Zealand businesses are currently moving away with PDF-based operations to organized e-invoicing. This change is more of an efficiency than a regulatory change.
See how businesses improved invoice processing efficiency
Government/Official Programs that are contributing to the adoption
The New Zealand electronic invoicing system is powered by Trans-Tasman project with Australia, which guarantees international interoperability and standardization.
Key initiatives:
- MBIE named PEPPOL Authority (2019)
- PEPPOL framework to be rolled out nationwide.
- Quickening of e-invoice payments.
- mandated agencies are expected to pay 95% of domestic trade e-invoices within 5 business days and other qualifying invoices within 10 business days.
Why this matters:
- Motivates suppliers to use PEPPOL.
- Enhances the cash flow of businesses.
- Standardizes procurement processes
Strategic approach: “Enable first, mandate later”- a phased adoption model.
Conclusion
The e-invoicing ecosystem in New Zealand is developing in a silent, yet strategically purposeful manner. The strategy is not time-bound and compliance-led as compared to mandate-driven markets. Rather, it is informed by business practical value and facilitated by incremental government enablement. This has given a low-pressure atmosphere where adoption is a matter of efficiency as opposed to a mandate. This has led to e-invoicing gradually being integrated into normal business activities, especially in cases where organizations transact with the government or deal with a lot of transactions.
Early movers have already realized quantifiable rewards. Shorter accounts payable and accounts receivable (AP and AR) cycles will lessen delays in processing and payments, and automation will decrease the administrative expenses related to manual invoicing. Simultaneously, organized data enhances the visibility in the financial processes, thereby making the processes easier to track, predict, and make decisions. Here, e-invoicing in New Zealand is not a question of regulatory compliance, but rather of creating a more efficient, precise and scalable finance department.
Trust & Compliance
Cygnet’s platform is SOC 2 Type II certified and designed to support IRD audit requirements, including invoice retention (7+ years), data validation, and GST reconciliation. We use stringent data security policies and provide role-based security controls for sensitive invoice data.
Privacy and Legal Policies: Read about our Privacy Policy and Terms of Use.
FAQs
Yes, but you might have to run concurrent processes. A common approach by many businesses is to implement a hybrid model early on, with PEPPOL being used with related partners and traditional invoicing used with others until adoption.
The complexity of integration is based on your ERP. The older system is usually slower when it comes to integration using APIs compared to the outdated one.
PEPPOL makes the receipt of invoices easier without replacing internal approval processes. It can be used by businesses to combine it with the current approval systems to automate the validation and routing.
Yes, PEPPOL network is based upon standardized protocols and certified Access Point providers to provide secure and authenticated data exchange between parties.
Seek PEPPOL certification, established experience in the region, compatibility with ERP, and cloud deployment support. Important evaluation factors are service reliability and scalability.
Most organizations require a standardization process for their invoice data, verification of master data such as the New Zealand Business Number (NZBN), and synchronization of internal processes like AP and AR procedures for successful invoicing.