The UAE Electronic Invoicing System reaches beyond domestic B2B transactions. Scenario 8 of the PINT-AE specification — Exports — makes clear that goods or services supplied to customers outside the UAE are within scope. For UAE businesses that export to GCC markets, to buyers in Europe, to Indian counterparties, or to customers across the broader global trading network, the compliance obligation extends to every cross-border B2B supply from the Phase 1 go-live date of 1 January 2027.

The technical handling of these transactions differs depending on whether the overseas buyer is a Peppol-registered entity or not. Understanding this distinction — and building it into ERP and routing configuration before go-live — is one of the more technically specific preparation tasks for UAE exporters.

Why Exports Are Within the Electronic Invoicing Scope

MD 243 of 2025 applies to any person conducting business in the UAE in respect of every business transaction, subject to the exclusions in Article 4. Exports of goods and services are not excluded. The UAE VAT Decree-Law treats qualifying exports of goods and services as zero-rated supplies — a VAT treatment that does not affect the Electronic Invoicing obligation. A zero-rated export requires an Electronic Tax Invoice in exactly the same way as a standard-rated domestic B2B supply.

This means UAE businesses that currently issue PDF or paper invoices for cross-border supplies must transition those invoices to PINT-AE compliant electronic format from their mandatory go-live date. The export destination does not affect the UAE supplier's issuance obligation.

The Peppol Participation Question: Two Routing Paths

Where the Overseas Buyer Has a Peppol Participant Identifier

The UAE Electronic Invoicing System operates on the Peppol network — a global interoperability framework used in dozens of jurisdictions including Singapore, Australia, the EU, Japan, and increasingly across the GCC and wider Middle East. An overseas buyer registered on the Peppol network — for example, a Singapore-based entity participating in InvoiceNow, or an EU buyer in a Peppol-enabled jurisdiction — has a globally recognised Participant Identifier.

Where that identifier exists, the UAE supplier's ASP routes the electronic invoice across the Peppol network to the overseas buyer's access point (Corner 4). This is one of the architectural advantages of building UAE electronic invoicing on the Peppol network — it creates interoperability with other Peppol-enabled jurisdictions without requiring bilateral technical agreements.

Where the Overseas Buyer Has No Peppol Registration

Where the overseas buyer does not have a Peppol Participant Identifier — and the majority of UAE export counterparties will fall into this category in the near term — the supplier must use the predefined endpoint 0235:9900000099 on the electronic invoice. This predefined endpoint signals to the ASP that the buyer is an overseas party without Peppol registration. The electronic invoice is transmitted and reported to Corner 5 through the supplier's ASP, but there is no exchange with a receiving ASP on the buyer's side.

The practical implication is that the supplier's obligation to transmit the electronic invoice is fulfilled through the predefined endpoint routing. The overseas buyer continues to receive the invoice through whatever channel is agreed commercially — PDF, EDI, or other format. The UAE supplier must generate and transmit the PINT-AE compliant XML document regardless of what format the overseas buyer expects to receive.

This creates a dual-format obligation for many UAE exporters: the system-transmitted PINT-AE XML document for regulatory compliance, and the commercially agreed format for the buyer relationship. The AR workflow must accommodate both without the PINT-AE version being delayed waiting for the commercial format to be finalised.

Free Trade Zone Supplies and the Cross-Border Dimension

Scenario 1 in the UAE E-Invoicing Guidelines — Free Trade Zone supplies — interacts with the export scenario where a supply involves a Free Trade Zone entity or the supply itself takes place within or from a Free Zone. The FTZ transaction flag must be set in the electronic invoice. For FTZ suppliers making cross-border supplies, the electronic invoice carries both the FTZ flag (Scenario 1) and the Export scenario flag (Scenario 8).

The PINT-AE specification permits multi-scenario combinations, and where the transaction triggers more than one scenario, all applicable scenario flags and their specific field requirements must be included. Customs reference numbers (BTAE-21) and Incoterms (BTAE-22) are mandatory fields for export transactions — fields that must be available in the source system and mappable to the PINT-AE XML at the point of invoice generation.

Customs and Export Documentation

The UAE E-Invoicing Guidelines V1.1 note that for exports, the Tax Invoice for VAT purposes should be issued as an Electronic Invoice and the same may be provided to Customs. This signals a potential alignment path between the electronic Tax Invoice and the export customs documentation. For compliance programme planning, the primary obligation is the PINT-AE electronic invoice transmission; the Customs alignment is a downstream benefit.

B2C Export Supplies

Business-to-consumer transactions are excluded from the Electronic Invoicing System under MD 244 Article 5(2) until a future ministerial decision brings them into scope. UAE businesses making B2C export sales — direct-to-consumer e-commerce dispatched to GCC, European, or Indian end customers — are not required to issue Electronic Invoices for those transactions. The export B2B transactions of the same business remain within scope.

Practitioner Insight: The most common error I see in cross-border transaction mapping work is treating the export scope as narrower than it is. Businesses assume that because the overseas buyer is outside the UAE tax perimeter, the UAE supplier's e-invoicing obligation does not apply. That assumption is incorrect. The obligation sits with the UAE supplier, in the UAE, at the point of invoice issuance. The destination of the supply is relevant to the VAT rate — zero-rated exports — but irrelevant to the e-invoicing format and transmission requirement.

What UAE Exporters Must Prepare Before Go-Live

The cross-border preparation checklist for UAE exporters covers several distinct areas. First, every export customer must be assessed for Peppol Participant Identifier status. This requires a customer data enrichment programme that goes beyond existing master data — UAE businesses currently hold commercial and banking data for overseas buyers, but Peppol identifier data is an entirely new category requiring proactive outreach and registration tracking.

Second, the ERP and billing system must be configured to route export invoices to the correct predefined endpoint where the buyer has no Peppol registration, and to the buyer's Peppol identifier where one exists. Third, the mandatory BTAE extension fields for export transactions — customs reference number (BTAE-21) and Incoterms code (BTAE-22) — must be available in the source system and properly mapped to the PINT-AE XML structure.

Fourth, the commercial invoice workflow for overseas buyers must be preserved alongside the PINT-AE electronic transmission. For UK, EU, and Indian counterparties that receive UAE invoices as part of their own AP processes, the commercial invoice they receive after 1 January 2027 may look identical to what they received before — but behind it, a PINT-AE XML document is now being transmitted to the FTA on every transaction.