What is E-invoicing?

An e-invoice is not a PDF sent by email. That distinction matters more than it sounds. A true e-invoice is a structured data file, machine-readable from creation to receipt, that moves through a regulated network and feeds directly into accounting systems and, increasingly, tax authority reporting pipelines. The PDF in your inbox is a human-readable document. An e-invoice is a data transaction.

Governments worldwide have figured this out. Over 60 countries now mandate some form of e-invoicing for B2B transactions, and more are legislating requirements every year. The drivers are straightforward: VAT gaps in the EU alone exceed €60 billion annually, and structured e-invoicing lets tax authorities close that gap by receiving transaction data in near real-time rather than waiting for annual returns.

For finance and billing teams, e-invoicing compliance is no longer optional in most markets. The question is how your billing infrastructure connects to the regulated networks your customers and governments require.

What Makes an Invoice "Electronic"

The word electronic is doing heavy lifting in most e-invoicing regulations. A PDF is electronic in the colloquial sense. Regulators mean something specific: a structured data format where invoice fields are machine-readable and can be validated, processed, and reported without human intervention.

The three main structured formats used across global e-invoicing mandates:

UBL (Universal Business Language): An XML-based standard maintained by OASIS, widely used in Europe and Asia-Pacific. UBL defines a common vocabulary for invoice fields so that any system reading UBL can extract line items, tax amounts, payment terms, and party identifiers without custom parsing.

CII (Cross Industry Invoice): An XML standard developed by UN/CEFACT, used in Germany, France, and several EU member states. Conceptually similar to UBL with different schema conventions.

Factur-X / ZUGFeRD: A hybrid format that combines a human-readable PDF with embedded structured XML. Useful for the transition period: the PDF satisfies human readers, the embedded XML satisfies machine processing requirements. France and Germany use variants of this hybrid approach.

PEPPOL BIS: Not a format but a transmission framework. PEPPOL (Pan-European Public Procurement OnLine) provides the network infrastructure over which UBL and CII documents travel. Widely adopted in the EU, Singapore, Australia, and New Zealand.

How E-Invoicing Mandates Work: Two Models

Countries have converged on two architectural approaches for mandatory e-invoicing.

Clearance model (real-time): The invoice must be submitted to the tax authority for validation before it can be sent to the buyer. The authority issues a clearance token; without it, the invoice is legally invalid. Mexico's CFDI system and Brazil's NF-e are the most mature examples. Italy's SDI (Sistema di Interscambio) routes every B2B invoice through the government's central hub. In these models, the tax authority sees every invoice in real time.

Reporting model (post-transmission): Invoices are exchanged directly between supplier and buyer, but a defined subset of data must be reported to the tax authority, either simultaneously or within a short window. France's reform uses this model: invoices route between accredited private platforms, with regulatory data transmitted to the public portal in parallel. Spain's SII (Suministro Inmediato de Información) requires transaction data reported within four days.

The clearance model gives authorities more control and closes VAT gaps faster. The reporting model preserves more flexibility for businesses and platforms but still achieves near-real-time visibility for tax administration. Most new mandates are moving toward clearance or hybrid approaches.

The Global Mandate Landscape

The EU's VAT in the Digital Age (ViDA) directive, expected to phase in from 2028, will introduce mandatory e-invoicing and digital reporting for intra-EU B2B transactions. Member states operating ahead of ViDA (France, Germany, Italy, Spain) are already shaping what the bloc-wide standard will look like in practice.

What E-Invoicing Compliance Requires Operationally

Most finance teams underestimate how much their billing stack needs to change to support e-invoicing mandates.

Structured data at invoice creation. Your billing system needs to produce invoices in the required structured format, not just generate a PDF. If your billing tool produces PDFs and you convert them to XML downstream, that conversion introduces error risk and usually doesn't satisfy regulatory requirements that call for native structured output.

Connection to the regulated network. In clearance-model countries, your billing system needs a certified connection to the tax authority's API or hub. In reporting-model countries, you need a connection to an accredited platform or intermediary. Direct connectivity is possible; most companies use a certified service provider as the integration layer.

Buyer identification. E-invoicing networks route invoices to buyers via electronic addresses registered in central directories. Your billing system needs to store and transmit the correct electronic identifier for each customer, which in practice means collecting registration numbers (VAT ID, SIREN, SIRET, GSTIN depending on jurisdiction) at onboarding and keeping them current.

Lifecycle status handling. Most mandate frameworks require suppliers to receive and process status messages back from the network: invoice received, accepted, rejected, disputed, paid. Your billing system needs to handle these status updates and tie them back to the original invoice record. For accounts receivable, this replaces manual follow-up with structured workflow.

Archiving requirements. E-invoices must typically be archived in their original structured format for 7-10 years depending on jurisdiction, not just stored as PDFs. The archive needs to maintain the integrity of the original data, which means storing the XML alongside any human-readable rendition.

E-Invoicing vs. EDI

Electronic Data Interchange (EDI) has existed since the 1970s and is widely used in retail, logistics, and manufacturing supply chains. EDI is structured machine-to-machine data exchange, which sounds like e-invoicing. The difference is standardization and mandate.

EDI implementations are typically bilateral: two trading partners agree on a specific message format (EDIFACT, X12, or a proprietary schema) and build a point-to-point integration. It works well within established supply chains but doesn't scale to open networks where you may need to exchange invoices with hundreds of counterparties using different systems.

Modern e-invoicing mandates use standardized formats (UBL, CII) over open networks (PEPPOL) so that any two businesses can exchange invoices without a bilateral integration agreement. This is the infrastructure shift that makes tax authority reporting feasible at scale: a single standard that all participants connect to once.

E-Invoicing and AI-Era Billing

For companies billing on usage-based or AI-native models, e-invoicing mandates add a layer of complexity that traditional subscription billing doesn't face. A flat monthly SaaS invoice is structurally simple. An invoice for variable API consumption, with usage-based line items, credit offsets, and tiered pricing, requires more precise structured data at the line-item level.

Mandates that require real-time or near-real-time reporting also interact with usage-based billing cycles. If you bill monthly in arrears for consumption that occurred throughout the month, your reporting timeline needs to align with the mandate's reporting window. In some jurisdictions, that requires transmitting transaction data as it occurs, not just when you invoice.

FAQ

Q: Is a PDF invoice sent by email an e-invoice?

No, under any current mandate. A PDF is a document. An e-invoice is structured data. Some jurisdictions accept hybrid formats like Factur-X (PDF with embedded XML) as compliant, but a plain PDF does not satisfy e-invoicing requirements regardless of how it was transmitted.

Q: Does e-invoicing apply to B2C transactions?

Most mandates focus on B2B domestic transactions. Some jurisdictions extend requirements to B2C at higher transaction volumes, and some (notably Brazil and Mexico) cover both. The French reform covers B2B domestic invoices but uses a separate e-reporting flow for B2C and cross-border transactions.

Q: What's the difference between e-invoicing and e-reporting?

E-invoicing governs how invoices are exchanged between buyer and supplier. E-reporting governs what transaction data is reported to the tax authority. In reporting-model countries, the two are parallel obligations: you exchange the invoice through the regulated network and separately report a defined data subset to the tax authority. They use different data flows and may have different timing requirements. See France's e-invoicing reform for how the two flows work in practice.

Q: How does PEPPOL relate to e-invoicing mandates?

PEPPOL is a network and a set of technical specifications for transmitting structured documents between registered access points. It is not a mandate, but several countries have adopted PEPPOL as the technical infrastructure for their mandate. France's reform uses PEPPOL interoperability for platform-to-platform exchange. Germany's XRechnung uses PEPPOL for public sector invoicing. Singapore and Australia have built their voluntary e-invoicing networks on PEPPOL. Using PEPPOL-compatible infrastructure means a single integration can serve multiple markets.

Q: What happens if my billing system doesn't support structured invoice formats?

You typically have two options: upgrade your billing system to produce native structured output, or use a certified intermediary that takes your existing output and transforms it into the required format. The second option is faster to implement but introduces a dependency and a point of failure. For companies with significant invoice volumes in mandate markets, native structured output is the more durable solution.

Q: How do I know if my current billing system is ready for e-invoicing mandates?

Most billing systems built around PDF generation and email delivery are not. The gaps show up in three places: structured format output (your system needs to produce UBL, CII, or equivalent natively), network connectivity (you need a certified connection to the relevant accredited platform or tax authority hub), and lifecycle status handling (your AR workflow needs to receive and process status callbacks). Solvimon's billing infrastructure is built to support e-invoicing compliance across mandate markets, including the structured data pipelines and platform connectivity that legacy billing tools weren't designed for.

Q: Can Solvimon help us comply with e-invoicing requirements in markets where we're growing?

Yes. Solvimon supports e-invoicing compliance as part of its core billing infrastructure, including structured invoice generation, accredited platform connectivity, and the lifecycle status flows that mandate frameworks require. If you're expanding into EU markets with active mandates or preparing for the French reform rollout, talk to the Solvimon team about what your compliance stack needs to look like.

Q: We use a legacy ERP for invoicing. Do we need to replace it to comply?

Not necessarily, but it depends on what your ERP can produce natively. If it outputs structured XML in a supported format, connecting it to an accredited platform is the primary integration task. If it only produces PDFs, you'll need either a transformation layer (a certified intermediary that converts your output) or a billing system that generates structured invoices upstream of the ERP. Solvimon can sit in that upstream layer, producing compliant structured invoices that feed your ERP and connect to the regulated network.