Why invoices now arrive as XML
EU countries are moving business invoicing to structured e-invoices based on the EN 16931 standard: Belgium made PEPPOL exchange mandatory for domestic B2B in January 2026, France requires every company to be able to receive e-invoices from September 2026, Germany's receive obligation has applied since January 2025, and more mandates follow through 2028–2030. The practical effect: suppliers increasingly send an .xml file where a PDF used to be.
Those XML files are perfect for software and useless for human eyes. The viewer bridges the gap — see what the structured invoice actually says without buying or installing anything.
Viewer, validator or converter?
View an invoice you received to read its content. Validate a file to check it against the official format rules (EN 16931, PEPPOL, XRechnung, Factur-X and more) — typically before sending. Convert between formats (CII to UBL, Facturae to UBL, e-arve to UBL and more) when your system needs a different syntax. All three are free on aiDoks and accept the same files.
Need to create an e-invoice instead?
If you need to send rather than read one: the free generator builds compliant PEPPOL BIS 3.0, XRechnung, Factur-X, Facturae and e-arve invoices from a simple form — with the same validation engine built in.