UAE eInvoicing cross-border trade: B2B exports, imports, non-resident trading partners, and predefined endpoints 0235:9900000098 and 0235:9900000099

Published 27 October 2026 · Ministerial Decisions 243/2025, 244/2025, 197/2026 and MoF Guidelines V1.1 read in official texts on 25 October 2026 · Other official sources last reviewed 22 October 2026 · 13 min read

When UAE businesses look at electronic invoicing, domestic transactions within the mainland are straightforward under the standard rules. However, operational reality involves significant cross-border trade: exporting goods and services to overseas customers, importing materials from foreign suppliers, trading with non-resident counterparties, handling reverse-charge supplies, and dealing with transactions where neither party has a standard local Peppol participant identifier. This guide examines how the UAE eInvoicing framework applies to cross-border transactions, how non-resident trading partners are identified, and how predefined endpoints such as 0235:9900000098 and 0235:9900000099 function in practice.

Our analysis is built strictly on verified primary sources: Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System, its amending Ministerial Decision No. 197 of 2026, Ministerial Decision No. 244 of 2025 on implementation timelines, and the UAE Electronic Invoicing Guidelines Version V 1.1 published by the Ministry of Finance. Where statutory texts do not provide explicit cross-border rules or leave mechanics to future technical bulletins, we explicitly mark those points as unconfirmed. This guide is designed for finance directors, tax leads, and system architects who need to design compliant cross-border billing workflows before go-live.

Decision 243/2025 Article 3 scope and cross-border transactions

The foundational scope of the UAE eInvoicing system is established by Ministerial Decision No. 243 of 2025, Article 3(a). This provision applies the system to any Person conducting Business in the State in respect of every Business Transaction, except where the Person or the Business Transaction is excluded under Article 4. Article 1 defines a Person as any natural or juridical person, and Business as any industrial, commercial, agricultural, professional, vocational or service activity conducted regularly and independently.

In cross-border trade, the crucial jurisdictional distinction lies in whether the supplier is conducting business in the State. A UAE-resident supplier registered for VAT or conducting economic activity within the UAE falls squarely within Article 3(a) as a Person conducting Business in the State. Consequently, its outbound commercial invoices issued to customers—whether domestic or foreign—form part of its business transaction inventory. However, the operational handling of inbound and outbound international invoices differs substantially depending on whether the trading partner is connected to the OpenPeppol network and how the Ministry's predefined endpoints are utilized.

For a comprehensive foundation on general transaction boundaries, see our UAE eInvoicing transaction scope guide and our detailed breakdown of Decision 243/2025 scope and exclusions.

Article 4(1)(b)-(d) international transport and aviation exclusions

While general commercial exports are subject to the electronic invoicing framework when issued by UAE-resident suppliers, specific international transport and aviation activities receive targeted statutory treatment under Article 4 of Decision 243/2025. Following the amendments introduced by Ministerial Decision No. 197 of 2026 (in force since 1 October 2026), the revised Article 4 exclusions set out precise carve-outs for international transport.

Specifically, Article 4(1)(b), (c), and (d) exempt certain international transportation supplies, aircraft leasing, and associated operational transactions from mandatory electronic invoicing exchange through the central system, avoiding operational friction for international carriers and global logistics providers whose billing structures do not map cleanly to standard domestic B2B invoicing schemas. It is essential to distinguish these specific Article 4 exclusions from general export invoices. While international transport operations covered by paragraphs (b) through (d) enjoy specific statutory relief, standard exports of goods and services to foreign commercial buyers remain governed by general eInvoicing transmission rules and utilize dedicated routing mechanisms such as endpoint 0235:9900000099.

For further details on how airline and financial sector rules interact with the system, consult our sector exclusions guide for airlines and financial services and the legislation map and amendment history.

Cross-border B2B exports: routing and electronic invoicing

Exporting goods or services from the UAE to an overseas business customer involves distinct considerations under the 5-corner model defined in the MoF Guidelines V1.1 (C1 supplier, C2 supplier's ASP, C3 buyer's ASP, C4 buyer, C5 Federal Tax Authority). When a UAE-resident supplier issues a commercial invoice for an export to a foreign B2B customer, the invoice data must still be generated in structured XML (PINT-AE format) and transmitted through the supplier's Accredited Service Provider (ASP) to report the transaction to the FTA (Corner 5).

If the foreign buyer is connected to the international OpenPeppol network through its own foreign access point, the invoice travels across international access points from C2 to C3. However, if the foreign buyer does not maintain a Peppol participant identifier or is not connected to the Peppol network, the transaction cannot be routed to a foreign C3 access point. To accommodate this common export reality without breaking system reporting compliance, the MoF Guidelines provide specialized predefined routing endpoints.

For guidance on managing outbound accounts receivable records and complying with issuer obligations, see the accounts receivable issuer guide and our comprehensive eInvoicing FAQ.

Import transactions and non-resident foreign suppliers

Inbound cross-border trade—purchasing goods, software, or professional services from non-resident suppliers located outside the UAE—operates under a different perspective within the eInvoicing framework. Under UAE VAT law, imports of services or certain goods from non-resident suppliers frequently trigger the reverse-charge mechanism, where the UAE recipient accounts for the VAT directly.

From an eInvoicing standpoint, a non-resident supplier with no physical establishment, permanent presence, or VAT registration in the UAE is generally not a "Person conducting Business in the State" under Article 3(a) of Decision 243/2025. Consequently, foreign suppliers are not directly mandated to onboard with a UAE ASP or issue invoices through the UAE eInvoicing central system. Instead, the compliance burden shifts to the UAE recipient (the importer).

When a UAE business receives a cross-border invoice from a non-resident supplier who is not part of the UAE eInvoicing network, the UAE buyer must process the inbound document through its accounts payable workflow, verify the underlying supply, account for reverse-charge VAT where applicable, and maintain adequate records. Where self-billing arrangements apply under Article 9 of Decision 243/2025 between registered parties, specific rules govern electronic generation, but inbound supplier invoices from foreign non-residents are handled through standard AP intake and validation. Review our accounts payable recipient guide for detailed operational workflows.

Predefined endpoints: 0235:9900000098 and 0235:9900000099

A critical technical component of the UAE eInvoicing architecture is the provision of fallback participant identifiers and predefined routing endpoints in Section 6.1 of the MoF Guidelines V1.1. These endpoints solve the operational deadlock that occurs when an electronic invoice must be generated and reported through the system, but the recipient lacks a standard UAE participant identifier or OpenPeppol ID.

• Endpoint 0235:9900000098 (Buyer without identifier): Designated for domestic or general business transactions where the recipient does not possess a recognized participant identifier or Peppol ID at the time of issuance, enabling the issuer to complete structured reporting without stalling.
• Endpoint 0235:9900000099 (Exports and buyers without Peppol ID): Specifically engineered for cross-border export transactions where the foreign commercial buyer is not registered on the Peppol network or lacks a UAE Tax Registration Number (TRN) / participant identifier, ensuring that export sales can be correctly formatted in PINT-AE XML and transmitted via the supplier's ASP to the FTA.

These predefined endpoints act as routing placeholders. However, businesses must exercise care in capturing actual counterparty identifiers whenever available. For an in-depth technical analysis of participant identifier structures (0235 scheme prefix + 10-digit TIN derived from TRN), consult our dedicated guide on participant identifiers and predefined endpoints.

Non-resident trading partner identification and TRN rules

Identifying trading partners accurately is the cornerstone of eInvoicing compliance. Under the MoF Guidelines, standard UAE participant identifiers follow a strict convention: the scheme identifier 0235 combined with a 10-digit Tax Identification Number (TIN), which corresponds to the first 10 digits of the UAE Tax Registration Number (TRN).

For non-resident counterparties who do not hold a UAE TRN, establishing a standard 0235 participant identifier is not applicable. When transacting with overseas entities on OpenPeppol, international participant identifiers (such as GLN, ISO 6523 scheme codes, or country-specific tax IDs) are utilized where supported by the foreign access point. When no foreign Peppol identifier exists, the transaction relies on endpoint 0235:9900000099 as outlined above. UAE entities must maintain robust master data management to distinguish resident taxable persons, tax group members, and foreign non-resident trading partners.

Practical compliance checklist for cross-border transactions

To operationalize cross-border eInvoicing readiness, finance and IT teams should execute the following structured steps:

1. Inventory Cross-Border Flows: Map all current export sales, import purchases, reverse-charge services, and non-resident vendor payments to separate domestic B2B transactions.
2. Classify Export Counterparties: Determine whether foreign buyers are connected to OpenPeppol or require routing via predefined endpoint 0235:9900000099.
3. Verify Import Documentation: Ensure accounts payable workflows correctly capture non-resident invoices, apply reverse-charge VAT accounting, and archive records in compliance with the Tax Procedures Law.
4. Configure ASP Mapping: Coordinate with your Accredited Service Provider to verify that export XML generation correctly applies the PINT-AE standard and populates fallback endpoints when foreign identifiers are absent.
5. Establish Master Data Governance: Maintain clean master data records separating UAE resident TRNs from foreign counterparty tax references.

For an overarching project roadmap and milestone scheduling, see our readiness project plan and internal workstreams.

Frequently asked questions

Are foreign suppliers required to issue UAE electronic invoices?

No. Non-resident suppliers with no permanent establishment or TRN in the UAE are not "Persons conducting Business in the State" under Decision 243/2025 Article 3(a) and are not mandated to use UAE ASPs. The compliance obligation for inbound cross-border purchases rests on the UAE importer.

How should export invoices to non-Peppol foreign buyers be reported?

Export invoices must be generated in structured PINT-AE XML format by the UAE supplier's ASP and transmitted to the FTA. Where the foreign buyer has no Peppol ID, predefined endpoint 0235:9900000099 is used for routing.

Do international transport services fall under standard export eInvoicing rules?

Certain international transport, aviation, and aircraft leasing supplies are specifically addressed under Article 4(1)(b)–(d) of Decision 243/2025 (as amended by Decision 197/2026), providing targeted exemptions from mandatory central system exchange.

How do Tax Group members handle cross-border transactions?

While domestic transactions between members of the same Tax Group enjoy a temporary exclusion for 24 months starting 1 January 2027 under Decision 197/2026, cross-border export and import transactions involving group members follow standard export and import rules.

What participant identifier scheme is used for UAE entities versus foreign entities?

UAE entities use the 0235 scheme prefix followed by their 10-digit TIN (derived from the TRN). Foreign entities on OpenPeppol use their respective jurisdiction's scheme identifiers or international participant schemes.

Not confirmed: cross-border operational details

Not confirmed: To maintain editorial accuracy, the following cross-border operational details are not established by the official texts reviewed for this guide:

• The exact technical validation rules enforced by the FTA and ASPs for foreign participant identifier schemes.
• Whether future FTA technical bulletins will mandate specific validation for export customs declaration numbers within PINT-AE XML payloads.
• The precise treatment of triangular trade and drop-shipping transactions involving multiple foreign jurisdictions and a UAE intermediary.
• Whether additional predefined fallback endpoints will be introduced for specialized international trade scenarios.