PEPPOL · EUUAE · DCTCE

PEPPOL 4-Corner vs UAE 5-Corner Model

The structural difference between the standard PEPPOL 4-corner network and the UAE's 5-corner DCTCE model — and why that fifth corner changes everything for tax authority visibility.

Published 28 February 2026 · AutoFact AI

Quick Answer

PEPPOL uses a 4-corner model: Supplier → Sending AP → Receiving AP → Buyer. Tax authorities are not in the transmission path. The UAE adds Corner 5 — the FTA — which receives the Tax Data Document (TDD) from the Sending ASP in near real-time. This turns a pure invoice delivery network into a continuous transaction control system.

The PEPPOL 4-Corner Model

PEPPOL (Pan-European Public Procurement On-Line) is an international e-invoicing network that uses a standardized 4-corner architecture. The model ensures interoperability: any business connected to any PEPPOL-certified Access Point can exchange invoices with any other PEPPOL-connected business, regardless of their software or geography.

1

Supplier (Sender)

Creates and submits the invoice to their Access Point.

2

Sending Access Point

PEPPOL-certified provider. Validates format and routes the invoice to Corner 3.

3

Receiving Access Point

PEPPOL-certified provider used by the buyer. Receives invoice and delivers to Corner 4.

4

Buyer (Receiver)

Receives the validated invoice from their Access Point.

In the 4-corner model, the tax authority has no visibility into individual transactions in real-time. Tax reporting is handled separately (e.g., periodic VAT returns). The network's only purpose is invoice delivery.

The UAE 5-Corner Model (DCTCE)

The UAE's Decentralized Continuous Transaction Control and Exchange (DCTCE) model extends the PEPPOL 4-corner architecture by adding a fifth corner: the Federal Tax Authority (FTA). The Sending ASP (Corner 2) is responsible for extracting the Tax Data Document from the PINT-AE XML invoice and transmitting it to the FTA in near real-time — simultaneously with routing the invoice to the Receiving ASP.

1

Supplier

Creates PINT-AE XML invoice and submits to Sending ASP.

2

Sending ASP

Validates PINT-AE XML, extracts Tax Data Document (TDD), transmits TDD to FTA (Corner 5), routes invoice to Receiving ASP.

3

Receiving ASP

Receives validated invoice from Sending ASP and delivers to Buyer.

4

Buyer

Receives PINT-AE invoice from Receiving ASP.

5

Federal Tax Authority (FTA)← the key difference

Receives Tax Data Document (TDD) from Sending ASP in near real-time. This is the key difference from PEPPOL.

Key Differences: 4-Corner vs 5-Corner

AspectPEPPOL (4-Corner)UAE DCTCE (5-Corner)
Tax authority in path?NoYes — FTA as Corner 5
Real-time tax reporting?No (periodic returns)Yes — TDD to FTA in near real-time
Invoice formatUBL 2.1 or CII (PEPPOL BIS)PINT-AE XML (UAE-specific)
Intermediary typeAccess Point (AP)Accredited Service Provider (ASP)
Intermediary requirementsPEPPOL AP certificationISO 27001, ISO 22301, UAE data residency
Control modelPost-audit (periodic reporting)Continuous transaction control
Used inEU, Singapore InvoiceNow, AU, NZ, etc.UAE only

Frequently Asked Questions

Why does the UAE use a 5-corner model instead of the standard PEPPOL 4-corner?

The UAE's primary objective is continuous transaction control — the FTA receiving invoice data in near real-time to monitor VAT compliance. The standard PEPPOL 4-corner model only facilitates invoice delivery without tax authority visibility. By adding Corner 5, the UAE achieves both B2B invoice exchange and real-time tax reporting in a single transmission event.

Does Singapore's InvoiceNow have a 5th corner?

No. Singapore's InvoiceNow is a standard 4-corner PEPPOL implementation. IRAS (the Singapore tax authority) is not in the invoice transmission path. InvoiceNow is an invoice delivery network, not a continuous transaction control system.

Can a PEPPOL Access Point also serve as a UAE ASP?

A PEPPOL-certified Access Point could potentially obtain UAE ASP accreditation separately, but the requirements differ. UAE ASPs must additionally hold ISO 27001, ISO 22301, and comply with UAE data residency requirements — obligations not imposed on standard PEPPOL APs.

PEPPOL & PINT-AE E-Invoice Generation

AutoFact AI generates both PEPPOL-compliant UBL invoices (for EU/Singapore/cross-border) and PINT-AE XML invoices (for UAE), with routing to the appropriate access point or ASP.

Related Resources

AI Summary

  • PEPPOL 4-Corner: Supplier → Sending AP → Receiving AP → Buyer. No tax authority in path. Used in EU, Singapore InvoiceNow, AU, NZ.
  • UAE 5-Corner (DCTCE): Same 4 corners + Corner 5 = FTA. Sending ASP transmits Tax Data Document to FTA in near real-time.
  • Key Difference: 4-corner = invoice delivery only; 5-corner = invoice delivery + continuous transaction control
  • ASP vs AP: UAE ASPs require ISO 27001, ISO 22301, UAE data residency — additional to standard PEPPOL AP requirements
  • Format: PEPPOL uses UBL 2.1 or CII; UAE uses PINT-AE XML (UAE-specific PEPPOL profile)

Disclaimer: For informational purposes only. Not legal or tax advice.

© 2026 AutoFact AI. All rights reserved.