Menu Example
Menu Icon

Customer FAQ

This FAQ is designed for UAE businesses that need to comply with the e-invoicing mandate and are evaluating or implementing SunTec’s e-invoicing solution. It explains the mandate, what changes for you, and how SunTec’s Access Point and E-Invoicing Processor fit into your landscape.

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:

All of this happens in a standard, Peppol-compliant format (Pint-AE).

In scope:

Currently out of scope:

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:

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:

This becomes a one-time KYC-like exercise, similar to when you collected TRNs at VAT introduction, but now focused on entity-level TINs.

You can optionally exchange invoices over Peppol, though this may not yet be mandated cross-border.

You continue to invoice as today. These flows are handled via VAT returns rather than via the UAE e-invoicing network.

For e-invoicing compliance, the primary in-scope universe is domestic B2B/B2G transactions where both buyer and seller are in UAE and VAT-registered.

Self-billing is used when your UAE suppliers cannot themselves connect to the e-invoicing network (for example, very small businesses or individuals):

For UAE suppliers, every invoice must either:

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 keep your ERP changes focused on ensuring all required data fields are available and exposed.

Yes.

SunTec’s solution is designed for:

The platform:

Some changes are likely, but they are targeted:

For each transaction, SunTec:

1. Checks presence of all mandatory and conditional fields required by UAE rules.
2. Applies compliance rules (e.g., invoice types, credit note rules, FX treatments).
3. Enriches technical attributes (codes, IDs, references) required by Pint-AE.
4. Only then forwards the transaction to the Access Point.

This reduces rejections at Peppol or Ministry level and avoids incorrect reporting.

If connectivity between Access Points or with the Ministry is interrupted:

From your perspective, transient network issues do not mean silent failures; transactions are either successfully delivered or flagged for investigation.

A typical program for a multi-entity, multi-ERP group looks like:

  1. Discovery and gap analysis (2–4 weeks)
    • Map entities, systems, flows, and master data.
    • Identify gaps vs. UAE e-invoicing requirements.
  2. Solution design and configuration
    • Set up SunTec’s processor and Access Point.
    • Define integration patterns and mappings.
  3. Build and integration
    • Implement APIs, file transfers, or data extracts.
    • Configure validations and transformations.
  4. Testing and UAT
    • Run end-to-end scenarios across invoices, credit notes, and edge cases.
  5. Go-live and hyper care

Total duration is usually around 10–16 weeks depending on complexity and internal resourcing.

From the customer side, SunTec will need:

SunTec brings:

Not all entities or flows justify deep integration. For low-volume scenarios, SunTec can:

This is useful for small entities, special-purpose vehicles, or exceptional transaction types.

Yes.

One of the strategic benefits of using a Peppol-based Access Point and configurable processor is that:

Pricing typically has:

  • A one-time implementation and onboarding fee.
  • A recurring fee based on:
    • Number of entities.
    • Invoice/credit note volumes.
    • Integration and hosting model.

Commercials are finalized case by case, and can be tuned for group structures, shared services, and high-volume environments.

Discover the right e-Invoicing solution tailored to your business needs.

Related Insights on E-Invoicing

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