UAE E-Invoicing for Exporters in NetSuite: The 0235:9900000099 Endpoint Explained

UAE e-invoicing for exporters is not optional, and it is not a simplified process. If your business issues invoices for goods or services sold outside the UAE, those transactions must still travel through the UAE Peppol network as structured PINT-AE/UBL 2.1 documents, submitted to an FTA-accredited service provider. The fact that the buyer is overseas does not exempt the transaction from the mandate. What changes is how the buyer’s Peppol endpoint is resolved, which transaction type code applies, and how foreign currency amounts are expressed. This post walks through each of those requirements in the context of NetSuite, where customer records, transaction fields, and integration configuration all need to reflect the correct export-specific settings before a single invoice leaves your system.

Why Export Invoices Still Go Through the UAE Peppol Network

A common assumption among UAE exporters is that e-invoicing only applies to domestic B2B transactions. That assumption is incorrect. The UAE Ministry of Finance mandate covers all VAT-registered businesses, and export supplies are treated as zero-rated, not exempt. Zero-rating affects the VAT rate applied to the invoice, not whether the invoice must be submitted electronically.

Every invoice you issue for an export supply, whether it covers physical goods shipped to Germany, consulting services delivered to a client in Singapore, or software licenses sold to a buyer in the United States, must be submitted through your accredited e-invoicing service provider (ASP) and routed through the UAE Peppol network. The ASP handles the actual transmission. The seller’s obligation is to generate a compliant PINT-AE document and pass it to the ASP with the correct metadata.

For a broader overview of how the UAE system works end to end, see this UAE e-invoicing integration guide for NetSuite, which covers both domestic and cross-border flows.

The Predefined Export Buyer Endpoint: 0235:9900000099

On the UAE Peppol network, every invoice requires a buyer endpoint, which is the Peppol participant identifier that tells the network where to route the document. For domestic UAE buyers who are registered on the network, the endpoint follows a standard format: 0235:TIN, where TIN is the first ten digits of the buyer’s Tax Registration Number (TRN). You look up the buyer’s TRN, take the first ten digits, and prepend the UAE country scheme code 0235.

For foreign buyers, this logic breaks down immediately. A buyer based in the Netherlands or Japan has no UAE TRN. They may not be registered on any Peppol network, or they may be registered on a different regional Peppol network that is not interconnected with the UAE’s. The UAE MoF resolves this with a single predefined endpoint that covers all buyers located outside the UAE:

• 0235:9900000099, the predefined export buyer endpoint, used for every buyer with a physical or registered address outside the UAE, regardless of whether that buyer participates in any Peppol network

There is also a second predefined endpoint for a different scenario:

• 0235:9900000098, for UAE-based buyers who are not yet registered on the UAE Peppol network

These two endpoints are distinct. Do not use 9900000098 for a foreign buyer. The endpoint 9900000099 is specifically reserved for cross-border sales. When your ASP receives an invoice addressed to 0235:9900000099, it knows the buyer is outside the UAE and handles routing accordingly. The seller does not need to establish any direct connection with the foreign buyer’s systems.

Because the buyer TIN field (Field 24 in the PINT-AE schema) must still be populated, export invoices use the placeholder TIN associated with the predefined endpoint, specifically the value tied to 0235:9900000099. Your ASP will confirm the exact placeholder value to enter, but it derives from the endpoint itself.

Transaction Type Codes for Export Invoices

The UAE e-invoicing schema requires a transaction type code on every invoice. This is an 8-bit binary string where each bit signals a specific characteristic of the transaction. For export invoices, bit 8 must be set to 1. The full code for a straightforward export invoice with no other special characteristics is 00000001.

If the export transaction also qualifies as an e-commerce sale, bits 7 and 8 are both set to 1, giving a transaction type code of 00000011.

Getting this code wrong causes validation failures at the ASP or network level. In NetSuite, the transaction type code must be passed as a field in the outbound payload that your integration builds per invoice. It is not a field that exists natively in NetSuite; it is derived from the invoice’s customer category or a custom field that flags the transaction as an export. See the full reference on UAE e-invoicing transaction type code for NetSuite for the complete bit mapping across all transaction types.

The 51 Mandatory Fields Still Apply to Every Export Invoice

There is no reduced field set for export invoices. All 51 mandatory fields defined in the PINT-AE/UBL 2.1 specification apply equally to cross-border transactions. The only differences are in specific field values, not in which fields are required.

Key field-level differences for export invoices compared to domestic invoices:

• Field 24 (Buyer TIN): populated with the placeholder TIN for the predefined export endpoint rather than a real UAE TRN
• Field for buyer Peppol endpoint: 0235:9900000099 instead of 0235:[buyer TRN first 10 digits]
• VAT rate: 0% (zero-rated), with the appropriate VAT exemption code populated
• Transaction type code: bit 8 set to 1
• Fields 43 and 44 (net and gross line amounts in AED): required even when the invoice is denominated in a foreign currency

For the complete field list and the corresponding NetSuite field mapping for each, refer to the post on UAE e-invoicing mandatory fields and their NetSuite mapping.

Currency Conversion on Export Invoices: AED Line Amounts Are Required

Many UAE exporters invoice in foreign currencies: USD for clients in North America, EUR for European buyers, or GBP for the UK. The UAE e-invoicing mandate does not prohibit foreign currency invoices, but it does require that line-level amounts also be expressed in AED.

Specifically, Fields 43 and 44 in the PINT-AE schema capture the net and gross line amounts in AED. These must be calculated at the exchange rate on the invoice date. If you issue a USD invoice on 15 June, the AED conversion must use the rate as of 15 June, not an average rate or a rate from the day the invoice is processed in your ERP.

In NetSuite, this requires your integration to:

1. Read the invoice date from the transaction
2. Retrieve the exchange rate for the invoice currency against AED at that date, either from NetSuite’s currency rate table or from a rate feed your integration maintains
3. Multiply each line’s net and gross amounts by that rate to produce the AED equivalents
4. Include both the original currency amounts and the AED amounts in the PINT-AE document submitted to the ASP

If your NetSuite instance does not have daily AED exchange rates loaded for all currencies you invoice in, this becomes a gap that must be addressed before the mandate applies to your transactions. Most integration configurations include a currency rate synchronisation step for exactly this reason.

How NetSuite Customer Records Must Be Configured for Export Buyers

In NetSuite, the customer record is the primary source of buyer data that feeds into each invoice. For UAE e-invoicing for exporters, the customer record for every foreign buyer must carry specific configuration that differs from a domestic customer.

The configuration points that need to be in place:

• A custom field (or a field managed by your integration middleware) that stores the Peppol buyer endpoint: for all foreign buyers, this value is 0235:9900000099
• A customer category or custom boolean flag that identifies the customer as an export buyer, which the integration uses to derive the correct transaction type code (bit 8 = 1) on every invoice
• Country field populated correctly, since the integration logic may derive the export flag from the customer’s billing country rather than requiring manual entry
• The buyer TIN field configured to store the predefined export placeholder TIN rather than a real TRN

Some businesses have a mix of domestic and export customers, and occasionally sell domestically to foreign-headquartered companies that have a UAE branch with a TRN. In those cases, the customer record should reflect the UAE entity’s TRN and domestic endpoint, not the predefined export endpoint. The deciding factor is whether the invoice is addressed to a UAE entity with a UAE TRN.

For a detailed walkthrough of the integration architecture, including how customer records, saved searches, and middleware components interact, see the guide on how to integrate NetSuite with a UAE e-invoicing service provider.

Data Retention for Export Invoices

Export invoices are subject to the same data retention requirements as domestic invoices. The UAE mandate specifies a minimum retention period of five years for standard invoices and seven years for real estate transactions. This applies to the original PINT-AE/UBL 2.1 XML documents, not just the PDF or printed copy of the invoice.

In practice, this means your ASP must archive the submitted XML, or your NetSuite environment must store a copy, or both. Most accredited service providers include archiving as part of their service. Confirm with your ASP whether the archived documents are accessible on demand for FTA audit purposes, and whether the archive covers the full XML payload including all mandatory fields.

There is no QR code requirement in the UAE system, which is a point of difference from Saudi Arabia’s ZATCA mandate. UAE e-invoices do not need a QR code embedded in the PDF or the XML, so this is one compliance element that does not require additional configuration in NetSuite or your integration.

UAE e-invoicing for exporters requires the same structured compliance approach as domestic transactions, with additional configuration for buyer endpoints, transaction type codes, and AED currency conversion. Getting NetSuite set up correctly before the mandate applies to your business means auditing customer records, confirming exchange rate data availability, and validating your integration against the 51 mandatory fields. For organisations with significant cross-border revenue, these are not minor adjustments. They require deliberate configuration and testing against an accredited service provider’s sandbox before going live. Our NetSuite implementation and integration services cover the full scope of UAE e-invoicing compliance for businesses of all export volumes.