Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian enterprises run MPLS WAN across multiple telecom vendors (BSNL, Airtel, Tata Communications, Reliance Jio) with hundreds of circuits, hub-vs-spoke pricing, uptime SLAs and tiered penalty credits, and contractual one-time install charges. The reconciliation must tie circuit inventory against vendor invoices, compute SLA penalty credits from downtime evidence, validate hub-vs-spoke rate application, apply 18 percent GST and Section 393 payment code 1002 TDS, and recover SLA credits through Section 34 CGST credit notes within the 30 September following-FY deadline.
Maintain a circuit master with site, vendor, bandwidth, contract rate, hub-vs-spoke tier, install date and SLA threshold; ingest vendor invoices and validate each circuit-line against the master; ingest downtime evidence from NOC ticket logs and monitoring data; compute SLA penalty credits against the contractual tier table; flag misbilled circuits (decommissioned but still billed, wrong bandwidth, wrong tier); apply Section 393 code 1002 TDS at 2 percent on the service value net of GST; track Section 34 CGST credit notes for SLA credits within the 30 September window and reverse Rule 42 ITC.
Multi-vendor circuit master with contract terms; SLA tier table per contract with downtime thresholds and credit percentages; NOC downtime ingestion; install-charge amortisation schedule per Ind AS 116 where applicable; GST 18 percent service classification; Section 393 code 1002 withholding rule; Section 34 CGST credit note tracker with 30 September deadline; Rule 42 ITC reversal logic.
A reconciled MPLS billing dashboard showing circuit-by-circuit invoice tie against the master, SLA-credit-eligible downtime per circuit, applied vs contractual rate validation per hub/spoke tier, decommissioned-but-billed flags, Section 393 code 1002 TDS withheld, and Section 34 CGST credit notes claimed with Rule 42 ITC reversal — feeding the WAN cost-of-operations close and the GST 3B.
A large Indian enterprise — a financial services major with 612 branch and depot sites — runs MPLS WAN across four telecom vendors: Tata Communications on the metro and tier-1 footprint, Airtel on tier-2 and tier-3, BSNL on rural and tier-4 sites where no private vendor has last-mile, and Reliance Jio on the newer JioBusiness build-out. Every month, four invoice files arrive with roughly 600 circuit lines, four NOC downtime files arrive, and the reconciliation must produce a single payable position per vendor — net of SLA penalty credits — within the close. This is MPLS circuit billing reconciliation India.
Quick reference
| MPLS rail | What it covers | Vendor examples | Reconciliation anchor |
|---|---|---|---|
| Circuit inventory | Active sites, bandwidth, contract rate | BSNL, Airtel, Tata Comm, Reliance Jio | Circuit master |
| Hub-vs-spoke pricing | Hub bandwidth and port charges vs spoke bundled rental | All vendors | Contract tier table |
| Uptime SLA | 99.5 percent or 99.9 percent monthly uptime threshold | All vendors | NOC downtime log + tier table |
| GST on service | 18 percent on circuit charges | CGST Act | Vendor invoice + GSTR-2B |
| Service TDS | Section 393 code 1002 at 2 percent | Income Tax Act 2025 | Net of GST |
| SLA credit recovery | Section 34 CGST credit note | CGST Act | 30 September following FY deadline |
The circuit master is the anchor
The reconciliation cannot start without an accurate circuit master: site code, vendor, bandwidth, hub-vs-spoke tier, contract rate, install date, decommission date (if any), and SLA threshold. The master decides whether each invoice line is valid, whether the rate applied matches the contract, and whether a decommissioned circuit is still being billed. For an enterprise of 612 sites, the master typically carries 30 to 50 lifecycle events per month — installs, upgrades, decommissions, vendor swaps — that have to be tied back into the master before reconciliation runs.
Hub-vs-spoke pricing
An MPLS WAN is shaped as a star: a hub at the data centre or HQ at high bandwidth (typically 100 Mbps to 1 Gbps), and spokes at branches and depots at lower bandwidth (typically 2 Mbps to 20 Mbps). Hub pricing carries a port charge, an access charge, and a per-Mbps bandwidth rental; spoke pricing is typically bundled. The reconciliation must validate the tier of every circuit before it validates the rate — applying a hub rate to a spoke circuit, or vice versa, is a common misbilling pattern.
SLA penalty credits
Each circuit carries an uptime SLA — commonly 99.5 percent or 99.9 percent on the monthly bandwidth window — with a tiered penalty credit table for breaches:
- Uptime 99.0 percent to 99.5 percent: 5 percent credit on monthly rental
- Uptime 98.0 percent to 99.0 percent: 10 percent credit
- Uptime below 98.0 percent: 25 percent credit or higher per contract
The reconciliation ties the vendor’s NOC ticket log against the enterprise’s own monitoring data, settles on the accepted downtime per circuit, and applies the tier table. Disputed downtime — vendor logged 3 hours but enterprise monitoring shows 7 hours — sits in a dispute register with a contractual closure window.
Section 393 code 1002 — service TDS
Circuit charges paid to an Indian telecom service provider are payments for services and fall under Section 393 of the Income Tax Act 2025, payment code 1002 (which replaced legacy Section 194C). TDS is withheld at 2 percent for company deductees on the invoice value net of GST. For cross-border leg paid to a foreign provider, Section 413 payment code 1062 applies. Mechanics of the framework are covered in the Section 393 framework article.
Quantify the MPLS billing exception cost
Decommissioned-but-billed circuits, wrong-tier rates, and unrecovered SLA credits map cleanly onto the three-way match exception model.
Open the three-way match cost calculatorRecovering the SLA credit via Section 34 CGST
The enterprise does not short-pay the invoice. Instead, under Section 34 of the CGST Act, the vendor issues a credit note for the SLA credit amount with GST reversed at 18 percent. The enterprise reverses the corresponding ITC under Rule 42 if originally claimed in full. The credit note must be issued by 30 September following the financial year of the original invoice — beyond that window, the GST element is unrecoverable and the credit becomes a P&L recovery only. A persistent failure pattern is enterprises that flag SLA credits in the operating ledger but never trigger the credit note request — and lose the GST 18 percent line after the September deadline.
Worked example — one branch site for one month
Take one tier-2 branch site on Airtel MPLS:
- Contract: 10 Mbps spoke, monthly rental Rs 18,000, SLA 99.5 percent.
- Invoice: Rs 18,000 plus 18 percent GST of Rs 3,240, total Rs 21,240.
- Monitored uptime: 98.7 percent (4 hours of unplanned downtime).
- SLA tier applied: 98.0 to 99.0 percent bucket equals 10 percent credit on rental — Rs 1,800 SLA credit.
- Section 393 code 1002 TDS at 2 percent on Rs 18,000 service value: Rs 360.
- Section 34 credit note from Airtel: Rs 1,800 plus 18 percent GST of Rs 324, total Rs 2,124. ITC reversed on Rs 324 under Rule 42.
- Net cost: Rs 16,200 service value, Rs 2,916 ITC retained, Rs 360 TDS deposited.
Repeat across 612 sites and four vendors, every month — the reconciliation has to do it without rate-tier errors and without missing the September 30 credit-note window.
Where MPLS sits in the telecom reconciliation surface
MPLS circuit billing is the enterprise-WAN view of telecom services, complementary to the IUC and ILD carrier-to-carrier views. For service providers, MPLS revenue reconciliation is a mirror problem — ensuring every active circuit is billed, that SLA penalty credits are computed accurately, and that decommissioned circuits stop being billed. TRAI’s enterprise QoS framework anchors the regulatory side at the Telecom Regulatory Authority of India.
What automated reconciliation changes
A 600-site MPLS WAN across four vendors produces 600-plus invoice lines and 600-plus downtime records every month. Manual reconciliation misses decommissioned-but-billed circuits, applies hub rates to spoke circuits, and loses SLA credits to the September 30 GST deadline. Purpose-built reconciliation software India ingests the circuit master and lifecycle events, ties vendor invoices line-by-line, applies the SLA tier table against accepted downtime, surfaces tier-rate misbilling, withholds Section 393 code 1002 TDS, and tracks Section 34 credit notes against the deadline. For the GST recovery side, see GST reconciliation software.