The UAE has made electronic invoicing mandatory for all B2B and B2G transactions under Ministerial Decisions No. 243 and No. 244 of 2025, issued by the Ministry of Finance on 29 September 2025. The system requires all invoices to be structured XML documents transmitted through a Ministry-accredited Accredited Service Provider (ASP) on the Peppol network — PDFs no longer qualify.
For construction, manufacturing, and distribution businesses, compliance is not straightforward. Progress billing, retention releases, subcontractor flows, high-volume dispatch invoices, intercompany transactions, and mixed B2B/B2C models each carry specific obligations that standard compliance guides do not address. This article sets out what those businesses must know and do before their deadline.
Compliance Timeline and Revenue Thresholds
The mandate rolls out in phases based on annual revenue:
| Phase | Revenue Threshold | ASP Appointment Deadline | Mandatory Go-Live |
| Phase 1 | ≥ AED 50 million/year | 30 October 2026 | 1 January 2027 |
| Phase 2 (SMEs) | < AED 50 million/year | 31 March 2027 | 1 July 2027 |
| Government Entities | All in-scope | 31 March 2027 | 1 October 2027 |
| Voluntary Pilot | Any qualifying business | — | From 1 July 2026 |
The MoF extended the Wave 1 ASP appointment deadline from 31 July 2026 to 30 October 2026 on 10 May 2026. The go-live date of 1 January 2027 remains unchanged. For a full breakdown of all key dates and the associated penalty exposure at each stage, see the UAE e-invoicing compliance timelines and penalties guide.
Three scope rules that catch businesses off guard: the mandate applies regardless of VAT registration status; zero-rated B2B/B2G exports remain in scope; and B2C transactions are currently excluded. Intra-group transactions within the same VAT group have a 24-month grace period from 1 January 2027.
Technical Standard: PINT AE
PINT AE is the UAE’s official e-invoice data dictionary, built on Peppol BIS Billing 3.0 and UBL 2.1. The UAE Electronic Invoice Mandatory Fields v1.0, published by the FTA on 23 February 2026, defines the full field requirements. A standard tax invoice requires approximately 50 mandatory fields. The full schema contains 135+ elements split into mandatory, conditional, and optional categories.
Key mandatory fields include: invoice number and date, invoice type code (IBT-003), seller and buyer TRNs and legal identifiers (EID, PAS, CD), line-level quantity, unit price, tax category and rate, AED-equivalent amounts for foreign currency transactions, and transaction flags for free zone supplies, margin scheme, and deemed supply where applicable.
The EIS supports six document types: Electronic Tax Invoice, Electronic Tax Credit Note, Electronic Tax Debit Note, Commercial Electronic Invoice, Self-Billed Electronic Tax Invoice, and Self-Billed Electronic Tax Credit Note. Electronic signatures are not required. E-invoices must be retained for 7 years.
Industry-Specific Compliance: Construction
Construction businesses face billing structures that do not map cleanly to a standard single-supply invoice model.
Progress billing
Each Interim Payment Certificate (IPC) is a separate taxable event requiring its own compliant XML e-invoice. Treating a progress claim as a single annual summary is not valid.
Retention release
Retention is a separate taxable supply at the point of release, not at the point of the original contract value. Businesses must configure their ERP or billing system to trigger a distinct e-invoice when retention is released, which may be months or years after project completion.
Variation orders
Any change to contract value requires either a new invoice or a debit/credit note in PINT AE format. Manual adjustments or revised PDFs are non-compliant.
Subcontractor invoice receipt
Main contractors must be capable of receiving PINT AE-compliant XML e-invoices from all subcontractors. If a subcontractor is not EIS-capable, the main contractor’s AP process breaks. Updating subcontractor agreements now — before the go-live date — is critical.
Joint ventures and consortia
Each legal entity in a JV must have its own TRN and ASP connection. The invoicing entity must be defined clearly in the JV agreement.
Industry-Specific Compliance: Manufacturing
Manufacturing businesses typically face high invoice volumes, intercompany billing complexity, and cross-border supply chains.
High-volume dispatch
Manufacturers converting hundreds or thousands of delivery notes to invoices daily need ERP-to-ASP integration that supports batch XML generation. Web portal entry via an ASP is not viable at this volume.
Deemed supply
When goods are removed from business use (e.g., samples, personal use by employees), a deemed supply is triggered. The PINT AE mandatory fields document requires a specific transaction flag for deemed supply. This is a common gap in ERP configurations.
Intercompany transactions
Invoices between a manufacturing entity and its distribution subsidiary are in-scope B2B transactions. Both entities must be EIS-capable. The 24-month intra-group grace period applies only to entities within the same UAE VAT group.
Multi-currency invoices
PINT AE requires AED-equivalent amounts alongside any foreign currency line items. ERP systems that currently record only USD or EUR values need reconfiguration.
Zero-rated exports
A zero-rated invoice to an overseas B2B buyer still passes through the EIS. The tax category is zero-rated, not exempt, and the invoice must carry the correct PINT AE tax code.
Industry-Specific Compliance: Distribution
Distribution businesses often combine high invoice frequency with mixed B2B/B2C customer bases and agency or logistics arrangements.
B2B/B2C segregation
B2C transactions are excluded from the mandate; B2B transactions are not. Businesses with mixed customer bases must correctly classify every customer account in their ERP master data. Misclassification is a direct compliance risk.
Agency and commission invoicing
Where an agent invoices on behalf of a principal, the arrangement must be mapped to either a self-billed invoice or a principal-issued invoice in PINT AE format. Existing contractual arrangements may need to be reviewed.
Credit notes for returns
High-volume return processing requires Electronic Tax Credit Note workflows. Each credit note must carry the same PINT AE field set as the original invoice.
Logistics provider invoicing
Third-party logistics providers who invoice for warehousing or transport are in scope if those are B2B transactions. Vendor onboarding processes should verify that all logistics providers can issue PINT AE-compliant e-invoices before the mandatory date.
Penalties for Non-Compliance
Penalties are defined under Cabinet Decision No. 106 of 2025:
- AED 5,000 per month for failing to implement the EIS or appoint an ASP
- AED 100 per invoice or credit note not transmitted as required, capped at AED 5,000 per month
- AED 1,000 per day for failing to report a system malfunction to the FTA within 2 business days
- Up to AED 20,000 for repeated violations
Businesses that adopt e-invoicing voluntarily before their mandatory date are not subject to these penalties during the pilot phase.
Pre-Compliance Checklist
Assessment
- Confirm annual revenue against the AED 50 million threshold using audited financials
- Identify all in-scope legal entities, TRNs, and transaction types
- Audit invoice types: progress billing, retention, variation, intercompany, credit/debit notes
- Map existing invoice fields against PINT AE mandatory fields; identify data gaps
System readiness
- Select an MoF-accredited ASP; check the official MoF e-invoicing programme for the current accredited provider list
- Configure ERP for PINT AE XML output covering all mandatory fields
- Enable AED-equivalent currency conversion for multi-currency transactions
- Set transaction flags: free zone, margin scheme, deemed supply, reverse charge
- Establish a 7-year electronic archiving
Testing and go-live
- Run end-to-end tests in the ASP sandbox environment
- Test all document types: tax invoice, credit note, debit note, self-billed variants
- Test subcontractor inbound e-invoice receipt (construction)
- Test high-volume batch transmission (manufacturing/distribution)
- Train AP and AR teams; update supplier and subcontractor agreements
Key Takeaways
- PDF invoices are no longer valid for B2B or B2G transactions; only structured XML via an accredited ASP qualifies.
- Wave 1 businesses (≥ AED 50 million revenue) must appoint an ASP by 30 October 2026 and go live by 1 January 2027.
- PINT AE requires ~50 mandatory fields per standard tax invoice; the full schema has 135+ elements.
- Construction: progress billing, retention release, and variation orders each require a distinct e-invoice event, not a single annual invoice.
- Manufacturing: deemed supply flags, AED-equivalent amounts, and intercompany invoice flows are the most common configuration gaps.
- Distribution: B2B/B2C segregation in ERP master data is a prerequisite; agency and logistics invoice arrangements must be reviewed.
- Non-compliance costs AED 5,000/month plus AED 100 per non-conforming invoice from the mandatory go-live date.
- Voluntary adoption from 1 July 2026 is penalty-free and recommended for businesses with complex billing structures.
Frequently Asked Questions
Does UAE e-invoicing apply to construction companies that are not VAT-registered?
Yes. The mandate applies to any business conducting B2B or B2G transactions in the UAE, regardless of VAT registration status. A construction firm issuing invoices to a developer or government entity is in scope even without a Tax Registration Number.
Does each progress billing claim need a separate e-invoice?
Yes. Each Interim Payment Certificate represents a distinct taxable supply. A single consolidated invoice at project completion does not satisfy the requirement. Each IPC must be issued as a separate XML e-invoice through the EIS at the time of the billing event.
Are subcontractor invoices received by the main contractor subject to e-invoicing?
Yes. The obligation runs in both directions. Main contractors must be capable of receiving PINT AE-compliant XML e-invoices from all subcontractors. If a subcontractor cannot issue a compliant e-invoice, it is the main contractor’s AP process — and potentially its input tax recovery — that is affected.
Do manufacturing companies need e-invoicing for intercompany transactions between group entities?
Yes, with a qualification. Intercompany B2B invoices between separate legal entities are in scope. However, transactions between entities within the same UAE VAT group benefit from a 24-month grace period starting 1 January 2027. Businesses should confirm their VAT grouping status before assuming the grace period applies.
Can distribution companies exclude B2C customers from the EIS?
B2C transactions are currently excluded from the mandate, so those invoices do not need to pass through the EIS. However, businesses with mixed B2B and B2C customer bases must correctly classify every account in their ERP master data. Issuing an EIS-format invoice to a B2C customer is not a violation, but failing to issue one to a B2B customer is.
What is the penalty if a manufacturer misses the January 2027 go-live without appointing an ASP?
The penalty is AED 5,000 per month for failing to implement the EIS or appoint an ASP — recurring each month until compliance is achieved. Separately, each invoice not transmitted through the EIS after the mandatory date carries an AED 100 penalty, capped at AED 5,000 per month. These two penalties can run concurrently.
Is a PDF invoice acceptable if it is generated from an ERP system?
No. The EIS requires structured XML invoices conforming to the PINT AE schema, transmitted through an accredited ASP. A PDF — regardless of how it is produced or sent — is not a valid e-invoice under the UAE framework from the mandatory go-live date.
Primary sources: UAE Ministry of Finance — Ministerial Decisions No. 243 and 244 of 2025 | FTA Mandatory Fields v1.0 (PDF) | MoF E-Invoicing Programme (PDF)
