# How to connect SAP to UAE e-invoicing the right way > SAP e-invoicing UAE guide covering Peppol connection, PINT AE mapping, deadlines, and integration steps for SAP ECC, S/4HANA, and Business One. Source: https://einvoicedirect.ae/e-invoicing-uae/sap-e-invoicing-uae Last updated: 2026-06-05 Publisher: EInvoice Direct (Massive FZCO), UAE e-invoicing software. ## What is SAP e-invoicing in the UAE? SAP e-invoicing UAE refers to connecting an SAP system, such as S/4HANA, ECC, or Business One, to the UAE's Peppol 5-corner network through an accredited service provider. Outbound invoices are converted to PINT AE format, exchanged between providers, and reported to the Federal Tax Authority (FTA) in near real time. ## Why SAP customers need to act before 2027 The UAE Ministry of Finance (MoF) has confirmed the Decentralized Continuous Transaction Control and Exchange (DCTCE) model. Every taxable business will route invoices through an Accredited Service Provider (ASP) instead of sending PDFs by email. For SAP customers, this is a finance and IT project. Invoice data from sales, billing, and accounts receivable modules must leave SAP in a structured format, reach the buyer's ASP through Peppol, and be reported to the FTA at the same time. Manual exports or PDF prints will not satisfy the mandate. The cluster overview on [E-Invoicing UAE](https://einvoicedirect.ae/e-invoicing-uae) explains the wider framework. This page focuses on what SAP teams specifically need to plan, build, and test. ### Key dates SAP teams should plan against | Milestone | Date | Who it affects | | --- | --- | --- | | Pilot phase | Q2 2026 | Volunteer large taxpayers | | ASP appointment deadline | October 30, 2026 | Businesses with revenue AED 50M and above | | Phase 1 mandatory go-live | January 1, 2027 | Large taxpayers (AED 50M+) | | SME go-live | July 1, 2027 | Businesses under AED 50M revenue | | Government entities | October 1, 2027 | Federal and local government | If you run SAP and report more than AED 50M in revenue, you have a hard internal deadline well before January 2027 because user acceptance testing, master data cleanup, and Peppol onboarding all need time. ## How SAP fits into the UAE Peppol 5-corner model The UAE model has five corners: - Corner 1: the seller's accounting or Enterprise Resource Planning (ERP) system, such as SAP. - Corner 2: the seller's ASP, which validates and signs the invoice. - Corner 3: the buyer's ASP, which receives the invoice through Peppol. - Corner 4: the buyer's ERP or accounting system. - Corner 5: the FTA, which receives a tax data report from both ASPs. SAP sits at Corner 1 on the sales side and Corner 4 on the purchase side. SAP does not connect directly to the FTA. The ASP handles Peppol transport, PINT AE validation, digital signing, and FTA reporting. ### What changes inside SAP Three SAP areas usually need work: - Master data: customer and supplier records need Tax Registration Numbers (TRNs), correct legal names, and Peppol participant identifiers where available. - Output management: the billing output type needs a new channel that produces a structured file or calls an Application Programming Interface (API). - Document mapping: SAP invoice fields must map cleanly to PINT AE, the UAE Peppol International invoice specification. ## SAP product variants and what each one needs The integration approach depends on which SAP product you run. The data model is similar across them, but the technical hooks differ. ### SAP S/4HANA (on-premise and private cloud) S/4HANA supports the eDocument Framework, which generates structured invoice files from billing documents. Customers typically build or buy a connector that takes the eDocument output, transforms it to PINT AE, and posts it to the ASP through an API. The FI-CA, SD, and FI modules are the usual sources. ### SAP S/4HANA Cloud (public edition) The public cloud edition has tighter extensibility rules. Integration usually goes through SAP Business Technology Platform (BTP) using prebuilt integration packages, or through the Document and Reporting Compliance service. The ASP receives data through a standard API call from BTP. ### SAP ECC 6.0 Many UAE businesses still run ECC. Integration is feasible but needs middleware or a custom IDoc to PINT AE transformer. ECC will not receive Peppol updates from SAP indefinitely, so plan accordingly. Most teams use SAP Process Integration (PI/PO) or a lightweight middleware layer to bridge ECC and the ASP. ### SAP Business One Business One is common in mid-market UAE companies. Integration uses the Service Layer API or DI API to push invoice data to the ASP. Add-ons or direct API calls are both workable. ## Mapping SAP invoice fields to PINT AE PINT AE is the UAE profile of the Peppol International Invoice. The mandatory fields are well defined, and most map directly from standard SAP tables. | PINT AE field | Typical SAP source | Notes | | --- | --- | --- | | Seller TRN | Company code tax number (T001Z) | 15-digit UAE TRN | | Buyer TRN | Customer master (KNA1, KNAS) | Required for B2B | | Invoice number | VBRK-VBELN | Unique per legal entity | | Issue date | VBRK-FKDAT | Must match the tax point | | Currency | VBRK-WAERK | AED for domestic supplies | | Line item description | VBRP-ARKTX | Plain text | | Unit price and quantity | VBRP-NETWR, VBRP-FKIMG | Net of VAT | | VAT rate and amount | Condition tables (KONV) | 5%, 0%, or exempt | | Payment terms | VBKD-ZTERM | Optional but recommended | Credit notes, debit notes, self-billed invoices, and simplified invoices each have their own document type codes in PINT AE. Your mapping must handle all of them. ## Three integration patterns for SAP and an ASP SAP customers in the UAE generally choose one of three patterns. The right one depends on volume, IT capability, and how clean the SAP data already is. ### Pattern 1: Direct API from SAP to the ASP SAP calls the ASP's REST API at the moment a billing document is released. This is the cleanest option for S/4HANA and Business One. Latency is low, status flows back quickly, and there is no middleware to maintain. ### Pattern 2: Middleware in between SAP sends an IDoc or XML file to middleware (SAP BTP Integration Suite, SAP PI/PO, or a third party). The middleware transforms to PINT AE and forwards to the ASP. This suits ECC, complex landscapes, or businesses with multiple ERPs feeding one ASP. ### Pattern 3: File-based batch SAP exports a daily file that the ASP picks up. This is the simplest, but it does not match the spirit of continuous transaction controls. Use it only as a fallback or for very low volumes. ## A realistic SAP UAE e-invoicing project plan A typical SAP implementation runs 4 to 6 months. Compressing it below 3 months usually means skipping testing, which causes rejected invoices in production. ### Month 1: scoping and master data - Pick the SAP entities in scope and confirm financial year ends. - Audit customer and supplier master data for TRNs and addresses. - List all invoice scenarios: standard, credit note, multi-currency, reverse charge, designated zone, free zone. ### Month 2: ASP selection and design - Choose an ASP from the Ministry of Finance's published ASP list. - Agree the integration pattern and authentication method. - Design the field mapping and exception handling. ### Month 3 to 4: build and unit test - Develop the SAP output type, eDocument configuration, or BTP iFlow. - Build retry logic for ASP outages. - Unit test every invoice scenario in a sandbox. ### Month 5: end-to-end testing - Run pilot invoices through the ASP test environment. - Validate PINT AE output against the official schema. - Confirm FTA reporting acknowledgements. ### Month 6: cutover and hypercare - Switch production output to live mode on the go-live date. - Monitor rejections daily for the first month. - Train AR and AP teams on exception handling. The [UAE E Invoicing Implementation](https://einvoicedirect.ae/e-invoicing-uae/uae-e-invoicing-implementation) guide expands on each phase, and the [UAE E Invoicing Go Live](https://einvoicedirect.ae/e-invoicing-uae/uae-e-invoicing-go-live) checklist covers the final cutover. ## Common SAP gotchas in UAE e-invoicing ### Customer master TRNs are missing or wrong This is the single biggest cause of invoice rejection. TRNs must be the full 15-digit number, not partial. Run a data cleanup before integration testing. ### Free zone and designated zone supplies The VAT treatment differs between regular free zones and designated zones. SAP needs the correct tax codes and place of supply rules so that PINT AE shows the right VAT category code. ### Multi-currency invoices Foreign currency invoices must include the AED equivalent and the exchange rate used. The exchange rate source should match the FTA's accepted sources. ### Document numbering Invoice numbers must be unique and sequential within a legal entity. If you reset SAP number ranges annually, confirm the ASP accepts the format. ### Cancellations and reversals You cannot delete a reported invoice. Cancellations go through credit notes that reference the original. SAP's VF11 reversal must trigger a proper credit note flow. ## Costs and licensing considerations SAP customers usually budget for four cost categories: ASP fees, internal SAP development effort, middleware licenses if used, and ongoing support. Penalties under Cabinet Decision 106 of 2025 range from AED 2,500 to AED 50,000 per violation, which makes the business case for proper testing straightforward. Cross-check your readiness on the [ERP Integration E Invoicing UAE](https://einvoicedirect.ae/e-invoicing-uae/erp-integration-e-invoicing-uae) page if you run SAP alongside other systems. Teams comparing platforms can also review [Oracle E Invoicing UAE](https://einvoicedirect.ae/e-invoicing-uae/oracle-e-invoicing-uae) and [Tally E Invoicing UAE](https://einvoicedirect.ae/e-invoicing-uae/tally-e-invoicing-uae) for parallel guidance. ## Regulatory references for SAP teams Three official sources cover the bulk of what SAP teams need: - [UAE Ministry of Finance](https://mof.gov.ae) for policy and the accredited ASP list. - [MoF e-invoicing portal](https://einvoicing.mof.gov.ae) for the PINT AE specification and updates. - [Federal Tax Authority](https://tax.gov.ae) for VAT and corporate tax rules that the invoice data must reflect. The legal basis sits in Federal Decree-Law 16 of 2024, Federal Decree-Law 17 of 2024, and Ministerial Decisions 243 and 244 of 2025. Penalty amounts come from Cabinet Decision 106 of 2025. ## Where to go next If your SAP landscape is complex, start with master data and integration design well before the October 30, 2026 ASP appointment deadline. The [UAE E Invoicing Onboarding](https://einvoicedirect.ae/e-invoicing-uae/uae-e-invoicing-onboarding-process) walkthrough shows the order of activities, and the [E-Invoicing UAE](https://einvoicedirect.ae/e-invoicing-uae) hub covers the broader regulatory picture. EInvoice Direct connects SAP S/4HANA, ECC, and Business One to the UAE Peppol network. An accredited service provider is included with the software at no extra charge, so you do not need a separate ASP contract. To plan timelines, mapping work, and pricing for your SAP entities, [get UAE e-invoicing pricing](https://einvoicedirect.ae/for-businesses#contact). ## Frequently asked questions ### Does SAP have built-in UAE e-invoicing? SAP provides frameworks like eDocument Compliance and Document and Reporting Compliance, but these do not connect to the UAE Peppol network on their own. You still need an Accredited Service Provider (ASP) to handle PINT AE validation, Peppol transport, and Federal Tax Authority (FTA) reporting. The ASP integrates with SAP through an API or middleware. ### Can SAP ECC 6.0 be used for UAE e-invoicing in 2027? Yes, SAP ECC 6.0 can comply with UAE e-invoicing in 2027 through middleware or a custom connector that transforms IDocs or XML output into PINT AE format. SAP PI/PO or a lightweight integration layer typically sits between ECC and the ASP. Plan extra testing time because ECC will not get new compliance content from SAP indefinitely. ### What is PINT AE and how does it relate to SAP? PINT AE is the UAE country profile of the Peppol International Invoice. It defines the mandatory fields, code lists, and validation rules for UAE e-invoices. SAP must produce output that maps to PINT AE, either natively through the eDocument Framework or by transformation in middleware. The ASP validates the final file against the PINT AE schema. ### How long does a SAP UAE e-invoicing project take? A typical SAP UAE e-invoicing project runs 4 to 6 months. The phases cover scoping, master data cleanup, ASP selection, build, end-to-end testing, and hypercare. Larger SAP landscapes with multiple legal entities, free zone entities, and high invoice volumes can run longer. Starting before mid-2026 gives Phase 1 taxpayers a safety buffer before January 2027. ### Do I need separate connectors for S/4HANA and Business One? Usually yes, because the integration mechanisms differ. S/4HANA uses the eDocument Framework or SAP Business Technology Platform (BTP), while Business One uses the Service Layer or DI API. A good ASP supports both with prebuilt connectors so the underlying PINT AE output and Peppol transport stay consistent across your SAP estate. ### What happens if my SAP invoice fails PINT AE validation? The ASP rejects the invoice before it reaches the buyer or the FTA, and SAP receives an error status. The AR team must fix the data, usually a missing TRN, wrong VAT code, or invalid date, and resubmit. Good integration design surfaces these errors inside SAP so users can correct and reissue without leaving their normal workflow. ### Are SAP customers exempt from the October 30, 2026 deadline? No. The October 30, 2026 deadline to appoint an Accredited Service Provider applies to all UAE businesses with revenue of AED 50 million or more, regardless of which ERP they use. SAP customers above this threshold must appoint an ASP and be ready for the January 1, 2027 mandatory go-live. SMEs follow on July 1, 2027. --- This content is informational and is not tax, legal, or financial advice. For UAE e-invoicing pricing, see https://einvoicedirect.ae/for-businesses#contact