PINT OM invoice viewer

Got an .xml file from a supplier or your service provider? Drop it below. You'll see a readable invoice: seller, buyer, invoice number and dates, lines, VAT breakdown, totals and payment details. The file is read in your browser and is never uploaded.

The file never leaves your browser: it is opened and shown on your device only.

Which files can it open?

• Omani e-invoices in PINT OM: tax invoices, credit notes and debit notes, and self-billed invoices ^[1].
• Peppol BIS Billing 3.0 and PINT invoices from other countries, including the UAE's PINT AE, and CII files.

From your go-live date, an Omani tax invoice is an XML file; a PDF or a paper copy is not the invoice ^[3][4]. Your accounting software usually shows it for you. A viewer helps when you only have the file: a test file from your provider, a file a supplier emailed, or an auditor's request.

What is Omani about an Omani e-invoice?

The XML follows the Peppol PINT model with Omani rules on top ^[1][2]. When you read a file, these points matter:

• Seller and buyer are addressed by their VAT number (scheme 0248). VAT numbers in the tax fields must be OM followed by 10 digits ^[2].
• Each invoice has a UUID, a unique identifier on top of the invoice number ^[2].
• A transaction type of 20 flags (a string of 1s and 0s) says what kind of invoice it is: full or simplified tax invoice, self-billed, third party, summary, continuous supply, export, deemed supply, reverse charge on imports, profit margin, e-commerce, import of goods, special zone or prepayment ^[2].
• Document types: tax invoice (380), credit note (381), debit note (383), self-billed invoice (389) and self-billed credit note (261) ^[2].
• Amounts are in Omani rials with three decimals (baisa) on the lines and two on the VAT totals; a rounding difference of one baisa per line is tolerated for tax-inclusive retail prices ^[2].
• Imports are reported with a self-billed invoice issued by the Omani buyer ^[3].

Alongside each invoice, the providers send a separate Tax Data Document to the Oman Tax Authority ^[1]. You never see it in your invoice file, and our viewer does not open it. The QR code the rules require for B2C sales goes on the printed or PDF copy, not in the XML ^[3].

How well it works (our test)

We opened the 49 official PINT OM sample files published by OpenPeppol ^[1], and all 49 open: the 40 invoices and credit notes and the 9 self-billing documents. The standard view leaves out a few PINT OM fields, so an "Oman details" box above the invoice lists them: the UUID, the issue time, the exchange rate, the credit note reason, references with letter codes, and the per-line amounts including VAT, line VAT and exemption codes.

What it doesn't do

• It does not check the Omani rules. It shows what is in the file. It does not tell you whether the invoice passes PINT OM validation. Your service provider validates invoices before sending them ^[3]. For what common rule codes mean, see the validation errors explained.
• It does not create, edit or send invoices. For that you need an accredited service provider.
• It does not archive. Keeping your invoices is your job, not the Tax Authority's ^[3]. Keep the original XML.

Credits

Rendering uses the KoSIT xrechnung-visualization stylesheets (Apache-2.0) ^[5]. PINT OM is a specification published by OpenPeppol ^[1]. Full licences are on the licence page.

Related: How Oman e-invoicing works · Peppol ID lookup

Checked on 9 October 2026.