Why an e-invoice looks like code
An e-invoice is not a document: it is structured XML meant for accounting software to read. When one arrives as a file, through a portal or attached to an email, opening it shows tags and numbers rather than an invoice. This viewer reads that XML and lays it out as a normal invoice, with the seller and buyer, every line, the VAT breakdown, totals, payment details and any attached files, and it checks that the totals add up. It works for the UAE's PINT AE format and for the European formats built on the same standard.
Which e-invoice formats can it open?
Almost all e-invoices use one of two XML syntaxes defined under the European standard EN 16931, and the viewer reads both:
- UBL 2.1 (invoices and credit notes): Peppol BIS Billing 3.0, Peppol PINT including PINT AE in the UAE, XRechnung UBL in Germany, and the national Peppol profiles used in Belgium, the Netherlands, the Nordics, Australia, New Zealand, Singapore and Japan.
- UN/CEFACT Cross Industry Invoice (CII): XRechnung CII and the XML inside ZUGFeRD and Factur-X invoices.
Files received over Peppol are often wrapped in a Standard Business Document Header; the viewer finds the invoice inside. It names the profile from the invoice's CustomizationID, so you can see at a glance whether you received a PINT AE, Peppol BIS or XRechnung document.
How to convert an XML invoice to PDF
Open the file, check it, then use Print or save as PDF and choose Save as PDF as the printer. Only the invoice is printed, not the rest of the page. The PDF is a readable copy for approvals, filing or a customer who asks for one, but it is not the legal invoice: in the UAE the Ministry of Finance is explicit that PDF, Word, scanned or emailed invoices are not e-invoices. Keep the original XML for as long as the law requires (five years in the UAE, seven for real estate).
What the checks tell you
Receiving matters as much as sending. In the UAE, recipients have their own e-invoicing duties, and a buyer that accepts a broken invoice can struggle to recover its input VAT. The viewer runs the arithmetic rules every EN 16931 invoice must meet:
- The line net amounts add up to the lines total.
- Lines total, minus allowances, plus charges, equals the total without VAT.
- The VAT breakdown adds up to the VAT total, and the total without VAT plus VAT equals the total with VAT.
- The amount due equals the total with VAT, minus anything prepaid, plus rounding.
- Both parties have a Peppol electronic address.
For UAE PINT AE invoices it also checks that both electronic addresses use scheme 0235 with a 10-digit TIN, and that a foreign-currency invoice states the VAT total in AED. These checks catch the common errors quickly, but they are not a full schema or Schematron validation: your Accredited Service Provider validates every e-invoice in full before it is delivered.
Attachments inside the XML
Senders often embed a PDF copy of the invoice, a timesheet, a delivery note or a purchase order in the XML as base64 data. The viewer lists each one with its file name and lets you download it. Attachments are always saved as files rather than opened in the page.
Private by design
Invoices carry prices, bank details and customer data, so the file is read by your browser and never uploaded. To create a UAE e-invoice of your own, use the PINT AE generator; to look up what any field means, use the PINT AE data dictionary; and to fix the TRNs and Peppol IDs in your customer list, use the TRN to Peppol ID converter.