TLDR
- France’s e-invoicing mandate for large companies takes effect September 1, 2026. Mid-size companies follow in 2027. US companies billing French clients are in scope if they are VAT-registered in France.
- Germany requires all businesses to accept e-invoices from January 1, 2025, and mandates structured sending for most companies by January 1, 2027.
- The EU’s ViDA (VAT in the Digital Age) package, now formally adopted, sets a 2030 cross-border baseline but individual member states are moving faster with their own timelines.
- US SaaS companies selling into the EU through a Merchant of Record or with local VAT registrations are often directly in scope, not just their European subsidiaries.
- Standard invoicing API stacks typically generate PDFs or basic JSON , most do not support structured e-invoicing formats like XRechnung, Factur-X, or PEPPOL out of the box, which is a compliance gap that surfaces late.
E-invoicing mandates by country vary widely in scope, format, and timeline, but the 2026 to 2028 window is when most major European markets enforce structured sending requirements. France, Germany, Poland, Romania, and Belgium all have active or imminent mandates. US companies with VAT registrations in the EU, or those selling through entities that hold local tax IDs, are frequently in scope. The PDF invoice that worked everywhere last year may trigger penalties in France as soon as September 2026.
Why US Companies Think E-Invoicing Is Someone Else’s Problem
The assumption is that e-invoicing mandates apply to local companies selling locally. That is wrong in most European contexts. The trigger is not where your company is headquartered. It is where you are VAT-registered, who your customer is, and whether the transaction is business-to-business within a mandate’s jurisdiction.
A US SaaS company that registered for VAT in France to handle local enterprise sales, or that uses a Merchant of Record that is VAT-registered there, may be a “supplier” under French rules. The obligation to issue a structured Factur-X or UBL invoice falls on whoever is the VAT-liable seller in that country. Your headquarters in Austin does not exempt you.
The same logic applies to Germany. Any business registered for German VAT and issuing B2B invoices to German companies is required to be able to receive structured invoices as of January 1, 2025, and must be able to send them in a structured format by January 1, 2027. The law covers domestic transactions, not just German-incorporated companies.
The FintechSpecs Mandate Exposure Map: How to Read Your Risk by Country
Not every mandate works the same way. Some countries require real-time clearance through a government platform before an invoice is legally valid. Others simply require a structured machine-readable format. A few use a hybrid model where invoices go through a certified service provider rather than directly to a tax authority. Understanding which model applies changes what your technical stack needs to do.
Below is the current compliance timeline for the markets most relevant to North American companies selling into Europe and Latin America. Dates reflect the most recently published official timelines. Verify each against the relevant tax authority before making infrastructure decisions, as these timelines have shifted more than once.
| Country | Model | Format(s) | B2B Mandate Effective | Who Is In Scope | Penalty Risk |
|---|---|---|---|---|---|
| France | Y-shape (PPF + PDPs) | Factur-X, UBL 2.1, CII | Sept 1, 2026 (large); Sept 1, 2027 (mid); Sept 1, 2027 (small) | VAT-registered businesses issuing B2B invoices to French entities | High; invoice may not be legally valid without structured format |
| Germany | Decentralized (no clearance) | XRechnung, ZUGFeRD (Factur-X equivalent) | Jan 1, 2025 (receive); Jan 1, 2027 (send, large); Jan 1, 2028 (send, SMEs) | All German VAT-registered B2B sellers | Medium; recipient must be able to process structured invoices now |
| Poland | Centralized clearance (KSeF) | FA_VAT (national XML) | Feb 1, 2026 (large taxpayers); April 1, 2026 (others) | All VAT-registered businesses in Poland | High; uncleared invoices may be legally void |
| Romania | Centralized clearance (RO e-Factura) | UBL 2.1 | Jan 1, 2024 (B2G); July 1, 2024 (B2B large); Jan 1, 2025 (all B2B) | All businesses issuing invoices to Romanian entities | High; fines apply per non-compliant invoice |
| Belgium | PEPPOL 4-corner | PEPPOL BIS Billing 3.0 | Jan 1, 2026 (B2B, phased) | Belgian VAT-registered companies | Medium to high; enforcement ramps through 2026 |
| Italy | Centralized clearance (SDI) | FatturaPA (XML) | Already mandatory (since 2019 for domestic B2B) | All Italian VAT-registered entities | High; already enforced |
| Spain | VERI*FACTU + SIF | XML (national schema) | 2025 (large); 2026 (SMEs, phased) | Spanish tax-resident businesses | Medium; real-time reporting to AEAT required |
| Brazil | Centralized clearance (NF-e/NFS-e) | XML (SEFAZ schema) | Already mandatory for goods; services mandate expanding 2025 to 2027 | All Brazilian tax-registered entities | High; already enforced with real-time clearing |
| Mexico | Centralized clearance (CFDI via SAT) | XML 4.0 (CFDI) | Already mandatory; CFDI 4.0 since Jan 2022, full enforcement 2024 | All Mexican tax-registered entities | High; already enforced |
| EU Cross-Border (ViDA) | Digital reporting requirements (DRR) | To be defined; PEPPOL-aligned likely | 2030 (baseline for EU-wide cross-border) | Intra-EU B2B cross-border transactions above VAT thresholds | Low until 2030; member state rules apply in the interim |
What Is ViDA and Does It Change Anything Before 2030?
The EU’s VAT in the Digital Age package, commonly called ViDA, was formally adopted by the EU Council in 2024. Its headline cross-border digital reporting requirement does not take full effect until 2030. That date leads many finance teams to treat ViDA as a distant problem.
What ViDA actually does in the near term is remove an obstacle. Before ViDA, EU member states needed a formal derogation from the EU Commission to mandate domestic e-invoicing. ViDA eliminated that requirement. The result: every member state can now legislate its own domestic mandate without waiting for Brussels. France, Germany, Belgium, and Poland all moved quickly once that barrier dropped. The 2026 to 2028 wave of mandates is a direct consequence of ViDA clearing the path, even though ViDA’s own cross-border rules come later.
For North American companies, the practical implication is that there is no single EU e-invoicing standard yet. Each member state has its own format, its own platform, and its own timeline. A company selling into France, Germany, and Belgium simultaneously needs three different technical implementations today, not one.
What Does the France E-Invoicing Mandate Actually Require?
France’s mandate is structured around a “Y-model.” Invoices flow from the seller’s system through a registered private platform, called a PDP (Plateforme de Dématérialisation Partenaire), which validates and transmits the invoice to a government hub called the PPF (Portail Public de Facturation). The buyer’s PDP then retrieves it.
Three structured formats are accepted: Factur-X (a hybrid PDF with embedded XML, also known internationally as ZUGFeRD 2.x), UBL 2.1, and UN/CEFACT CII. A standard PDF invoice does not satisfy the mandate, even if it contains all the required VAT fields. The structured data must be machine-readable in one of those schemas.
The September 1, 2026 deadline applies to large companies, defined in France as those with more than 5,000 employees or annual turnover exceeding 1.5 billion euros. Mid-size companies (250 to 5,000 employees, or turnover between 50 million and 1.5 billion euros) follow on September 1, 2027. Small companies and microenterprises have until September 1, 2027 as well for receiving, though that date has been subject to revision. The French tax authority (DGFiP) publishes and updates the official schedule; check that page directly to confirm the September 1, 2026 large-company deadline remains in effect before finalizing any implementation timeline.
US companies that are VAT-registered in France and bill French B2B customers are treated as large suppliers under the mandate if they exceed the thresholds above globally, not just in France. If your French subsidiary is the contracting entity, it is subject to the same rules as any French company.
When Is E-Invoicing Mandatory in Germany?
Germany’s approach differs from France’s in a critical way: there is no centralized government clearance platform. Germany does not route invoices through a tax authority hub before they reach the buyer. The mandate is format-based rather than platform-based.
As of January 1, 2025, all German VAT-registered businesses must be technically capable of receiving structured e-invoices in XRechnung or ZUGFeRD format. Sending those formats became mandatory for large companies on January 1, 2027. SMEs have until January 1, 2028.
XRechnung is Germany’s national XML standard, based on the European EN 16931 semantic data model. ZUGFeRD is a hybrid format that, at its highest profile level (EN 16931 compliant), is interchangeable with Factur-X. A ZUGFeRD invoice looks like a PDF to a human but contains machine-readable XML embedded in the file. That dual nature is why some companies default to ZUGFeRD: it satisfies the mandate while remaining readable without special software.
The receiving obligation from January 2025 is already live. If you issue invoices to German companies and they request an XRechnung or ZUGFeRD format, you are obligated to provide one. Continuing to send plain PDFs puts the transaction at risk and, depending on the contract, may delay payment legally.
Poland’s KSeF: The Most Technically Demanding Mandate in Europe
Poland’s National e-Invoicing System, KSeF (Krajowy System e-Faktur), uses a centralized clearance model similar to Italy’s SDI but more tightly controlled. Every B2B invoice must be submitted to the KSeF platform before it has legal validity. The platform assigns a unique KSeF number to each invoice. An invoice without that number is, legally speaking, not an invoice.
The mandate became mandatory for large taxpayers on February 1, 2026, and for all other VAT-registered businesses on April 1, 2026, per the timeline published by the Polish Ministry of Finance , a schedule that was confirmed following two prior delays and reflects the ministry’s February 2025 announcement. Poland’s rollout has been delayed twice since it was first announced, so teams working with Polish entities should verify the current status on that page before finalizing any implementation timeline.
The required format is a national XML schema called FA_VAT, which is not compatible with PEPPOL or any other standard used elsewhere in Europe. If your invoicing API vendor supports PEPPOL but not KSeF’s FA_VAT schema, you need a separate integration for Poland. That is not an edge case. It is the situation most mid-market finance teams are walking into.
Which Invoicing API Vendors Actually Cover These Mandates?
The compliance gap in most stacks is not awareness. It is that the invoicing API the company already uses for domestic billing was never built for structured cross-border e-invoicing. Standard invoice generation APIs produce PDFs or basic JSON representations. They do not embed EN 16931-compliant XML, connect to government clearance platforms, or manage the lifecycle of a KSeF-cleared invoice.
Vendors that specifically address multi-country e-invoicing mandates include Avalara E-Invoicing, Sovos, Storecove, Basware, and Coupa on the enterprise side. For API-first companies, InvoiceXpress covers Iberian markets, and Unimaze focuses on PEPPOL network connectivity. Dedicated compliance middleware like Complyance sits between your billing system and government platforms, handling format conversion and clearance without requiring a full ERP replacement.
A full breakdown of API options by format coverage, PEPPOL access point support, and KSeF/SDI clearance capability is in our separate guide to e-invoicing compliance APIs for multi-country mandates. That list covers per-transaction pricing, setup costs, and which vendors have certified PDP status in France.
The FintechSpecs Country Coverage Gap Test: How to Audit Your Stack in 30 Minutes
Most companies discover their invoicing stack’s compliance gaps during a vendor questionnaire or a sales process with a European enterprise buyer, not proactively. The FintechSpecs Country Coverage Gap Test is a structured four-step audit any finance or engineering team can run without a consultant , designed to surface mandate exposure by country, model type, and format requirement in a single sitting.
Step 1: List every country where you hold a VAT or local tax registration. Include registrations held by entities you use, such as a Merchant of Record. If a MoR is VAT-registered in France and issues invoices on your behalf, their compliance status is your compliance risk. Our comparison of Merchant of Record platforms for B2B SaaS covers which providers actively manage e-invoicing compliance in their covered jurisdictions.
Step 2: Cross-reference each country against the mandate table above. Flag any country with a mandate effective date in the next 18 months. Note the model type: clearance-based (France, Poland, Italy) or format-based (Germany, Belgium).
Step 3: Ask your invoicing API vendor three questions. Can it produce XRechnung or Factur-X? Does it connect to a PDP certified by the French DGFiP? Does it support KSeF’s FA_VAT schema submission? If all three answers are no, the vendor is not a compliance solution for 2026 and 2027.
Step 4: Check your invoice archive requirements. Most mandates carry an obligation to store e-invoices in their original structured format for 7 to 10 years, in a government-accessible system. A PDF archive does not satisfy this. If your storage layer converts structured invoices to PDF for archival, you may fail a tax audit even if you generated the right format at time of sending.
What Penalties Apply for Non-Compliance?
The penalty structures vary more than the mandate timelines. Romania has published specific per-invoice fines for non-compliance with RO e-Factura. Italy’s SDI system has been enforced with penalties since 2019, and the Italian tax authority (Agenzia delle Entrate) routinely applies them. Poland’s KSeF law specifies financial penalties tied to invoice value for invoices submitted late or outside the system.
France and Germany have not yet published a penalty schedule for the 2026 and 2027 mandates with the same specificity. That does not mean there are no consequences. In France, an invoice that does not meet the structured format requirement may not be deductible for VAT purposes by the buyer, which shifts pressure to the buyer to reject non-compliant invoices. German buyers already have the right to refuse non-structured invoices when the mandate kicks in.
The practical penalty for US companies often precedes any regulatory fine: enterprise buyers in mandate-covered countries are starting to include e-invoicing format compliance in vendor contracts. Failure to deliver compliant invoices can constitute a billing breach, delaying or blocking payment without any tax authority involvement at all.
How Does PEPPOL Fit Into All of This?
PEPPOL (Pan-European Public Procurement On-Line) is a network of certified access points, not a format in itself. It uses a four-corner model: the sender’s access point transmits to the receiver’s access point using a standardized envelope format. The document inside that envelope is typically PEPPOL BIS Billing 3.0, which is an implementation of the European EN 16931 standard.
Belgium’s 2026 mandate runs through PEPPOL. Several Nordic countries already mandate PEPPOL for public sector invoices and are extending it to B2B. If you connect to a certified PEPPOL access point, you can reach buyers in Belgium, the Netherlands, Norway, Sweden, Denmark, and several other markets through a single network connection. That is the closest thing to a multi-country solution that exists today, but it does not cover France’s PDP network, Germany’s XRechnung (though PEPPOL can carry it), or Poland’s KSeF.
Connecting to PEPPOL is a reasonable first move for companies with exposure across Northern Europe. It is not sufficient on its own if France or Poland are in scope. Those require additional integrations regardless of PEPPOL connectivity.
What About US Domestic E-Invoicing Requirements?
There is no federal e-invoicing mandate for US domestic B2B transactions as of late 2026. The IRS does not require structured invoice formats for domestic sales. US-based B2B companies operating purely domestically face no equivalent of the European mandates right now.
Where US companies do encounter structured invoicing requirements is in federal government contracting. The US Treasury’s Bureau of the Fiscal Service operates the Invoice Processing Platform (IPP), and many federal agencies require suppliers to submit invoices through it. That is narrower in scope than European B2B mandates and only affects companies with federal contracts.
The IRS’s 1099 reporting requirements for contractor payments are a separate and more immediate concern for US platforms paying contractors. That is a reporting obligation, not an invoice format requirement, and it operates on a different compliance track. Our guide to 1099 and tax compliance APIs for platforms paying contractors covers that separately.
How Should Finance Teams Prioritize When Multiple Mandates Hit at Once?
A company with VAT exposure in France, Germany, and Poland is staring at three different formats, three different technical models, and deadlines clustered between late 2025 and early 2028. Sequencing matters.
Poland’s KSeF, as a clearance-based system with a hard legal-validity requirement, should come first for any company with meaningful Polish revenue. An invoice that has not been cleared through KSeF is not a legally valid invoice in Poland. That is a revenue risk, not just a compliance risk. France follows for the same reason: the PDP-based model makes invoice validity contingent on routing through a certified platform.
Germany, being format-based without a clearance requirement, carries less immediate legal-validity risk. The practical priority there is that German enterprise buyers are increasingly demanding XRechnung or ZUGFeRD formatted invoices even before the sending mandate kicks in, because they need structured formats for their own ERP processing. Losing a buyer’s payment approval cycle because your invoice is the wrong format is a material problem regardless of the mandate’s enforcement date.
For companies managing cross-border billing complexity alongside broader payment infrastructure decisions, the overlap between e-invoicing compliance and payment reconciliation is real. A structured e-invoice contains payment reference data that should flow directly into reconciliation workflows. Finance teams building out their stack should look at how their payment reconciliation software consumes structured invoice data before choosing an e-invoicing vendor, because the two systems need to talk.
Frequently Asked Questions
Are US companies subject to e-invoicing mandates in Europe?
Yes, if they hold a VAT registration in a mandate country. The trigger is VAT registration status and the B2B transaction location, not corporate headquarters. A US company VAT-registered in France issuing invoices to French businesses falls under France’s mandate starting September 1, 2026, for large companies. Companies selling through a Merchant of Record that holds EU VAT registrations should verify what format that MoR issues invoices in.
What is the difference between a clearance model and a format-only mandate?
A clearance model, used in countries like Italy, Poland, and France, requires the invoice to pass through a government or government-certified platform before it has legal validity. The platform assigns an ID and timestamps the document. A format-only mandate, like Germany’s, requires that the invoice be in a structured machine-readable format but does not route it through a government hub before delivery to the buyer. Clearance models carry higher legal-validity risk if non-compliant.
Does ViDA replace country-level mandates?
No. ViDA’s cross-border digital reporting requirement applies from 2030 onward and covers intra-EU B2B transactions across borders. Domestic B2B mandates within each member state are set by national law and operate on their own timelines. France’s 2026 mandate, Germany’s 2027 sending requirement, and Poland’s 2026 KSeF mandate all proceed independently of ViDA. ViDA removed a legal barrier that previously required EU approval for domestic mandates, which is why so many national mandates launched after 2023.
What formats do I need to support for EU e-invoicing compliance?
At minimum: XRechnung and ZUGFeRD for Germany, Factur-X or UBL 2.1 for France, FA_VAT XML for Poland’s KSeF, UBL 2.1 for Romania and Belgium, and FatturaPA XML for Italy. PEPPOL BIS Billing 3.0 covers Belgium and several Nordic markets. There is no single format that satisfies all mandates simultaneously. A compliant multi-country stack requires either a vendor with pre-built country adapters or a middleware layer that handles format conversion per jurisdiction.
How long must e-invoices be archived, and in what format?
Retention periods range from 5 years in some jurisdictions to 10 years in others. Most mandates require storing the original structured XML or hybrid format, not a PDF rendering of it. Italy requires invoices cleared through SDI to be stored in their original FatturaPA format. Archiving only a PDF copy of a ZUGFeRD invoice, without the embedded XML, typically fails the structured retention requirement during a tax audit.
What is PEPPOL and which countries use it for e-invoicing?
PEPPOL is a four-corner network of certified access points that transmit structured invoices between businesses without requiring point-to-point connections. Belgium mandates PEPPOL for B2B e-invoicing from January 2026. Norway, Sweden, Denmark, the Netherlands, and Finland either mandate or strongly incentivize PEPPOL for public sector and, in some cases, private sector invoicing. Connecting to a certified PEPPOL access point gives network reach across these markets but does not satisfy France’s PDP requirement or Poland’s KSeF submission requirement.
France’s e-invoicing deadline has already shifted once. Is September 2026 confirmed?
France’s mandate was originally scheduled for July 2024, then delayed. The current published date of September 1, 2026, for large companies reflects the schedule as of the DGFiP’s most recent official guidance. Regulatory timelines in this area have shown a pattern of delay across multiple countries, including Poland. Treating any date before final implementing regulations are published as firm is optimistic. That said, building toward the published date rather than assuming another delay is the lower-risk posture. An implementation delayed by six months costs less than a missed mandate that invalidates invoices and blocks payment collection.
What the Next 24 Months Actually Look Like
The cluster of mandates hitting between late 2025 and end of 2028 is not coincidental. ViDA’s passage cleared the legal path, and tax authorities across Europe moved quickly to legislate. The pattern from countries where mandates are already live, Italy, Brazil, Mexico, is that enforcement starts selectively and then broadens. Italy’s SDI was technically live in 2019 but penalties ramped over 18 months. Poland and France will likely follow a similar enforcement ramp, giving companies a narrow grace window that most teams will waste by assuming it applies to them.
For North American SaaS companies, the highest-value question is not “when is the deadline” but “who is the VAT-liable entity on our European invoices right now.” If the answer is a Merchant of Record, find out in writing what formats they generate and whether they have certified PDP status in France. If the answer is your own entity or a subsidiary, audit your invoicing API stack against the format and clearance requirements for every country where you hold a VAT registration. The fintech product and compliance readiness checklist on FintechSpecs covers the broader vendor evaluation process for compliance infrastructure decisions like this one.
The invoicing API space is consolidating around vendors that can demonstrate certified access point status, government-platform integrations, and format coverage across multiple jurisdictions simultaneously. A company that picks a domestic PDF invoicing API for international billing today will be replacing it in 12 to 18 months. Choosing a vendor that covers your current exposure plus your next two likely markets is worth the additional evaluation time now.
