What XML format does aiDoks generate?
The output is UBL 2.1 XML conforming to the PEPPOL BIS Billing 3.0 specification. PEPPOL BIS 3.0 is the European standard for cross-border e-invoicing, built on top of the EN 16931 norm. It defines which fields are mandatory, which are optional, the allowed code lists for currency, VAT category and unit of measure, and the business rules that calculations and dates must satisfy.
Practical consequence: the XML produced by aiDoks is accepted by the PEPPOL network and by every accounting platform that speaks PEPPOL β Xero, SAP, Odoo, Microsoft Dynamics 365, NetSuite, Standard Books, Merit Aktiva, Visma and many others. You can also send it directly to government tax portals that accept PEPPOL submissions.
Why XML, not PDF?
PDFs are visual layouts β they look the same to every reader, but a computer cannot reliably parse them. UBL XML is structured: every value has a named field with a known type, so accounting software can auto-create entries, match purchase orders, run tax reports and reconcile payments without human intervention. For B2G and increasingly B2B in the EU, structured XML is required by law.
Validation runs automatically
Every export is validated against PEPPOL BIS 3.0 / EN 16931 business rules. Errors are reported with the exact rule ID (BR-CO-13, BR-CO-15, BR-S-08 and so on) and a plain-English explanation. You can also run the standalone PEPPOL validator on any XML invoice you received from a supplier.