GSTR-2B reconciliation for telecom and internet service providers: towers, bandwidth, and multi-circle matching

A national telecom operator or regional internet service provider (ISP) does not run a standard purchase ledger. A single circle operation receives tens of thousands of line items every month, ranging from monthly tenancy fees on shared passive towers to energy cost pass-through reimbursements, dark fiber pairs, and international IP transit pipes. When network procurement is negotiated centrally in Mumbai or Delhi while network elements operate across twenty-two circles, input tax credit easily ends up trapped in the wrong state registration.

Under statutory provisions in Section 16(2)(aa) of the CGST Act, credit is allowed only when vendor invoices appear in your auto-drafted Form GSTR-2B. When a passive tower company bills an Uttar Pradesh tower to your Haryana registration, that input tax credit cannot be claimed in Haryana or offset against Uttar Pradesh outward liabilities. It sits as an unreconciled mismatch that triggers notices if claimed in Form GSTR-3B.

This guide explains the statutory place of supply framework, passive infrastructure billing mechanics, Input Service Distributor rules, and a tested multi-circle reconciliation procedure.

Circle footprints versus state GSTIN registrations

The core mismatch in telecom reconciliation stems from the gap between telecommunications licensing and the GST registration structure. The Department of Telecommunications (DoT) licenses operators across twenty-two telecom service areas. Many of these circles do not follow state boundaries:

• The Maharashtra circle excludes Mumbai, which operates as an independent metro circle. Both fall under the same state GSTIN prefix (27), yet internal operating divisions often treat them as separate business entities.
• The Delhi circle covers the National Capital Territory of Delhi (GSTIN 07) plus adjoining National Capital Region cities in Haryana (Gurugram, Faridabad, GSTIN 06) and Uttar Pradesh (Noida, Ghaziabad, GSTIN 09).
• The North East circle encompasses six distinct states (Arunachal Pradesh, Manipur, Meghalaya, Mizoram, Nagaland, and Tripura), each requiring its own unique state GSTIN registration under Section 25.
• The Punjab circle includes the Union Territory of Chandigarh (GSTIN 04) along with Punjab (GSTIN 03).

When vendors invoice for passive tower rentals, optical ground wire stringing, or local fiber splicing, they often bill according to the operational circle code rather than the physical location where the immovable infrastructure sits. If an invoice for a tower in Ghaziabad is billed to the Delhi GSTIN, the vendor charges Central Tax and Delhi State Tax. The tax is completely ineligible for the Delhi registration because the place of supply is Uttar Pradesh. If claimed in Delhi, the automated validation flags it as invalid. In Uttar Pradesh, where the credit legitimately belongs, it is missing from Form GSTR-2B.

For more details on managing multiple state books side by side, review our practical guide to GSTR-2B reconciliation for multiple GSTINs.

Place of supply rules for telecom infrastructure and leased bandwidth

Telecom reconciliation teams must classify inward vendor charges under two distinct place of supply rules in the Integrated Goods and Services Tax (IGST) Act, 2017.

Tower tenancy and passive site rentals under Section 12(3)

Telecom towers, ground-based masts, rooftop poles, and pre-fabricated shelters are treated as immovable property for place of supply purposes. Under Section 12(3) of the IGST Act, the place of supply of services directly in relation to immovable property, including grant of rights to use such property, is the location where the property is situated.

Consequently, the tower operating company (such as Indus Towers or ATC) must issue an invoice with the place of supply set to the state where the tower stands. If your registered operating entity in that state holds a valid GSTIN, the supplier charges CGST and SGST (if the vendor is registered in the same state) or IGST (if billing from another state). Your purchase register for that state must match that exact invoice.

Fixed telecommunication lines and leased circuits under Section 12(11)

For transmission media, the statutory provision is governed by Section 12(11) of the IGST Act. The statutory rule provides:

• Under clause (a), for services by way of fixed telecommunication lines, leased circuits, internet leased circuits, or cable connections, the place of supply is the location where the line or circuit is installed for receipt of services.
• Under the Explanation to Section 12(11), where a leased circuit is installed in more than one state or Union territory and a single consolidated amount is charged, the place of supply is apportioned among each respective state or Union territory in proportion to the value separately collected or determined under the agreement.

When an ISP leases a point to point 100 Gbps dark fiber pair running between Bengaluru (Karnataka) and Hyderabad (Telangana) from a national infrastructure provider, the agreement must specify the circuit length or value split between Karnataka and Telangana. The vendor must split the billing across two invoices or issue separate tax items identifying each state place of supply. If the supplier bills the entire charge to Karnataka, the Telangana registration loses its legitimate credit, and Karnataka faces audit scrutiny for claiming credit on out of state infrastructure.

Passive infrastructure sharing: mast tenancies and energy cost pass-through

The monthly reconciliation with tower infrastructure providers (TowerCos) involves two distinct billing components that create recurring friction in Form GSTR-2B matching:

1. Fixed mast tenancy fees: Standard monthly charges per slot or per antenna mounted on the mast, governed by long-term master service agreements. These are predictable and generally supported by automated enterprise billing engines.
2. Variable energy and diesel pass-through reimbursements: TowerCos incur commercial electricity charges from state distribution companies (DISCOMs) and consume diesel fuel for backup generator sets during grid outages. These charges are passed through to telecom tenants based on shared power consumption formulas.

Energy reimbursements frequently arrive late. Power bills from electricity boards arrive with a lag of 30 to 60 days, and diesel logsheets from remote rural sites require physical verification. Consequently, the telecom operator books an unbilled revenue provision or accrued expense at month-end. When the actual tax invoice arrives two months later, the invoice date belongs to the current month, but the operational consumption relates to an earlier quarter.

If the accounting software tries to match by financial period rather than invoice number and supplier GSTIN, the invoice is misclassified as an unexplained variance. Teams must use normalized invoice number matching and date tolerance rules to link delayed energy invoices to earlier expense accruals without delaying GSTR-3B filings.

Central procurement: ISD distribution versus internal cross-charge

Most telecom companies and large ISPs negotiate enterprise software, satellite transponder capacity, national network operations center (NOC) contracts, and central billing software (OSS/BSS) from a single corporate office. Distributing this inward tax credit to operating circles is governed by strict compliance boundaries.

Under Section 20 of the CGST Act and Rule 39 of the CGST Rules, any office receiving tax invoices for input services procured for or on behalf of distinct persons must register as an Input Service Distributor (ISD) and distribute that credit to the beneficiary branches.

Here is how the distinction works in daily practice:

• Input Service Distributor (ISD): Applies strictly to third-party vendor input services. For example, when Oracle or Ericsson bills the corporate office in Gurugram for national BSS software maintenance used across all twenty-two circles, that invoice must be accepted into the ISD registration and distributed in Form GSTR-6 pro rata based on circle turnover. The distributed credit appears in Table 4(A)(4) of each recipient circle's Form GSTR-2B.
• Internal cross-charge: Applies to internally generated services supplied by head office personnel to regional circles, such as central executive management, network planning engineers, legal advisory, and internal IT support under Section 25(4) and Schedule I. These are billed out using regular tax invoices reported in Form GSTR-1, appearing in Table 4(A)(5) of the circle's Form GSTR-2B.

For an in-depth breakdown of how statutory amendments impact central corporate overhead, read our analysis on cross-charge vs Input Service Distributor rules.

Import of bandwidth and reverse charge under Section 5(3)

Internet service providers and unified access licensees regularly purchase international bandwidth, IP transit from overseas Tier 1 transit providers (such as Lumen, Telia, or NTT), and indefeasible rights of use (IRU) on undersea submarine cable systems landing at landing stations in Mumbai or Chennai.

Because the overseas transit provider does not have a taxable presence in India, these transactions constitute an import of services. Under Section 5(3) of the IGST Act, the recipient is liable to pay integrated tax on a reverse charge basis.

Reconciliation checkpoints for reverse charge bandwidth:

• Import of services is not reported in GSTR-1 by overseas suppliers, so it never appears in auto-drafted GSTR-2B files.
• The telecom operator must self-compute reverse charge liability, issue a self-invoice under Section 31(3)(f), and discharge the liability in cash in Table 3.1(d) of Form GSTR-3B.
• Once paid, the identical amount is claimed as input tax credit in Table 4(A)(2) of Form GSTR-3B for that same tax period.
• Monthly reconciliation files must isolate overseas bandwidth invoices from standard domestic B2B registers so automated matching algorithms do not flag them as missing supplier uploads.

Worked multi-circle reconciliation example

Consider Bharat Fiber Net Limited, an ISP operating across three southern circles with registered GSTINs in Karnataka (29), Tamil Nadu (33), and Andhra Pradesh (37). Its corporate office in Bengaluru holds an ISD registration (29-ISD) in addition to its operating registration.

During a monthly reconciliation run for September 2026, the accounts team compares the internal purchase registers against auto-drafted Form GSTR-2B statements. Below is the multi-circle exception register:

In this run, invoice INDUS-90188 for ₹1,80,000 represents a classic circle boundary failure. The tower sits in Tirupati (Andhra Pradesh), but the vendor account manager mapped it to the Chennai regional office, charging Tamil Nadu GST. Claiming that tax in Andhra Pradesh would trigger an automated mismatch notice under Rule 88D. The invoice must be marked as Rejected in the Invoice Management System (IMS), and the supplier must issue an amendment in Form GSTR-1A or the subsequent tax period.

Standard operating procedure for monthly multi-circle matching

To avoid recurring mismatches and manage the tight window between the 14th and the 20th of every month, network finance teams should implement a five-step monthly protocol:

1. Step 1: Ingest and isolate data by state GSTIN. Pull the individual Form GSTR-2B JSON or Excel files for all state registrations on the 14th. Ensure purchase register exports from SAP, Oracle, or Tally Prime are split strictly by legal entity GSTIN, not internal circle cost centers.
2. Step 2: Segregate reverse charge and ISD flows. Filter out foreign carrier IP transit bills and cross-border bandwidth contracts from the standard matching queue. Verify that corporate ISD credits distributed via Form GSTR-6 match the auto-populated figures in Table 4(A)(4) of each circle's GSTR-2B.
3. Step 3: Run place of supply and GSTIN consistency validation. Check that the POS state code in the vendor's Form GSTR-2B line item matches the first two digits of your receiving GSTIN. Flag any lines where POS differs from the recipient state code for immediate technical verification.
4. Step 4: Match passive tower invoices with normalized tenancy IDs. Match tenancy invoices against monthly site master lists using site identification codes and billing period dates rather than pure invoice numbers, as TowerCos frequently change alphanumeric invoice prefixes.
5. Step 5: Action variances in IMS and adjust Form GSTR-3B. Use the Invoice Management System on the GST portal to Accept clean records and Reject or mark Pending any invoices with incorrect state place of supply or wrong GSTIN assignments before re-computing final eligible credit.

Related guides

• GSTR-2B reconciliation: complete guide to ITC matching
• GSTR 2B reconciliation for co working space operators: leases, utilities, and multi-state compliance
• GSTR-2B reconciliation for travel agencies and tour operators
• GSTR-2B reconciliation for real estate promoters under RREP framework

Frequently asked questions

Explore our complete archive of technical guides on the GSTR-2B reconciliation guides index.

Last checked: 18 October 2026. Sources: CBIC Tax Information Portal (CGST Act Section 16 & Section 20), CBIC Tax Information Portal (IGST Act Section 12 & Section 5), GSTN Portal GSTR-3B Return Manual.