FinSanad ยท UAE Compliance

E-Invoicing & Peppol Access Point Integration

How FinSanad connects to the UAE's Peppol-based e-invoicing network (the "5-corner" model) to exchange structured tax invoices between businesses and report tax data to the Federal Tax Authority in real time.

๐Ÿ‡ฆ๐Ÿ‡ช FTA InvoiceNow / Peppol UBL 2.1 ยท PINT AE Ministerial Decision No. 64 of 2025 Pilot Jul 2026 โ†’ Mandatory 2027
On this page: What is Peppol 5-Corner Model FinSanad Integration FinSanad Readiness Compliance Checklist Roadmap References

1What is a Peppol Access Point?

The UAE Federal Tax Authority (FTA) is moving all B2B and B2G invoicing onto Peppol โ€” an international network for exchanging structured electronic documents. Businesses do not connect to Peppol directly; they connect through an Accredited Service Provider (ASP) that operates a certified Access Point (AP).

Access Point (AP)
A certified gateway that sends and receives Peppol documents on your behalf, guaranteeing format, routing, and delivery.
ASP
The Accredited Service Provider that runs the AP. In the UAE, ASPs are accredited by the Ministry of Finance under Ministerial Decision No. 64 of 2025.
SMP / Directory
The Service Metadata Publisher โ€” a registry that maps a company's Peppol ID (its TRN-based participant ID) to the AP that serves it.

FinSanad's role is Corner 1 (the supplier's software): it produces a compliant structured invoice, hands it to an ASP's Access Point over an API, and stores the returned identifiers and status. The ASP handles the network transport and the real-time tax report to the FTA.

2The UAE 5-Corner (CTC) Model

Classic Peppol is a 4-corner exchange (supplier โ†’ supplier's AP โ†’ buyer's AP โ†’ buyer). The UAE adds a 5th corner: the invoice's tax data is reported to the FTA at the same time it is delivered to the buyer โ€” a Continuous Transaction Control (CTC) model.

CORNER 1
Supplier
FinSanad generates the invoice (UBL 2.1)
โ†’
CORNER 2
Supplier Access Point
Accredited ASP validates & transmits
โ†“
CORNER 4
Buyer
Receives structured invoice into their ERP
โ†
CORNER 3
Buyer Access Point
Buyer's ASP receives & routes
CORNER 5
๐Ÿ›๏ธ Federal Tax Authority
Receives the Tax Data Document (TDD) in real time from the supplier's ASP โ€” the Tax Data Submission (TDS)
Key point for FinSanad: we never talk to Corner 3, 4, or 5 directly. We deliver a correct document to Corner 2 (the ASP) and record the acknowledgements. The ASP fans it out to the buyer and the FTA.

3FinSanad โ†’ ASP Integration Architecture

FinSanad already generates signed UBL 2.1 XML per invoice (see the E-Invoicing guide). Peppol readiness adds a thin outbound integration layer to an ASP:

StepWhat happensWhere in FinSanad
1. GenerateProduce the structured invoice in UBL 2.1, aligned to the PINT AE data dictionary (mandatory fields, TRN, tax categories)./api/v1/einvoice/{id}/generate (implemented)
2. ValidateSchematron / PINT AE validation of every mandatory field before transmission.Validation service (to add)
3. TransmitPOST the document to the ASP's Access Point API (REST) or SFTP; receive a Peppol message ID.ASP connector (to add โ€” per chosen ASP)
4. AcknowledgeStore the ASP's delivery status + the FTA Tax Data Submission (TDS) reference against the invoice.Extend e_invoices table
5. ArchiveRetain the XML, signature, hash and acknowledgements for 7 years.e_invoices retention (implemented)
Requires a commercial ASP. Steps 3โ€“4 depend on selecting an MoF-accredited ASP and signing a service agreement โ€” FinSanad ships the document generation, validation hooks, and archival; the live network connection is configured per ASP once selected.

4FinSanad Readiness Map

How FinSanad's current capabilities map to the UAE e-invoicing / Peppol requirements:

RequirementStatusDetail
Structured invoice generation (UBL 2.1 XML)ImplementedPer-invoice UBL 2.1 with type codes 380/381/383, TRN party IDs, per-line tax categories.
Supplier TRN & VAT registration captureImplemented15-digit TRN validated; company settings on the tenant.
VAT calculation (standard / zero-rated / exempt)Implemented5% engine + VAT201 return generation.
Digital signature & QR codeImplementedRSA-2048 / SHA-256 signature over the XML; QR payload. (Self-signed cert โ€” swap for CA cert for production.)
Sequential, unique invoice numberingImplementedPer-tenant sequential numbers (INV-YYYY-#####).
7-year electronic archivalImplementede_invoices stores XML + hash + signature + fingerprint.
REST API for integrationImplemented/api/v1/โ€ฆ tenant-scoped API.
Data security & encryptionImplementedTLS 1.3, Argon2 password hashing, RBAC, tenant isolation.
PINT AE data-dictionary alignmentPartialUBL 2.1 base present; PINT AE mandatory-field profile + Schematron validation to be finalised.
Peppol participant registration (TRN-based ID)Needs ASPRegistered through the chosen ASP / SMP.
Access Point connectivityNeeds ASPOutbound connector to the ASP AP (REST/SFTP).
Tax Data Submission (TDS) to FTANeeds ASPDelivered via the 5-corner model by the supplier's ASP.
CA-issued signing certificateConfigReplace the self-signed cert with an accredited CA certificate.

5UAE E-Invoicing Compliance Checklist

A 25-point readiness assessment across five categories (adapted from the UAE InvoiceNow compliance checklist). Tick items as you complete them โ€” your progress is saved in this browser.

0 of 25 complete

6UAE Rollout Timeline

July 2026 โ€” Pilot phase
Voluntary/pilot participation. Target window to complete ASP selection, Peppol participant registration, and end-to-end connectivity testing in a sandbox.
January 2027 โ€” Mandatory rollout, phase one
First wave of mandatory e-invoicing (typically large enterprises). Production ASP connection and TDS to the FTA must be live.
July 2027 โ€” Mandatory rollout, phase two
Broader mandate covering remaining VAT-registered businesses (SMEs).
Dates reflect the phased schedule referenced in the UAE InvoiceNow compliance material and are subject to FTA/MoF confirmation. Verify the current mandate dates and your business category with the FTA before relying on them.

7References

FinSanad status summary: document generation, VAT, signing, QR, sequential numbering, 7-year archival and a REST API are Implemented. Going live on Peppol additionally needs an MoF-accredited ASP, participant registration, the Access-Point connector, and a CA signing certificate โ€” a configuration/integration project, not new core accounting code.