VAT Telecom Calculation in the UAE: Billing Guide

Telecom is high-volume standard-rated supply: postpaid bills, prepaid usage, handset sales, and enterprise contracts all at 5%. Consumer-facing prices are VAT-inclusive — the AED 100 monthly plan includes the VAT — so the operator extracts output VAT at 5/105 from billing runs. Enterprise contracts are usually VAT-exclusive, with 5% added on the invoice.

Prepaid vouchers follow the voucher rules: a single-purpose voucher (fixed credit for the operator's own services) is taxed at sale; a multi-purpose voucher's VAT waits until redemption. In practice, most telecom credit behaves as single-purpose — VAT on the top-up. Roaming needs the place-of-supply analysis: the operator's roaming charges to its own subscribers are generally UAE supplies (the subscriber is here), while wholesale roaming settlements between operators follow telecom-specific rules. Handsets sold with plans are goods at 5% — the instalment plan for the handset is a goods supply, not a service.

An operator's consumer postpaid billing run totals AED 100,000 VAT-inclusive for the month, plus AED 20,000 of VAT-exclusive enterprise invoices.

Verify: 100,000 × 5 ÷ 105 = 4,761.905 → AED 4,761.90; net 95,238.10. Enterprise: 20,000 × 0.05 = AED 1,000. Total output VAT AED 5,761.90 on AED 115,238.10 net revenue. The two streams must never be blended into one extraction: the inclusive stream extracts at 5/105, the exclusive stream adds at 5% — blending them misstates both. The billing system's stream flags are the VAT control.

• Blending inclusive and exclusive streams. One extraction rate for both misstates the VAT — keep the streams separate.
• Prepaid timing errors. Single-purpose top-ups are taxed at sale; waiting until usage understates the period.
• Handset instalments as services. The handset is goods at 5% — its VAT treatment follows the goods, not the plan.
• Roaming assumptions. Apply the place-of-supply analysis per roaming product; 'all roaming is the same' is wrong.

Build the VAT extraction into the billing system per stream — manual extraction on millions of records is not viable. Reconcile the billing VAT to the general ledger and to the return monthly; the three must agree to the fils. Keep the voucher classification documented (single vs multi-purpose) and the roaming product analysis per product. Test the extraction quarterly on a sample of bills recomputed by hand. Given the volumes, even a 0.01% systematic error is material — precision is the whole game. Keep a VAT control file per billing run: records billed, gross, VAT extracted, net, and the ledger posting — signed off before the return is filed. Any billing-system upgrade or tariff migration needs a VAT regression test: rerun the extraction on a sample and compare to hand computation before the new system goes live. And archive the billing data for the statutory retention period — reconstructing a billing run years later from summaries is not possible, and the FTA can ask.

A customer takes a AED 2,100 handset on 12 instalments of AED 175 with a AED 100/month plan. The handset is goods: VAT of 2,100 × 5 ÷ 105 = AED 100 is due on the supply of the handset — normally at the start (the goods are delivered), not spread across instalments, unless the contract genuinely structures it as separate periodic supplies. The plan is services: AED 100/month inclusive carries VAT of 100 × 5 ÷ 105 = AED 4.76 per month. Total first-month VAT: 100 + 4.76 = AED 104.76. The common error is spreading the handset VAT across the 12 months — the tax point for goods is delivery, so the 100 belongs to month one. Contract wording decides edge cases, so the VAT team should review plan terms before launch, not after.