EU · EN 16931
EN 16931 defines the European semantic invoice model. UBL 2.1 and CII D16B carry that model in structured XML.
Peppol: not supported yet
Choose the recipient’s country and required invoice profile before selecting a validator. A European business model, a national restriction and a delivery network describe different parts of the process. This directory connects those requirements with the checks available in XSDHub and the guides that explain their results.
EN 16931 defines the European semantic invoice model. UBL 2.1 and CII D16B carry that model in structured XML.
Peppol: not supported yet
XRechnung is the German CIUS of EN 16931 for structured invoices. Germany also uses the hybrid ZUGFeRD/Factur-X format, whose profile must be checked separately.
Peppol: not supported yet
Factur-X combines a PDF invoice with structured CII XML. The French reform also recognises UBL and CII; a Factur-X check has a narrower technical scope than the entire reform.
Peppol: not supported yet
KSeF uses Poland’s structured FA(3) XML schema. XSDHub checks that schema’s structure and data types, without simulating KSeF acceptance or business-rule validation.
Peppol: not supported yet
RO e-Factura uses Romania’s CIUS-RO requirements for structured invoices exchanged through ANAF. This checker applies its pinned UBL 2.1 schema and ANAF rule package.
Peppol: not supported yet
Croatian eRačun uses national HR-CIUS requirements and extensions on structured invoices. XSDHub checks supported UBL 2.1 files against the pinned Croatian and European rules.
Peppol: not supported yet
Start with the document you can export from your invoicing system. A plain XML file can carry UBL, CII or a national structure such as FA(3); those formats are not interchangeable. A hybrid invoice includes machine-readable information inside its readable container. Follow the country page to the matching tool, which selects the appropriate package without running or uploading anything automatically.
Each country page names the exact artefacts applied by this release. Some tools evaluate schema structure plus business rules, while the Polish checker evaluates its fixed XSD only. Look at the reported validation layers and follow a rule link to a repair example. A green result cannot certify legal compliance, establish a taxpayer’s registration or confirm that an authority received the invoice.
You can check an individual supported invoice for free using the linked tool and its existing processing notice. For repeated work, the country pages also connect to the current Pro and Team checkout and the public API documentation. Plan details and limits remain on the pricing page. Technical validation, paid access and official delivery are separate decisions; buying a plan does not turn XSDHub into an accredited exchange platform.