What is UAE eInvoicing and who needs to comply?

The UAE Ministry of Finance mandates that businesses send invoices electronically via the Peppol network in structured XML format. The mandate rolls out in two phases: Phase 1 (January 2027) covers businesses with revenue of AED 50M or more, and Phase 2 (July 2027) covers all remaining businesses below AED 50M. Businesses who wish to be early adopters can start testing now. The mandate applies to any person conducting business in the UAE, regardless of VAT registration status. B2C transactions are excluded until a future ministerial decision.

Does the mandate apply only to VAT-registered businesses?

No. The mandate applies to any person conducting business in the UAE, regardless of VAT registration status. Non-VAT-registered entities must register with the FTA to obtain a Tax Identification Number (TIN). For VAT groups, each member must have its own ASP endpoint using its own TIN (the first 10 digits of its own TRN, not the group representative's TRN), with a 24-month grace period from January 2027 for intra-group transactions.

Are B2C transactions covered by the mandate?

No. Business-to-consumer (B2C) transactions are excluded from the Electronic Invoicing System until a future ministerial decision. Businesses engaged exclusively in B2C are fully exempt for now. However, businesses with mixed B2B and B2C operations must comply for their B2B and B2G transactions. Voluntary eInvoicing for B2C is permitted, though all technical requirements then apply.

Do both invoice senders and receivers need an ASP?

Yes. Both the invoice issuer and the recipient must appoint an Accredited Service Provider connected to the Peppol network. This is a bilateral obligation. For overseas buyers without UAE tax obligations, if they are on the Peppol network in their home jurisdiction, their existing endpoint is used; otherwise, a fallback mechanism (PDF copy) applies.

What about VAT group members and intra-group transactions?

Each VAT group member must register a separate Peppol endpoint using its own TIN, which is the first 10 digits of its individual TRN, not the group representative's. A 24-month grace period for intra-group transactions runs from 1 January 2027 to 31 December 2028, during which eInvoicing obligations do not apply between members of the same VAT group. Transactions with external parties must comply per the normal phase schedule.

Do non-VAT-registered businesses need to comply?

Yes. Any person conducting business in the UAE is within scope, even without VAT registration. Non-VAT-registered businesses must register with the FTA to obtain a TIN. They issue "Commercial Invoices" rather than "Tax Invoices" through the system, and must do so within 14 days from the date of the business transaction.

What about overseas or international buyers?

If the overseas buyer is on the Peppol network in their home jurisdiction, their existing Peppol endpoint is used to receive the eInvoice. If not, a fallback mechanism applies where the buyer receives a PDF copy. A buyer's eInvoicing onboarding status does not affect the supplier's obligation to issue eInvoices; predefined endpoints exist for scenarios where the buyer hasn't yet appointed an ASP.

Are free zone entities in scope?

Yes. The mandate applies to "any Person conducting Business in the State," which explicitly includes designated zones and free zones. The PINT-AE specification has a dedicated transaction type flag (position 1 in the 8-bit ProfileExecutionID) for Free Trade Zone transactions, with additional mandatory fields like Beneficiary ID.

Are export and e-commerce transactions in scope?

Yes. Both are explicitly covered. The PINT-AE ProfileExecutionID includes dedicated flags for exports (position 8) and e-commerce (position 7). Export invoices require a delivery address with a country code that is not "AE." E-commerce invoices require a full delivery address including emirate code. If you sell online to other businesses or export goods, your eInvoicing setup must accommodate these transaction types.

Are import invoices required through the eInvoicing system?

No. Foreign supplier invoices received by UAE buyers are not mandated through the system. The MoF has stated it seeks to avoid imposing additional reporting obligations for import transactions. If your foreign supplier is in a Peppol-compliant country, you can receive invoices via the Peppol network, but the UAE's data dictionary cannot be imposed on them, and you are not mandated to report the transaction through the eInvoicing system.

Are there any exemptions from the eInvoicing mandate?

Yes. Exemptions include sovereign government activities, international airline passenger transport where electronic tickets are issued, and international air cargo transport by airlines (24-month temporary exclusion). VAT-exempt and zero-rated financial services under Article 42 of the VAT Executive Regulation are also excluded. B2C transactions and supplies to or from natural persons not in business are outside scope.

Are voluntary adopters subject to penalties?

No. Article 2(2) of Cabinet Decision 106 of 2025 explicitly exempts voluntary participants from penalties. Businesses that adopt eInvoicing before their mandatory phase begins face no penalty risk. Businesses who wish to be early adopters can start testing now, and it is a good way to resolve integration issues before penalties apply.

What is the Peppol Participant ID format for UAE entities?

The Peppol Participant Identifier for UAE entities follows the format 0235:[10-digit TIN], where 0235 is the UAE's scheme identifier on the Peppol network and the TIN is the first 10 digits of the TRN issued by the FTA. Every business in scope needs this identifier registered with their ASP. If you don't have a TRN yet, you must register with the FTA to get one before you can onboard.

How does the Peppol 5-Corner model work?

The UAE uses the Decentralized Continuous Transaction Control and Exchange (DCTCE) model, extending the standard Peppol 4-corner model with a fifth corner for the tax authority. The five corners are: (C1) the Supplier, (C2) the Supplier's ASP, which validates and transmits the invoice, (C3) the Buyer's ASP, which receives and delivers it, (C4) the Buyer, and (C5) the Federal Tax Authority, which receives tax data from both C2 and C3 for cross-validation. Calculus operates as your ASP, handling corner 2 (for suppliers) or corner 3 (for buyers).

What is DCTCE and why did the UAE choose this model?

DCTCE stands for Decentralized Continuous Transaction Control and Exchange. Unlike centralized clearance models (such as Italy's SDI or Saudi Arabia's FATOORAH), the UAE model is decentralized: the FTA acts as a data repository, not an invoice clearance gateway. Both the sender's and receiver's ASPs independently extract and report tax-relevant data to the FTA, which cross-validates. This dual-reporting design ensures data integrity without creating a single point of failure.

What role does an Accredited Service Provider (ASP) play?

ASPs validate all eInvoice data against the UAE data dictionary, transmit invoices through the Peppol network, and report Tax Data Documents (TDDs) to the Federal Tax Authority. They ensure every invoice meets PINT-AE compliance before it enters the network. Calculus, powered by Taxilla, is an approved ASP listed by the UAE Ministry of Finance. Taxilla is number 19 of 21 providers on the approved list.

PINT-AE (Peppol International, UAE Extension) is the specific XML format required for UAE eInvoicing. It extends the European EN16931 standard through a multi-layer derivation: EN16931 to Peppol BIS Billing 3.0 to PINT (global template) to PINT-AE (UAE specialization). It uses UBL 2.1 XML syntax and adds UAE-specific business rules like TRN validation, AED currency handling, and 5% VAT calculations.

How does PINT-AE relate to EN16931?

PINT-AE is built on a multi-layer standards chain: the European standard EN16931 forms the semantic base, which Peppol BIS Billing 3.0 implements, which PINT (the global template) extends, which PINT-AE then customizes for the UAE. The specification defines approximately 135 total data elements, of which 51 are mandatory for a standard tax invoice, including 15 fields not currently required under UAE VAT law. Fields cover invoice metadata, seller/buyer details, document totals, tax breakdowns, and line-level requirements.

Can I use different ASPs for sending and receiving?

No. Each business entity must use the same Accredited Service Provider for both sending (accounts receivable) and receiving (accounts payable) eInvoices. You appoint exactly one ASP that handles both directions. Choose carefully, as switching providers later adds integration complexity.

What is self-billing under UAE eInvoicing?

Self-billing is when the buyer is authorized by the seller to issue the invoice. This is distinct from reverse charge. Under UAE eInvoicing, the buyer creates the eInvoice and exchanges the document with the seller; the buyer's ASP reports to the FTA. Self-billing uses a separate PINT-AE Self-Billing specification with a different specification identifier (urn:peppol:pint:selfbilling-1@ae-1). If you use self-billing arrangements, you need the correct spec from your ASP.

How are errors or disputes handled on eInvoices?

There is no concept of invoice cancellation or amendment in UAE eInvoicing. All corrections require issuing a credit note. A credit note reason code is mandatory (from an official code list, not free text), and the preceding invoice reference is mandatory (except for voluntary disclosure with reason code "VD"). Technical rejections by Corner 2, 3, or 5 are based on Schematron validations only; commercial disputes are handled outside the system.

How many validation rules does a UAE eInvoice go through?

Over 250 validation rules run on every single eInvoice before it can be transmitted. Validation happens at three layers: your ASP (Corner 2 or 3) validates all fields against the UAE data dictionary, the receiving ASP validates again independently, and the FTA (Corner 5) performs Schematron validation on the tax data. Rules check data formats, calculations, code lists, cross-field dependencies, and structural integrity. One wrong field format, one missing code, or one calculation error means rejection.

Does Peppol support cross-border eInvoicing?

Yes. The Peppol network is designed for seamless cross-border eInvoicing. Once you are on the network for UAE compliance, you can send and receive invoices with trading partners in Australia, New Zealand, Singapore, Japan, and 30+ other Peppol-connected countries.

How is "revenue" defined for determining my phase?

Revenue is defined as "gross income earned by a Person during the most recent Accounting Period, based on the financial statements." This means gross income, not taxable income and not profit. If your most recent financial statements show gross income of AED 50M or more, you fall under Phase 1 regardless of net profit or VAT-taxable turnover.

What are the ASP appointment deadlines vs go-live dates?

Phase 1 (revenue >= AED 50M): appoint an ASP by 30 October 2026, go live by 1 January 2027. Phase 2 (revenue < AED 50M): appoint an ASP by 31 March 2027, go live by 1 July 2027. Revenue is defined as gross income during the most recent accounting period based on financial statements. Businesses who wish to be early adopters can start testing now.

My business revenue is below AED 50M. Do I still need to comply?

Yes, but on a later timeline. Businesses below AED 50M must select an ASP by 31 March 2027 and go live by 1 July 2027. Starting early gives you more time to test, train staff, and resolve integration issues before penalties apply.

How long does implementation take?

For most businesses, you can be live within days. Standard setup involves connecting your invoice source, configuring your company details, and running a test transmission. Our team handles the Peppol network registration.

Can penalties start before I send my first eInvoice?

Yes. The AED 5,000/month penalty for not appointing an ASP starts from the ASP appointment deadline, not the go-live date. For Phase 1, this means penalties can begin accumulating from 1 November 2026, two months before you need to send your first eInvoice on 1 January 2027. A Phase 1 business that does nothing could face AED 10,000+ in penalties before the first invoice is even due.

What happens if I miss the deadline?

Non-compliance carries tiered penalties under Cabinet Decision 106 of 2025: AED 5,000 per month for failure to implement an Electronic Invoicing System or appoint an ASP, AED 100 per invoice for late transmission (capped at AED 5,000 per calendar month), and AED 1,000 per day for failure to notify the FTA of system failures. The AED 5,000/month cap applies separately to invoices and credit notes, meaning a combined exposure of up to AED 10,000 per month. These penalties apply once your mandatory phase begins.

What are the exact penalties under Cabinet Decision 106 of 2025?

Six violations are defined: (1) failure to implement the system or appoint an ASP: AED 5,000/month. (2) Failure to issue/transmit an eInvoice on time: AED 100/invoice, capped at AED 5,000/calendar month. (3) Failure to issue/transmit an eCredit Note on time: AED 100/credit note, capped at AED 5,000/calendar month. (4) Issuer fails to notify FTA of system failure: AED 1,000/day. (5) Recipient fails to notify FTA of system failure: AED 1,000/day. (6) Failure to notify ASP of data changes: AED 1,000/day. System failure notification must occur within 2 business days.

Does UAE eInvoicing require QR codes?

No. Unlike Saudi Arabia's ZATCA system, the UAE approach does not mandate QR codes on eInvoices. There are also no additional digital signature requirements beyond those supported by the Peppol network. Peppol's PKI (Public Key Infrastructure) is sufficient for signing and encryption.

Must every ASP offer free invoices?

Yes. Every Accredited Service Provider must provide a minimum of 100 eInvoices per year free of charge, per customer. If your business processes fewer than 100 invoices annually, your ASP invoicing costs could be zero. Implementation and onboarding fees are separate and can still apply; the free minimum covers only the invoice transmission itself.

What are the data retention requirements for eInvoicing?

The data retention requirements are consistent with current UAE law, which mandates a retention period of 7 years. The shift to eInvoicing does not change your existing archival obligations. Whatever the VAT law requires continues to apply. Your ASP stores and forwards invoices but long-term archival remains your responsibility.

Do I need to change my ERP system?

No. Calculus integrates with your existing ERP system. You can upload invoices as PDFs or connect via API. We handle the XML conversion, validation, and Peppol transmission.

How do businesses integrate with Calculus?

Multiple integration methods are supported: API integration for automated workflows, SFTP for batch file processing, and direct file upload through our web portal. We support SAP, Oracle, QuickBooks, Xero, Zoho, Tally, and other major ERP systems.

Is Calculus an approved eInvoicing provider?

Yes. Calculus is powered by Taxilla FINOPS 360, which is listed by the UAE Ministry of Finance as an approved eInvoicing Service Provider and a certified Peppol Access Point. Our platform holds AICPA SOC, ISO 27001, ISO 27701, and ISO 9001 certifications.

Can I use Calculus without changing my existing accounting software?

Yes. Calculus is ERP-agnostic and works alongside your current system. If your software can export invoice data in any format (PDF, CSV, JSON, XML), we can ingest it. For businesses without API capability, we support SFTP and manual file upload.

Yes. All data is encrypted in transit and at rest. We never store your invoice data longer than necessary for transmission. Our infrastructure is hosted in the UAE (Dubai Silicon Oasis) and complies with local data residency requirements.

How much does implementation cost?

Implementation costs depend on both the fit gap analysis and integration method selected. This covers onboarding, platform configuration, integration support and staff training. Please reach out to discuss pricing tailored to your organization's needs.

What happens to invoices if the Peppol network is temporarily unavailable?

The platform includes built-in retry logic and queue management. If transmission is temporarily interrupted, invoices are queued and automatically resubmitted once connectivity is restored. No manual intervention required.

What is the difference between Calculus and Taxilla?

Taxilla is our technology partner and an approved UAE eInvoicing ASP. They provide the Peppol-certified platform infrastructure. Calculus is your local implementation partner: we handle onboarding, ERP integration, compliance consulting, and ongoing support. You get global-grade technology with hands-on local service.

We are in a VAT group. Which numbers do we use?

Each member prints the group Tax Registration Number (TRN), which the members share. Each member also has its own 10-digit Tax Identification Number (TIN), and its Peppol ID is built from that own TIN, not the representative member's.

Where do I find our 10-digit TIN?

In your EmaraTax account. It is often the first 10 digits of your TRN, but always confirm it from EmaraTax. In a VAT group, take each member's TIN from its own EmaraTax account, never from the group TRN.

Can we keep our trading name on the letterhead?

Yes, as branding. The seller name sent on the eInvoice must be the legal name exactly as on the trade licence.

Our licence shows a different address from our warehouse. Which one goes on the invoice?

The address on your trade licence. If your licence or your EmaraTax record is out of date, update it before go-live.

Seller details: one legal name, one address, one licence number

Your eInvoice carries your legal name, licence, address and tax numbers as data. Hold one version of each and use it on every document.

In short

Your eInvoice sends your company details as data fields, not as a picture of your letterhead. Agree one legal name, one licensed address, one licence number and your tax numbers. Store them once and use them on every template, letterhead and footer.

Why eInvoicing needs it

A tax invoice must already show the name, address and Tax Registration Number (TRN) of the supplier. eInvoicing turns each of these into a checked field. The Ministry of Finance list of mandatory fields asks for the seller's full formal name as registered, its legal registration identifier and type, its tax identifier, and an address with a street line, a city and a region.

The PINT AE format (the UAE eInvoice standard) then checks them:

The seller address must have address line 1, a city and the emirate, written as a code (AUH, DXB, SHJ, AJM, UAQ, RAK or FUJ).
The seller must give a legal registration identifier. For most companies this is the trade licence number. When the type is a trade licence, the issuing authority's name must be given too.
Your Tax Identification Number (TIN) is 10 digits and starts with 1. Your Peppol ID, the UAE network address each invoice is delivered from and to, is 0235 followed by that TIN.

When the letterhead says one thing and the footer another, nobody can tell which version is your legal identity. Trading names, old names and second addresses cause this most often.

VAT groups. Every member of a VAT group shares the group TRN. Each member keeps its own TIN, and so its own Peppol ID. Your TIN is your company's own number, shown in its own EmaraTax account. It is not the first 10 digits of the group TRN.

What good looks like

An invented example for Al Noor Trading LLC:

Field	Before	After
Legal name	"Al Noor Trading" on the letterhead, "Al Noor General Trading" in the footer	AL NOOR TRADING LLC, exactly as on the licence
Licence	Not printed	Trade licence 123456, Department of Economy and Tourism, Dubai
Address	Warehouse address on one template, office on another	Office 204, Example Building, Al Qusais, Dubai, emirate DXB
P.O. Box	Two different boxes	P.O. Box 12345
TRN	Printed	101010100200003
TIN and Peppol ID	Not known	TIN 1010101002, Peppol ID 0235:1010101002

A P.O. Box is not a street address. Keep one P.O. Box if you like, but the street line, city and emirate must be there.

How to fix it in Tally

Collect your current trade licence and your EmaraTax company details. Check that both show the same legal name and address.
Press Alt+K (Company), choose Alter, and set the company name, address and emirate exactly as licensed. Save with Ctrl+A.
Check that the TRN and TIN in Tally match EmaraTax.
In TallyPrime releases with UAE eInvoicing, press F11 (Company Features) and open the eInvoicing details. Under Agency ID, choose Trade License Number, and enter the licence number and the issuing authority's name.
Print one invoice from each voucher type and check every one shows the same name, address and numbers.

How to fix it in Excel or another system

Create a "Company" sheet that holds each detail once: legal name, licence number, licence authority, address line, city, emirate code, P.O. Box, TRN, TIN, Peppol ID. Example value for emirate: DXB.
Point every template header and footer at those cells. Delete any typed copy of the address.
If you run two companies, keep one Company sheet per entity and one template per entity.

On an ERP, ask your ERP partner to hold these as company constants and send them on every document.

Checklist

The legal name matches the trade licence letter for letter.
The licence number and issuing authority are recorded.
One address with street, city and emirate, the same on every template.
One P.O. Box, if you print one.
The TRN, the 10-digit TIN and the Peppol ID are confirmed from EmaraTax.
In a VAT group, each member uses its own TIN.

The law

VAT Executive Regulation (Cabinet Decision No. 52 of 2017, as amended), Article 59(1)(b): a tax invoice shows the name, address and TRN of the registrant making the supply. https://mof.gov.ae/wp-content/uploads/2025/10/Cabinet-Decision-No.-52-of-2017-of-the-Executive-Regulation-of-the-Federal-Decree-Law-No.-8-of-2017-on-Value-Added-Tax-and-its-amendments.pdf
Ministerial Decision No. 243 of 2025, Article 7: eInvoices carry the data fields the Ministry prescribes. https://mof.gov.ae/wp-content/uploads/2025/09/Ministerial-Decision-no.-243-of-2025-on-the-Electronic-Invoicing-System.pdf
MoF UAE Electronic Invoice mandatory fields V1.0, seller fields (seller name, electronic address, legal registration identifier and type, tax identifier, address line 1, city, country subdivision). https://mof.gov.ae/wp-content/uploads/2026/02/UAE-Electronic-Invoice-mandatory-fields_V-1.0-23Feb2026.pdf
MoF UAE Electronic Invoicing Guidelines V1.1, sections 2 and 3: the TIN, the Peppol ID (0235 plus TIN) and TINs in a tax group. https://mof.gov.ae/wp-content/uploads/2026/06/UAE-Electronic-Invoicing-Guidelines_V-1.1-01June2026.pdf
Peppol PINT AE rules IBR-143-AE (seller address line 1 IBT-035, city IBT-037, subdivision IBT-039), IBR-128-AE (emirate codes), IBR-150-AE (seller legal registration identifier IBT-030), IBR-172-AE (authority name BTAE-12 for a trade licence) and IBR-148-AE (TIN IBT-032, 10 digits). https://docs.peppol.eu/poac/ae/pint-ae/trn-invoice/rule/PINT-jurisdiction-aligned-rules/

General guidance on UAE eInvoicing and VAT as they shape the eInvoice. It is not tax advice for a specific transaction. Last reviewed 2026-10-19.