Last updated at
July 4, 2026
Learn more about this by booking a demo call with us. Our team will guide you through the process and answer any questions you may have.
Book NowThe May 2026 update to Oman's Fawtara FAQ confirms the architecture, accreditation rules, and transaction obligations that service providers and taxpayers need to finalise before their go-live date. This guide breaks down every revised answer from the OTA's 31st May 2026 publication, section by section, using the official FAQ text as the sole source for every point.
The Fawtara FAQ on the OTA Tax Portal is organised into six sections: general scope, service provider accreditation, taxpayer responsibilities, e-invoice issuance, OpenPeppol integration, and taxpayer-to-service-provider linking. The May 2026 update revised six of these subsections with confirmed answers on accreditation requirements, submission timelines, VAT group rules, and Peppol membership obligations.
The table below outlines what changed in each updated subsection:
| Updated Subsection | What Changed |
| 2.2 Service Provider Accreditation | Expanded answers on experience, legal structure, paid-up capital evidence, and CR activity requirements |
| 2.3 General Service Provider Questions | Revised treatment of historical invoices, paper format after go-live, and export invoice flow |
| 3.2 VAT Group | Clarified how VAT group companies adopt e-invoicing and when input VAT can be claimed from non-network sellers |
| 4.2 E-invoice Implementation | Confirmed the step-by-step sequence for both taxpayers and service providers |
| 4.4 B2B and B2C Submission Timeline | Confirmed real-time for B2B, 24-hour window for B2C, and no separate B2C phase |
| 5.7 Regulatory and Compliance Context | Clarified when Peppol membership becomes mandatory and how parent company membership can be shared |
Applicants must have at least two years of operational experience before submitting an accreditation application, and that experience does not need to have been gained within Oman. For Riyada cardholders, the OTA applies a reduced threshold of one year of operational experience, recognising the early-stage nature of businesses operating under that programme.
Where the applicant is a newly established entity without its own operational history, the OTA will accept the parent company's operational experience to satisfy this requirement. The applicant must still hold a local commercial registration in its own name, and relying on a parent company's history does not remove that independent registration requirement.
Service providers incorporated in other GCC countries can apply for Fawtara accreditation under the same framework. They must meet every requirement the OTA has published, and they must maintain a local presence inside Oman. GCC origin does not create a simplified or alternative accreditation path.
There are no restrictions linked to a company's legal form, provided every other criterion is satisfied. A Single Person Company can apply for accreditation on the same basis as any other entity type.
Service providers can apply for accreditation at any point ahead of their planned go-live date, as the OTA has not set a deadline for submissions. The OTA aims to respond to submitted applications within 30 days, and the Authority will inform the applicant directly if that timeline is delayed.
The applicant's own commercial registration must include at least two activities related to IT services. The FAQ provides examples such as designing and programming software, and cloud and hosting services. This requirement applies to the applicant's own CR, not the parent company's.
Audited financial statements or the commercial registration must be submitted to evidence paid-up capital. These documents form part of the accreditation application package that the OTA reviews before issuing a decision. Applicants should prepare these documents before submitting their application, since the 30-day response window begins from the point of submission.
The Omanisation certificate is not a criterion for accreditation, and its absence will not disqualify an application. The OTA requests this document for its own record-keeping and information purposes only. Including it in the submission package as a supporting document avoids unnecessary follow-up from the OTA during the review process.
The May 2026 FAQ settles how Peppol routing and discovery will operate across the entire Fawtara network. Three points are confirmed directly by the OTA:
Peppol membership is not required at the point of initial application, but it must be confirmed before the OTA grants final accreditation. Applicants can open their OTA accreditation application and pursue Peppol membership simultaneously, without waiting for one process to complete before starting the other.
A Peppol membership can also be shared between an applicant and its parent company, provided both entities qualify as one legal entity under the applicable framework. This arrangement removes the need for duplicate membership costs when group structures are entering the Oman market together.
A QR code is mandatory for all B2C transactions under Fawtara, covering both full invoices and simplified invoices, not simplified formats alone. This was a point of uncertainty before the May 2026 update, and the OTA has now confirmed the full scope without exception.
The taxpayer at Corner 1 is responsible for generating the QR code, and the code is required only on the human-readable invoice, not on the underlying e-invoice data file transmitted through the Peppol network to the OTA. The OTA plans to use the QR code to verify invoice authenticity through a dedicated mobile application once that application becomes available, and service providers and taxpayers should refer to Section 4 of the Peppol Oman Architecture V1.0.1 document for the full list of required fields.
B2C implementation proceeds on the same overall timeline as B2B and B2G, with no separate phase-in period. Businesses that anticipated a later wave for B2C transactions should plan for all three transaction types as simultaneous obligations from their go-live date.
The table below outlines the required submission window for each invoice type under the Fawtara programme:
| Invoice Type | Submission Window |
| B2B | Real-time |
| B2C | Within 24 hours |
| B2G | Same rollout as B2B |
Invoices must be issued electronically using the prescribed XML format from the outset. An invoice cannot be created manually first and entered into the system afterward.
The OTA has confirmed the following sequence for each party:
The OTA reaches out to each rollout group at least six months before their go-live date and runs multiple clarification and support sessions during that preparation window. Taxpayers are expected to complete integration with their chosen service provider on or before their respective go-live date.
The table below summarizes the key milestones and their expected timelines for the Fawtara rollout:
| Milestone | Timeline |
| First rollout | August 2026 |
| Accredited service provider list announced | Q2 2026 (OTA target at time of FAQ publication) |
| Oman Test Suite availability | Q2 2026 (OTA target at time of FAQ publication) |
| OpenPeppol data dictionary and specifications (final version) | Q2 2026 (draft published; final version expected) |
Companies under the same VAT group adopt e-invoicing according to their own respective rollout assignments, not as a single combined entity. For intra-group transactions, invoice details must follow current accepted practice under VAT legislation.
If the seller does not meet VAT registration requirements, they are not required to join the Fawtara e-invoicing network. Such sellers cannot legally collect VAT, and there is no input VAT for the buyer to claim. If a non-VAT-registered seller issues an invoice that includes VAT, buyers should report the case to the OTA.
If the seller is a VAT-registered taxpayer that has not been included in the current or any previous rollout group, they can continue issuing invoices through their existing process, provided those invoices comply with VAT laws and regulations. Buyers receiving invoices under this scenario can claim input VAT under the standard eligibility rules currently in place.
In a cross-border export transaction, the customer at Corner 4 and the customer's service provider at Corner 3 are not part of the Oman Fawtara network. The supplier shares the invoice with the overseas customer using the existing invoicing process and format. Tax reporting through the e-invoicing network follows a reduced flow of C1 to C2 to C5 only, since the buyer-side corners sit outside the Fawtara perimeter. The supplier's accredited service provider submits the tax data directly to the OTA without routing through a receiving access point on the buyer side.
Historical invoices do not need to be submitted to the OTA as part of the Fawtara rollout. Businesses are not expected to retroactively upload or migrate past transactions into the e-invoicing system. The obligation to issue e-invoices applies from each taxpayer's respective go-live date going forward, and all invoices issued from that date must be in the prescribed electronic format.
After official implementation, paper invoices are no longer a valid format for B2B and B2G transactions. B2C transactions are the only exception, where a paper invoice can continue to be issued alongside the required electronic format. B2C sellers must produce both the e-invoice through their accredited service provider and a paper copy for the end customer, rather than replacing one with the other.
The May 2026 Fawtara FAQ update gives service providers and taxpayers the confirmed answers they need to move from planning into execution. The centralised SMP requirement defines how every accredited provider must build its technical integration. The B2C QR code requirements, Peppol membership sequencing, and VAT group adoption rules are now officially confirmed by the OTA. Businesses that were waiting on these answers can now move forward with their preparation work. The first rollout is scheduled for August 2026, and the available preparation window is closing quickly.
Reach out to sales@flick.network to get your Fawtara preparation on track before the first rollout.
1. Can a service provider run its own SMP instead of using the OTA's?
No. Oman will operate a centralised SMP for the entire Fawtara network. Accredited service providers must use the OTA's SMP and are not permitted to run or maintain their own.
2. Is Peppol membership required before submitting an accreditation application?
No. Peppol membership is required before final accreditation is granted, but applicants can begin the OTA process before confirming membership, with both tracks running in parallel.
3. Is a QR code required on every B2C invoice, including simplified invoices?
Yes. The OTA confirms that a QR code is mandatory for all B2C transactions, covering both full invoices and simplified invoices without exception.
4. What is the submission window for B2C e-invoices?
B2C e-invoices must be submitted within 24 hours of issuance, while B2B e-invoices must be submitted in real time.
5. Do VAT group members adopt e-invoicing together as a single entity?
No. Each company within a VAT group follows its own individual rollout assignment under the Fawtara programme.
Quick Navigation
Learn more by booking a demo with our team. We'll guide you step by step.