Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian telecom operators settle billions of inter-carrier minutes every month under TRAI's IUC tariff framework, with mobile-to-mobile termination at Rs 0.06 per minute post-BAK and asymmetric rates for fixed-line and international traffic. The reconciliation must tie Call Detail Records (CDRs) carrier by carrier, net bilateral positions, apply 18% GST on the supply, run reverse charge for international inbound IUC, and withhold Section 393 payment code 1002 TDS on Indian carrier settlements — across CDR-count, rate-applied, traffic-classification and dispute-ageing variance streams.
Aggregate originated and terminated CDRs by peer carrier and traffic type (M2M, F2M, M2F, intra-LSA, STD, ILD-inbound); apply the TRAI-mandated termination rate per traffic class; net the bilateral position; raise/receive the inter-operator invoice with 18% GST; tie to GSTR-2B for the receiving side and discharge reverse-charge GST for international inbound IUC; withhold Section 393 payment code 1002 TDS on Indian carrier payouts and Section 413 code 1062 on foreign carrier remittances with DTAA documentation; age disputed minutes within the bilateral SLA window.
Peer-carrier master with bilateral SLA windows; TRAI tariff-rate table by traffic class and effective date; CDR ingestion from MSC/switch with traffic-classification tags; bilateral netting ledger; GST classification with reverse-charge flag for ILD inbound; Section 393 code 1002 and Section 413 code 1062 TDS withholding rules; dispute register with ageing and write-back trigger.
A reconciled IUC settlement dashboard showing originated-vs-terminated CDR ties per peer carrier per traffic class, applied-rate validation against TRAI tariff, netted bilateral position, GST charged and ITC claimed, reverse-charge discharge on ILD inbound, Section 393 code 1002 / Section 413 code 1062 TDS withholding, and a dispute-ageing view that feeds the suspense write-back decision.
An Indian telecom operator handling 8 billion outbound and 7.6 billion inbound minutes a month settles IUC with roughly 12 active peer operators — three private mobile operators, two PSU operators (BSNL and MTNL), several fixed-line LDOs, and the international ILD carriers. The IUC settlement file is the second-largest line on the network-operations finance close, behind only revenue. This is telecom IUC reconciliation India — where the regulator (TRAI) sets the rate, the switch (MSC) writes the evidence, and the variance lives in the gap between two operators’ counts of the same call.
Quick reference
| IUC layer | What it covers | Regulator anchor | Reconciliation anchor |
|---|---|---|---|
| Mobile-to-mobile (M2M) | Termination of M2M voice | TRAI Telecom Interconnection (Charges) Order | CDR count + rate per minute |
| Fixed-to-mobile (F2M) | F2M voice termination | TRAI tariff order | CDR count + asymmetric rate |
| Mobile-to-fixed (M2F) | M2F voice termination | TRAI tariff order | CDR count + landline-side rate |
| ILD inbound | International inbound voice | TRAI ILDO interconnection regulation | Foreign carrier settlement file |
| GST on IUC | Telecom service supply | CGST Act, 18 percent | Inter-operator tax invoice; reverse charge on ILD inbound |
| Settlement TDS | Carrier payout withholding | Income Tax Act 2025 | Section 393 code 1002 (domestic); Section 413 code 1062 (foreign) |
How IUC is set in India
TRAI sets IUC through periodic Telecom Interconnection (Charges) Orders. The mobile-to-mobile termination charge moved through a phased reduction to Rs 0.06 per minute as the post-BAK (Bill-and-Keep) transition rate, with fixed-line and ILD legs carrying their own asymmetric rates. For carrier finance teams, the rate table is not the difficulty — the difficulty is proving, every month, that the rate was correctly applied to the right minutes in the right traffic class against the right peer.
CDR aggregation — the evidence layer
Every voice call writes a CDR at the originating MSC and another at the terminating MSC. The reconciliation aggregates CDRs by peer carrier, by traffic class (M2M, F2M, M2F, intra-LSA, STD, ILD inbound), and by billing period. The two sides — originated minutes claimed by the originating operator and terminated minutes claimed by the receiving operator — should tie. They rarely tie perfectly. Switch-clock drift, dropped CDRs at one node, and re-classification of a call as voice vs VoIP all create gaps. The bilateral SLA defines the tolerance band and the dispute window.
Bilateral netting
For each peer carrier, the reconciliation nets the two-way position: minutes A originated and B terminated (A owes B) less minutes B originated and A terminated (B owes A), at the TRAI-mandated termination rate for each traffic class. The net amount becomes the settlement payable or receivable. A monthly settlement file carries the accepted minutes, the disputed minutes flagged for the bilateral dispute process, and the GST and TDS treatment for the net.
GST on IUC — and reverse charge on ILD inbound
IUC is a taxable supply of telecommunication service. The terminating operator raises a tax invoice for the settlement amount with 18 percent GST. The originating operator avails ITC subject to the usual conditions and the GSTR-2B entry. For international inbound IUC paid to a foreign carrier, the Indian operator is the recipient of an import of service and discharges GST under reverse charge at 18 percent, then claims ITC — the reverse-charge entry must be reconciled to the GSTR-3B 3.1(d) and 4(A)(3) lines.
Section 393 code 1002 — TDS on domestic settlement
Settlement payouts to another Indian operator are payments for telecom termination services and fall under Section 393 of the Income Tax Act 2025, payment code 1002 (replacing legacy Section 194C). TDS is withheld on the settlement amount net of GST, typically at 2 percent for company deductees. For settlement to a foreign carrier, Section 413 payment code 1062 (replacing Section 195) applies, with chargeability determined under the relevant DTAA and the no-PE / TRC documentation file. Mechanics of the 393 framework are covered in the payment code 1002 article and the Section 413 code 1062 article.
Quantify the IUC dispute drag in rupees and analyst hours
The same three-way logic that finds AP exception cost surfaces the inter-operator dispute drag — open minutes, ageing buckets, and the analyst hours to clear them.
Open the three-way match cost calculatorWorked example — settlement with one peer mobile operator
Take settlement with one peer mobile operator for a month:
- Operator A originates 1.42 crore minutes M2M to Operator B. At the BAK transition rate of Rs 0.06 per minute, the payable from A to B is Rs 85.2 lakh.
- Operator B originates 1.06 crore minutes M2M to Operator A. At the same Rs 0.06 per minute, the payable from B to A is Rs 63.6 lakh.
- Net: A owes B Rs 21.6 lakh.
- Disputed minutes: 4 lakh minutes A claims it terminated for B but B does not concede (CDR-count gap, in suspense within the 30-day bilateral SLA).
- GST: B raises a tax invoice on A for Rs 21.6 lakh plus 18 percent GST of Rs 3.89 lakh, total Rs 25.49 lakh.
- TDS: A withholds Section 393 payment code 1002 TDS at 2 percent on the Rs 21.6 lakh service value, which is Rs 43,200, and pays B the net plus GST.
- Recon outcome: A’s books show Rs 21.6 lakh IUC expense, Rs 3.89 lakh ITC claimed against GSTR-2B, Rs 43,200 TDS payable to the credit of B’s PAN under code 1002, and a Rs 4 lakh open dispute that must close before the SLA window expires or convert to a credit note.
Where IUC sits in the telecom reconciliation surface
IUC settlement is one of four reconciliation rails an Indian telecom operator runs — alongside ILD international carrier settlement, enterprise MPLS circuit billing, and prepaid and postpaid revenue recognition under Ind AS 115. The IUC reconciliation feeds the cost-of-revenue line and consumes ITC on inter-operator invoices. The TRAI tariff orders and IUC framework are documented at the Telecom Regulatory Authority of India.
What automated reconciliation changes
CDR volumes — billions of records a month — make manual carrier-wise reconciliation infeasible. The variance lives at the CDR-class level, not the aggregate, and aggregate-only ties hide misclassification and rate-application errors. Purpose-built reconciliation software India ingests CDRs from the MSC switch, aggregates by peer carrier and traffic class, applies the TRAI tariff-rate table by effective date, runs the bilateral netting, and produces audit-ready inter-operator invoice, GST reverse-charge, and Section 393 code 1002 TDS evidence. Match-rate outcomes on live customer data: 51 percent to 88 percent. For the GST side specifically, see GST reconciliation software.