A comprehensive guide to e-invoicing: Formats, networks and implementation

E-invoicing is the exchange of structured, machine-readable invoice data between accounting systems over a compliant network. A PDF sent by email doesn’t count as an e-invoice, even though it’s technically a digital invoice. The structured data in e-invoices will validate automatically, flow into the enterprise resource planning (ERP) system without manual keying and meet the compliance requirements that governments are now mandating across countries in Europe, Asia-Pacific and beyond.

This guide covers what electronic invoicing is, how it works, which countries require it in 2026 and how to implement it inside NetSuite.

Key highlights:

• E-invoicing sends structured invoice data (often in formats such as XML UBL) between systems over compliant networks like Peppol. 
• Governments worldwide are mandating e-invoicing to close tax gaps and gain transaction-level visibility.
• Successful implementation requires native ERP integration so e-invoices don't create a separate workflow outside the accounting system.
• ZoneCapture e-invoicing handles compliant inbound and outbound e-invoicing directly inside NetSuite across Peppol and local networks.

What is e-invoicing?

An e-invoice is a structured data set – often XML or UBL format, though this varies by country – that contains all the information of an invoice and is transmitted electronically through a regulated network. The network validates the data in transit and routes it to the correct recipient.

Three things that are often confused with e-invoicing but aren’t:

• A PDF emailed to a customer. This is a digital invoice, but it’s unstructured. A person still needs to open it, read it and type the data into an accounting system.
• A scanned paper invoice. Even with optical character recognition (OCR) aiding input, this is a digitised image of an invoice instead of a structured data exchange.
• An invoice entered manually into a portal. This shifts the data entry from one party to another, but it doesn’t eliminate it.

E-invoicing means data flows machine to machine. The sender’s ERP generates a structured invoice, the network validates it and the receiver’s ERP ingests it automatically. The big most important takeaway is that there’s no human data entry on either side.

How e-invoicing works

The process follows five stages, regardless of which country or network is involved:

1. Invoice creation: The sender’s ERP generates the invoice in a structured format. The format depends on the country and network.
2. Validation: The invoice data is checked against the network’s schema before it leaves the sender’s system. Required fields, tax calculations, format compliance and recipient identifiers are all validated. Invalid invoices are rejected before transmission. 
3. Transmission: The validated invoice is sent through a compliant network. Peppol handles multi-country routing using the four-corner model (sender → sender’s Access Point → receiver’s Access Point → receiver). Country-specific clearance models like Italy’s SDI or Poland's KSeF route invoices through a government platform that approves them before delivery.
4. Receipt and processing: The receiver’s ERP ingests the structured data automatically without manual keying. This includes vendor details, line items, amounts and tax. The invoice enters the accounts payable workflow for matching, approval and payment.
5. Compliance reporting: In many mandates, the tax authority receives a copy of the invoice data during transmission (clearance models) or through periodic reporting (post-audit models like Portugal’s SAF-T). The European Union’s VAT in the Digital Age (ViDA) framework will introduce near-real-time digital reporting for intra-EU transactions from July 2030.

Key benefits of e-invoicing

E-invoicing delivers value both for the businesses exchanging invoices and governments mandating the shift.

For businesses, e-invoicing eliminates manual data entry on both the sending and receiving side. Invoices arrive as structured data that flows directly into the ERP, which means AP teams aren’t re-keying vendor details, line items or tax amounts from PDFs. That alone reduces processing errors and accelerates payment cycles. 

Structured data also enables automated three-way matching against purchase orders (POs) and delivery receipts, cutting exception handling time and speeding up the financial close. And because invoices validate before transmission, rejected or incorrect invoices get caught at the source rather than weeks later during reconciliation. 

For finance teams processing hundreds or thousands of invoices per month, the cost-per-invoice drops significantly when manual touchpoints are removed from the workflow.

For governments, e-invoicing gives tax authorities transaction-level visibility into commercial activity. Real-time or near-real-time reporting makes it harder to underreport revenue or issue fraudulent invoices, which is a key reason mandates are accelerating globally. 

Countries using clearance models – where the tax authority validates each invoice before delivery – gain even deeper oversight, effectively closing the gap between when a transaction happens and when the government sees it.

E-invoicing formats and networks

The format your e-invoice needs to use depends on which country you’re invoicing into and which network carries the transaction:

• Peppol: This is the dominant multi-country network, now operational in more than 30 countries and uses the Peppol BIS Billing 3.0 format based on UBL 2.1. Originally designed for B2G, it’s now expanding into business-to-business (B2B) transactions.
• UBL (Universal Business Language): UBL is the underlying XML standard used by Peppol and many national formats. UBL 2.1 is the most widely adopted version.
• Factur-X / ZUGFeRD: This is a hybrid format that embeds structured XML data inside a human-readable PDF that’s used in France and Germany. The invoice is readable by both machines and people, which makes it a bridge format for businesses transitioning from PDF to fully structured e-invoicing.
• FatturaPA: Italy’s mandatory format, transmitted through the SDI (Sistema di Interscambio) clearance platform. Every domestic B2B, business-to-government (B2G) and business-to-customer (B2C) invoice in Italy passes through SDI.
• CIUS-PT: Portugal’s national implementation of EN 16931 for B2G e-invoicing, submitted through the eSPap FE-AP platform.
• XRechnung: Germany’s structured e-invoice format for B2G and B2B, conforming to EN 16931.
• Country-specific formats: India (IRN via GST portal), Saudi Arabia (ZATCA FATOORA), Mexico (CFDI), and Brazil (NF-e). Each has its own format, transmission network and validation rules.

E-invoicing mandates in 2026: where compliance is required

E-invoicing mandates accelerated sharply in 2026. The EU’s VAT in the Digital Age package, adopted in March 2025, set the regulatory trajectory for all 27 member states, and individual countries are moving faster than the EU-wide 2030 deadline requires.

That said, mandates aren’t limited to the EU. Governments across the Middle East, Asia-Pacific and the Americas are rolling out their own requirements on independent timelines.

Here’s where mandates stand as of September 2026.

EMEA 

The EU’s ViDA framework itself requires structured e-invoicing for all intra-EU B2B transactions by 1 July 2030, using the EN 16931 standard. Member states are required to transpose the ViDA Directive into national law by 31 December 2026.

Current mandates in the EMEA region include: 

• Belgium went live with mandatory B2B e-invoicing on 1 January 2026. All VAT-registered businesses exchange structured e-invoices via the Peppol network in UBL format. There’s no phase-in by company size – the mandate applied to every business at once, with a three-month tolerance period that ended 31 March 2026.
• Poland activated its national e-invoicing platform, KSeF, for large taxpayers (annual turnover above 200 million zł) in February 2026, with most other VAT-registered businesses following in April 2026. Poland uses a clearance model where the tax authority validates each invoice before it reaches the buyer.
• France began its phased B2B e-invoicing mandate on 1 September 2026. From that date, all businesses are required to receive e-invoices. Large and mid-sized businesses are also required to send e-invoices for domestic B2B transactions, with small businesses following in September 2027.
• Germany required all businesses to receive structured e-invoices (EN 16931 format) from 1 January 2025. Sending obligations are being phased in from 2027 for businesses with annual turnover above €800,000, with all businesses covered by 2028.
• Italy has mandated e-invoicing for B2G, B2B and B2C transactions since 2019 through its SDI clearance system, making it one of the most mature e-invoicing regimes in Europe. The FatturaPA format was updated to v1.9.1 in May 2026.
• Spain is rolling out its Crea y Crece B2B e-invoicing mandate in phases, with large companies going first and smaller businesses following.
• Greece mandated structured B2B e-invoicing under Law 5222/2025. Large businesses (revenue above €1 million in 2023) have been required to comply since 2 March 2026. All remaining businesses follow from 1 October 2026. Invoices pass through the myDATA clearance platform for validation before reaching the buyer.
• The Netherlands has mandatory B2G e-invoicing in place and is evaluating a domestic B2B mandate alongside the EU’s ViDA requirements, with cross-border B2B mandated from July 2030.
• The Nordics – Norway, Denmark, Sweden and Finland – have long-standing B2G e-invoicing mandates and are among the most mature Peppol markets in Europe.
• The UK confirmed on 23 June 2026 that Peppol will be the interoperability framework for its planned B2B e-invoicing mandate, targeted for April 2029. A detailed roadmap is expected at the November 2026 budget.
• Portugal mandates B2G e-invoicing for all supplier sizes as of January 2026, with strict process requirements (ATCUD, QR code, monthly SAF-T reporting) applying to all invoices regardless of format. A B2B structured e-invoicing mandate is committed under ViDA but the effective date hasn't been finalised.
• Switzerland has no B2B mandate but requires B2G e-invoicing for federal contracts above CHF 5,000. Swiss businesses invoicing into the EU are increasingly affected by trading partners' mandates.
• Saudi Arabia is implementing its ZATCA FATOORA B2B e-invoicing mandate in phases. 

APAC

• Australia has mandatory B2G e-invoicing for federal agencies, with 30% Peppol processing targets by July 2026 and fully automated sending by December 2026. B2B remains voluntary.
• New Zealand requires B2G e-invoicing for central government agencies, with a large supplier mandate (revenue above $33 million NZD) taking effect 1 January 2027.
• Singapore is rolling out InvoiceNow (Peppol-based) with a phased mandate for government vendors.
• India requires e-invoicing for businesses above specified turnover thresholds via the GST e-invoicing portal.

United States 

The United States has no federal B2B e-invoicing mandate. Adoption is voluntary and market-driven through the Digital Business Networks Alliance (DBNAlliance), a Peppol-style exchange framework.

For finance teams operating across multiple countries, compliance is no longer a single-country project. It’s a rolling set of deadlines, formats and network requirements that varies by jurisdiction.

How to implement enterprise e-invoicing solutions in your ERP

Moving to e-invoicing isn’t a rip-and-replace project. You’re building on existing workflows by automating invoice capture, validation and transmission without disrupting how your team operates.

1. Assess your current invoicing and payment workflow

Before implementing anything, map out how invoices move through your organization today. Walk through the entire process from the moment a vendor invoice arrives to when payment hits their account. Identify where manual work happens in data entry, approval routing, exception handling and reconciliation.

Look at invoicing volume by entity, region and currency to understand where automation will have the biggest impact. Common findings include:

• Invoice approval delays caused by manual routing
• Duplicate data entry when invoices arrive via email then get keyed into the ERP
• Reconciliation gaps between what’s approved and what’s actually paid
• Compliance risks in regions with e-invoicing mandates your team isn’t meeting yet

2. Identify systems and data that require integration

E-invoicing doesn’t work in isolation. Look at every system that touches your invoice-to-pay process, including your ERP, procurement platform, approval workflows, banking systems and tax compliance tools. Determine what data needs to flow between these systems and where integrations already exist.

If you’re running NetSuite with third-party AP tools, this is where you’ll see how many handoffs and syncs are actually happening behind the scenes. The goal is to bring as much of this workflow as possible inside your ERP, reducing the number of systems you’re maintaining.

Key integration points to evaluate:

• Vendor master data and how it syncs across procurement and finance systems
• Purchase order data feeding into three-way matching logic
• Approval hierarchies and delegation rules
• Banking and payment processing connections for automatic reconciliation

3. Select an e-invoicing provider that supports your regions

Not all e-invoicing solutions handle every region’s requirements. If you operate in Europe, you need Peppol support. If you’re doing business in Mexico, Comprobante Fiscal Digital por Internet (CFDI) compliance is required. If you’re expanding into Asia-Pacific, you need a provider that understands the regulatory landscape in Singapore, Australia and beyond.

Choose a provider with proven experience in your markets who has already navigated the mandates, format requirements and network integrations you’ll need. Beyond regional coverage, evaluate how the solution fits your ERP architecture:

• Native ERP integration that doesn’t require middleware
• Support for multi-entity and multi-currency operations without custom development
• Validation against local tax rules and e-invoicing mandates
• Scalability to handle transaction volume growth

4. Map invoice fields and test end-to-end automation

Once you’ve selected a provider, you’ll need to map your invoice data to the structured formats required by e-invoicing networks. You’re defining how your business data translates into compliant e-invoices that meet regulatory requirements in every jurisdiction where you operate.

Work with your provider to map line items, tax codes, payment terms and vendor identifiers to the correct XML schema for each region. Run end-to-end tests covering:

• Invoice creation with all required fields populated correctly
• Validation against regional mandates and tax rules
• Transmission through the appropriate network with delivery confirmation
• Receipt and matching in the buyer’s system
• Exception handling when invoices don't match purchase orders or have data errors

5. Train staff and roll out in phases

Your AP team doesn’t need to become e-invoicing experts overnight. Focus training on what changes in their day-to-day work, including how invoices arrive in the system, how exceptions get flagged and how approvals route differently. Walk them through the new workflows with real examples from your test environment.

Phase your rollout by starting with a single entity or region where you can control variables and learn from the process:

• Start with a small vendor group processing invoices through the new system
• Expand to high-volume vendors once the team is comfortable
• Add regions and entities methodically based on regulatory timelines
• Monitor exception rates and approval cycle times to refine automation rules before scaling to full adoption

How to evaluate e-invoicing software for NetSuite

Choosing an e-invoicing solution for NetSuite comes down to these six criteria: 

1. Network support: Does the solution connect to Peppol and the local clearinghouses your countries require? Belgium and the UK use Peppol, Italy routes through SDI and Poland uses KSeF. If you operate across multiple regions, your provider needs to support multiple networks without requiring a separate connector for each one.
2. Format coverage: UBL, Factur-X, FatturaPA, XRechnung and local XML schemas all serve different markets. Your e-invoicing tool needs to generate and receive the formats your trading partners and tax authorities require. 
3. Inbound and outbound: Does the solution handle both receiving supplier e-invoices (AP) and sending customer e-invoices (AR), or only one direction? A tool that covers inbound but not outbound means you’re managing two separate e-invoicing workflows.
4. ERP architecture: Does the e-invoicing solution run inside NetSuite as a native SuiteApp, or does it require an external platform with a sync layer? Native means e-invoices enter the AP workflow directly without any portal switching required. 
5. Validation before posting: Does the tool validate invoice data against the network schema before the e-invoice enters NetSuite? Pre-posting validation catches compliance issues before they become rejected invoices or tax authority penalties.
6. Multi-country scalability: As new mandates go live, can the solution add countries without a separate implementation per mandate? With compliance timelines accelerating across Europe, Asia-Pacific and the Middle East, your e-invoicing solution needs to scale by configuration instead of by project. 

Best practices for your e-invoice workflow

E-invoicing implementation is the starting point. Long-term success depends on how well your workflow adapts to changing regulations, scales with business growth and maintains accuracy across your business operations.

Choose a platform that integrates with your ERP

The worst e-invoicing implementations happen when finance teams bolt another system onto their tech stack. You end up with invoices living in one platform, approval data in another and financial records in your ERP, all requiring manual reconciliation.

When e-invoicing runs natively in NetSuite or your core system, every invoice is automatically tied to your chart of accounts, vendor records and payment history without syncing delays or data gaps. Native integration means:

• Direct access to vendor master data without duplicate records or sync conflicts
• Automatic posting to the correct GL accounts based on invoice coding
• Unified approval workflows using your existing ERP hierarchies

Standardize data formats across vendors and partners

Your vendors aren't all sending invoices the same way. Some use XML, others send PDFs and a few still mail paper invoices. This inconsistency forces your AP team to handle each format differently, manually entering data from PDFs while structured invoices flow through automatically.

Work with your vendor base to standardize on e-invoicing formats that your system can process without manual intervention. The more vendors you convert to structured formats, the less manual work your team does. Vendor onboarding processes should explain your e-invoicing requirements upfront, and data validation rules should catch incomplete or incorrect invoices before they enter your system.

Prioritize compliance and auditability

E-invoicing mandates aren’t static. Governments update requirements, add new fields and change validation rules, sometimes with minimal notice. Your e-invoicing workflow needs to adapt quickly without disrupting business operations.

Build compliance into every step so that when auditors or tax authorities come calling, every invoice is instantly retrievable with a complete history of actions taken. 

Key elements include:

• Automated updates when regional e-invoicing mandates change
• Validation rules that catch errors before invoices leave your system
• Digital signature preservation proving invoices haven’t been altered post-transmission
• Retention period management based on the longest requirement across all jurisdictions where you operate

Communicate early with suppliers and internal teams

Your vendors don’t automatically know you’re switching to e-invoicing. If you flip the switch without warning, you’ll get confused calls, rejected invoices and vendors who keep sending PDFs because that’s what they’ve always done.

Start communications months before go-live for both internal and external stakeholders. Explain what’s changing, why it matters and what vendors need to do differently. Give them resources including onboarding guides, format examples and contact information for questions.

Internally, make sure your team understands:

• How invoice arrival and routing changes under the new system
• What exceptions look like and how to resolve them quickly
• Where to find invoice status and approval history

Automate validation and monitor performance continuously

E-invoicing without validation is faster chaos. Build automated checks that catch errors the moment an invoice enters your system, including wrong tax rates, missing purchase order numbers, duplicate invoice IDs and amounts that exceed tolerances. The system should flag these exceptions and route them to the right person for resolution, not let them sit unnoticed until month-end close.

Monitoring doesn’t stop after go-live. Track:

• Invoice processing time from receipt to approval compared to pre-automation benchmarks
• Exception rates by vendor to identify training opportunities or data quality issues
• Straight-through processing percentage showing how many invoices require zero manual intervention
• Days payable outstanding trends indicating whether you’re capturing early payment discounts

ZoneCapture automates e-invoicing inside NetSuite

ZoneCapture e-invoicing connects NetSuite directly to compliant e-invoicing networks for select markets, so your team sends and receives structured invoices without leaving the ERP.

• Peppol network connectivity. ZoneCapture connects to the Peppol network as a certified Access Point through a single integration inside NetSuite.
• Multi-country compliance. Support for Peppol, local clearance platforms and country-specific formats – so as new mandates go live, your team adds coverage without bolting on a separate tool per country.
• Inbound and outbound in one workflow. Receive supplier e-invoices into your AP workflow and send customer e-invoices from AR – both directions handled natively inside NetSuite.
• Pre-posting validation. Invoice data is validated against network schemas and tax authority requirements before it enters NetSuite, catching compliance issues before they become rejected invoices.