E-invoicing for SAP, connected to the service provider you choose.
Pranix and our technology partner iMach Technologies connect SAP S/4HANA and SAP ECC to any accredited service provider (ASP) for the UAE and Oman e-invoicing mandates. Your invoices leave SAP at the right moment, in the right format, and every status comes back into SAP.
Two countries, one integration approach.
United Arab Emirates
FTA · PINT AE- 30 Oct 2026
Phase 1 businesses (revenue ≥ AED 50m) must appoint an ASP
- 1 Jan 2027
Phase 1 go-live: revenue ≥ AED 50m
- 31 Mar 2027
Phase 2 and government entities appoint an ASP
- 1 Jul 2027
Phase 2 go-live (revenue below AED 50m) and government entities
- In scope
- B2B and B2G supplies, including zero-rated exports and exempt supplies. B2C is out of scope for now.
- Format
- Peppol PINT AE (UBL 2.1 XML), with 51 mandatory data fields to source from SAP
- Model
- Decentralised Peppol five-corner model. Invoices go through accredited ASPs, not directly to the FTA.
- Providers
- 54 Ministry of Finance accredited ASPs and 8 pre-approved ASPs (as of 17 Sep 2026)
Oman
OTA · FAWTARAThe Oman Tax Authority's Fawtara programme uses the same five-corner model, with invoices exchanged through accredited service providers in the Peppol PINT OM format. The rollout is phased, starting with selected large taxpayers in 2026, with more businesses following under the OTA's published timeline.
The same SAP integration layer serves both countries, so groups that operate in the UAE and Oman build it once.
Who talks to whom.
Your SAP system is corner 1. We build the connection from corner 1 to your ASP, and from your ASP back into SAP.
What SAP must do, what the ASP does, and the layer in between.
The integration layer runs on iConnect, iMach's SAP integration platform. It works with any ASP, so you can choose or change provider without rebuilding SAP.
Your SAP system
- Hold correct master data: TRN, TIN, Peppol ID, legal registration and structured address
- Decide the tax treatment and derive the 8 UAE transaction flags
- Create the e-document at the right moment and send it
- Block changes or cancellation once transmitted, and force credit notes
- Store the ASP status and reference against the SAP document
- Archive the invoice and status evidence
Built by Pranix and iMach
- Map SAP data to the ASP payload (JSON or PINT XML)
- Authenticate (OAuth2, API key or mTLS) and call the ASP
- Retry technical failures safely without duplicate invoices
- Receive webhooks or poll status, and update SAP
- Route inbound invoices into SAP (IDoc, eDocument or VIM)
- Monitor and alert
Your service provider
- Validate against the PINT schema and Schematron rules
- Look up the buyer on the Peppol SMP and deliver via AS4
- Report the tax data document to the tax authority
- Return message-level and tax authority status
- Receive inbound invoices on your Peppol ID
- Host data locally, retain records and register your Peppol participant ID
We fit the pattern to your SAP landscape.
E-documents are created when SAP billing or FI documents post to accounting, then sent asynchronously. ASP APIs differ in payload format, status updates, inbound delivery and SAP connectors, so we test against your ASP's sandbox before go-live.
SAP DRC
SAP Document and Reporting Compliance, using the standard eDocument cockpit
SAP Integration Suite
Cloud integration on SAP BTP between SAP and the ASP
ABAP connectors
Direct API calls from SAP for landscapes without middleware
IDoc / middleware
Reuse of existing IDoc output and middleware for SAP ECC
Every ASP status lands back in SAP.
| ASP status | SAP eDocument status | What SAP does |
|---|---|---|
| Accepted for processing | Sent / waiting | Store the ASP document ID against the billing or FI document and lock it |
| Validation failed | Rejected, correctable | Fix master data or mapping and resubmit the same invoice number |
| Delivered to buyer's ASP | Accepted / delivered | Invoice legally exchanged; release a PDF copy to the customer if used |
| Transmission failed | Error, resend | Retry or correct; escalate if the buyer is not on Peppol |
| Tax data reported | Completed | Close monitoring; archive the XML and status evidence |
| Business rejection by buyer | Completed, with note | Treat as a commercial dispute and issue a credit note; never cancel |
From assessment to a scalable integration.
Assess
Understand your current SAP invoicing landscape, master data and gaps.
Connect
Integrate SAP with the e-invoicing provider you choose.
Transform
Map and exchange structured invoice data in the PINT format.
Automate
Streamline invoice workflows and response handling in SAP.
Scale
Reuse the integration for new entities, countries and processes.
UAE penalties under Cabinet Decision 106/2025.
For not implementing e-invoicing or not appointing an ASP on time
For each invoice or credit note not issued electronically, capped at AED 5,000 per month
For not notifying the FTA of a system failure within 2 business days
Delivered with iMach Technologies.
iMach Technologies helps businesses accelerate digital transformation through SAP solutions, enterprise integration and technology services. Its iConnect platform connects SAP and enterprise applications through API-based data exchange.
- SAP SD, FI and billing process design for the e-invoicing flow
- Master data readiness and tax treatment design
- Testing, cutover and go-live support
Not sure if your SAP is ready for e-invoicing?
We review your SAP version, invoicing flow, master data and ASP options, and give you a clear plan for go-live.