Which e-invoice format each country requires
The mandates are national and they move. This is what a supplier in each country sends you, and what InvoiceIn checks it against.
15 countryChecked: 2026-09-11
| Country | System | Mandate | Format received | What we check | Not covered |
|---|---|---|---|---|---|
| Germany DE | B2B e-invoicing (no central platform) | 2025-01-01 · everyone must be able to receive 2027-01-01 · above the threshold (turnover over €800,000) 2028-01-01 · all businesses | xrechnung-ubl xrechnung-cii zugferd facturx | XSD UBL 2.1 / CII D16B EN 16931 XRechnung (KoSIT) | — |
| France FR | PDP platforms + e-reporting | 2026-09-01 · everyone must be able to receive 2026-09-01 · large and mid-cap companies 2027-09-01 · small and medium businesses | facturx ubl cii | XSD UBL 2.1 / CII D16B EN 16931 CTC-FR (FNFE 1.4.0.04, transition profile) | France declares no customization id of its own, so the French rules run when the seller and the buyer are both in FR; a cross-border invoice is judged by EN 16931 alone |
| Italy IT | SdI clearance | 2019-01-01 · all businesses | fatturapa | XSD FatturaPA 1.2.2 arithmetic | Italy publishes no Schematron for FatturaPA; beyond the schema we check the arithmetic |
| Poland PL | KSeF clearance | 2026-02-01 · above the threshold (turnover over PLN 200 million) 2026-04-01 · all businesses 2027-01-01 · micro-entrepreneurs | ksef-fa3 ksef-fa2 | XSD FA(3) / FA(2) arithmetic KSeF number checks | Poland publishes no Schematron either; the KSeF number that travels beside the invoice is checked separately (?ksef=) |
| Romania RO | RO e-Factura (SPV clearance) | 2024-01-01 · all businesses | efactura-ro | XSD UBL 2.1 CIUS-RO 1.0.1 (ANAF's own artefact) | — |
| Belgium BE | Peppol 4-corner | 2026-01-01 · all businesses | peppol-bis3 ubl | XSD UBL 2.1 EN 16931 Peppol BIS Billing 3 | — |
| Croatia HR | e-invoicing + real-time reporting | 2026-01-01 · all businesses | peppol-bis3 ubl cii | XSD UBL 2.1 / CII D16B EN 16931 Peppol BIS Billing 3 | the Croatian national rules are not shipped; the EN 16931 and Peppol layers are |
| Greece GR | B2B e-invoicing alongside myDATA | 2026-02-02 · above the threshold (turnover over €1 million) 2026-10-01 · all businesses | peppol-bis3 ubl | XSD UBL 2.1 EN 16931 Peppol BIS Billing 3 (carries the Greek rules) | myDATA's own reporting XML is a different document and is not read here |
| Slovakia SK | Peppol 5-corner + near real-time reporting | 2027-01-01 · all businesses | ubl cii peppol-bis3 | XSD UBL 2.1 / CII D16B EN 16931 | — |
| Slovenia SI | B2B and B2G e-invoicing | 2027-01-01 · planned (draft law) | ubl cii peppol-bis3 | XSD UBL 2.1 / CII D16B EN 16931 | — |
| Estonia EE | B2B on request, Peppol | 2027-01-01 · planned (draft law) | ubl cii peppol-bis3 | XSD UBL 2.1 / CII D16B EN 16931 | — |
| Latvia LV | B2B and B2G e-invoicing | 2028-01-01 · all businesses | ubl cii peppol-bis3 | XSD UBL 2.1 / CII D16B EN 16931 | — |
| Portugal PT | certified billing software, CIUS-PT for B2G | 2020-01-01 · invoices to public bodies | ubl cii | XSD UBL 2.1 / CII D16B EN 16931 | the Portuguese CIUS, ATCUD and the QR code on the printed document are not checked |
| Spain ES | FacturaE + VeriFactu / SII reporting | 2027-01-01 · all businesses | not supported yet | — | FacturaE 3.2.2 is a different syntax with its own signature, and is not supported yet — a Spanish supplier sending UBL or Factur-X is read normally |
| Peppol network (NO, DK, SE, NL, IS, IE and others) XX | Peppol 4-corner | — | peppol-bis3 ubl cii | XSD UBL 2.1 / CII D16B EN 16931 Peppol BIS Billing 3 | the Peppol rule set carries each country's own national rules (NO-R-, DK-R-, SE-R-, NL-R-, IS-R-), so those are checked with it |
Dates are national law and change. Verify a deadline you are planning around with the tax administration that set it; this table says what we validate, not what a sending platform must do for you.
Send one of those invoices through the API and see the verdict.
Open the live demoSame explanation over the API: GET /v1/countries