Last updated at
November 6, 2026
Learn more about this by booking a demo call with us. Our team will guide you through the process and answer any questions you may have.
Book NowOman's e-invoicing mandate begins on 1 April 2027, and once your business is in scope, every invoice you issue to a consumer (B2C) must carry a QR code. The Oman Tax Authority (OTA) applies the same requirement to buyers not registered for VAT, whether the invoice is full or simplified. You generate the code, and it appears only on the human-readable copy, not on the XML e-invoice.
The first phase covers businesses with annual supplies above OMR 5 million, and all other VAT-registered taxpayers follow on 1 October 2027. Based on the OTA’s Fawtara FAQ of 30 September 2026, this guide explains which invoices need the Oman e-invoicing QR code, who generates it, where it appears, what goes inside it and how to prepare.
The OTA's Fawtara FAQ, last updated 30 September 2026, sets out the requirement in Section 4.1, "QR Code, UUID and Invoice Hash". It answers five questions on the Oman e-invoicing QR code and points to the Peppol Oman technical documents for the detailed specification.
The legal basis sits in Decision No. 189/2026, published in Official Gazette issue 1660, which replaces Article 143 of the VAT Executive Regulation. Under the new Article 143, tax invoices must be issued in an approved and secured electronic format with a unique number, within 15 days. This includes invoices for supplies to a person not subject to tax. The Decision also adds item 11 to Article 147, which allows the OTA to specify further data for simplified tax invoices.
The table below summarises what Section 4.1 confirms:
| Point | What the OTA confirms |
| Which transactions | All B2C transactions and transactions where the buyer is not registered for VAT |
| Which invoice types | Full and simplified invoices |
| Who generates it | The taxpayer (Corner 1) |
| Where it appears | The human-readable invoice only |
| Where it does not appear | The e-invoice |
| What it is for | OTA verification of authenticity through a future mobile app |
| What goes inside | Defined in Appendix D of the Peppol Oman Architecture v1.0.2 |
The 30 September 2026 FAQ answers a common question directly: is the QR code mandatory only for simplified invoices? The OTA's answer is that it is mandatory for all B2C transactions and for transactions where the buyer is not registered for VAT. Articles that limit the Fawtara B2C QR code to simplified invoices, or to consumers alone, do not reflect the current guidance.
The Oman invoice QR code requirements depend on who the buyer is, not on the size or format of the invoice. E-invoices are needed wherever the VAT legislation requires an invoice, and a QR code is added when the sale is B2C or the buyer is not registered for VAT. Your billing and POS systems therefore need to know the buyer's VAT status at the point of sale, because the same product can need a QR code for one customer and not for another.
A B2C sale is a supply to an individual consumer, such as a retail purchase, a restaurant bill or a household utility bill. The second trigger is wider: it covers any buyer without Oman VAT registration, including businesses and government bodies. For example, a laptop sold to a small trading company with no VAT registration number needs a QR code on its printed invoice, even though the buyer is a business. The OTA also confirms there are no industry exceptions, so retail, hospitality and utility businesses follow the same rules as every other taxpayer in their rollout.
For both types of buyer, you still submit the invoice to your service provider, which sends the tax data document to the OTA. The buyer's copy travels separately, through your current process and format, because the buyer is not part of the Fawtara network.
Under the PINT OM specification, a simplified tax invoice contains fewer fields than a full tax invoice and is generally issued for B2C sales. Every e-invoice records its type in a mandatory transaction type field, a 20-position code where the first position marks a full tax invoice and the second marks a simplified one. The QR requirement applies to both types, so issuing a full tax invoice to a consumer does not remove the QR code.
It depends on the buyer's VAT registration, not on whether the buyer is a business or a government body. A sale to a VAT-registered business or government buyer follows the standard e-invoice flow between both parties' service providers, and Section 4.1 sets no QR requirement for it.
A sale to a business or government body that is not registered for VAT does need the QR code. Your billing system should therefore check registration status, not customer type, before it prints the invoice. Our Oman e-invoicing guide explains the B2B and B2G flows in full.
The taxpayer at Corner 1, meaning you as the seller, generates the QR code. The OTA does not issue it, and the FAQ does not assign the task to the service provider. Your accredited service provider (Corner 2) validates the invoice against the Oman Schematron and reports the tax data to the OTA. Responsibility for invoice compliance still rests with you, and the OTA monitors service provider performance separately.
Decision No. 189/2026 adds a security duty as well. You must issue e-invoices through an electronic system that meets the OTA's technical security specifications, with measures in place for breakdowns and data recovery.
In practice, this means the following for your business:
Every in-scope sale produces two separate outputs. The structured e-invoice in XML goes to your service provider for validation and tax reporting, and the human-readable copy with the QR code goes to the buyer. Keep the two apart in your process, because the OTA states that a PDF invoice is not an e-invoice and that XML is the mandatory structured format for every e-invoice in Oman.
The table below compares the two outputs:
| Point | Human-readable invoice (buyer's copy) | Structured e-invoice |
| Who receives it | The consumer or non-VAT-registered buyer | Your accredited service provider |
| Format | Paper, PDF or another readable form | XML per PINT OM |
| QR code | Required | Not included |
| Route | Your current delivery process | Accredited service provider, with tax data to the OTA |
| Valid invoice for tax purposes | No | Yes |
For a sale to a consumer or non-VAT-registered buyer in Oman, tax data goes to the OTA through your service provider, and the QR code travels on the buyer's copy.
The OTA confirms that paper invoices can still be issued, but only e-invoices are considered valid invoices for tax purposes. A printed receipt for a consumer or non-VAT-registered buyer must still carry the Oman e-invoicing QR code, and the XML e-invoice for the same sale goes through your service provider as usual. The paper copy serves the buyer, while the e-invoice is the record that counts.
The Oman e-invoicing QR code is required only on the human-readable invoice, not on the e-invoice. The PINT OM Billing v1.0.1 semantic model has no QR code field, so there is nothing to map for it in your XML. It does include a Seller UUID for B2C transactions, which is covered below.
The Fawtara FAQ does not list the QR code fields. Instead, it refers taxpayers and service providers to Appendix D of the Peppol Oman Architecture v1.0.2, so the field list should come from that document rather than from summaries elsewhere.
Appendix D belongs to the Peppol Oman technical set. The same set includes the PINT OM Billing, PINT OM Self-Billing and Oman Tax Data Document specifications v1.0.1, which OpenPeppol published on 29 July 2026. Because the QR content is defined in Appendix D, ask your service provider or system vendor for the exact fields and encoding before you change your receipt templates. The FAQ names v1.0.2, so confirm with your service provider that you are working from the latest version.
Points the FAQ does not cover: The FAQ does not say whether the human-readable copy of a credit note or debit note needs a QR code, or how the QR code applies to exports. For exports, tax reporting follows the C1, C2 and C5 route, while the customer receives its invoice as per current practice. These points may still be covered in Decision No. 189/2026, Appendix D or the PINT OM specification, so confirm each one with your service provider. For questions about using the Fawtara Portal, the OTA offers support through portal tickets, email at ticketing@taxoman.gov.om and its 1020 call centre.
A UUID is a unique reference code created for a document, so no two documents share the same identifier. The PINT OM Billing specification includes a Seller UUID, defined as the receipt UUID generated by the seller for B2C transactions only. Every invoice also carries a mandatory version 5 UUID, which is generated from fixed inputs so the same inputs always produce the same value. Every invoice requires its mandatory invoice UUID. The specification also provides a separate Seller UUID field for B2C receipts.
The OTA will use the QR code to verify the authenticity of e-invoices through a future mobile app. The official sources checked on 24 October 2026 give no launch date for the app, so treat it as a future feature rather than something you can test against today.
There is no separate B2C start date. The OTA confirms that B2C is implemented at the same time as B2B and B2G, so consumer receipts cannot be treated as a later project. The QR code applies from your own e-invoicing date under Decision No. 189/2026, which also allows the OTA Chairman to grant a time-limited exemption on application, provided the taxpayer files returns and pays tax on time.
Your phase depends on annual supplies as of 31 March 2027. The calculation includes taxable supplies excluding capital assets, plus supplies subject to the reverse charge mechanism and intra-GCC supplies. VAT groups are assessed at group level, and non-residents count only supplies made in Oman. The OTA's Potential Rollout Checking page shows your potential start date.
The dates that bring the QR code into force are:
| Phase | Who it covers | Start date |
| Early adoption | Taxpayers ready before their mandate date; the OTA encourages Pilot participation | Before the mandate date |
| Phase 1 | Supplies above OMR 5,000,000 from 1 April 2026 to 31 March 2027, or expected from 1 April 2027 to 31 March 2028 | 1 April 2027 |
| Phase 2 | All other VAT-registered taxpayers | 1 October 2027 |
The submission window is 24 hours for B2C and real time for B2B. The window applies to the structured e-invoice and its tax data, not to the buyer's copy, so track the two separately: a receipt in the customer's hand does not mean reporting is complete. Our Oman Fawtara FAQ page covers the remaining OTA answers on timing and onboarding.
The Oman e-invoicing QR code touches sales channels, customer data, print templates and your service provider connection, so finance and IT should work from one shared list. Use the steps below as recommended preparation, not as legal requirements:
Flick Network's Oman e-invoicing solution helps your business get ready for Oman e-invoicing, including sales to consumers (B2C) and non-VAT-registered buyers. Here is what Flick offers:
In Oman, every sale to a consumer (B2C) or to a buyer not registered for VAT needs a QR code on the buyer's copy, whether the invoice is full or simplified. You, as the seller, generate the code, while the XML e-invoice goes separately through your service provider, within 24 hours for B2C sales.
To prepare, check each buyer's VAT status, add QR generation to your billing or POS system using Appendix D, update your invoice templates and test them before your e-invoicing date, either 1 April 2027 or 1 October 2027. To discuss your Oman e-invoicing QR code readiness, contact sales@flick.network.
1. Do invoices issued before my e-invoicing date need a QR code?
No. Historical invoices do not need to be submitted to the OTA. The QR code applies to invoices you issue under Fawtara from your rollout date, so receipts issued before that date do not need to be reissued.
2. Can invoices with the QR code be issued in Arabic and English?
Yes. The OTA supports invoice issuance in different languages, provided invoices follow the Oman VAT legislation. A bilingual receipt for a consumer or non-VAT-registered buyer still needs the QR code in the same way as a single-language one.
3. Do I need to replace my ERP or POS system to add QR codes?
Not necessarily. ERP systems can be retained, depending on your arrangement with your accredited service provider. The system you keep still needs to generate the Oman e-invoicing QR code on every invoice in scope.
4. Is an Oman e-invoicing QR code required before my rollout date?
No, not under Fawtara. A VAT-registered seller not yet in a rollout can keep issuing invoices through its existing mechanism, provided it complies with the VAT legislation. The OTA does encourage testing and issuing e-invoices before your mandate date.
5. Who is responsible for storing B2C e-invoices?
Taxpayers are responsible for storing and archiving e-invoices under the VAT legislation. The OTA will not provide invoice-related information to taxpayers or service providers.
6. How do I correct a B2C e-invoice after issuing it?
You adjust an issued e-invoice by issuing an electronic credit note or debit note. The PINT OM specification lets the note reference the original invoice and its UUID, so both documents stay linked in your records.
7. Can I use separate service providers for B2C and B2B invoices?
No. You can connect with one service provider at a time, so your B2C and B2B invoices go through the same provider. You can disconnect and switch to another provider through the Fawtara Portal, and if a provider starts the disconnection, the final decision rests with you.
8. Can a large retailer become its own e-invoicing service provider?
Yes. Any company that meets the service provider criteria and passes the OTA's prescribed tests can be accredited and act as its own service provider. Those tests are the Peppol eDelivery and PINT OM test suites, completed on the official Peppol Testbed.
9. Are there penalties for non-compliant invoices in Oman?
Yes. The OTA states that penalties will apply according to the VAT legislation after the mandate begins. The Fawtara FAQ does not list penalty amounts.
Quick Navigation
Learn more by booking a demo with our team. We'll guide you step by step.