SAP ERP Integration · Oman · Saudi Arabia · UAE

SAP across the Gulf.

SAP covers Saudi Arabia and the UAE well — through two entirely different pipes that groups routinely mistake for one. For Oman it covers nothing: Fawtara is now law — Decision 189/2026 sets 1 April 2027 for annual supplies above OMR 5 million and 1 October 2027 for everyone else, with a voluntary pilot from end-August 2026 — and SAP has published no Oman e-invoicing task, no note, no component, no date. This page is about running a multi-country GCC programme against that reality.

Oman: none No Oman e-invoicing task in any SAP coverage list — ECC, S/4HANA, Cloud or DRC
2 pipes KSA runs through SAP Integration Suite; the UAE through DRC cloud edition on BTP
2027 End of mainstream maintenance for Business Suite 7 — extended to 2030 at a premium
ECC works Both KSA and UAE are documented on SAP ERP — the constraint is the clock, not capability
The Oman gap

SAP has not shipped Fawtara, and the dates are now law.

We checked four separate SAP-published coverage lists — SAP ERP, S/4HANA on-premise, S/4HANA Cloud public edition, and Document and Reporting Compliance cloud edition. Oman appears as an e-invoicing task in none of them. There is no Oman component code, no implementation note, and no published delivery date.

What SAP does ship for Oman is statutory reporting: a VAT return, a withholding tax declaration and a cash flow statement. All three are generally available — and all three are marked manual filing. That is useful, and it is not electronic exchange.

The only statement of intent we found is a sentence in an SAP-authored community blog from September 2025 saying SAP plans to deliver an Oman e-invoicing solution as part of continuous localisation, with no release and no date attached. A blog sentence is not a delivery commitment, and we would not build a programme plan on it. There is also an older SAP blog on Oman still carrying a superseded 2024–2025 timeline; treat it as stale.

None of this is a criticism. Oman's legal basis arrived only on 9 August 2026 (Decision 189/2026 amending the VAT Executive Regulations) and PINT OM reached version 1.0.0 only in June 2026. But if you are among the 100 companies in the voluntary pilot, or above the OMR 5 million annual-supplies line with a 1 April 2027 date, the practical position is that your ERP vendor is not going to close this for you in time, and the gap has to be closed at the integration layer.

SAP's GCC position, by country
  • Oman — statutory reporting only (VAT, WHT, cash flow), all manual filing. No e-invoicing anywhere
  • Saudi Arabia — generally available on ECC, S/4HANA on-premise and S/4HANA Cloud, split into Generation and Integration tasks
  • UAE — generally available on ECC, S/4HANA, S/4HANA Cloud and Ariba, with PINT AE schematron maintained into July 2026
  • Watch the version — SAP's coverage tables are per product and per release, and they do not all agree. Pin the one matching your stack

Full Fawtara timeline and obligations →

The expensive misconception

Saudi and the UAE do not share a pipe.

KSA

Integration Suite, direct to ZATCA

SAP splits Saudi into two compliance tasks — Generation for Phase 1 and Integration for Phase 2 — and documents submission through SAP Integration Suite.

  • Available on ECC, S/4HANA on-premise and S/4HANA Cloud public edition
  • SAP ships certificate onboarding reports that request the stamp identifier from ZATCA directly
  • Submission runs from the eDocument Cockpit through an ABAP proxy to Integration Suite
  • Self-billing is covered as its own Generation and Integration pair
UAE

DRC cloud edition, on BTP

An entirely different route. The UAE runs through Document and Reporting Compliance cloud edition, which is a subscription on SAP Business Technology Platform.

  • Requires an enterprise global account on SAP BTP — a separate commercial and technical footprint
  • Covers outbound and inbound documents, across ECC, S/4HANA, S/4HANA Cloud and Ariba
  • For ECC the connection is made through Cloud Connector, not Integration Suite
  • SAP documents this Peppol exchange as acting as an access point in the Peppol network
Consequence

A group needs both

This is where multi-country programmes lose time and money. The two are not alternatives and one does not substitute for the other.

  • Two subscriptions, two tenants, two sets of skills, two cost lines
  • Different components and different implementation notes per country
  • Oman, having neither, needs a third answer at the integration layer
  • Budget and resource them separately — a single "SAP e-invoicing" line item will be wrong
Naming

DRC is not ACR renamed

A trap that bites during activation. Document and Reporting Compliance merged two previously separate licensed products, and the legacy paths are mutually exclusive.

  • The DRC licence replaced the former separate licences for Document Compliance and Advanced Compliance Reporting
  • Activating the DRC business function means you can no longer use the legacy Document Compliance features
  • The same warning applies in reverse for legacy statutory reporting
  • If no countries are entered in the activation view, the features silently do not enable
ECC and S/4HANA

ECC can do this. The question is for how long.

A persistent myth says GCC e-invoicing forces an S/4HANA move. It does not. SAP documents both Saudi Arabia and the UAE as available on SAP ERP, with the same components and notes as the S/4HANA path.

What is real is the clock, and the two dates in circulation are both correct because they describe different things. Mainstream maintenance for Business Suite 7 core applications runs to the end of 2027. That is followed by optional extended maintenance to the end of 2030, at a premium of two percentage points on the maintenance basis, available for three years from the start of 2028. After that, customer-specific maintenance. For contrast, SAP has committed to innovation for S/4HANA to 2040.

So the sequencing question is genuine and it is about collision, not capability. A group facing Oman's 1 April 2027 date, a UAE go-live in January 2027, and an ECC maintenance decision in 2027 has three deadlines inside eighteen months. Doing the migration and the mandates as one programme is how organisations end up doing neither well.

Our usual counsel: bridge the mandate on the platform you have, deliberately and with the lightest compliant build, and let the S/4HANA decision be made on its own merits and its own timeline. Compliance deadlines are a terrible reason to choose a target architecture.

Documented limits worth knowing
  • Peppol document size — 100 MB per document including attachments, with up to 200 attachments, outbound and inbound
  • Activation is exclusive — turning on DRC disables the legacy Document Compliance features
  • Silent no-op — features do not enable unless countries are entered in the activation view
  • KSA certificate lifecycle — deactivating a stamp identifier at the tax portal must be mirrored in SAP
  • Release specifics — minimum support-package levels live in SAP's implementation notes, which are login-gated. Ask for them by number rather than accepting a summary
Groups

Multi-company-code, multi-registration, three countries.

This is the shape of almost every SAP client we meet in the Gulf, and it is the part SAP documents least. Country activation in DRC is multi-select, so Oman reporting, Saudi and the UAE can all be switched on in one system. What SAP does not publish is a design guide for a group running several tax registrations across those three regimes at once.

That absence matters, because the hard problems are all at that level: which company code issues under which registration, how the Saudi per-unit certificate model maps to your entity structure, where the UAE participant identifier comes from for each entity, and what happens to a shared customer master when three authorities want three different things from it.

Our position is that this is a data and governance problem wearing an integration costume. The integration layer is the straightforward part. What decides your rejection rate is whether each entity's registration data, tax determination and counterparty identifiers are correct — and that work is identical whether the invoice ends up in Muscat, Riyadh or Dubai.

One honest ambiguity to flag rather than paper over: SAP's generic Integration Suite documentation says you also need to register with a service provider, while its Saudi-specific pages show SAP obtaining the stamp identifier from ZATCA and submitting to the tax authority with no intermediary. SAP publishes no clean statement resolving whether an accredited provider is required for Saudi. We would establish that with SAP and the authority for your specific configuration rather than assume either way.

Sequencing a three-country programme
  • Oman first if you are in the pilot or above the OMR 5m annual-supplies line (1 April 2027) — it has the least vendor support
  • Master data once — registrations, tax determination and counterparty identifiers serve all three
  • Two SAP footprints — plan Integration Suite and BTP separately, with separate owners
  • Bridge, do not migrate — keep the ECC decision off the mandate critical path
  • Test the regimes together — concurrent multi-country behaviour is the least documented area

Verified against SAP's published Help Portal documentation and maintenance strategy on 28 July 2026. SAP's UAE Ministry of Finance status was pre-approval pending final accreditation as at its April 2026 announcement. SAP notes are login-gated and were not read; they are cited by number.

Questions we actually get

Asked on most SAP discovery calls.

Does SAP support Oman Fawtara?

No. Oman does not appear as an e-invoicing compliance task in any of SAP's four published coverage lists. SAP ships Oman VAT return, withholding tax and cash flow statement reporting, all as manual filing. The only statement of intent is a sentence in an SAP community blog with no release or date. If a partner tells you SAP supports Oman e-invoicing, ask which coverage table it appears in.

We are live on ZATCA. Does that get us most of the way to the UAE?

Less than you would hope. The Saudi solution runs through SAP Integration Suite; the UAE runs through DRC cloud edition on BTP. Different components, different subscription, different connection method — for ECC the UAE path uses Cloud Connector rather than Integration Suite. What transfers is your master data and your team's understanding of what a mandate programme costs. The plumbing does not.

Do we need to be on S/4HANA?

Not for compliance. SAP documents both Saudi and the UAE on SAP ERP. You need to be on S/4HANA eventually for maintenance reasons — mainstream support for Business Suite 7 ends at the close of 2027, with optional extended maintenance to 2030 at a two-point premium — but that is a separate decision on a separate timeline. Let a mandate deadline drive the migration and you will make a ten-year architecture choice under six months of pressure.

Is SAP our access point, or do we still need one?

For the UAE Peppol leg, SAP documents that the DRC cloud edition Peppol exchange acts as an access point in the Peppol network — which genuinely differs from some other ERP vendors, who state plainly that they are not. You remain responsible for registering your company in the relevant networks and directories, and for your own regulatory compliance. For Oman, the question does not arise yet, because SAP has nothing there. For Saudi, SAP's own documentation is ambiguous and we would confirm it rather than assert it.

What is the most common thing that goes wrong?

Activation and scope, not code. Turning on DRC disables legacy Document Compliance features, which surprises estates mid-transition. Features silently fail to enable if countries are not entered in the activation view. And the coverage tables differ by product and release, so a team reads the S/4HANA Cloud list while running ECC and plans for a capability they do not have. None of these are hard to avoid — they are just easy to miss.

How should we budget a three-country GCC programme?

As three workstreams over one data foundation, not as one project. The drivers are the number of company codes and registrations, which SAP products are in scope, whether both Integration Suite and BTP footprints are needed, master-data condition, and how much has to be built for Oman where SAP offers nothing. We do not publish a rate card because those factors move the number more than a list price would. You get directional pricing on the first call and a written fixed-fee quote within 24 hours.

Other ERPs

We integrate on your ERP — we don't replace it.

Each mandate lands differently on each platform. These are the ones we implement most often in the GCC.

Oracle Dynamics 365 Zoho Tally Odoo

Mandate Monitor

Deadlines move. We will tell you when.

Short, source-checked notes when a GCC mandate actually changes — a wave announced, a specification revised, a date moved. Written by the people doing the implementations. No sequence, and you can leave in one click.

We use it to send mandate updates and nothing else. See our privacy policy.

Start with thirty minutes.

Tell us which SAP you run, how many company codes and registrations issue invoices, and which countries you file in. We will tell you what SAP covers, what it does not, where the Oman gap has to be closed, and what it will cost — with a written fixed-fee quote within 24 hours.

Book a consultation → Read the Oman Fawtara briefing Free · Senior practitioner · Quote in 24 hours