UAE E-Invoicing Mandate:

Phase 1 mandatory 1 January 2027 (revenue ≥ AED 50M). Get ready now →

Learn how to prepare
UAE 4-corner Peppol exchange model explained
Peppol & Technical

How the FTA's 4-Corner Peppol Model Works in the UAE

The UAE has adopted the Peppol 4-corner exchange model for e-invoicing. Learn how invoices flow between supplier, ASPs, and customer, and how the FTA receives data in near real-time as a fifth corner.

Last updated: 12 May 2026 4 min read 1 views
UAE 4-corner Peppol exchange model explained

What is the 4-Corner Model?

The UAE's e-invoicing system does not route invoices through a central government portal. Instead, it uses the Peppol 4-corner model - the same architecture used in Singapore, Australia, New Zealand, and most of Europe. The four corners are the supplier, the supplier's Accredited Service Provider (ASP), the customer's ASP, and the customer.

The Federal Tax Authority sits alongside this exchange as an additional reporting corner, receiving structured data in near real-time. That is why some references describe the UAE as a "5-corner" implementation.

The Four Corners

  • Corner 1 - Supplier. The business issuing the invoice. They create the invoice in their ERP or accounting software.
  • Corner 2 - Supplier's ASP. The Accredited Service Provider on the seller side. Receives the invoice data from the supplier, transforms it to PINT AE format, signs it, and sends it through the Peppol network.
  • Corner 3 - Customer's ASP. The Accredited Service Provider on the buyer side. Receives the document from Peppol, validates it, and delivers it to the customer.
  • Corner 4 - Customer. The business receiving the invoice. They accept it into their AP system.

Both ASPs also simultaneously report the document to the FTA - the fifth corner.

Why a 4-Corner Network and Not a Portal?

A central portal model would force every business to integrate directly with the government. That works at small scale but breaks at national scale. The 4-corner network distributes the work:

  • Businesses only need to integrate with their chosen ASP, not with the government.
  • ASPs handle the heavy lifting - format conversion, signing, validation, exchange, and reporting.
  • Suppliers and customers can choose different ASPs and still exchange seamlessly because the network is interoperable.
  • The FTA gets clean, structured data without bottlenecking the exchange itself.

How a Single Invoice Travels

  1. Supplier creates an invoice in their ERP.
  2. The supplier's ASP picks up the invoice data (via API, file feed, or direct integration), transforms it to PINT AE XML, validates it against the FTA business rules, and signs it.
  3. The supplier's ASP looks up the customer's Peppol identifier in the network and routes the document to the customer's ASP.
  4. The customer's ASP receives the document, validates it again, and delivers it to the customer's AP system.
  5. Both ASPs simultaneously report the invoice metadata to the FTA.
  6. The customer accepts the invoice and processes payment via their normal AP workflow.

The whole exchange typically completes in seconds.

What if the Customer Does Not Have an ASP Yet?

During Phase 1, many B2B counterparties will already be on the network. For customers that have not yet appointed an ASP, the supplier's ASP can still report the invoice to the FTA so the supplier remains compliant, while the customer onboards. The Peppol network supports phased rollout.

What the Supplier's ASP Does Behind the Scenes

  • Data extraction - reads invoice data from your ERP via API or file.
  • Mapping - converts ERP fields to PINT AE elements.
  • Validation - checks against FTA business rules and PINT AE cardinality.
  • Signing - applies a digital signature for integrity and authenticity.
  • Routing - looks up the customer's Peppol participant ID and sends.
  • FTA reporting - submits invoice metadata in near real-time.
  • Archive - retains the structured document for audit.

What This Means for Your Implementation

You do not need to learn Peppol or PINT AE schemas in detail. You need to:

  1. Appoint an Accredited Service Provider via EmaraTax.
  2. Connect your ERP to the ASP through API or batch integration.
  3. Ensure your master data (customer TRN, Peppol IDs, addresses, item catalogue) is clean.
  4. Run pilot exchanges in sandbox before going live.

How InvoiceNet Sits in the Model

InvoiceNet is a Peppol Access Point and Accredited Service Provider operating in the UAE. We act as Corner 2 (or Corner 3) for our customers - extracting invoice data from your ERP, transforming to PINT AE, exchanging via Peppol, and reporting to the FTA simultaneously. You stay on your existing ERP. We handle the network plumbing.

I

Written by

InvoiceNet Team

Share this article