Oman vs UAE: two e-invoicing mandates, one architecture

If your group operates on both sides of the border, you're facing two e-invoicing mandates arriving on similar clocks. The good news first: Oman and the UAE made the same fundamental design choice, so work done for one genuinely carries over to the other. The details, though, diverge in ways that matter for planning.

Where they're the same

• Architecture: both chose the decentralized five-corner model (DCTCE) — invoices travel between accredited providers over Peppol while tax data flows to the authority in parallel. Our corner-model guide explains why that matters.
• Format family: both build on Peppol PINT. Oman's flavor is PINT-OM; the UAE's is PINT AE. Same skeleton, different national fields.
• Accredited providers: in both countries, invoices must flow through service providers accredited by the authority — you don't connect to the regulator directly.
• Phased rollout: both start with larger taxpayers and expand toward SMEs, with B2B and B2G in scope.

Where they differ

Timelines in both countries are set — and occasionally adjusted — by the regulators, so treat their official portals as the source of record and everything else, including this page, as orientation.

What multi-country groups should actually do

The trap is running two disconnected compliance projects with two vendors, two field mappings, and two support relationships. Because both mandates ride the same Peppol rails, a saner pattern is one integration layer feeding both: your ERP maps once to the shared PINT core, with country rules (OM vs AE) applied at the provider level.