European E-Invoicing Coverage Matrix

This matrix lists every European country INVOX has a rule pack for today, what INVOX actually does for it (validation, generation, Peppol transport, real-time reporting, national clearance), and — separately, since these are not the same kind of claim — what INVOX knows about that country's own e-invoicing mandate and timeline.

Method: every "INVOX Support" cell was checked directly against the invox/country_packs/, invox/generate/, invox/validators/ and invox/transmit/ source on 2026-09-02, not copied from older marketing copy. Every "Mandate / Effective Date" and "Authority" cell is sourced from one of four tiers: (a) INVOX's curated, dated mandate-research dataset (invox/seo/mandates.py, most recently refreshed 2026-08); (b) a dated research note embedded in the relevant transmission module's code comments; (c) a public, citable source checked in a follow-up research pass on 2026-09-02 (primarily the European Commission's own eInvoicing Country Factsheets); or (d) marked unconfirmed where none of the above exists. Tier (b) and (c) facts were researched by engineers, not by a compliance professional retained for this page — treat them as a strong lead, not a legal citation, and reconfirm before using them in anything customer-facing with legal weight.

Legend

The matrix

Note on ordering: the table above is not strictly alphabetical — the countries with a verified or code-documented national mandate (Germany through Croatia) are listed first, followed by the remaining Peppol-interoperability countries in alphabetical order, so the rows needing the most compliance follow-up are grouped together rather than scattered.

Also in the codebase, not European

INVOX has three further country rule packs built on the same Peppol-based architecture, outside the scope of a European matrix: Australia (Peppol A-NZ), New Zealand (Peppol A-NZ) and Singapore (Peppol InvoiceNow / IMDA). Validation and generation are LIVE for all three via the same generic engine; no dedicated national reporting/clearance sender exists for any of the three as of this writing.

Sources for [W] fields (checked 2026-09-02)

Austria, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland, Ireland, Latvia, Lithuania, Luxembourg, Malta, Slovakia, Slovenia, Sweden, Spain (FACe B2G date). The same 16 factsheets were also used in a 2026-09-02 follow-up pass to source the Reporting/Clearance columns for these countries — most state explicitly ("there is no real-time reporting system in [country]") that no national real-time reporting or clearance mechanism exists today, which is why most of these rows now read "n/a" / "No" for Reporting/Clearance rather than "unconfirmed."

invoicedataextraction.com — Swiss E-Invoicing Requirements. No EC Country Factsheet exists for Switzerland (non-EEA); no single named federal e-invoicing authority was confirmed, only the general federal procurement framework — flagged for compliance follow-up below. The 2026-09-02 follow-up pass specifically targeting the reporting/clearance mechanism could not find one single authoritative, directly-quotable source on this point either — CH's Reporting and Clearance cells remain unconfirmed rather than guessed.

network for UK e-invoicing mandate](https://www.vatupdate.com/2026/06/26/peppol-confirmed-as-core-interoperability-network-for-uk-e-invoicing-mandate/); peppolvalidator.com — Peppol in the United Kingdom; EDICOM — NHS e-Procurement Strategy; VATupdate — UK e-invoicing mandate won't alter tax reporting cycle, HMRC official confirms; VATupdate — Briefing Document: E-invoicing/e-reporting in the United Kingdom, scope and implementation overview; Zoneandco — United Kingdom e-invoicing compliance guide. No EC Country Factsheet exists for the UK (non-EU); the 2029 mandate was only announced in June 2026 and its implementation roadmap is not yet published — treat the date, and the "no clearance/no CTC planned for the first wave" statement, as directional and pre-implementation, not final.

ecosio.com — ANAF RO e-Factura and e-invoicing in Romania; VATupdate — Briefing Document: Romanian E-Invoicing, E-Reporting, and E-Transport. These are vendor/compliance-tracker summaries, not ANAF's own primary text — treat as tier [W], same caveat as every other field in this tier.

Slovenian National Assembly adopts ZIERDED, mandatory B2B e-invoicing from 1 January 2028](https://epos.si/en/news/slovenian-national-assembly-adopts-zierded-mandatory-b2b-e-invoicing-from-1-january-2028); VATupdate — Slovenia postpones mandatory B2B e-invoicing to 2027; Sovos — Slovenia e-invoicing. These secondary trackers report a later legislative state (law adopted, B2B date pushed to 2028-01-01, real-time e-reporting to FURS dropped) than the EC factsheet, which still shows the earlier 2027 draft — flagged in the table as [W][U] pending direct confirmation against the Uradni list (Slovenian Official Gazette).

reporting model): banqup.com — Slovakia's next step: a 5-corner model for e-invoicing in 2027; EDICOM — Slovakia continues to advance its e-invoicing project; ecosio.com — E-invoicing in Slovakia compliance guide; vatcalc.com — Slovakia IS EFA e-invoice proposal 2024, delay to B2G. These describe a decentralized 5-corner Peppol model with a parallel post-issuance transaction-data-reporting duty ("SK TDD"), not a blocking clearance step — flagged [W][U] pending direct confirmation against the Slovak Financial Administration's own published text.

• European Commission, eInvoicing Country Factsheets (DIGITAL Building Blocks):
• Switzerland: Avalara — E-invoicing in Switzerland;
• United Kingdom: [VATupdate — Peppol confirmed as core interoperability
• Romania: marosavat.com — E-Invoicing in Romania: Complete Guide;
• Slovenia (B2B regime detail, follow-up on the ZIERDED law): [epos.si —
• Slovakia (B2B regime detail, follow-up on the enacted law and "SK TDD"

These are vendor/tracker/EC-summary sources checked by an engineer in one research pass, not a compliance professional's sign-off. Government legislative text (Amtsblatt/Staatsblad/Official Gazette equivalents) was not independently pulled for any of these; treat every [W] fact the same way as a [C] fact — a strong, dated lead, not a legal citation.

Known gaps / roadmap

invox/generate/cius_ro.py + invox/validators/cius_ro.py (2026-09-02) close the gap this page previously flagged, verified against the Romanian Ministry of Finance's own ro16931-ubl-1.0.9 Schematron artifact (primary source, not a secondary summary). Explicitly NOT yet implemented, per the module's own docstring: non-RON dual-currency VAT accounting (BR-RO-030 — only currency: "RON" invoices are supported, others raise a clear error rather than guessing exchange-rate handling), RO_CIUS credit notes (a separate UBL document type), tax-representative/delivery-party address rules, and roughly 20 of the ~90 official BR-RO-L* max-length rules for fields outside this generator's current data model. Treat this as a verified subset, not full official-ruleset conformance — a compliance-team review against the primary ANAF source is recommended before this is marketed as certified.

Both invox/transmit/atcud_sender.py and invox/transmit/fiskalizacija_sender.py carry dated (2026-08-18) docstrings stating the live endpoint hostname and exact wire format could not be confirmed from public sources; both fail closed (configured is False) until an operator supplies a verified base URL and credentials. This research pass did not find a public source strong enough to upgrade either to LIVE — both remain BETA. Follow-up: verify directly against the Autoridade Tributária / Porezna uprava (or an accredited intermediary) sandbox before production use.

• Romania: CIUS-RO generator now built, with a documented subset of rules.
• Portugal (ATCUD) and Croatia (Fiskalizacija): senders remain BETA.

Fields that need a compliance-team follow-up before this page goes fully public with legal confidence

countries (AT, BG, CH, CY, CZ, DK, EE, FI, GB, IE, LT, LU, LV, MT, SE, SI, SK) — a 2026-09-02 follow-up pass verified the Reporting/Clearance columns for 16 of the 17 against public sources (14 directly against the European Commission's own eInvoicing Country Factsheets — AT, BG, CY, CZ, DK, EE, FI, IE, LT, LU, LV, MT, SE, and SK/SI's B2G channel — plus GB, SI and SK's B2B-regime detail against secondary compliance trackers where the EC factsheet was silent or stale). The pattern that emerged: most of these countries have no national real-time reporting or clearance mechanism at all** today (several EC factsheets say so explicitly, verbatim: "there is no real-time reporting system in [country]") — Bulgaria and Latvia have a post-issuance data-submission duty (SAF-T-phased and VID-submission, respectively) that is not clearance; Slovakia's upcoming 2027 regime adds a similar near-real-time reporting duty ("SK TDD") without clearance; none of the 17 has an Italy/Poland-style pre-issuance clearance system. Switzerland (CH) remains unconfirmed — no EC factsheet exists (non-EEA) and the follow-up pass could not find one single authoritative, directly-quotable source specifically on its reporting/clearance mechanism; that field is left "unconfirmed" per this page's convention rather than guessed. See the per-country [W] citations in the matrix and the "Sources for [W] fields" section above for the exact source used per country. As with every [W] fact on this page, these were researched by an engineer in one pass, not signed off by a compliance professional — reconfirm before a customer-facing legal claim, and note that Slovenia's and Slovakia's B2B regimes are enacted-but-not-yet-in-force law (2028-01-01 and 2027-01-01 respectively) so their reporting/clearance design could still change before go-live.

2026-09-02 follow-up pass re-confirmed against invox/transmit/ and invox/country_packs/ that none of the 17 has a dedicated sender/reporting module (the only dedicated senders in the codebase are choruspro_sender.py/face_sender.py/sdi_sender.py/ksef_sender.py/ mydata_sender.py/nav_sender.py/efactura_sender.py/atcud_sender.py/ fiskalizacija_sender.py, covering FR/ES/IT/PL/GR/HU/RO/PT/HR — not any of these 17). Each of the 17 country-pack modules (invox/country_packs/{at,bg,ch,cy,cz,dk,ee,fi,gb,ie,lt,lu,lv,mt,se,si,sk}.py) was grepped directly and confirmed to carry no sender/transmit/reporting logic. The existing "LIVE for validation/generation/Peppol; national reporting/clearance status not verified" wording in the INVOX Support column was already accurate on this point — no change was needed there.

dates are now sourced ([W], see above), but whether/how the B2G side of e-Factura differs from B2B was not confirmed in this pass; still unconfirmed.

from secondary sources and the code itself says the live endpoint could not be confirmed with confidence (dated 2026-08-18 in both files, and still unconfirmed as of this 2026-09-02 pass — see "Known gaps" above). Do not represent either as production-ready to a customer without re-verifying against the actual government sandbox first.

research notes in the sender modules (tier [C]), not from a compliance professional's independent check for this page.

actively moving in 2026–2028; treat every date here as "true as researched, on the date shown," not as a live-updating legal source. This is especially true for [W] fields, which reflect one engineer's single research pass against public trackers and the European Commission's own factsheets, not a law firm's or tax advisor's sign-off.

• **Reporting/Clearance mechanism for the 17 Peppol-interoperability
• INVOX Support column, re-checked for these same 17 countries — the
• Romania's B2G e-Factura scope — the B2B domestic mandate scope and
• Portugal and Croatia's entire "BETA" rows — both senders were written
• Greece and Hungary's mandate dates — sourced from dated engineering
• Any date on this page generally — e-invoicing mandates in the EU are

Disclaimer: this matrix is a technical/product reference, not legal or tax advice. Confirm current mandate dates, thresholds and authority names with your tax advisor or the relevant national authority before relying on anything stated here.