Fawtara Implementation Timeline 2026–2028: What Businesses Should Prepare for at Each Phase

This is the milestone that made e-invoicing in Oman a formal, structural reality rather than a policy intention. Once the OTA became an official Peppol Authority, the technical shape of Fawtara, a five-corner model routing invoices through Accredited Service Providers, was locked in. For most businesses, this milestone didn't require action yet, but it's the point after which "we'll deal with it later" stopped being a low-risk position.

The OTA published the PINT OM Billing specification through OpenPeppol, setting out the structured XML (UBL 2.1) and PDF/A-3 requirements that every compliant electronic invoice needs to meet. This is the point at which "we'll figure out the format later" became something concrete enough to actually test against. IT teams and AP automation vendors alike use this specification as the reference point for building and validating an automated invoicing system.

Roughly 100 large taxpayers were brought into a pilot group and expected to go live in August 2026 as originally planned. If a business wasn't part of this cohort, the pilot is still useful; it's the first real-world stress test of the Fawtara portal, validation rules, and exception handling, and the lessons from it tend to filter into how the OTA communicates expectations for Phase 1 and Phase 2.

• Watch for OTA guidance updates that follow directly from pilot-phase experience
• Treat pilot cohort feedback as an early signal of common validation and rejection patterns

This decision moved Phase 1 from February to 1 April 2027 and set Phase 2 at 1 October 2027. It's worth being precise about what changed and what didn't: the phase thresholds, document scope, and technical requirements stayed the same; only the dates shifted. Businesses that read the extension as reduced urgency, rather than as extra runway, tend to be the ones scrambling closer to their actual go-live date.

This is the date for all large taxpayers with annual VAT-able supplies above OMR 5 million. Businesses in this bracket should be treating the months leading up to it as their working deadline, not the later Phase 2 date. Key preparation at this stage includes:

• Confirmed ERP capability to generate a compliant Oman VAT invoice format
• A contracted and tested Accredited Service Provider connection
• Clean, validated master data across all active customer and supplier records
• A rehearsed exception-handling process for rejected invoices

Every remaining VAT-registered business, including SMEs, falls under this date. Six months separate Phase 1 and Phase 2, which is a meaningful advantage for smaller businesses; they can watch how Phase 1 businesses experience their cutover, learn from early ASP relationships and common rejection causes, and avoid repeating the same mistakes. The risk for this group isn't lack of time; it's treating eighteen months as effectively infinite and starting the ERP assessment work too late to benefit from that lead time.

Fawtara isn't a one-time technical project that ends at go-live. Ten-year e-archiving obligations, ongoing OTA guidance, and the likely tightening of validation rules as the OTA gains more live data all point to 2028 being a stabilization and optimization year rather than a quiet one. Businesses that treat their initial go-live as the finish line, rather than the sta rt of an ongoing compliance relationship, tend to find gaps reappear during their first full audit cycle.

It's also worth remembering that this timeline hasn't necessarily finished moving. The Fawtara timeline has already shifted once via Decision No. 189/2026, and the OTA has shown it's willing to adjust dates in response to real-world pilot experience. That's not a reason to plan around further delay; it's a reason to build a preparation plan robust enough to hold whether the dates move again or not, rather than one that only works if nothing changes between now and go-live.

The most useful way to use this timeline isn't to read it forward from today, it's to work backward from your actual go-live date. Most Fawtara rollouts benefit from leaving 60 to 90 days between final testing and go-live, which means ERP assessment, ASP selection, master data cleanup, and pilot testing all need to be scheduled with that buffer already subtracted, not added as an afterthought.

COVORO tracks this evolving timeline closely across the markets it operates in. As a Peppol PINT-AE certified, UAE Ministry of Finance pre-approved platform built to ISO 27001 and ISO 22301 standards, already live across the UAE and Malaysia and currently pursuing OTA accreditation for Oman, COVORO works with businesses to map their specific go-live date against the milestones that actually matter for their systems and industry, rather than treating the whole timeline as one undifferentiated deadline.