An e-invoice you can actually read

Because e-invoicing is becoming mandatory. Belgium has required structured B2B e-invoices since 1 January 2026, and the rest of Europe follows: from 1 July 2030 it applies to cross-border B2B invoicing within the EU. An e-invoice is meant to be read by software, not people — which is why it arrives in your inbox as unreadable code. This tool turns it back into a readable invoice.

UBL 2.1 (both Invoice and CreditNote) and UN/CEFACT CII. In practice that covers Peppol BIS Billing 3.0, the Dutch NLCIUS profile and German XRechnung. The tool recognises the profile itself and labels it.

Yes. Many e-invoices carry the human-readable PDF as an attachment inside the XML itself. If one is there, a download button appears. That also happens entirely in your browser.

No, and the difference matters. We check the arithmetic: do the lines add up to the subtotal, does the VAT bridge excl. to incl., and does the payable amount survive a prepayment. That catches the errors that actually appear in hand-built files. A real EN 16931 or Peppol validation runs hundreds of Schematron rules, so an invoice can add up here and still be rejected by an access point.

No. The file is read in your own browser and never leaves your computer. That's deliberate: an invoice contains your revenue, your customer details and your bank account number, and it is exactly the kind of file you should not drag into an arbitrary online converter.

As a Dutch supplier you fall formally outside the Belgian mandate, but in practice Belgian customers are standardising on Peppol and expect you to join. Invoices that don't arrive structured get processed late or refused. Practically it means you need a way to send over the Peppol network. That's something we help with.