The UAE e-invoicing pilot opened on 1 July 2026. Telecom and ICT businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider by 30 October 2026 and issue PINT AE invoices over Peppol from 1 January 2027. Consumer subscribers stay out of scope for now — but enterprise and SME accounts, interconnect and wholesale settlements, dealer commissions, managed services contracts, SLA credits, and equipment channel invoicing are all in, at billing-run scale. KGRN delivers end-to-end readiness for telecom and ICT businesses across all seven Emirates.
A practical, telecom-specific assessment of your billing stack, account segmentation, settlement flows, and go-live risk — with a prioritized remediation plan.
Where most UAE telecom and ICT businesses stand today
Telecom billing is the most industrialized invoicing in the economy: rating engines, billing cycles, proration, dunning — millions of documents on schedule. That maturity hides the new problem. From your go-live date, the same billing run splits into two legal regimes: consumer bills continue as today, while every business account — from a two-SIM SME to a thousand-line enterprise — must be issued as structured PINT AE XML, validated by an Accredited Service Provider, exchanged over Peppol, and reported to the Federal Tax Authority in near real time.
And the split is only the start. Telecom's adjustment layer — proration on mid-cycle changes, usage disputes, goodwill credits, SLA penalties — becomes referenced credit and debit notes on business accounts. Interconnect and wholesale settlements, dealer commissions, content revenue shares, and ICT project milestones each carry their own flow.
A telecom or ICT business that cannot segment its account base cleanly — and generate compliant documents at billing-run volume — is not facing a formatting task. It is facing re-engineering inside the most change-controlled system it owns, on a regulatory clock.
Awareness is important. But readiness is what will matter on 1 January 2027.
E-invoicing is not just a finance project. It touches the billing stack, enterprise sales, channel management, wholesale teams, network procurement, and tax compliance — governed by Ministerial Decisions No. 243 and 244 of 2025 (as amended by No. 56 of 2026).
Selecting and appointing an Accredited Service Provider, aligning commercial terms, and completing onboarding with throughput proven at monthly billing-run volumes and month-end settlement peaks.
Segmenting business from consumer accounts across the base, collecting and verifying TINs on every business account, and resolving PINT AE mandatory fields — tax categories, invoice types, references — at line level.
Redesigning adjustment, dispute, SLA credit, and settlement workflows so every correction on a business account becomes a referenced, validated document — at the cadence billing cycles already run.
Defining who owns exceptions, rejection SLAs, archival controls, and reconciliation with VAT returns and Corporate Tax — across operating, infrastructure, and services entities, before go-live.
Operators, ISPs, major integrators, and equipment distributors typically exceed the AED 50 million Phase 1 threshold. Smaller resellers and contractors in Phase 2 face pressure earlier: Phase 1 operators and vendors will e-invoice them from January 2027, and enterprise clients will expect compliant billing as their own receiving obligations arrive.
| Milestone | Date | Who It Affects |
|---|---|---|
| Pilot phase opens | 1 July 2026 | Selected taxpayers, voluntary adoption |
| ASP appointment deadline — Phase 1 | 30 October 2026 | Businesses with revenue ≥ AED 50 million |
| Mandatory go-live — Phase 1 | 1 January 2027 | Businesses with revenue ≥ AED 50 million |
| ASP appointment deadline — Phase 2 | 31 March 2027 | All other businesses |
| Mandatory go-live — Phase 2 | 1 July 2027 | All other businesses |
| Government entities go-live | 1 October 2027 | B2G — critical for telecoms and ICT providers serving government accounts |
The mandate applies to B2B and B2G transactions regardless of VAT registration status. Consumer subscriptions (B2C) are currently excluded until a later phase is announced. International carrier and roaming settlements with overseas operators sit outside the Peppol flow — cross-border telecom charges carry place-of-supply treatment that is mapped per arrangement, with export-treated invoices FTA-reported without exchange.
Under the 5-corner DCTCE model, invoice data travels supplier → their ASP → the buyer's ASP → buyer, with tax data reported to the FTA in near real time. Here is how that maps to telecom and ICT flows:
Each cycle, business accounts generate validated PINT AE XML — subscriptions, usage, devices on installment, one-time charges — while consumer accounts continue under existing VAT invoicing. The segmentation must live in account data and fire automatically at generation, at full billing-engine volume.
Proration on mid-cycle changes, usage dispute resolutions, goodwill credits, and SLA penalty credits on enterprise contracts flow through referenced credit and debit notes tied to the original invoices — replacing account-level adjustments that today never touch a document.
Domestic interconnect, wholesale capacity, MVNO settlements, and fiber or tower arrangements between UAE entities are structured B2B invoices — while international carrier and roaming settlements with overseas operators follow their own treatment outside the Peppol flow, routed automatically per counterparty.
Dealer commissions and incentives, device and recharge distribution invoices, content and VAS revenue-share settlements, and IoT connectivity billing to business customers each become structured flows — with the channel's TIN base collected and settlement statements reconciled against referenced documents.
Managed services, cloud, and systems integration contracts bill milestones and recurring charges as structured invoices; network equipment and contractor invoices arrive inbound and match against POs to protect input VAT recovery at capex scale; and flows between operating, infrastructure, and services entities are e-invoiced like third-party sales.
Telecom invoices are born in the billing stack, not the ERP — and neither needs replacing. KGRN's integration layer connects both to compliance: PINT AE field mapping, UBL 2.1 XML transformation, ASP validation, Peppol transmission, and status write-back — engineered for billing-run volume with the business/consumer split resolved at generation.
Running a dedicated BSS or subscription platform alongside the ERP? KGRN designs the bridge so rated, cycle-generated invoices reach the e-invoicing layer as structured data — without re-engineering the billing engine itself. Call +971 4557 0204.
Billing stacks are the most change-controlled systems in any company — release windows are quarterly, testing is exhaustive, and nobody hot-fixes a rating engine in December. That is precisely why the e-invoicing split cannot be a late addition: the account segmentation, TIN enrichment, and generation-time routing must ride scheduled release cycles that are being planned now.
E-invoicing should be approached as a readiness program across billing operations, enterprise sales, channel, wholesale, and IT — with the business-account TIN campaign started immediately, because it is the longest-lead task in the sector.
Phase 1 telecom and ICT businesses should be in end-to-end testing no later than Q4 2026 to hold the 1 January 2027 go-live.
The earlier the start, the more controlled, informed, and commercially sensible the transition becomes.
A realistic single-entity implementation on a mainstream landscape runs 10–14 weeks. Operators with BSS integration, or groups spanning network, services, and channel entities, need longer — and must align with billing release windows. Another reason to start now.
Flow mapping across enterprise billing, interconnect, channel, and ICT contracts, billing stack and ERP landscape review, account segmentation and TIN audit, entity scoping, gap report with priorities.
PINT AE field mapping, business-account TIN enrichment campaign, generation-time routing design, treatment rules for settlements, credits, and cross-border flows.
Billing-stack and ERP bridges, connector or middleware configuration, credit note automation for adjustments and SLA credits, XML generation and validation, status write-back, exception alerting.
Sandbox testing of every scenario — cycle invoice, proration credit, dispute resolution, interconnect settlement, dealer commission, milestone invoice, intercompany — plus full billing-run volume testing and role-based training.
Controlled cutover aligned to a billing cycle, exception monitoring through the first full runs, channel and enterprise client onboarding support, rejection-rate tracking, transition to managed compliance.
Get your gap report and a fixed-scope proposal within two weeks.
Book a Readiness AssessmentIf you cannot tick at least the first five items today, your timeline is at risk.
Generic e-invoicing rollouts miss the flows that define telecom and ICT. KGRN's playbooks cover them by segment:
The billing-run split at full scale — enterprise and SME accounts as structured invoices each cycle, consumer bills continuing unchanged, interconnect and MVNO settlements structured, and the dealer network made TIN-ready.
Business broadband, leased lines, and satellite capacity billed as recurring structured invoices — with installation charges, SLA credits, and enterprise contract adjustments as referenced documents.
Cloud, data center, cybersecurity, and SI contracts billing milestones and recurring charges — with license resale invoices, support renewals, and project variations flowing as structured, referenced documents.
Tower, fiber, and network rollout contractors billing operators on milestone and unit-rate terms — the construction discipline applied to telecom capex, with subcontractor chains matched inbound.
Device, network hardware, and accessory distribution at volume — dealer invoicing, rebates and sell-through incentives as referenced notes, and recharge distribution flows structured end to end.
Revenue-share settlements with operators, content licensing invoices, and IoT connectivity billed to fleets, utilities, and industry — recurring B2B flows with settlement statements reconciled against structured documents.
An international network for exchanging electronic business documents between accredited access points. Each party connects once — through its service provider — and can exchange documents with any enterprise client, dealer, or vendor on the network.
The UAE's Decentralised CTC and Exchange (DCTCE) model: (1) supplier, (2) supplier's ASP, (3) buyer's ASP, (4) buyer, and (5) the Federal Tax Authority, which receives tax data reported by the ASPs in near real time.
The UAE's invoice data specification — an extension of the Peppol International Invoice on a UBL 2.1 XML foundation, with UAE-specific fields for VAT treatment, invoice type codes, and local regulatory data defined in the Ministry of Finance's Mandatory Fields specification.
An Accredited Service Provider approved by the UAE Ministry of Finance to validate invoices against PINT AE rules, exchange them over Peppol, and report tax data to the FTA. Every in-scope business — operator, integrator, or distributor — must appoint one before its deadline.
The practical takeaway for telecom: your billing engine already generates every document on time, at scale — the work is teaching it which documents are now legal instruments, and giving them a validated route out. That is precisely the scope KGRN delivers.
KGRN delivers workshops, systems integration, and ongoing compliance management wherever your operations, data centers, and channel networks run.
Regional ICT headquarters, integrators, and distributors — Dubai Internet City and free zone technology entities are in scope, with enterprise billing and channel flows at regional-hub scale.
Providers serving government, energy, and enterprise accounts — pair Phase 1 B2B readiness with B2G preparation ahead of the October 2027 government go-live, where telecom's public-sector book is among the largest of any industry.
ICT resellers, infrastructure contractors, and equipment traders — often on mid-market stacks squarely within KGRN's integration experience.
Resellers and IT service firms, many in Phase 2 — but Phase 1 operators and vendors will e-invoice them from January 2027, so inbound readiness comes first.
RAKEZ technology entities and northern-Emirates ICT providers — free zone scope confirmed and routing configured from day one.
East coast connectivity, maritime communications, and ICT suppliers — cross-border arrangements mapped per treatment alongside domestic flows.
SME IT and telecom service businesses, largely Phase 2. Right-sized implementation avoids enterprise pricing for SME needs.
ICT providers serving Al Ain's institutions and enterprises — dual readiness for B2B now and B2G from October 2027.
Direct answers to the questions telecom CFOs, billing operations leads, enterprise sales heads, and IT owners ask most.
KGRN supports operators, ISPs, integrators, and channel businesses in moving from mandate awareness to implementation readiness — not just in theory, but in execution at billing-run scale.
E-invoicing sits at the intersection of FTA compliance and systems integration. KGRN brings chartered accountancy depth in UAE VAT — including cross-border and place-of-supply treatment — alongside hands-on implementation capability. One accountable team, not a software vendor and a tax advisor pointing at each other.
Billing-run segmentation, TIN enrichment campaigns, adjustment and SLA credit automation, interconnect and settlement routing, channel TIN readiness, and BSS-bridge design — the scenarios generic rollouts miss are the core of our methodology.
Readiness assessment, account base audit, billing-stack and ERP integration, full-volume testing, go-live hypercare aligned to billing cycles, and managed compliance — delivered in Dubai, Abu Dhabi, Sharjah, Ajman, RAK, Fujairah, UAQ, and Al Ain.
"Telecom already runs the most industrialized billing in the economy — millions of documents, on schedule, every cycle. E-invoicing doesn't question that machine; it asks one new thing of it: know which documents are now legal instruments, and give them a validated route out. The providers that segment their base and enrich their business accounts now will run January 2027's billing cycle like any other — while others discover their biggest system needs its most delicate change on the tightest clock."
Phase 1 telecom and ICT businesses must appoint an ASP by 30 October 2026 and go live on 1 January 2027 — with billing-stack changes riding release windows planned months ahead, and government accounts moving to B2G from October 2027. Every week of delay compresses testing on the system that generates your entire revenue.
The KGRN Readiness Assessment includes: an account segmentation and TIN quality audit, a flow map across enterprise billing, settlements, and channel, a billing-stack and ERP integration feasibility report aligned to your release calendar, and a phased timeline mapped to your regulatory deadline. Clear, fixed-scope proposal. No obligation.
A KGRN e-invoicing consultant will respond within one business day.
Avoid compliance gaps. Let UAE tax experts help you stay on track.
The UAE is moving toward mandatory e-invoicing. Start preparing your systems, data, and processes before the compliance deadline.