Oman Data Dictionary for E-Invoicing: Key Facts Businesses Need to Know

What Is the Data Dictionary?

E-invoicing requires the standardization of invoice-level data and interoperability across different ERP and billing systems. The Data Dictionary is the central component that makes this possible. It defines the standard data elements, the fields and configurations, required to issue a compliant e-invoice.

It is built on three components:

• Business Terms. Set out the document types for which e-invoicing applies and specify the content and fields for each, marking them as mandatory, optional, or conditional. This covers invoice details, seller and buyer details, amounts, and VAT.
• Business Rules. Define the validations and compliance requirements each invoice must pass. They may require identifiers, enforce data formats, or mandate the presence of a field based on transaction type, and they maintain data integrity through checks such as positive monetary amounts, correct date formats, and matching line-item totals.
• Code Lists. Provide the standardized, permissible values for defined fields such as invoice types, currencies, VAT categories, and countries. These reduce errors and support smoother integration with Accredited Service Providers (ASPs) and the OTA.

The framework follows a five-corner model and is built on the PEPPOL framework, which the OTA formally adopted when it became a PEPPOL Authority in January 2026. E-invoices are issued as structured UBL files aligned with PEPPOL standards, so any e-invoicing software in Oman will need to produce and exchange documents through a PEPPOL Access Point rather than as plain PDFs. The model also incorporates Oman-specific requirements, including dedicated business rules for import transactions, invoice type codes, and a framework for generating the UUID, Invoice Hash, and QR Code.

Scope of E-Invoicing

The Oman e-invoicing mandate applies to all transaction types: standard rated, zero rated, exempt, and out-of-scope supplies. It also applies across all three supply categories - Oman B2B e-invoicing, B2C, and Oman B2G e-invoicing.

Issuance for B2C transactions is expected to be challenging, particularly in high-volume sectors. B2B and B2G transactions also carry practical hurdles, such as conforming to specific formats and obtaining customer approvals before issuance, which can require process changes.

Data Fields

The volume of required data rises sharply under the new framework. A standard tax e-invoice requires 53 mandatory fields, with up to 66 additional fields applied if certain conditions are met. The human-readable printed version requires 46 mandatory fields, with up to 50 conditional fields. This is a major increase from the 18 to 20 fields required on a standard tax invoice under current Oman VAT rules.

In practice, businesses will need to ensure these fields either exist in their ERP or billing systems in the prescribed formats, or build workarounds to populate them from outside those systems. This is where ERP-integrated e-invoicing in Oman matters, since platforms such as SAP, Oracle, and Microsoft Dynamics will need to map their data to the Data Dictionary, often through a cloud e-invoicing layer or data warehouse.

Document and Transaction Types

Business rules are defined for 8 document types: tax invoice, simplified invoice, prepayment invoice, simplified prepayment invoice, debit note, credit note, simplified debit note, and simplified credit note. The Code List also includes 14 specific transaction types, and the OTA has clarified that the rules for these follow the rules already defined for the 8 document types.

Key Technical Requirements

• UUID, QR Code, and Digital Signature: A UUID is assigned to every document. QR Code and Digital Signature are mandatory for simplified tax invoices, which the OTA has indicated are intended for B2C transactions. Technical guidance on compliance is expected in due course.
• Reporting timelines: B2B and B2G e-invoices are expected to be generated through real-time integration with an ASP, so real-time e-invoicing in Oman will become the operating norm. For B2C, the OTA is expected to release specific guidance, including whether batch submissions will be allowed.
• Cancellation: Once issued, an e-invoice cannot be cancelled. Only a tax credit note issued through the e-invoicing framework can reverse it, with the reason selected from the Code List. Businesses must follow the conditions and timelines in the Oman VAT legislation for credit notes.
• Imports: Self-billed e-invoices will be required for the import of goods and services. This is a new compliance step, as no invoice is currently required for imports, where VAT is handled through the reverse charge mechanism or paid at customs clearance.
• Zero-rating and exemptions: The basis for any zero-rating or exemption, as set in the Code List, must be stated. Zero-rated exports of services require additional detail on the nature of the service.
• HS codes: A 12-digit item classification identifier based on the Harmonised System (HS) is required on e-invoices involving goods, except for simplified tax invoices.
• Seller and buyer details: Multiple address fields are mandatory for both parties, including PO box, postal code, and location.
• Registration: No separate e-invoicing registration is needed. The existing VAT registration number (VATIN) serves as the unique electronic address. VAT Groups await further guidance, and each member is likely to require a separate ASP endpoint.

Rollout Timeline

The Oman e-invoicing rollout is being introduced in phases, beginning with the largest VAT-registered taxpayers who have already been notified. Phase 1 begins in August 2026, with later phases extending to all remaining VAT-registered businesses, including SMEs, through 2027. Exact dates and group sizes have been adjusted as the program has developed, so confirm your phase on the OTA portal.

Industry Impact

The mandate reaches every VAT-registered sector. E-invoicing in Oman for retail and hospitality will need to handle high B2C volumes and QR-coded simplified invoices, while e-invoicing for manufacturing, logistics, construction, oil and gas, trading companies, telecom, healthcare, and banking will focus on accurate master data, HS codes on goods, and real-time B2B integration. Businesses in Muscat, Salalah, Sohar, and across free zones all fall within the same framework.

What Businesses Should Do Now

Ahead of full technical guidance and ASP accreditation details, businesses should begin.

• Assessing ERP and billing systems against the Data Dictionary
• Identifying required system enhancements and workarounds
• Updating internal SOPs and compliance workflows
• Evaluating readiness for real-time API integration with an ASP
• Ensuring VAT classification and master data accuracy, especially customer and supplier details

A Note for Gulf Businesses

Although the UAE has announced a similar e-invoicing model, several Oman requirements differ, including those for B2C and import transactions and the QR Code and Digital Signature rules on simplified invoices. As a GCC e-invoicing framework built on PEPPOL and aligned with EN 16931 principles, it supports cross-border interoperability, but businesses operating in both countries should review each jurisdiction's requirements separately rather than reusing a single setup.

Final Words

The Data Dictionary may read as a technical document, but its message to businesses is simple. The standard is coming, the timeline is fixed, and preparation is the only real advantage available. Review your systems, align your data, and engage an accredited service provider early, so that compliance becomes a routine step rather than a scramble.

Need help preparing for Oman e-invoicing? SMARTeIS by Skill Quotient Technologies, an OTA pre-approved ASP, handles ERP integration and end-to-end Fawtara compliance. Contact us for a consultation or request a demo .

Frequently Asked Questions

1. What is the Oman e-invoicing Data Dictionary?

It is the official rulebook for e-invoicing in Oman . It defines the standard data elements, business rules, and code lists that every compliant e-invoice must follow, ensuring consistency across different ERP and billing systems. Business Terms specify which fields apply to each document type and whether they are mandatory, optional, or conditional. Business Rules enforce validations such as correct date formats and matching line-item totals. Code Lists provide the approved values for fields like currencies, VAT categories, and countries. Together they create a single shared standard so that invoices can be generated, exchanged, and validated automatically.

2. When does e-invoicing become mandatory in Oman?

Phase 1 begins in August 2026 for the largest VAT-registered taxpayers, who have already been notified by the Oman Tax Authority. Later phases extend to all remaining VAT-registered businesses, including SMEs, through 2027. The rollout is deliberately staged so that the largest and most complex businesses go live first, giving smaller companies more time to prepare their systems. Exact dates and the size of each group have been adjusted as the program has developed, so businesses should confirm their specific phase on the OTA portal rather than assuming a fixed date.

3. Who needs to comply with Oman e-invoicing?

All VAT-registered businesses will eventually be covered. The rollout is phased, starting with large taxpayers and expanding to SMEs, across B2B, B2C, and B2G transactions. In practice this means almost every business that issues tax invoices in Oman will need a compliant e-invoicing setup once its phase arrives. Even companies not in the early phases benefit from preparing ahead, because their buyers and suppliers in earlier phases will already expect to send and receive structured e-invoices.

4. How many data fields does an Oman e-invoice require?

A standard tax e-invoice requires 53 mandatory fields, with up to 66 additional fields applied conditionally. This is a sharp increase from the 18 to 20 fields required under current Oman VAT rules. The human-readable printed version requires 46 mandatory fields, with up to 50 conditional fields. For many businesses this means capturing data they do not record today, such as multiple address fields for buyers and sellers or item classification codes, so the fields will need to exist in the ERP system or be populated through a workaround before go-live.

5. What format must Oman e-invoices use?

E-invoices must be issued as structured files using the UBL standard, aligned with Oman's PEPPOL specification, rather than as plain PDFs. The OTA became an official PEPPOL Authority in January 2026. A structured file is machine-readable, which is what allows invoices to be validated automatically before they are sent. A standard PDF or scanned image will no longer qualify as a valid tax invoice once a business is in scope, although a human-readable version, often carrying a QR code, can still accompany the structured file for the customer.

6. What is the five-corner model in Oman e-invoicing?

It is the workflow Oman uses to exchange invoices. The invoice passes between the seller, the seller's accredited service provider, the buyer's accredited service provider, the buyer, and the Oman Tax Authority, allowing real-time validation without a single central portal. The seller's provider validates the invoice and routes it across the network to the buyer's provider, while the tax authority receives the reporting data in parallel. This decentralized design keeps the system fast and resilient, since invoices do not all funnel through one government gateway.

7. Do I need a separate e-invoicing registration in Oman?

No. The existing VAT registration number (VATIN) serves as the unique electronic address, so no separate e-invoicing registration is required. This keeps onboarding simpler, since businesses already hold the identifier they need to participate in the network. The main exception to watch is VAT Groups, where further guidance is expected and each member is likely to require its own connection to an accredited service provider.

8. Can an Oman e-invoice be cancelled once issued?

No. Once issued, an e-invoice cannot be cancelled. It can only be reversed by issuing a tax credit note through the e-invoicing framework, with the reason selected from the Code List. This makes accuracy at the point of issuance critical, because errors cannot simply be deleted. Businesses will also need to follow the conditions and timelines set out in the Oman VAT legislation when issuing credit notes, and consider how credit or debit notes link to invoices issued before e-invoicing began.

9. What document types are covered by the Data Dictionary?

Business rules are defined for 8 document types: tax invoice, simplified invoice, prepayment invoice, simplified prepayment invoice, debit note, credit note, simplified debit note, and simplified credit note. The Code List also includes 14 transaction types. The OTA has clarified that the rules for these transaction types follow the rules already defined for the 8 document types, so businesses do not face an entirely separate rulebook for each scenario. Mapping your real-world transactions to the correct document type is an important early step in implementation.

10. How should businesses prepare for Oman e-invoicing?

Start by assessing your ERP and billing systems against the Data Dictionary, identifying gaps and workarounds, cleaning up customer and supplier master data, ensuring VAT classifications are correct, and planning for real-time integration with an accredited service provider. It also helps to update internal procedures and train finance teams on the new flow, since e-invoicing changes how invoices are created, corrected, and archived. Beginning early, even before your phase is confirmed, turns compliance into a planned project rather than a last-minute rush.