UAE to KSA B2B Invoicing: Handling FATOORA and PINT AE Together for Regional Trade
NOV 10, 2026

UAE to KSA B2B Invoicing: Handling FATOORA and PINT AE Together for Regional Trade

Your Saudi customers already expect invoices cleared through FATOORA, and from 1 January 2027 the UAE side of the same transaction has to be reported through an Accredited Service Provider (ASP) under PINT AE. For a Dubai finance team shipping goods to Riyadh, or buying components from Dammam, one commercial relationship now touches two tax authorities with two different technical models. This guide sets out which rulebook applies to each leg of a UAE to KSA trade, where the two flows differ in daily operation, and the data decisions that keep cross-border invoices from failing validation.

Why one Saudi order now creates two compliance events

Saudi Arabia’s Zakat, Tax and Customs Authority (ZATCA) runs a clearance model. A standard tax invoice for a business or government buyer goes to FATOORA first, is validated and stamped, then reaches the buyer. The UAE’s Federal Tax Authority (FTA) took a different route. Its system is built on Peppol, the global e-document exchange network, using a UAE-specific invoice profile called PINT AE (Peppol International Invoice, UAE profile). Invoices travel from seller to buyer through ASPs, and tax data is reported to the FTA under a Continuous Transaction Control (CTC) model, with no approval step before delivery.

Under FATOORA the authority sits before the buyer. Under PINT AE the authority sits alongside the buyer. A UAE group with a Saudi subsidiary, or a Saudi exporter with a Dubai office, ends up running both logics, usually from one ERP.

Which rulebook applies to each direction of UAE to KSA trade

The assumption we correct most often in readiness reviews is that the two regimes overlap on a single invoice. They do not. Each authority governs its own resident supplier.

  • UAE seller invoicing a KSA buyer. This is an export from the UAE. Exports fall within the scope of e-invoicing B2B B2G UAE rules, so invoice data must be reported to the FTA through your ASP. If the Saudi buyer has no Peppol participant identifier, the invoice carries a predefined export endpoint and is delivered outside the network, typically as a PDF by email, a route the UAE Ministry of Finance confirms for buyers in non-Peppol countries. ZATCA does not expect a UAE supplier to clear this invoice; the Saudi buyer accounts for VAT on the import.
  • KSA seller invoicing a UAE buyer. The Saudi supplier generates an export e-invoice through its FATOORA-integrated solution; ZATCA’s guidance confirms exports require an electronic invoice under the E-Invoicing Regulation. On the UAE side, the buyer accounts for import VAT under reverse charge, and imports of concerned goods and services sit outside current UAE e-invoicing requirements, so no inbound e-invoice arrives through your ASP.
  • UAE entity with a KSA VAT registration or branch. Saudi supplies fall under ZATCA and its wave schedule; UAE supplies fall under PINT AE. Two registrations, two sets of obligations, no netting between them.

FATOORA clearance versus PINT AE reporting: the practical differences

Finance and IT leads planning dual compliance should expect these gaps:

  • Timing of validation. FATOORA validates before the buyer sees the invoice, so a rejection stops the sale. PINT AE validation happens at your ASP; a failed invoice is corrected and resent without holding up the buyer relationship.
  • Document security. ZATCA requires a cryptographic stamp, a hash chain linking each invoice to the previous one, and a QR code. The UAE framework requires no QR code on B2B invoices; integrity rests on structured XML and ASP validation.
  • Currency. FATOORA invoices carry SAR amounts. PINT AE invoices in a foreign currency must show the AED tax amount at the UAE Central Bank rate.
  • Who connects to the authority. In Saudi Arabia your ERP integrates with FATOORA directly after obtaining a Cryptographic Stamp Identifier. In the UAE your ERP connects to an accredited ASP, never directly to the FTA.

Four data decisions that decide if cross-border invoices pass validation

Dual compliance is a master data problem before it is a software problem. These four areas cause most rejections in testing.

  1. Customer master records. A Saudi buyer’s VAT number does not fit the UAE TRN format, and the reverse is also true. Each customer record needs a country-specific tax identifier, a Peppol endpoint field (including the UAE predefined export endpoint for non-Peppol buyers), and a flag driving the correct document type.
  2. Tax category and reason codes. Both countries zero-rate qualifying exports, but each demands its own reason code on the line. A ZATCA export line needs the Saudi zero-rate reason; a PINT AE export line needs the UAE tax category and export use case. One code mapped to both systems is a frequent failure.
  3. Document type selection. A commercial invoice, a tax invoice for a zero-rated export, and a self-billed invoice are distinct document types under PINT AE. ZATCA distinguishes standard from simplified invoices. Your ERP must select the right type per transaction leg, not per customer.
  4. Currency, units, and rounding. Exchange rate sources, unit-of-measure codes, and line-level rounding rules differ. A template built for domestic UAE sales usually fails ZATCA’s schema on the first cross-border test.

Running both regimes from one ERP without a second finance team

For a CFO, the question is cost and control: can one SAP, Oracle, Dynamics, or Zoho environment serve both countries without doubling headcount? In our implementation work, three early choices decide it.

First, a readiness assessment that maps every transaction type you actually issue across both countries, including credit notes, intercompany recharges, and milestone billing, against each authority’s requirements. Most gaps surface here, before configuration spend.

Second, ASP selection in the UAE made independently of your ZATCA solution vendor. Some providers cover both jurisdictions; many do not. A vendor-neutral review of ASP capability (export endpoint handling, multi-entity support, ERP API compatibility) avoids locking into a tool chosen for Saudi Arabia that cannot serve UAE reporting. Our UAE e-invoicing compliance guides cover ASP evaluation criteria in depth.

Third, a single integration layer between the ERP and both authorities, tested on real export and import invoices before go-live. IT managers get one mapping document; compliance officers get one exception queue. This is the model behind our compliance-led e-invoicing implementation approach, from assessment through managed operation.

Where the timelines stand as of late 2026

  • UAE. Under Ministerial Decision No. 66 of 2026, businesses with annual revenue of AED 50 million or more appoint an ASP by 30 October 2026 and implement from 1 January 2027. Smaller businesses appoint by 31 March 2027 and implement from 1 July 2027; government entities follow from 1 October 2027.
  • KSA. FATOORA Phase 2 integration has been rolling out in revenue-based waves since January 2023, with ZATCA notifying each group at least six months ahead. A UAE group with a Saudi entity is likely already inside or approaching a wave.

UAE non-compliance penalties are set under Cabinet Decision No. 106 of 2025; the current schedule is on the FTA portal.

Conclusion: one order, two authorities, one data model

Trading between the UAE and Saudi Arabia now means one order, two authorities, two technical models: FATOORA clears before delivery, PINT AE reports alongside it. Each authority governs its own resident supplier, so the real work sits in direction-aware document types, country-specific identifiers and reason codes, the correct Peppol endpoint for Saudi buyers, and one integration layer shared by your ERP, your ASP, and your Saudi solution. Get those right and dual compliance becomes a configuration project, not a parallel finance operation.

If your business invoices across the UAE and KSA, the AA Tech advisory team can map your cross-border flows, assess your ERP, and guide ASP selection without tying you to one vendor. Book a cross-border compliance assessment for a tailored dual-compliance roadmap.

Frequently Asked Questions

Do UAE companies need to register with ZATCA to invoice Saudi customers?

No, not for exports from the UAE. ZATCA’s FATOORA clearance applies to suppliers resident or VAT-registered in Saudi Arabia. A UAE business selling to a KSA buyer issues an export invoice under the UAE system, reports it to the FTA through its ASP, and the Saudi buyer accounts for VAT on the import. Registration with ZATCA becomes relevant only if you hold a Saudi VAT registration or branch.

How does a UAE exporter send a PINT AE invoice to a Saudi buyer not on Peppol?

The invoice is still created in PINT AE format and validated by your Accredited Service Provider. Because the Saudi buyer has no Peppol participant identifier, the predefined UAE export endpoint is used instead, and the tax data is reported to the FTA. The buyer then receives a conventional copy, usually a PDF by email. The reporting obligation does not disappear because the buyer sits outside the network.

Does a UAE buyer receive e-invoices from Saudi suppliers through its ASP?

Typically no. A Saudi supplier clears its export invoice through FATOORA under ZATCA rules and sends it to the UAE buyer by conventional means. On the UAE side, imports of concerned goods and services fall under the reverse charge mechanism and currently sit outside the e-invoicing requirement, so nothing arrives through your ASP. Your accounts payable process still needs to capture the cleared invoice for VAT recovery.

What is the main difference between FATOORA clearance and PINT AE reporting?

Timing and control. FATOORA is a clearance model: ZATCA validates and stamps a standard B2B invoice before the buyer can receive it. PINT AE is a decentralised reporting model: the invoice goes from seller to buyer through accredited ASPs on the Peppol network, while tax data is reported to the FTA in parallel. One system holds the invoice until approval; the other validates at the ASP and reports alongside delivery.

Can one ERP handle both FATOORA and PINT AE compliance from the UAE?

Yes, provided the master data and integration layer are designed for both from the start. Each customer record needs country-specific tax identifiers, the correct Peppol endpoint, and a document-type flag. Exchange rates, reason codes, and rounding rules must be mapped per jurisdiction. A readiness assessment that tests real export and import invoices against both schemas usually reveals the gaps before configuration spend, keeping dual compliance inside one SAP, Oracle, Dynamics, or Zoho environment.