Sample e-invoices you can download

Known-good UBL, CII and Factur-X documents to test your implementation against — plus one that is broken on purpose.

UBL invoice (EN 16931 / Peppol BIS)

A complete, valid UBL invoice. The usual starting point when you are implementing EN 16931 from scratch and want a known-good document to diff against.

Download · CEF eInvoicing EN 16931 artefacts (EUPL-1.2)

UBL credit note

A credit note is its own document type in UBL, not an invoice with a negative total - this shows the shape.

Download · CEF eInvoicing EN 16931 artefacts (EUPL-1.2)

CII invoice (UN/CEFACT, the Factur-X payload)

The CII syntax, which is what sits inside a Factur-X or ZUGFeRD PDF. Same semantic model as UBL, entirely different element names.

Download · CEF eInvoicing EN 16931 artefacts (EUPL-1.2)

Factur-X / ZUGFeRD PDF (hybrid)

A PDF carrying the invoice XML as an attachment named factur-x.xml. Deliberately NOT a fully compliant Factur-X file - it has no XMP metadata and is not PDF/A-3 - so validating it also demonstrates the container checks that tell you exactly what a hybrid PDF is missing.

Download · built here from the CEF CII example

Deliberately broken invoice

A UBL invoice whose VAT amount is wrong on purpose. Valid XML, valid structure, and it fails 2 EN 16931 rules, 9 Peppol rules and 14 XRechnung rules - a compact way to see what each profile actually adds.

Download · built here

Every file here is checked by this validator before each release, so the description above each one is what you will actually get. The three taken from the CEN artefacts are redistributed under EUPL-1.2 with attribution; the other two were built here.