Oman Fawtara E-Invoicing Latest Updates: 15 Key Questions Answered

1. Who needs to register on the Fawtara Portal, service providers, taxpayers, or both?

Both service providers and taxpayers register on the Fawtara Portal. This is an important point of clarity, because many businesses assume only accredited service providers would have a presence on the portal.

In practice, taxpayers do not go through a separate or new registration process. They access the Fawtara Portal using their existing Oman Tax Authority credentials, the same login they already use for other tax services. This keeps onboarding simple and avoids creating a duplicate identity for every business in the country.

For service providers, registration on the portal is part of the broader accreditation journey. If you are planning to offer an e-invoicing solution in Oman, expect to maintain an active presence on the Fawtara Portal both to manage your own status and to handle the taxpayers who connect to you.

2. What is the paid-up capital requirement to become a service provider in Oman?

The paid-up capital requirement to operate as an e-invoicing service provider in Oman has been reduced to 6,000 OMR, down from the previous 60,000 OMR.

This is a significant change. The earlier 60,000 OMR threshold was a meaningful barrier for smaller technology firms and regional players hoping to enter the Omani market. By lowering the requirement to 6,000 OMR, the Oman Tax Authority has effectively opened the door to a wider pool of service providers, which should increase competition and choice for taxpayers selecting a Fawtara-compliant solution.

If you previously ruled out becoming an accredited provider because of the capital requirement, it is worth revisiting your plans under the updated figure.

3. How long does the pre-approval process take after submission?

The pre-approval review is expected to take approximately two weeks from the date of submission, provided that all required information and supporting documents are complete and in order.

Two weeks is the working expectation, not a guaranteed service level, and the timeline depends heavily on the quality of your submission. Incomplete documentation, missing certificates, or unclear technical details will extend the review. To keep your Fawtara accreditation on track, prepare your application carefully, double-check every required field, and ensure all supporting documents are attached before you submit.

Building this two-week window into your go-to-market plan is sensible, especially if you are coordinating an e-invoicing launch around the broader Oman rollout schedule.

4. Is there a deadline to register as a service provider, and how do I get the pre-approved ASP list?

There is no specific registration deadline for becoming a service provider, and the pre-approved Application Service Provider (ASP) list is updated on a continuous basis rather than published as a one-time fixed roster.

Because the list is dynamic, the most reliable way to obtain the current pre-approved ASP list is to contact the Oman Tax Authority directly.

For businesses choosing an e-invoicing partner in Oman, this means you should treat any ASP list as a living document and verify a provider's status close to the time you make your decision.

5. Can a taxpayer be linked to more than one service provider?

No. Under the current Fawtara model, a taxpayer can be linked to only a single service provider at any given time.

This one-to-one relationship is enforced technically. The SMP API handles the validation, so if two different ASPs attempt to register the same taxpayer, the system resolves the conflict at the API level rather than allowing a duplicate or ambiguous link. In effect, the most recent valid registration governs the relationship, and the SMP ensures there is never more than one active service provider mapped to a taxpayer.

For service providers, this underlines the importance of confirming that a taxpayer is genuinely ready to move to your platform before initiating registration, since the link is exclusive.

6. After a service provider approves a taxpayer request, is SMP registration automatic?

No. Once a service provider approves a taxpayer's connection request, the SMP participant registration is not triggered automatically by the portal. The registration, performed as a REST PUT request, must be carried out manually by the service provider.

In the current version of the SMP API, each taxpayer is registered individually rather than in bulk. This has real operational implications for providers expecting to onboard a large number of taxpayers, because each one requires a discrete registration action. If you are building or selecting an e-invoicing system in Oman intended to scale, plan your internal workflows and tooling around individual, manual SMP registration for now, and watch for future API updates that may introduce automation or batch handling.

7. How are connection requests between taxpayers and service providers handled?

Connection requests between taxpayers and service providers are managed through the user interface on the Fawtara Portal.

When a taxpayer selects a service provider, the provider currently receives an email notification only. At this stage there is no API webhook or callback that alerts the provider's systems automatically, and the portal UI is the only mechanism available to approve a request. In other words, the approval step is a manual, human-in-the-loop action carried out through the portal screens rather than something that can be fully automated end to end today.

Service providers should therefore monitor notification emails closely and assign clear internal ownership for reviewing and approving incoming connection requests, so that taxpayers are not left waiting.

8. Is the taxpayer view active on the Fawtara Portal?

Not yet. The taxpayer view has not been activated on the Fawtara Portal at this stage.

This is a useful expectation-setter for businesses eager to log in and explore their e-invoicing dashboard. The functionality is coming, but the taxpayer-facing experience is still pending activation. If you are advising clients or planning internal training, factor in that the taxpayer view may only become available closer to the relevant rollout milestones, and keep an eye on official OTA communications for the activation date.

9. Which invoice types must be tested for accreditation?

For accreditation, the testbed tests random invoice types rather than a fixed, predetermined set.

This means a service provider cannot prepare narrowly for a known checklist of invoice types and assume that is sufficient. Because the testing draws on random invoice types, your e-invoicing solution needs to handle the full range of supported PINT OM document scenarios correctly and consistently. The practical takeaway is to build and validate against comprehensive coverage of invoice types before entering the Fawtara accreditation process, rather than optimizing for a narrow slice.

10. Are self-billing tests required for accreditation?

Yes. Self-billing tests are part of the Oman Test Suite, and passing them is a requirement for accreditation.

Self-billing, where the buyer rather than the seller generates the invoice on the seller's behalf, is a legitimate and common arrangement in many industries. Because the Oman Test Suite includes self-billing scenarios, service providers must ensure their solution correctly supports PINT OM self-billing flows end to end, including generation, validation, and reporting. If your platform does not yet handle self-billing, treat it as a mandatory capability rather than an optional one, since it directly affects whether you can achieve accreditation.

11. Is a QR code required for all B2C transactions, even during disconnection?

Yes. Suppliers are expected to generate a B2C QR code for all business-to-consumer transactions regardless of connection status, including during periods of disconnection.

This is a critical compliance point. The obligation to produce a compliant QR code on the consumer-facing invoice does not pause just because the supplier's system is temporarily offline or disconnected from the network. The QR code, which encodes key invoice data in a defined Tag-Length-Value (TLV) structure and is generated by the taxpayer, must be present on every B2C invoice. Service providers should design their e-invoicing software so that QR code generation works reliably even in offline or degraded-connectivity situations, ensuring continuous compliance for retail, hospitality, and other high-volume consumer-facing businesses.

12. Is the seller required to send the TDD in a B2B invoice case?

Yes. In a B2B invoice scenario, C3 is required to send the Tax Data Document (TDD) to C5.

The TDD is the mechanism by which transaction data is reported to the tax reporting layer, and this confirms that the obligation applies in the B2B context as well, not only B2C. For service providers building Peppol e-invoicing in Oman, this means your exchange and reporting logic must correctly generate and route the TDD to the appropriate party in B2B flows. Mapping out the C1 through C5 roles in your architecture and confirming where the TDD originates and where it must be delivered is essential to staying compliant.

13. Will the Oman Tax Authority regulate service provider pricing?

No. The Oman Tax Authority will not regulate service provider pricing. Standard Peppol specifications apply between service providers' access points, and commercial pricing is left to the market.

This is welcome news for both providers and customers. It means e-invoicing service providers in Oman are free to set their own pricing models, whether that is per-document, subscription-based, or tiered, and to differentiate on service, integration depth, and support. For businesses selecting a provider, it also means it is worth comparing offers, since pricing and packaging can vary meaningfully from one accredited provider to another. The OTA's role is to set the technical and compliance framework, not to dictate commercial terms.

14. Has the first rollout date for large taxpayers changed?

No. There are no changes to the planned first rollout date for large taxpayers at this stage.

The Oman Tax Authority confirmed that the implementation timeline for the initial phase, which targets large taxpayers, remains as planned. Any future updates to the rollout schedule will be communicated through official channels. For large enterprises preparing for mandatory e-invoicing in Oman, this is a signal to continue your readiness work on the current timeline rather than waiting for a delay. Selecting a provider, integrating your ERP or accounting system, and completing testing all take time, so the absence of any postponement reinforces the value of starting early.

15. In the SMP API spec, the endpoint reference shows test.smpserver/as4, is that the access point endpoint or the SMP endpoint?

The value test.smpserver/as4 shown in the SMP API specification is only an example, not a literal endpoint you should hard-code.

The endpoint reference points to your own access point, so the correct value depends on your specific setup. For the testbed environment, the relevant reference is test-smp-ext-api.taxoman.gov.om. If you have specific technical concerns about endpoints or configuration, the Oman Tax Authority recommends raising them by email so they can be reviewed in detail. The broader lesson for developers integrating with the SMP API in Oman is to treat sample values in the specification as illustrative placeholders and to confirm the exact endpoints for your environment before going live.

Final thoughts: preparing for Fawtara e-invoicing in Oman

The picture is becoming clearer. Oman's Fawtara e-invoicing framework is becoming more accessible and more defined with each update. The reduced paid-up capital requirement lowers the barrier for new service providers, the accreditation path through the Oman Test Suite is well specified, and the technical mechanics of registration, connection requests, and B2C QR codes are coming into sharper focus.

At the same time, several capabilities, including the taxpayer portal view and full API automation for connection requests, are still being rolled out. Businesses and service providers that prepare now, choose an accredited partner, build comprehensive invoice-type and self-billing support, and design for reliable QR code generation will be best positioned as mandatory e-invoicing in Oman takes hold.

Navigating Fawtara accreditation and compliance is easier with the right partner. To stay updated on the pre-approved ASP list, rollout timelines, and what these requirements mean for your business, stay connected with us at SMARTeIS Contact Us.