Oman's Fawtara platform went live with Release 2 in July 2026, and the 144 large taxpayers the Oman Tax Authority notified under Phase 1 now have a live VATIN checker to confirm exactly when their August 2026 obligation starts.
The build behind that go-live has moved quickly. The OTA became an official Peppol Authority in January 2026 — the formal status that lets it govern accreditation and exchange standards for Oman's own network rather than borrowing another jurisdiction's framework. It published the PINT OM technical specification in April 2026, the Oman-specific invoice profile that plays the same role PINT-AE plays in the UAE: the country-level rules that sit on top of the shared Peppol base. In May 2026 it launched the VATIN-based rollout checker, giving businesses a direct way to confirm which phase their registration falls into rather than relying on a general timeline. ASP accreditation is now underway, and Phase 1 — the 144 large taxpayers notified — becomes mandatory in August 2026, with Phase 2 following in February 2027 and all VAT-registered businesses brought in by August 2027.
Real-Time Tax Transformation (forthcoming) frames this kind of regional build-out through the three-model picture set out in its opening chapter: jurisdictions are converging on structured, transaction-level tax data, but not on identical technical architecture. Clearance models, real-time reporting models and interoperability models each reduce the distance between the business transaction and the authority's visibility of it, and the underlying invoice data across frameworks is largely aligned — supplier, buyer, line items, tax treatment, totals — even where the transmission mechanics differ. Oman's choice of a Peppol-based interoperability model, like the UAE's, sits inside that same direction of travel. It is not, however, the same build.
That distinction matters for any business already running UAE PINT-AE readiness work. The instinct to treat Oman as a configuration variant of the UAE integration — same ASP, same field mapping, same access point — misreads what "Peppol-based" actually guarantees. Even where the foundational data model is closely aligned across jurisdictions adopting similar interoperability approaches, the country-specific portion sits in local fields, participant identifier schemes and validation rules — and those are exactly the details a fresh technical specification like PINT OM is built to define separately from PINT-AE. A UAE ASP contract does not automatically extend into Oman, and an ASP accredited for the UAE ecosystem is not automatically accredited for Oman's. Accreditation, as the book's treatment of the UAE ASP relationship makes clear, is a jurisdiction-specific regulatory status, not a portable technical capability.
The practical next step for a GCC-operating business is narrower than a full readiness programme repeated from scratch. Use the VATIN checker to confirm phase assignment rather than assuming the UAE timeline applies. Treat PINT OM accreditation as a separate procurement decision, evaluated on its own governance and dependency criteria rather than inherited from whichever provider already handles the UAE side. The two builds share a philosophy — structured, machine-readable transaction data replacing periodic reporting — but not a field mapping, and a business that conflates the two will discover the gap the way most implementation failures surface: at the point a transaction rejects and nobody can say why.