Global E-Invoicing Mandates: The Guide for US-Headquartered Companies

The United States has no e-invoicing mandate. There is no IRS clearance platform, no federal structured-invoice format, and no requirement to submit invoices to a government system before sending them to a customer.

That single fact explains why so many US-headquartered companies are behind on this. The tax function sits in the US, where the obligation doesn't exist — while the obligations themselves accumulate in Italy, Poland, France, Romania, Germany, Belgium, and a growing list of other countries where the company has subsidiaries, VAT registrations, or customers. E-invoicing compliance is a foreign problem that lands on a domestic desk.

This guide covers how mandates actually attach to a US company, why the "we're not established there" assumption is sometimes right and sometimes dangerously wrong, and what the map looks like in 2026.

Four Ways a Foreign Mandate Catches a US Company

E-invoicing mandates are national laws. They don't apply to you because you're American — they apply because of what your business does inside a mandating country. There are four distinct triggers, and most multinationals have at least two of them:

• 1. A local subsidiary. Your Italian, Polish, or French entity is a locally established business, and the local mandate applies to it in full — issuing, receiving, or both. This is the unambiguous case.
• 2. A foreign VAT registration without establishment. Many US companies hold VAT registrations in countries where they have no office or staff — common for digital services, e-commerce, and inventory held abroad. Whether the e-invoicing mandate follows the VAT registration differs by country (more on this below — it's the single most misunderstood point).
• 3. Selling to customers in a mandated country. France's mandate requires every French-established business to be able to receive structured e-invoices from September 2026. Germany's receiving obligation has been live since January 2025. If your enterprise customers are French or German, they will increasingly ask you to deliver structured invoices — not PDFs — even where you have no legal obligation of your own.
• 4. Receiving invoices from local suppliers. Several regimes regulate the inbound side: your small Romanian or Polish entity may be required to retrieve supplier invoices from a government platform even if it issues almost nothing. This is the accounts payable trap — we've written a dedicated guide to inbound e-invoicing and AP receiving obligations.

The Establishment Test: Where "We're Not Established There" Works — and Where It Doesn't

The most consequential technical question for a US tax team is whether a mandate applies to non-established businesses that merely hold a local VAT registration. Countries answer this differently, and getting it wrong in either direction is expensive — either you build compliance you don't need, or you silently accumulate penalties.

Countries where a non-established VAT registration is generally out of scope of the issuance mandate:

• Italy — the SDI mandate applies to businesses established in Italy. A US company with a direct Italian VAT registration (no establishment) is not required to issue FatturaPA through SDI.
• Poland — KSeF applies to taxpayers established in Poland or with a Polish fixed establishment that participates in the transaction. A bare VAT registration doesn't trigger it.
• Germany, Belgium, France — the core B2B mandates are framed around domestically established businesses (France pushes non-established, VAT-registered businesses into a separate e-reporting obligation instead).

Countries where the obligation follows the VAT registration — established or not:

• Romania — RO e-Factura covers domestic B2B supplies by non-established companies that are VAT-registered in Romania. A US company with a Romanian VAT number issuing domestic invoices is in scope.
• Hungary — real-time invoice reporting (RTIR) attaches to every invoice issued under a Hungarian VAT number, including by non-established businesses.
• Spain — SII real-time reporting applies to VAT-registered businesses meeting the criteria (monthly filers, large taxpayers, VAT groups) regardless of establishment.

Two practical consequences. First, you cannot answer "do we have e-invoicing obligations?" from a list of countries alone — you need the registration footprint and the establishment analysis per country. Second, the analysis has a shelf life: scopes change (Romania extended to B2C in 2025; Poland's rollout phased through 2026), so a position taken in 2024 is not evidence of compliance in 2026.

The 2026 Map: Where the Mandates Are

Live now:

• Italy — FatturaPA via SDI, mandatory for established businesses since 2019. The longest-running clearance mandate in Europe. Italy guide →
• Poland — KSeF went live in February 2026 for the largest taxpayers, extending to all established VAT payers from April 2026. Invoices are not legally valid until the government assigns a KSeF number. Poland guide →
• Belgium — structured B2B invoicing over the Peppol network, mandatory since January 2026. Belgium guide →
• Romania — RO e-Factura for B2B (since 2024) and B2C (since 2025), including non-established VAT registrations. Romania guide →
• Germany — receiving obligation live since January 2025: every German business must be able to accept EN 16931 structured invoices. Sending obligations phase in through 2027–2028. Germany guide →
• Hungary, Greece, Spain — real-time reporting regimes (RTIR, myDATA, SII) that are functionally as demanding as e-invoicing: transaction data must reach the authority within a mandated window. Real-Time Reporting →

Imminent:

• France (September 2026) — the largest mandate in Europe. All French-established businesses must be able to receive e-invoices from 1 September 2026; large and mid-size companies must also send. SMEs follow in September 2027. See the France September 2026 checklist.
• Spain VeriFactu — certified invoicing software requirements rolling out across 2026. VeriFactu guide →
• Gulf states — Saudi Arabia's ZATCA integration waves continue, and the UAE is phasing in B2B e-invoicing from 2026–2027.

The direction of travel: the EU's ViDA package makes structured digital reporting the default for intra-EU B2B by 2030 and removes the bureaucratic friction that used to slow national mandates down. Countries that haven't mandated yet, will. See the full 2026 EU mandate breakdown and our live coverage map.

The Mistakes US Tax Teams Actually Make

• Treating it as a finance-systems project per country. A per-country ERP bolt-on for Italy in 2019, another for Poland in 2026, another for France — each with its own vendor, format logic, and failure modes. By country five, the maintenance burden exceeds the original build.
• Assuming the ERP will handle it. ERP vendors ship format generators, but clearance mandates are integration problems: government APIs, authority credentials, asynchronous status polling, per-country accreditation. SAP's own gap here is well documented — see our S/4HANA e-invoicing guide.
• Ignoring the receiving side. Receiving obligations (Germany 2025, France 2026, Belgium's Peppol inbound) arrive before sending obligations and apply to small entities with trivial invoice volumes. The inbound guide covers this →
• Confusing e-invoicing with real-time reporting. Hungary and Spain don't clear invoices — they demand the data within seconds or days. Different plumbing, same deadline pressure, and a compliance inventory that only counts "e-invoicing countries" misses them.
• Taking a position once and filing it away. Scope rules changed in Romania, Poland, France, and Spain within the last 24 months alone. Mandate monitoring is a standing function, not a one-off memo — this is exactly what Clearvo's Compliance Radar exists for, free for up to 5 countries.

What a US Tax Team Should Do, In Order

• 1. Inventory the footprint. Every legal entity, every VAT registration, every country where you invoice or are invoiced domestically. This list — not the org chart — defines your exposure.
• 2. Run the establishment analysis per country. Which registrations are established vs. non-established, and does that country's mandate reach non-established registrations? The table above is the starting point.
• 3. Separate the three obligation types. Issuing (clearance or exchange), receiving, and real-time reporting. A country can impose any combination.
• 4. Sequence by enforcement date, not by revenue. Your smallest entity may carry the earliest deadline. A Romanian entity with 20 invoices a month was in scope two years before your French headquarters entity.
• 5. Consolidate onto one integration. The alternative to per-country projects is a single API that handles format generation, authority submission, clearance polling, and status webhooks in every mandated country. That is precisely what Clearvo's e-invoicing API does across 32 countries — with direct authority connections to SDI, KSeF, ANAF, myDATA, XRechnung and more, a certified Peppol Access Point, and no per-country implementation projects.

The compliance burden is real, but it's also bounded: mandates converge on a handful of technical patterns (Peppol exchange, clearance platforms, real-time reporting), and a platform that already speaks all of them turns each new country from a project into a configuration change. US companies have one genuine advantage here — no domestic legacy system to unpick. The ones that treat global e-invoicing as one architecture decision, made once, are done with this topic. The ones that treat it as a sequence of country fire drills never are.