UAE e-invoicing for SAP Business One: deadlines, PINT AE and how to connect your ASP

By Zain Abbas, Kodenova · Updated 16 October 2026

Short answerUAE e-invoicing is mandatory for B2B and B2G invoices from 1 January 2027 for businesses with revenue of AED 50 million or more (ASP appointment by 30 October 2026), and from 1 July 2027 for everyone else (ASP appointment by 31 March 2027). Invoices go as PINT AE UBL XML over Peppol through an Accredited Service Provider. SAP Business One needs extra fields and an integration that sends each document to the ASP and stores the result.

The UAE is the third Gulf-style e-invoicing project many SAP Business One teams will meet, after ZATCA in Saudi Arabia. It looks similar from far away, but it works very differently. There is no QR code, no clearance by the authority and no device onboarding. Instead, every invoice travels over the Peppol network through a licensed middleman, the Accredited Service Provider (ASP).

This guide explains what changes, when, and what your SAP Business One or other ERP needs before go-live.

Who must go live, and when

The Ministry of Finance splits businesses by revenue. The dates below are the ones in force in October 2026; the ASP deadline for large businesses was moved once already, from 31 July to 30 October 2026.

Group	Appoint an ASP by	Mandatory from
Revenue AED 50 million or more	30 October 2026	1 January 2027
Revenue below AED 50 million	31 March 2027	1 July 2027
Government entities	31 March 2027	1 October 2027

The scope is B2B and B2G. B2C invoices are not included yet. Free zone companies and businesses that are not VAT registered can still be in scope, so do not assume you are out because of your licence type.

Not sure where you stand? The free UAE e-invoicing readiness checker shows your dates, the days left and a to-do list.

How the UAE model works

The UAE uses a decentralised five-corner model:

Corner 1: you, the seller, create the invoice in your ERP.
Corner 2: your ASP validates it and sends it over Peppol.
Corner 3: the buyer’s ASP receives it.
Corner 4: the buyer gets it in their own system.
Corner 5: the tax data is reported to the Federal Tax Authority (FTA).

So your ERP never talks to the FTA. It talks to your ASP, usually through a REST API. This is good news for SAP Business One users: the integration is one clean API, and the ASP takes care of Peppol delivery and reporting.

What PINT AE needs from your ERP

PINT AE is the UAE flavour of the Peppol International Invoice. It is UBL 2.1 XML, like ZATCA, but the fields are different. The main ones that SAP Business One does not hold out of the box:

CustomizationID urn:peppol:pint:billing-1@ae-1 and ProfileID urn:peppol:bis:billing.
Peppol endpoints for seller and buyer: scheme 0235 plus the 10-digit TIN. The TIN is the first 10 digits of the 15-digit TRN. Putting the full TRN here is one of the most common mistakes.
Transaction-type flags: an 8-digit string of 0s and 1s for free zone, deemed supply, profit margin scheme, summary invoice, continuous supply, disclosed agent billing, e-commerce and exports. A normal invoice is 00000000.
Tax categories: S (standard 5%), Z (zero-rated), E (exempt), O (out of scope) and AE (reverse charge). Every SAP B1 tax code must map to exactly one of them.
Tax amounts in AED: if you invoice in USD or EUR, the tax amounts must still be stated in AED.
Document types: 380 for a tax invoice, 381 for a tax credit note, and 480 or 81 for out-of-scope documents, which may only use categories E or O.
No negative invoices: a reversal must be a credit note that refers to the original invoice.

You can paste any XML into our free PINT AE invoice validator to see these checks in your browser before your ASP does.

What this means for SAP Business One

A practical SAP B1 project has five parts.

1. Master data. Add the TIN or Peppol ID to business partners and check every customer’s TRN. B2B invoices cannot be delivered without the buyer’s identifier, so this is often the slowest part, because it depends on your customers.

2. Tax codes. Map each SAP B1 tax code to S, Z, E, O or AE. Watch out for old codes that mix zero-rated and exempt supplies; they must be split.

3. Document fields. Add user-defined fields for the transaction-type flags and any reason codes for credit notes. Decide which marketing documents (A/R invoice, A/R credit memo, down payment invoice) must be sent.

4. Integration. A Windows service or Service Layer job reads new documents, builds the PINT AE XML or the ASP’s JSON, sends it, and writes the status and the ASP’s message ID back to the document. This is the same pattern we use for ZATCA in SAP Business One.

5. Rejections. When the ASP rejects a document, finance must see why and fix it in SAP B1, not in a log file. Plan a simple screen for rejected and pending documents before go-live.

If you use Odoo, Tally, Zoho, Dynamics or a custom ERP, the ASP side is the same. Only the data mapping changes.

Penalties if you are late

Cabinet Decision No. 106 of 2025 sets the fines:

AED 5,000 per month for not appointing an ASP or not implementing the system after your deadline.
AED 100 per e-invoice and AED 100 per e-credit note not issued in time, each capped at AED 5,000 per month.
AED 1,000 per day for telling the FTA late about a system failure, and the same for late updates of your registered data to your ASP.

A company that is three months late with a few hundred invoices a month can quickly reach AED 30,000 or more. Try your own numbers in the UAE e-invoicing penalty calculator.

A simple plan from today

This month: confirm your group and deadline, and shortlist two or three ASPs. Ask each one for its API documentation and its sandbox.
Next month: clean business partner data (TRN and TIN) and map tax codes.
Then: build and test the integration in the ASP sandbox with real invoices, credit notes and a few deliberate errors.
Two to four weeks before go-live: train the finance team on rejections and run a parallel test.
After go-live: watch rejections daily for the first month.

How Kodenova helps

We have built e-invoicing integrations for SAP Business One in Saudi Arabia (ZATCA), Ecuador (SRI), Guatemala and El Salvador. For the UAE we map your documents to PINT AE, connect SAP B1 or your ERP to the ASP you choose, and give you a screen for rejected invoices. See our UAE e-invoicing page or send us your ERP version and invoice volume for a fixed price.

Dates and penalties were checked on 16 October 2026. They have changed before, so always confirm on the Ministry of Finance e-invoicing portal.

Sources

Related services

FAQ

Frequently asked questions

When does UAE e-invoicing become mandatory?

On 1 January 2027 for businesses with revenue of AED 50 million or more, on 1 July 2027 for businesses below AED 50 million, and on 1 October 2027 for government entities. The ASP appointment deadlines are 30 October 2026 for the first group and 31 March 2027 for the others.

Can SAP Business One send e-invoices to the FTA directly?

No. In the UAE model nobody sends invoices straight to the FTA. Your ERP creates the invoice data, your Accredited Service Provider validates it, delivers it to the buyer's provider over Peppol and reports the tax data to the FTA.

What is the difference between TRN and TIN in UAE e-invoicing?

The TRN is your 15-digit VAT registration number. The TIN is its first 10 digits. The TIN, with scheme 0235, is your Peppol participant ID, for example 0235:1001234567.

Do UAE e-invoices need a QR code like ZATCA?

No. PINT AE has no QR code and no cryptographic stamp from the authority. Validation and delivery are done by the ASPs on the Peppol network.

What happens if we miss the deadline?

Cabinet Decision No. 106 of 2025 sets AED 5,000 for each month without an ASP or a working system, AED 100 per late e-invoice or credit note (capped at AED 5,000 per month) and AED 1,000 per day for late failure notices.

Ready to get started?

Tell us what you need. You get a clear technical answer, a fixed scope and a price, usually within 24 hours.

Start a project Chat on WhatsApp