The short answer: an SAP landscape has three realistic ways to meet a Gulf e-invoicing mandate. You can use SAP Document and Reporting Compliance (SAP DRC), you can pair SAP with a certified middleware or service provider, or you can build the integration yourself. SAP DRC usually fits best when you run a supported SAP release and want one framework across countries. A provider fits best when the regulator requires one, or when your ERP release is old. A custom build fits only in narrow cases. This guide compares the three routes for Saudi Arabia (ZATCA) and the UAE (PINT AE), so you can pick a route before you pick a vendor.
What “e-invoicing in SAP” actually means
People use the phrase for several different jobs. First, your SAP system must create a structured invoice, usually XML, instead of a PDF. Next, something must send that invoice to a regulator, to a network, or to both. Finally, someone must monitor rejections and fix them.
The regulator decides how step two works. Saudi Arabia uses a direct model: ZATCA’s Fatoora platform clears standard invoices before they reach the buyer. According to ZATCA, Phase 1 started on 4 December 2021 and Phase 2 on 1 January 2023, and Phase 2 is rolling out in waves. The UAE uses a network model. SAP’s documentation describes it as a five-corner model: the supplier, the supplier’s access point, the buyer’s access point, the buyer and the tax authority. The Ministry of Finance (MoF) calls the Peppol exchange itself a four-corner model, and the two framings describe the same flow. SAP simply counts the tax authority as a fifth corner. In addition, the UAE sets up its mandate with Accredited Service Providers, which we cover below.
Direction matters too. Outbound invoices (sales) and inbound invoices (purchases) use different tools. We cover inbound later in this guide.
Route 1: SAP Document and Reporting Compliance
SAP DRC is SAP’s own answer. In SAP’s documentation for Saudi Arabia, you create electronic documents, such as customer and supplier invoices, and submit them to the tax authority. You configure this under Document and Reporting Compliance, in the country-specific settings. SAP documents a core-system version of DRC and a cloud edition. Coverage varies by product, release and country, so confirm which one applies to your landscape before you plan around it.
The same documentation shows how Saudi Phase 2 is switched on. For example, SAP’s S/4HANA Cloud Public documentation lets you maintain an effective date per company code, and the system moves from the generation process to the submission process on that date. Because the setting works per company code, you can switch legal entities one at a time.
For the UAE, SAP documents SAP Document and Reporting Compliance, cloud edition. It sends documents through the Peppol network and reports to the tax authority. Moreover, it can take invoices created in other systems, SAP or non-SAP, through an External Documents API, provided the invoices arrive as UBL 2.3 XML. Do not assume the editions split by country, though. SAP’s Architecture Center lists a Saudi e-invoicing mission, but confirm with SAP whether the cloud edition also covers Saudi Arabia for your landscape.
Strengths: one framework for several countries, e-document creation and submission from inside SAP, and a per-company-code effective date for Saudi Phase 2. For SAP ERP, SAP also delivers some localizations through SAP Notes. Limits: your release and support-package level must be recent enough. Therefore, ask SAP to confirm your exact release and scenario in writing.
Route 2: certified middleware or a service provider
In this route, a third party handles the regulator-facing work. Your SAP system sends invoice data to the provider, and the provider builds, signs, clears, delivers and archives the compliant document. Some providers also offer a portal for exceptions.
Whether this route is optional depends on the country. ZATCA states that taxpayers may choose any e-invoicing solution provider, as long as the solution meets its requirements. Its provider list is indicative, and ZATCA still treats a compliant taxpayer as compliant if the provider is not on the list. The UAE works differently. The Ministry of Finance guidelines require businesses in scope to appoint an Accredited Service Provider (ASP). Your supplier data goes to that ASP, which converts it into the UAE standard XML and transmits it.
Consequently, a UAE project always has an ASP in it. The real question there is whether SAP’s own service or another accredited provider fills that seat.
Strengths: fast start, regulator-facing expertise, and an option for old ERP releases. Limits: another contract and another interface to test, plus a dependency on the provider’s roadmap when rules change. Check the Ministry of Finance accreditation list for any UAE provider, and ask Saudi providers how they handle ZATCA onboarding and certificate renewal.
Route 3: a custom build
Technically, you can build the integration yourself. ZATCA allows any compliant solution, so a custom Saudi integration can pass. You would generate the XML, apply the cryptographic stamp, call the clearance and reporting interfaces, and handle every rejection.
In practice, this route rarely pays off. Specifications change, waves arrive on short notice, and every change lands on your own team. In the UAE, a custom build still needs an ASP, so you would only build the ERP-to-ASP mapping. That mapping can be worthwhile when your invoices come from non-standard sources. For a standard SAP billing flow, it duplicates work that SAP or a provider already maintains.
The three routes side by side
| Question | SAP DRC | Middleware or provider | Custom build |
|---|---|---|---|
| Who maintains format changes? | SAP delivers the framework; confirm the update path for your release | The provider | Your team |
| Saudi Arabia (ZATCA) | SAP documents a Saudi scenario; confirm your release and edition | Allowed if compliant | Allowed if compliant |
| UAE (PINT AE) | SAP documents a cloud-edition UAE scenario via Peppol; an ASP is still required | Required: an accredited ASP | Only the ERP-to-ASP mapping |
| Best fit | Supported releases, several countries | Old releases, or a provider mandate | Unusual invoice sources |
| Main risk | Release and support-package gaps | Extra contract and interface | Ongoing maintenance load |
How the Gulf mandates shape the choice
Two facts change the route choice. First, in Saudi Arabia a provider is optional, because ZATCA accepts any compliant solution. Second, in the UAE an ASP is always part of the design. Consequently, a group with entities in both countries needs one design that handles a clearance model and a network model together.
Deadlines and cohort dates move, so we keep them on the pages that own them. In addition, the UAE ASP appointment date for the largest cohort was 30 October (MD 66; the Guidelines table prints 31 October) and has now passed. Read our ZATCA Phase 2 guide and our ZATCA e-invoicing service page for Saudi Arabia. For the UAE, our PINT AE guide carries the dates, fields and format.
Choosing by landscape
- SAP S/4HANA Cloud public edition: start with SAP DRC. For example, SAP documents the Saudi setup, including the Phase 2 effective date, for this edition.
- SAP S/4HANA on premise: The SAP-delivered Saudi scope depends on your release, so confirm it with SAP before you compare SAP DRC with a provider on cost and effort. Likewise, for private cloud editions, ask SAP to confirm the scenario in writing.
- SAP ECC: SAP’s ERP documentation covers the Saudi setup, including the effective date, from specific support-package levels. However, ECC is a bridge, not a destination. Weigh the e-invoicing route against your ECC to S/4HANA decision before you invest.
- Mixed landscapes: if invoices originate in non-SAP systems, SAP’s External Documents API for the UAE or a provider can take them in. As a result, one SAP system need not own every invoice.
Where SAP’s documentation is silent on a release or country scenario, treat the gap as a question for SAP. Above all, do not treat it as a yes.
Inbound e-invoices in brief
Receiving invoices is a separate workstream. For the UAE, SAP’s cloud edition documentation lists a Peppol Exchange process that receives supplier invoices from the Peppol network, through SAP Business Network on BTP or Next-Gen SAP Ariba Invoicing. It works only when both buyer and supplier are registered on the network. Plan your accounts payable flow early, because suppliers will start sending structured invoices before your team expects them.
Questions to put to SAP and every provider
- Which exact release and support package does your Saudi and UAE scenario require for our system?
- Who owns a format change, and how fast does it reach production?
- How do we monitor and correct a rejected invoice?
- Which entities and countries does the price cover?
- For the UAE, is the provider on the Ministry of Finance accredited list today?
- What happens to our archive if we leave?
Get the answers in writing. Then, test them in a sandbox with your own invoice data before you sign.
Frequently asked questions
Does SAP have a built-in e-invoicing solution?
Yes. In short, SAP Document and Reporting Compliance is SAP’s framework for electronic documents and statutory reporting. Its coverage depends on your product, release and country, so verify your scenario with SAP.
Do I need a third-party provider for ZATCA?
No, not automatically. ZATCA allows any solution that meets its requirements. Instead, your release, timeline and in-house skills decide whether a provider helps.
Do I need a provider for the UAE?
Yes. The Ministry of Finance guidelines require an Accredited Service Provider for businesses in scope. After all, the ASP transmits your invoices and the tax data.
Can we build e-invoicing ourselves?
You can in Saudi Arabia if the solution is compliant, but you carry every future change. By contrast, in the UAE you still need an ASP.
Which route is fastest?
It depends on your starting point. A provider can start quickly. However, SAP DRC can be faster overall when your release already supports it and you add more countries later.
Next step
Altivate, an SAP Gold Partner, implements SAP Document and Reporting Compliance. Book a free SAP assessment and we will map your landscape, entities and deadlines to one of these routes.
