Menu Example
Menu Icon

Partner FAQ

This FAQ is for partners who advise, implement, or support clients on UAE e-invoicing and wish to work with SunTec as their platform provider. It focuses on roles, responsibilities, architecture, and commercial collaboration.

1. What is UAE e-invoicing in simple terms?

UAE e-invoicing is the mandatory, machine-to-machine exchange of electronic invoices over the Peppol network under the Ministry of Finance’s DCTCE (Decentralized Continuous Transaction Control and Exchange) model. Instead of emailing PDFs, your ERP sends structured data to a certified Access Service Provider (ASP), which validates and transmits it to:
• Your customer’s ASP; and
• The Ministry of Finance / FTA for real-time reporting.
All of this happens in a standard, Peppol-compliant format (Pint-AE).

In scope:
• B2B invoices between UAE VAT-registered entities.
• B2G invoices where government entities are the buyer.
• Commercial invoices for zero-rated, exempt and “out of scope” supplies, if they are between in-scope entities.
Currently out of scope:
• B2C invoices (sales to individuals without a TIN/Peppol ID).
• Non-UAE counterparties, except where Peppol is used voluntarily.
You must assume that every invoice between two UAE TIN-holding entities will need to flow via e-invoicing.

All UAE VAT-registered entities (TRN/TIN holders) must comply, with phasing based largely on turnover:
• Entities above a defined turnover threshold go live earlier (e.g., January 2027).
• Remaining in-scope entities follow (e.g., July 2027).
In addition, there is an earlier deadline by which ASPs and taxpayers must complete boarding on the EmaraTax portal (e.g., by July 2026). Practically, this is your effective latest date to have selected an ASP and started integration.

(You can keep dates generic or update once timelines are finalized in your customer-facing artefact.)

A Peppol ID is your “address” on the Peppol network. For UAE, it is constructed as:

0235 + your 10-digit TIN

Each legal entity has its own TIN and therefore its own Peppol ID. This is what allows the Peppol infrastructure to determine where to route invoices for that entity.

You need a robust database of all in-scope trading partners.
Practically:
• You must collect and store the correct entity-level TIN for each customer and supplier.
• SunTec’s solution can derive the Peppol ID automatically as “0235 + TIN”.
This becomes a one-time KYC-like exercise, similar to when you collected TRNs at VAT introduction, but now focused on entity-level TINs.

Imports/exports with Peppol-enabled countries:
You can optionally exchange invoices over Peppol, though this may not yet be mandated cross-border.
Non-Peppol countries:
You continue to invoice as today. These flows are handled via VAT returns rather than via the UAE e-invoicing network.

Self-billing is used when your UAE suppliers cannot themselves connect to the e-invoicing network (for example, very small businesses or individuals):
• You, as the buyer, issue invoices on their behalf.
• You report those self-billed invoices via e-invoicing.
• This is governed by a formal agreement between you and the supplier.
For UAE suppliers, every invoice must either:
• Come through their e-invoicing flow; or
• Be covered by a compliant self-billing arrangement.
Anything else is treated as non-compliant.

Once an invoice is sent into the e-invoicing network, it cannot be edited or overwritten.
To correct errors:
1. Issue a credit note referencing the original invoice.
2. Issue a new, corrected invoice and send it via e-invoicing.
This makes upfront validation critical, both in your ERP and in the e-invoicing layer before transmission.

SunTec offers two core components:

  1. Access Point (AP)
    • Certified Peppol Access Point.
    • Receives Pint-AE transactions, performs technical validations, and routing.
    • Delivers invoices to the buyer’s Access Point and reports them to the Ministry.
  2. E-Invoicing Processor
    • Sits between your ERPs and the Access Point.
    • Accepts data in your native formats (APIs, files, DB extracts, manual uploads).
    • Validates against UAE data dictionary and business rules.
    • Enriches and converts to Pint-AE before sending to the AP.

Yes.
Your ERP does not have to generate Pint-AE. Instead:
• You provide SunTec with your existing output (API payloads, flat files, extracts, etc.).
• The E-Invoicing Processor validates and enriches the data.
• It then generates Pint-AE and passes it to the Access Point.
You keep your ERP changes focused on ensuring all required data fields are available and exposed.

Yes.
SunTec’s solution is designed for:
• Multiple legal entities, each with its own TIN and Peppol ID.
• Multiple ERPs (SAP, Oracle, JDE, Dynamics, custom systems, etc.).
• Shared services or centralized finance models.
The platform:
• Receives data from multiple ERPs.
• Routes transactions by legal entity.
• Centralizes compliance logic so you do not replicate it in each ERP.

December 9, 2025

11 Questions Every Organization Should Ask Before Choosing
an E-Invoicing System

December 1, 2025

The Hidden Strategic Value of UAE’s E-Invoicing Mandate

November 14, 2025

Building Resilient E-Invoicing Architectures: Avoiding Tech Debt
and Siloes

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors