What does the UAE's Decentralized Continuous Transaction Control and Exchange (DCTCE) model mean for businesses?

The DCTCE framework—widely referred to as the 5-Corner e-billing model—establishes a non-clearance system. Rather than funneling billing records through a centralized government portal prior to client delivery, the UAE allows digital, structured invoices to move seamlessly directly from the vendor to the buyer via certified Access Points. Simultaneously, the billing data is automatically forwarded to the Federal Tax Authority (FTA) in near real-time.

When is the final date for large companies to select an Accredited Service Provider (ASP)?

According to updated regulatory directives from the Ministry of Finance, tier-1 taxpayers with gross annual revenues crossing AED 50 million have been granted an extension until October 30, 2026, to contract an official Accredited Service Provider (ASP). Despite this adjusted setup timeline, the mandatory deadline to begin issuing live e-invoices remains firmly scheduled for January 1, 2027.

What are the implementation timelines for mid-to-small enterprises and public sector groups?

Commercial organizations generating under AED 50 million in annual turnover, along with government bodies, must formally partner with an authorized ASP by March 31, 2027. Following onboarding, mandatory enforcement goes live on July 1, 2027 for smaller private companies, and on October 1, 2027 for all Business-to-Government (B2G) transactions.

Are companies operating in Free Zones or dealing in tax-exempt items subject to the mandate?

Yes. Ministerial Decision No. 243 of 2025 leaves no exceptions based on geographic or tax status. The digital invoicing mandate covers every domestic commercial transaction, meaning enterprises trading within UAE Free Zones, companies dealing in out-of-scope distributions, and entities providing tax-exempt services must comply completely.

What are the exact structural formats required for a valid UAE e-invoice?

Every digital invoice must strictly align with the Peppol PINT-AE data standard, utilizing UBL 2.1 XML architecture. The electronic files must correctly map out over 50 data variables, which include secure Universally Unique Identifiers (UUIDs), precise itemized tax calculations, and specific tax treatment justification codes.

Which types of business revenue are currently excluded from the initial rollout?

The early operational phases explicitly exclude retail Business-to-Consumer (B2C) transactions. Furthermore, specific sovereign actions handled exclusively by state agencies, passenger air travel ticket sales, and cross-border air freight managed via airway bills (exempt for 24 months) remain temporarily out of scope.

What are the specific regulatory penalties for missing the UAE e-invoicing requirements?

Regulated by Cabinet Resolution No. 106 of 2025, a business that fails to launch the digital system or misses its deadline to onboard an ASP will face a monthly penalty of AED 5,000. Furthermore, neglecting to transmit a compliant electronic invoice or electronic credit note triggers a fine of AED 100 per document, with a maximum accumulation limit of AED 5,000 per month for each category.

What should an enterprise do if its internal invoicing software suffers a technical crash?

If an ERP breakdown or unexpected connection outage interrupts your digital billing capabilities, both the sender and the recipient are required by tax law to notify the FTA of the system failure within two business days. Delaying this mandatory report beyond the deadline results in an administrative penalty of AED 1,000 for each day the delay continues.

For how long must companies store their digital invoicing files and metadata?

To stay compliant with the Tax Procedures Law and Corporate Tax rules, all generated XML structures, credit adjustments, and tracking metadata must be saved in an unalterable, audit-ready archive. General VAT documentation requires a storage timeframe of at least 5 years, whereas corporate tax documentation must be preserved for a minimum of 7 years.

How do organizations link their existing accounting software or ERP platforms to the national grid?

Businesses do not need to construct direct custom pipelines to the FTA network independently. Instead, your in-house accounting software or ERP application connects directly via standard APIs to an official Accredited Service Provider (ASP). The ASP serves as the middleware that instantly translates your data into valid PINT-AE XML, signs the document, and forwards the data to the government.

TLV Encoding for QR Codes Under Oman's E-Invoicing Mandate

The Oman Tax Authority (OTA) has published the PINT OM specification through OpenPeppol, giving businesses their clearest view yet of how electronic invoicing will work in the Sultanate. PINT OM is the technical foundation of Oman's e-invoicing program and the standard every e-invoicing solution in Oman must follow. This guide explains what PINT OM is, what the specification package contains, which data fields are mandatory, the accepted formats and validation rules, and what changed between the earlier draft and the current release.

What Is PINT OM?

PINT OM stands for Peppol International (PINT) Oman. It is the Omani localization of the international Peppol PINT standard: the technical specification that defines exactly how a compliant electronic invoice must be structured, validated, and transmitted in Oman. It sits at the heart of PEPPOL e-invoicing in Oman and was published in draft form by the OTA through OpenPeppol, currently open for final stakeholder review before being formally enacted.

The PINT OM specification is built on UBL 2.1 XML syntax and is fully interoperable with the global Peppol network and the European EN 16931 invoicing standard. This means a business in Oman using a PINT OM-compliant e-invoicing solution can also exchange structured invoices with international trading partners on the same network, enabling cross-border Peppol invoicing without needing a separate integration.

PINT OM defines the data structures, validation rules, business terms, code lists, and exchange processes for all invoice transaction types in Oman. It is the single authoritative technical reference for OTA compliant e-invoicing in the country from a data and format perspective, covering Oman B2B and Oman B2G e-invoicing alike.

For context, the OTA was officially approved as a Peppol Authority, making Oman the third GCC country to adopt mandatory e-invoicing after Saudi Arabia and the UAE. PINT OM is the technical expression of the Oman e-invoicing mandate.

How PINT OM Relates to PINT AE and Other GCC Standards

PINT AE (UAE) and PINT OM (Oman) are both national localizations of the same global Peppol PINT framework. Both use UBL-based structured invoice formats and the same underlying Peppol network architecture. The key differences lie in their local tax rules, mandatory field sets, code lists, and the role of the respective tax authority as the Peppol Authority.

Businesses operating across the GCC will need to implement separate but architecturally similar compliance setups for each jurisdiction. A GCC e-invoicing solution built for PINT AE will share the same foundations as one built for PINT OM, but the Oman-specific fields and code lists require separate mapping.

Inside the PINT OM Specification Package

PINT OM is not a single document but a structured package covering three core document types, each with its own data model and validation rules.

PINT OM Billing: Defines the framework for standard electronic invoices and credit notes issued between a supplier and a buyer. Covers the data model, mandatory and conditional fields, business rules, and Peppol compliance requirements for standard invoice transactions in Oman.
PINT OM Self-Billing: Defines the framework for self-billing scenarios, where the buyer issues the invoice on behalf of the supplier. Covers self-billed invoices and self-billed credit notes, which have distinct data requirements and business rules from standard supplier-issued invoices.
Oman Tax Data Document (TDD): Defines the structure for reporting invoice data to the OTA. The TDD is not exchanged commercially between trading parties. It is a regulatory submission used for tax reporting and e-invoicing compliance in Oman. A party may submit a TDD as either the invoice issuer or the invoice receiver, depending on the reporting obligation.

The package also includes Business Interoperability Specification (BIS) documentation, compliance measurement guidelines, Oman-specific release notes, code lists, and a semantic data model defining the business terms and data elements used across all three document types.

Mandatory Data Fields: What Changed in the Latest Release

One of the most consequential aspects of the PINT OM publication is the expansion of mandatory data fields. Any business or technology team that based their gap assessment on the earlier draft data dictionary needs to revisit that work.

Earlier Data Dictionary: 53 mandatory fields
Current PINT OM specification: 73 mandatory fields

Fields Removed From Mandatory Status: QR Code, Digital Signature, Invoice Hash.

Critical note: If your vendor or internal team built compliance architecture around QR codes, digital signatures, or invoice hash fields based on the earlier draft, that work needs to be reviewed. These fields are no longer mandatory under the current PINT OM specification. Choosing an OTA compliant e-invoicing solution that reflects the current specification avoids this risk.

Fields Reclassified as Optional: Invoice Issue Time, VAT Point Date, VAT Rate Category, VAT Rate for Invoiced Items, Item Type.

New Mandatory Fields Added: 28 new fields have been added as mandatory (generally or conditionally), while 45 fields from the earlier draft continue to be mandatory. The full list of 28 new fields requires detailed ERP mapping and data quality work before go-live, which is why ERP-integrated e-invoicing in Oman is central to a smooth implementation. The framework for credit notes and self-billed transactions carries additional specifications beyond those for standard invoices.

Decimal Precision Limitation: The current PINT OM specification limits all document-level monetary amounts to a maximum of two decimal places. An update to support three decimal places is planned and will be confirmed in a future release. This is relevant for industries where three-decimal pricing is common.

Accepted Formats Under PINT OM

E-invoices under PINT OM must be issued in XML (UBL 2.1) structured per the specification, or in PDF/A-3 format with embedded XML. JSON has not been officially confirmed as an accepted format. Standard PDF invoices sent by email are not compliant.

If your current systems produce only unstructured PDFs, format conversion to PINT OM-compliant XML is a mandatory part of any implementation. The invoice must be generated in structured format at the point of supply, not created manually and converted afterward. This is where electronic invoicing software in Oman, whether cloud-based or ERP-integrated, does the heavy lifting.

Validation Rules and Technical Requirements

Schematron Validation: PINT OM invoices are validated through a multi-layer process: structural validation against the XSD schema, business rule validation against PINT OM Schematron rules, and code list compliance checks. An invoice that fails any of these layers is rejected before it can be exchanged or reported.
Unique Invoice Identifiers: All invoices must contain unique identifiers (UUIDs). These serve as the primary reference for tracing an invoice and for reconciling it with its corresponding Tax Data Document.
EN 16931 Compliance: PINT OM is built on the European EN 16931 semantic data model for electronic invoicing, the same baseline used by Peppol BIS Billing 3.0. Businesses already compliant with Peppol BIS Billing 3.0 in other jurisdictions will find the technical architecture familiar, though the Oman-specific mandatory fields and code lists require separate mapping.

Language Support: The specification is expected to support both Arabic and English.

SMARTeIS: A PINT OM-Compliant E-Invoicing Solution for Oman

Implementing PINT OM means generating UBL 2.1 XML across all 73 mandatory fields, passing Schematron validation, connecting to the Peppol network, and reporting to the OTA. For most businesses, a purpose-built e-invoicing solution for Oman is the practical path to compliance.

SMARTeIS by Skill Quotient Technologies is a PINT OM-ready e-invoicing software solution built on the Peppol framework for the Oman market. It supports PINT OM (UBL 2.1 XML) and PDF/A-3 formats and offers ERP-integrated e-invoicing with major platforms including SAP, Oracle, and Microsoft Dynamics. As a Peppol Access Point, SMARTeIS handles the full workflow: invoice generation, PINT OM validation, network transmission, Tax Data Document reporting to the OTA, and compliant archiving. It is designed to serve both enterprise e-invoicing requirements and e-invoicing for SMEs in Oman.

To explore how SMARTeIS can support your PINT OM implementation, request a demo or speak with the compliance team.

Where to Access the PINT OM Specification

The draft PINT OM specifications are published on the Peppol test documentation site and were released for public consultation. The specification remains open for final revision based on stakeholder feedback before formal enactment. Businesses and technology teams should refer to the official OpenPeppol documentation and OTA guidance for the authoritative and most current version.

Because the current release is a draft, the final specification may contain further changes. Teams beginning their gap assessment now should treat the 73 mandatory fields and current validation rules as a strong working baseline while monitoring for the finalized version.

Conclusion

The PINT OM specification marks a defining step in Oman's move to structured electronic invoicing. For businesses, it sets clear technical expectations: UBL 2.1 XML output, 73 mandatory data fields, multi-layer validation, and full interoperability with the Peppol network. The shifts between the earlier draft and the current release, particularly the removal of QR codes, digital signatures, and invoice hashes from the mandatory list, show that the specification is still evolving, so teams should treat the current version as a strong working baseline rather than a final blueprint.

The businesses that fare best will be those that start their gap assessment early, map their data against the mandatory fields, and choose an implementation path, whether in-house or through a PINT OM-compliant e-invoicing solution in Oman, well before the specification is finalized. Monitoring the official OpenPeppol and OTA channels for the enacted version remains essential.

Frequently Asked Questions

What is PINT OM?
PINT OM (Peppol International Oman) is the technical specification that defines how compliant electronic invoices must be structured, validated, and transmitted in Oman. It is Oman's localization of the global Peppol PINT standard, built on UBL 2.1 XML, and underpins all OTA compliant e-invoicing in the Sultanate.

What is the difference between PINT OM and the earlier data dictionary?
The earlier draft data dictionary specified 53 mandatory fields. PINT OM expanded this to 73 mandatory fields. It also removed QR Code, Digital Signature, and Invoice Hash from the mandatory list, and reclassified five other fields as optional. The two should not be treated as interchangeable for compliance planning.

Is the QR code mandatory under PINT OM?
No. QR Code, Digital Signature, and Invoice Hash were all removed from the mandatory field list in the current PINT OM specification. They appeared in the earlier draft but are no longer required.

What invoice format does PINT OM require?
PINT OM requires XML in UBL 2.1 syntax, or PDF/A-3 with embedded XML. JSON has not been officially confirmed as an accepted format. Standard PDF invoices sent by email are not compliant, which is why most businesses adopt dedicated electronic invoicing software in Oman.

Is the PINT OM specification final?
Not yet. The current release is a draft, published for public consultation through OpenPeppol. It remains open for revision based on stakeholder feedback before formal enactment, so businesses should monitor the official OpenPeppol and OTA channels for the finalized version.

Talk to our Oman e-invoicing expert!

Get a personalized Fawtara readiness assessment and discover the fastest path to compliance before your wave goes live.

Enquire Now!

Blog