EU Cross-Border E-Invoicing: 5 Scenarios That Catch Businesses Off Guard
Complying with Germany's XRechnung, Italy's FatturaPA, France's Factur-X, and Poland's KSeF domestically is one thing. Cross-border invoicing between these systems introduces entirely new complications. These are the five most common traps.
Each EU country has solved domestic e-invoicing in its own way. But when a German company invoices an Italian customer, or a French business bills a Polish partner, the rules interact in ways that no single country's guidance explains.
Here are the five cross-border scenarios that most frequently create compliance problems — and exactly how to handle them.
Scenario 1: German Business Invoicing an Italian B2B Customer
The trap: A German company invoices an Italian business customer. The German business correctly generates a ZUGFeRD invoice. The Italian business's SDI intermediary receives it — and immediately has questions, because SDI expects FatturaPA XML, not ZUGFeRD PDF.
What actually happens:
- The Italian B2B customer must self-report the purchase invoice through their SDI intermediary as an autofattura (self-invoice for cross-border purchases)
- The German seller issues their invoice in whatever format they normally use (ZUGFeRD, PDF, etc.)
- The Italian buyer's SDI obligation is on the Italian side, not the German seller's
What the German seller needs to do: Nothing specific format-wise for the Italian customer — standard German invoice formats are fine. Confirm your Italian customer understands their self-invoicing obligation.
Peppol shortcut: If both parties have Peppol access points, the German seller can send a Peppol BIS 3.0 invoice to the Italian buyer. The Italian intermediary can accept Peppol BIS 3.0 and convert for SDI reporting purposes — eliminating the cross-border format confusion.
Scenario 2: Polish Business Invoicing a German B2B Customer
The trap: A Polish company issues an invoice through KSeF (mandatory for domestic Polish B2B). The KSeF reference number is generated. They send the invoice to the German customer. The German customer's accounting software doesn't know what to do with the FA_VAT XML format or the KSeF reference number.
What actually happens:
- The KSeF reference number is a Polish compliance requirement — it is the Polish entity's evidence of legal issuance
- The German customer has no obligation to receive KSeF-routed invoices
- For the German customer's purposes, the invoice document (which can be a PDF with KSeF reference, or the FA_VAT XML) is treated as a standard supplier invoice
What the Polish seller needs to do: Issue through KSeF as required (mandatory for the Polish VAT side), then send the invoice — either as a PDF with KSeF reference printed on it, or as the FA_VAT XML file — to the German customer. The German customer does not need to register with KSeF.
Scenario 3: French Business Invoicing a German B2G Customer
The trap: A French company has a contract with a German federal agency. The German agency requires XRechnung with a Leitweg-ID. The French company's accounting software generates Factur-X but not standalone XRechnung.
What actually happens:
- Factur-X and XRechnung are based on the same EN 16931 standard, but they are different formats
- Most German B2G systems accept XRechnung (UBL or CII) and ZUGFeRD — but not Factur-X natively
- The French company needs either: (1) software that generates standalone XRechnung, or (2) a conversion service
How to solve it: Most Peppol access points (including Cegedim, Storecove, and Pagero) can convert Factur-X to XRechnung for B2G delivery. Ask your PDP whether they support XRechnung conversion for cross-border B2G routing.
Scenario 4: Italian Business Invoicing a Belgian Peppol Recipient
The trap: An Italian company uses SDI for domestic invoices. A Belgian customer now requires Peppol BIS 3.0 (Belgium's mandatory B2B format since January 2026). The Italian company's SDI intermediary handles FatturaPA, not Peppol.
What actually happens:
- The Italian seller needs a Peppol access point in addition to their SDI intermediary
- Most Italian SDI intermediaries (Aruba, InfoCert, TeamSystem) also offer Peppol access points
- The two systems run in parallel: SDI for Italian domestic invoices, Peppol for the Belgian customer
What to do: Contact your current Italian SDI intermediary and ask if they provide Peppol access point services. Most do. Your Peppol ID for the Belgian recipient is separate from your SDI registration.
Scenario 5: Multinational Issuing Invoices Across Germany, France, Italy, and Poland
The trap: A medium-sized company operates in all four countries and wants one invoicing solution for everything. They buy an "EU e-invoicing" SaaS product that promises coverage — then discover it supports XRechnung but not FA_VAT KSeF routing, or supports Factur-X but not FatturaPA SDI direct submission.
What actually happens:
- As of May 2026, no single software product is natively certified for all four national systems with equal depth
- Most enterprise solutions (SAP S/4HANA, Oracle Fusion) cover all four with country localisation modules — but at enterprise pricing
- Middleware solutions (Storecove, Pagero, Basware) handle cross-format conversion and multi-country routing as their core business
Practical approach for mid-market: 1. Use your primary ERP for the largest country 2. Add Storecove or a similar Peppol access point for cross-border routing 3. Use a certified KSeF intermediary for Poland (Comarch, wFirma, iFirma) 4. Use a certified SDI intermediary for Italy 5. Connect everything via Peppol where possible — it handles DE, BE, NL, SE, and will handle FR (2026+)
The ViDA Solution (2030)
These scenarios exist because EU e-invoicing developed country-by-country rather than EU-wide. The ViDA directive's cross-border DRR (starting 2030) will create a mandatory interoperability layer — but until then, cross-border invoicing requires country-specific solutions.
If you invoice regularly across more than two EU countries, investing in a multi-country Peppol access point now is the most future-proof strategy.
