Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian telecom operators must apply Ind AS 115 across two opposite revenue shapes: prepaid recharge proceeds that must sit in unearned revenue and be recognised on consumption, and postpaid bill-cycle recognition. The reconciliation must tie cash recharge inflows to unearned-revenue movement and consumption events, present IUC pass-through gross or net based on principal-vs-agent analysis, withhold Section 393 payment code 1002 TDS on enterprise postpaid, evaluate Section 9(5) CGST where the operator intermediates third-party services, and discharge 18 percent GST on telecom services across both streams.
For prepaid: recognise the recharge inflow as a contract liability under Ind AS 115; track consumption per subscriber against the recharge balance; release the liability to revenue as minutes, data and validity are consumed; recognise the residual at validity expiry; for postpaid: bill on cycle and recognise revenue for committed services delivered; apply principal-vs-agent analysis on IUC pass-through and present revenue gross or net consistently; withhold Section 393 code 1002 TDS at 2 percent on enterprise postpaid net of GST and tie to Form 26AS credit by customer PAN; evaluate Section 9(5) CGST for any third-party digital services intermediated through the operator's platform; discharge 18 percent GST on telecom services.
Subscriber master with prepaid vs postpaid tag and contract terms; recharge ledger with unearned-revenue posting; consumption ingestion from billing platform; postpaid bill-cycle calendar; Ind AS 115 principal-vs-agent IUC policy; Section 393 code 1002 TDS rule on enterprise customers; Form 26AS reconciliation by customer PAN; Section 9(5) CGST scope assessment for intermediated services; 18 percent GST classification for telecom service.
A reconciled telecom revenue position showing prepaid recharge inflow tied to unearned-revenue liability movement and consumption release, postpaid bill-cycle revenue tied to receivables and collections, IUC presentation gross or net per the principal-vs-agent policy, enterprise Section 393 code 1002 TDS receivable per customer tied to Form 26AS, and 18 percent GST output liability tied to GSTR-1 and GSTR-3B.
Indian telecom revenue is conceptually simple at the meter — minutes used, data consumed, plan rental paid — but accounting-shaped revenue lives in a different place under Ind AS 115. Prepaid recharge cash is not revenue; it is a contract liability. Postpaid bill-cycle revenue is straightforward but layered with TDS and ITC pass-through. IUC — the cost paid to other carriers — interacts with whether revenue is presented gross or net. And enterprise postpaid customers withhold Section 393 payment code 1002 TDS on every invoice. This is prepaid postpaid revenue recognition telecom India.
Quick reference
| Stream | Recognition trigger | Standard anchor | Reconciliation anchor |
|---|---|---|---|
| Prepaid recharge | Consumption of minutes, data, validity | Ind AS 115 contract liability | Unearned revenue ledger to consumption |
| Postpaid bill cycle | Service delivered in cycle | Ind AS 115 performance obligation | Bill cycle to receivable |
| IUC pass-through | Cost of service (typically gross presentation) | Ind AS 115 principal-vs-agent | Policy disclosure |
| Enterprise postpaid TDS | Section 393 code 1002 at 2 percent | Income Tax Act 2025 | Form 26AS by customer PAN |
| GST on telecom service | 18 percent on supply | CGST Act | GSTR-1 to GSTR-3B |
Prepaid — recharge to unearned revenue
A subscriber recharges Rs 299 for a 28-day pack with 1.5 GB per day and unlimited voice. The Rs 299 received is not revenue at the point of sale. Under Ind AS 115, the operator records a contract liability (unearned revenue) of Rs 299, and recognises revenue as the performance obligation is satisfied:
- Voice consumption: as calls are made (ratable across the validity if unlimited),
- Data consumption: as data is consumed against the daily 1.5 GB allowance,
- Validity-only or unutilised: ratably over the 28-day window and the residual at expiry.
The reconciliation ties the recharge inflow to the unearned-revenue movement and the consumption events to revenue release. At any given balance-sheet date, the operator carries a large unearned revenue liability — the sum of unconsumed balances across the entire prepaid base — that must be reconciled.
Postpaid — bill-cycle recognition
Postpaid revenue is straightforward by comparison. The performance obligation is satisfied in the billing cycle: rental for the plan, included minutes and data consumed, and any usage above the included quota. The invoice is raised at cycle close, the trade receivable is recognised, and revenue is recognised at the same time — there is no large contract liability sitting on the balance sheet, only a receivable from billing to collection.
IUC pass-through — principal or agent?
IUC paid to other carriers for terminating outbound traffic is an input cost. Under Ind AS 115 principal-vs-agent analysis, the operator typically acts as principal for the end-subscriber’s voice service — it controls the service before transferring it, sets the tariff, and bears the credit risk — so revenue is presented gross with IUC as cost of service. Some specific pass-through items (selected value-added services where the operator clearly acts as agent) may be presented net. The classification must be consistent and disclosed in the accounting policy note. The mechanics of the IUC reconciliation feed the cost-of-service line.
Section 393 code 1002 — enterprise postpaid TDS
When the customer is a tax deductor — a company, firm, LLP, or other entity subject to TDS — paying for telecom services as a contractual service, Section 393 of the Income Tax Act 2025, payment code 1002 (which replaced legacy Section 194C) applies. The customer withholds at 2 percent on the invoice value net of GST. The operator’s revenue ledger must reconcile gross billed against net received plus TDS credited in Form 26AS by customer PAN — gaps here are working-capital leakage if the credit is delayed beyond the quarterly TDS return cycle. Retail postpaid to individual subscribers does not trigger TDS.
Quantify the postpaid TDS receivable drag
Size the unrecovered TDS and chase hours from delayed enterprise customer 26AS credits.
Open the three-way match cost calculatorSection 9(5) CGST — relevance to telecom
Section 9(5) of the CGST Act creates an electronic commerce operator GST liability for specified services supplied through the operator’s platform — primarily restaurants, transport, and accommodation. It is not the primary regime for telecom voice and data, which the operator supplies in its own name at 18 percent. Where a telecom operator runs a mobile marketplace or app store intermediating third-party digital services, the Section 9(5) considerations for that sub-stream must be evaluated separately, and that sub-stream’s revenue accounting is principal-vs-agent analysed under Ind AS 115 in its own right.
Worked example — month-end position
A mid-size operator at month end:
- Prepaid recharges in the month: Rs 480 crore inflow. Consumption in the month against current and prior recharge balances releases Rs 472 crore to revenue. Unearned revenue increases by Rs 8 crore net.
- Postpaid bill cycle: Rs 210 crore billed. Of this, Rs 38 crore is to enterprise customers withholding Section 393 code 1002 TDS — Rs 64 lakh TDS deposited and reflected in 26AS by customer PAN by the quarter close.
- IUC outbound to other carriers: Rs 88 crore — presented as cost of service under the gross-revenue policy.
- GST output liability: 18 percent on the recognised telecom service revenue, tied to GSTR-1 outward and GSTR-3B 3.1(a) lines.
Where revenue recognition sits in the telecom surface
Revenue recognition is the upstream view; IUC reconciliation, MPLS billing, and tower infrastructure revenue are the downstream cost and infrastructure-revenue views. The TRAI tariff and consumer-protection framework shapes the validity rules that decide unearned-revenue release at the Telecom Regulatory Authority of India.
What automated reconciliation changes
Prepaid unearned-revenue movement involves hundreds of crores of recharge transactions per month and consumption events that must be netted at subscriber level for the contract-liability movement to be correct. Manual close cannot tie this — and the audit risk on Ind AS 115 contract-liability presentation is material. Purpose-built reconciliation software India ingests recharge inflow, consumption events from the billing platform, postpaid bill cycle and collection, and Form 26AS credit, and produces the unearned-revenue movement, the postpaid TDS receivable position, and the GST output liability — all reconciled against the GL. For the GST side, see GST reconciliation software.