What is e-invoicing? A complete guide to models, mandates, and compliance

What e-invoicing actually is

E-invoicing is the structured, electronic exchange of invoice data between a seller and a buyer or a government tax authority. It is not a PDF emailed to a customer. The data is machine-readable, formatted to a government specification, and transmitted to a defined endpoint, such as a tax authority's platform or a customer's e-invoicing endpoint, often in real time or near real time. That makes every transaction auditable as it happens.

A scanned image or a Word file doesn't qualify either. Those are digital, but a human or an OCR tool still has to pull the numbers out. A true e-invoice carries the fields themselves, usually as XML, so they flow directly into an accounting system or a government platform.

The specific format varies by country, but every framework is built around the same core principle: enough structured detail to identify both parties, the goods or services exchanged, and the tax applied, so the transaction is independently verifiable. In Europe, most mandates build on a common standard called EN 16931, published by the European Committee for Standardization. EN 16931 is a semantic model, not a file format. It defines what data an invoice has to contain, then leaves the encoding to one of a few accepted formats:

• UBL (Universal Business Language), a structured XML format used widely across Europe and on the Peppol network.
• CII (Cross Industry Invoice), another structured XML format built for automated processing.
• Factur-X, a hybrid that embeds structured XML inside a human-readable PDF, used in France and Germany.

How does e-invoicing work?

The specifics vary by country, but almost every e-invoicing flow moves through the same four stages:

1. Create. Your billing system or ERP generates the invoice as structured data, usually XML, in the format the destination country requires, with every mandatory field populated.
2. Validate or exchange. Depending on the model, a government platform validates the invoice before it can be issued, or you exchange it directly and report the data to the authority.
3. Deliver. The invoice reaches your buyer through a government portal, a certified network like Peppol, or a direct connection.
4. Store. You archive the invoice in the required format for the country's retention period, so you can produce it in an audit.

Which of these steps involves the government, and when, is exactly what the four models below determine.

E-invoicing vs. an indirect tax return vs. a PDF invoice

A PDF invoice is a document you send to your customer. It proves what you charged, but a tax authority can't read it automatically.

An indirect tax return (a VAT, GST, or sales tax filing) is a periodic summary you submit after the fact, usually monthly or quarterly, reporting what you owe.

An e-invoice sits between the two. It's the transaction itself, reported in structured form at or near the moment it happens. That shift, from periodic summaries to real-time transaction data, is the whole point of the mandates.

Why governments mandate it

E-invoicing exists to combat VAT fraud and tax abuse, commonly known as the VAT gap. By capturing transaction data at the point of sale rather than the point of filing, tax authorities can cross-reference seller and buyer records in real time, closing the gap between what's owed and what's actually remitted. The European Commission expects the move to e-invoicing to cut VAT fraud by up to €11 billion a year and reduce compliance costs for EU traders by more than €4.1 billion a year over the next decade. Latin America proved the model works: Chile launched the first system in the early 2000s, and clearance-based e-invoicing has since spread to more than 80 countries.

The four common e-invoicing models, and what each one means for you

Countries don't enforce e-invoicing the same way. The differences can generally be broken down into two separate aspects, each of which is determined independently:

1. Timing Model: When will the government validate an invoice, and will an invoice only be considered legally issued once it has been validated? 
2. Architecture: How will an invoice be sent from the Seller to the Buyer, and will the government sit inside that flow?

Most explanations of e-invoicing focus primarily on the timing model, as it determines your operational workflow and whether a sale can be finalized before the government validates the invoice. However, architecture is a separate and equally important design decision. It dictates how invoices are transmitted between parties and explains why two countries that both use Peppol can have fundamentally different e-invoicing requirements.

Below, we break down the timing models and architectures most commonly used around the world today.

Post-audit

You send the e-invoice straight to your buyer in the required format. The tax authority doesn't touch it in real time, but it can request your records later and audit them. This is the traditional approach, and it puts the burden on you to store compliant invoices and produce them on demand. Germany's incoming B2B regime works this way.

Real-time reporting (CTC reporting)

The invoice goes directly to your buyer, and a copy of the data goes to the tax authority in near real time. The government sees every transaction but doesn't gate the invoice's validity on prior approval. Hungary and the upcoming French systems work this way.

Post-clearance

The invoice reaches your buyer first, and government approval follows shortly after — but that approval still decides whether the invoice was ever legally valid. It looks like RTR from the outside (invoice out, data follows fast), but a rejection here can undo the sale after the fact, which is what separates it from real-time reporting. South Korea is the reference case: its approval number arrives after delivery but still gates the buyer's input tax deduction.

Pre-clearance

You submit each invoice to a government platform before your buyer ever sees it. The platform validates it, and only then is it released for delivery. If an invoice fails clearance, it doesn't legally exist, so your buyer can't book it, and you can't recognize it cleanly. This is the strictest model. Italy's SdI, Poland's KSeF, Mexico's CFDI, India's IRP, and Malaysia's MyInvois all run this way.

Key takeaways:

• Post-audit: You carry the responsibility for record retention and audit risk after the transaction has occurred.
• Real-time reporting: Invoice data must leave your system within a defined timeframe, but a late or failed report results in a compliance penalty rather than unwinding the invoice.
• Post-clearance: You can send the invoice immediately, but a subsequent rejection can still invalidate the transaction.
• Pre-clearance: You cannot finalize a sale until the government approves the invoice.

The architecture comes next, determining how the invoice is transmitted to your end customer and whether the government is part of that exchange flow.

Who actually has to comply

Three things decide whether a mandate reaches you: who you sell to, what you sell, and where you're registered.

Who you sell to sets the timing. Business-to-government (B2G) sales trigger e-invoicing earliest almost everywhere. Business-to-business (B2B) mandates are the fast-expanding middle. Business-to-consumer (B2C) is usually last, with a few exceptions for digital services like Taiwan's.

The direction of e-invocing is clear. Under the EU's VAT in the Digital Age (ViDA) reforms, cross-border B2B e-invoicing and digital reporting will become mandatory across the EU by 2030, while many Member States are introducing domestic mandates even sooner.

Does e-invoicing apply to your business?

The mandate that catches you depends less on your industry label than on where you're registered, who you sell to, and what you sell. A few common cases:

• Software and digital services (SaaS). If you sell subscriptions or digital services as a non-resident, your exposure has historically been narrower: business-to-government sales, countries where you hold a local registration, and foreign business-to-consumer digital-services rules like Taiwan's. That's changing as B2B mandates widen to cover services, so cross-border software sales are increasingly in scope.
• Ecommerce and online retail. If you sell physical goods online across borders, you meet clearance mandates sooner, especially in Latin America, and you may also face marketplace or platform reporting rules where a platform collects and remits on your behalf.
• Physical goods, hardware, and manufacturing. Goods sellers carry the broadest exposure. Clearance systems in Latin America have covered goods for years, and B2B mandates across the EU and Asia reach wholesale and distribution transactions.
• Marketplaces and platforms. Under ViDA, platforms in some sectors take on deemed-supplier VAT obligations, which pulls invoicing and reporting duties toward the platform rather than the underlying seller.

Whatever you sell, the same three tests below decide scope: your registration footprint, your buyer type, and the countries you sell into.

Resident vs. non-resident: the distinction that trips up sellers

Whether you have a local presence usually decides whether a domestic mandate applies to you.

If you have a local entity, a permanent establishment, or a local VAT or GST registration, you generally fall under the country's domestic e-invoicing rules like any local business. A registered entity in Poland issues through KSeF; a GST-registered business in India over the threshold reports through the IRP.

If you're a non-established, foreign seller, the picture is different, and it varies by country. Many domestic B2B mandates apply only to businesses established in the country. France's mandate, for example, centers on establishments in France, and foreign VAT-registered but non-established businesses can fall outside the obligation to issue, while still facing e-reporting duties. Malaysia has excluded non-resident digital providers from its e-invoicing mandate.

But some countries specifically target foreign sellers. Taiwan requires foreign providers of digital services to consumers to issue cloud-based government uniform invoices (eGUI), even though Taiwan has no equivalent domestic mandate for local businesses. If you sell software to Taiwanese consumers, you're in scope regardless of where you're based. For the eGUI requirements, who's in scope, and how issuance works, see our full guide to e-invoicing in Taiwan.

Two more shifts to watch. Under ViDA, cross-border intra-EU B2B transactions will require e-invoicing and near-real-time digital reporting from 1 July 2030, which reaches any business trading across EU borders, resident or not. And more countries are extending digital reporting to non-residents each year, so an exemption today isn't a guarantee tomorrow.

One clarification on terminology: no live mandate governs e-invoicing between two countries yet, and ViDA’s 2030 rules will be the first. What exists today are domestic systems that already pull cross-border transactions into scope. Italy has required cross-border invoice data to flow through its SdI platform since 2022, and clearance systems like India’s IRP and Mexico’s CFDI already cover export invoices. So for now, cross-border usually means a domestic mandate reaching your foreign transactions, not a separate cross-border regime.

The practical test: check whether you have a local registration or establishment, whether you sell to government buyers, and whether you sell digital services to consumers in a country like Taiwan. Any one of those can put you in scope.

Where mandates stand in 2026

E-invoicing is rolling out on staggered timelines. A snapshot of the deadlines most relevant to global sellers:

The United States has no federal B2B, B2G, or B2C e-invoicing mandate. 

What Peppol is, and why it keeps coming up

Peppol is a network of certified access points that route structured invoices between trading partners across more than 40 countries. You connect to one access point, and it can reach any other party on the network, so you and your buyer don't need to run the same software. Because a single connection serves many countries, Peppol is often the shortest path to multi-country compliance, and it's the backbone of the mandates in Belgium, Australia, Singapore.

How e-invoicing changes the way you sell

E-invoicing runs inside your order-to-cash flow, not as a filing task you handle at month-end. That means it touches systems and habits you might not associate with tax:

• Your invoice has to be complete and correct at the moment of issuance, not reconciled later. Missing a buyer's tax ID or a required field can block the invoice from clearing.
• Under clearance models, you may not be able to deliver goods or provide digital goods until the invoice is validated.
• Your billing system, ERP, and tax engine all need to share the same transaction data, or you'll produce invoices that don't match your returns.
• You have to store invoices in the required format for the required retention period, which differs by country.

Benefits of e-invoicing

Compliance is the reason mandates exist, but structured invoicing pays off even in markets where it isn't required yet:

• Cleaner data everywhere downstream. Every invoice enters your systems as structured, validated fields instead of text trapped in a PDF, so your revenue reporting, forecasting, and reconciliations all draw from one accurate source.
• Faster payment. Structured invoices flow straight into your buyer's system and get approved without manual re-keying, which shortens your collection cycle.
• Fewer disputes, because the data is validated against a required schema before it's sent. Missing tax IDs, wrong rates, and typos get caught before they turn into rejected invoices.
• Producing records for an audit becomes a query instead of a scramble, since every invoice is stored in a structured, timestamped format.
• Real-time invoice data gives you a live view of what's been issued, cleared, and paid, without stitching together spreadsheets.

The catch: these gains only show up if your e-invoicing runs on the same data as the rest of your finance stack. Bolt on a separate tool and you trade manual invoicing for manual reconciliation.

What to look for in an e-invoicing vendor

Coverage is the first filter, but not the only one. Before you sign, check that a vendor can:

• Handle every model you're exposed to, whether clearance, post-audit, decentralized, or reporting, rather than one country's approach.
• Create, transmit, and store invoices in each country's required format, including connections to Peppol and government portals.
• Support the resident and non-resident scenarios that apply to you, including foreign digital-services rules like Taiwan's.
• Keep up with changing rules and deadlines so you're not tracking them yourself.
• Connect to your billing system or ERP without a custom build for every country.
• Tie e-invoicing to the rest of your tax compliance, from calculation to registration to filing, instead of running as a separate tool you reconcile by hand.

That last point matters more than it looks. E-invoicing runs on the same transaction data as your tax calculations and returns. When it lives in a different system, you reconcile twice, and you tend to find the mismatches during an audit.

How Anrok handles e-invoicing

Because Anrok already ingests your sales transactions and accounts receivable data to calculate and apply tax, it's well-positioned to package and submit that data to the required endpoints on your behalf, with no additional work in your billing or finance systems. The invoice data behind your calculations and filings is the data that produces your e-invoices, so there's no separate vendor to stitch in and no second system to reconcile against your returns.

E-invoicing mandates are expanding quickly, with new countries introducing requirements and existing frameworks maturing. Anrok monitors these developments closely and updates its coverage and this guidance as the rules change. Because Anrok pairs automation with an in-house team of tax experts, the details behind each country's format and model are checked, not just generated.

If you expect an e-invoicing requirement in a market you sell into, talk to our team about what compliance looks like there.

Frequently asked questions

Is a PDF invoice an e-invoice?

No. A PDF is a digital image of an invoice that a person or OCR tool has to read. An e-invoice carries structured data, usually XML, that software reads directly, and most mandates won't accept a PDF as compliant.

What's the difference between e-invoicing and a VAT or GST return?

A return is a periodic summary of what you owe, filed after the fact. E-invoicing reports the individual transaction in structured form at or near the moment it happens. Many countries are moving from returns toward real-time e-invoice data.

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

E-invoicing sends the structured invoice to your buyer or a clearance platform as the legal document. E-reporting sends transaction data to the tax authority for visibility, without the reported data being the invoice itself. Some countries require both: you issue the e-invoice and separately report the data.

Does e-invoicing apply to SaaS and digital services?

Yes, increasingly. Many mandates started with physical goods, but software and digital services are being pulled in as B2B rules expand and thresholds drop. Some countries, like Taiwan, specifically require foreign digital-services sellers to issue e-invoices for B2C sales.

I'm a US company with no foreign entity. Do I need to worry about it?

There's no US federal mandate today. It becomes relevant when you sell into countries that require e-invoicing, when you register for VAT or GST abroad.

I'm not established in a country but I sell there. Am I in scope?

Sometimes. Many domestic B2B mandates apply only to established businesses, and non-residents can be exempt from issuing while still owing e-reporting. But foreign digital-services rules (Taiwan) and cross-border EU rules under ViDA reach non-residents directly, so it depends on the country and what you sell.

What formats will I need?

It varies by country. In the EU, most mandates accept UBL, CII, or Factur-X under the EN 16931 standard. Latin America and Asia use their own national XML or JSON schemas, such as Mexico's CFDI or India's GST INV-01.

What is Peppol, and do I have to join it?

Peppol is an international exchange network used by countries like Belgium, France, and Australia. Whether you need it depends on where you sell. In network-model countries, connecting to a Peppol access point is how you send and receive compliant invoices.

What happens if I don't comply?

Consequences range from penalties and rejected invoices to blocked transactions. Under clearance models, an invoice that fails validation isn't legally valid, and in India an invoice without a valid IRN can't support your buyer's input tax credit.

When does ViDA take effect?

The EU adopted ViDA on 11 March 2025. E-invoicing and digital reporting for cross-border intra-EU B2B transactions become mandatory on 1 July 2030, and member states with domestic real-time reporting systems must align with the EU model by 1 January 2035.

‍