Sample e-invoice files, one per format
Every file below came out of the same engine that powers CrateAPI's /generate and /validate endpoints — and every one of them passed that engine's own validator before we published it. Use them to test your parser, viewer, ERP import or integration, without waiting on a real customer invoice.
These are format samples, not live transactions. None of them was submitted to Peppol, SDI, KSeF or any other network, and none carries a digital signature. All data — company names, VAT numbers, IBANs — is fictitious: valid in shape, invented in substance. Nothing here identifies a real business or needs to be attributed to anyone.
UBL / Peppol BIS 3.0
Standard invoice (type 380), UBL 2.1 syntax, Peppol BIS Billing 3.0 profile — the most widely used cross-border e-invoicing format in the EU.
CII — Cross Industry Invoice (EN 16931)
XRechnung 3.0 (Germany)
Standard invoice for German B2G/B2B e-invoicing, UBL syntax, XRechnung 3.0 profile, with a Leitweg-ID routing reference.
Factur-X / ZUGFeRD (PDF/A-3)
Hybrid PDF/A-3b: a human-readable invoice PDF with a machine-readable EN 16931 CII XML (factur-x.xml) embedded inside it — open it as a normal PDF, or extract the XML for automated processing.
RO_CIUS (Romania, e-Factura)
Standard invoice for Romania's e-Factura system, UBL syntax, RO_CIUS 1.0.1 profile, RON currency.
FatturaPA (Italy, SDI)
Built for SDI/FatturaPA tooling — the free validator on this site covers EN 16931 (UBL/CII) only, not FatturaPA.
Facturae (Spain)
Standard invoice for Spain (Facturae schema, InvoiceDocumentType FC/InvoiceClass OO), unsigned — XAdES signing stays the sender's own responsibility, same as the real workflow.
KSeF / FA_VAT (Poland)
Standard invoice for Poland's KSeF platform, FA_VAT schema FA(2), PLN currency, pre-flight only — not submitted to KSeF, no numer KSeF.
EHF Billing 3.0 (Norway)
Standard invoice (type 380), UBL 2.1 syntax, EHF Billing 3.0 profile — Norway's e-invoicing format, officially identical to Peppol BIS Billing 3.0, rule for rule.
NLCIUS / SI-UBL 2.0 (Netherlands)
Standard invoice (type 380), UBL 2.1 syntax, NLCIUS / SI-UBL 2.0 profile — the Netherlands' Peppol CIUS, seller and buyer both Dutch, tested against the BR-NL-* rules.
PINT Billing EU (international)
Standard invoice (type 380), UBL 2.1 syntax, PINT Billing EU 1.0.2 profile — OpenPeppol's EU-aligned international model, cross-border seller (Germany) and buyer (France).
Intentionally invalid (for error-handling tests)
Every file above shows what a correct export looks like. These three don't — each one deliberately breaks exactly one validation rule. Use them to test how your own parser, ERP import or error-handling code reacts to a broken document, before a real one shows up in production.
Peppol BIS invoice with a deliberately wrong grand total — the VAT-inclusive amount doesn't equal the taxable amount plus VAT.
Peppol BIS invoice with no buyer reference and no purchase order reference. Peppol requires at least one of the two.
XRechnung invoice with no Leitweg-ID (BT-10 buyer reference) — mandatory for German public-sector routing.
Need this with your own data?
Generate and validate documents like these from your own invoice data through the API — the free validator never asks for a key.