Key insights
- Connectivity structure (who provides it, who controls it, and how it’s billed) can trigger telecom tax and regulatory requirements — even when the core value is software.
- Telecom tax regimes often use different sourcing rules (e.g., place of primary use/service address) than sales/use tax, which is challenging for roaming or multi state IoT deployments.
- Early alignment across tax, product, and legal teams helps avoid late-stage registrations, retroactive exposures, and invoice/contract rework.
Plan IoT connectivity compliance early.
IoT in practice: Technologies, capabilities, and service models
IoT solutions typically combine:
- A connected device (sensors/actuators)
- A network connection (cellular, Wi-Fi, LPWAN, satellite, private LTE/5G)
- Software that provisions devices, moves data, and enables monitoring, analytics, and automation
From a compliance perspective, the key question isn’t whether the product is “IoT,” but who’s providing connectivity, how it’s priced and described, and where it’s used.
The compliance question: Who provides connectivity, and how is it sold?
Many offerings bundle hardware, embedded connectivity, and a subscription platform. Some companies resell data plans/SIMs directly; others embed carrier connectivity and don’t separately state it on the invoice.
These structuring decisions — along with contract terms and operational reality (provisioning, support, and control) — can materially change telecommunications-tax outcomes.
Why adding connectivity can create telecom compliance exposure
Connectivity may feel like an enabling feature, but telecommunications is regulated and taxed differently than general sales/use tax. The taxes at issue are generally state and local communications taxes, fees, and surcharges (rather than federal income tax), although federal telecommunications charges may also apply depending on the service.
Depending on the facts and the jurisdiction, a company that provides, resells, bundles, or controls connectivity can be viewed as offering a communications service — triggering registrations, filings, and surcharges even when the core value proposition is software or data.
Telecom taxes are commonly treated as a subset of general sales and use tax; however, there are many notable differences. In some jurisdictions, telecommunications services are subject to the imposition of tax under the state’s sales tax enabling statutes; in others, they are governed by separate communications tax statutes or utility-style tax regimes.
Even where sales tax concepts overlap, telecom often follows distinct sourcing, situsing, nexus, and billing rules, and may carry additional line-item obligations such as 911 fees, universal service-type charges, and other regulatory surcharges at the state or federal level.
Common triggers include:
- Being the customer-facing provider of connectivity (even if a carrier is behind the scenes)
- Separately pricing or labeling connectivity-related charges (such as data plans, SIMs, or activation)
- Controlling access through provisioning and plan management (including pooled plans and assigned identifiers/phone numbers)
- Passing through carrier charges
- Supporting mobile or multi-state deployments that complicate sourcing and documentation
Scope note: This discussion focuses on U.S. indirect taxes and related communications compliance concepts (state/local communications taxes, fees, and surcharges). Rules are highly fact-specific and vary by jurisdiction.
Indirect tax considerations when IoT capabilities are added
Nexus and footprint
A reclassification of revenue into communications categories can create filing obligations differing from sales tax triggers.
Situsing (sourcing)
Telecom taxes may rely on “place of primary use” or service address concepts — not ship to — creating challenges when devices roam or are deployed across multiple customer sites. Establish an address hierarchy and retain supporting evidence such as call detail records.
Bundling and invoice presentation
Whether connectivity is separately stated, labeled (data plan/SIM/activation), or bundled can impact taxability and whether allocation is needed when software, managed services, and connectivity have different tax profiles
In IoT, the compliance risk is rarely the device — it’s how connectivity is provided, controlled, and billed.
Operational reality
Provisioning/plan management, telecom vendor agreements, contract/terms and conditions, and invoicing can affect how jurisdictions view who is providing the communications service.
Documentation and audit readiness
Define what data will be collected and validated (service address/primary use), how changes will be tracked, and what records will be retained for mobile or multi-state deployments.
How CLA can help with IoT connectivity structuring
CLA’s telecom team can help you assess potential telecommunications tax and regulatory historical exposure, support registrations/filings and surcharge obligations, design defensible sourcing and documentation for IoT deployments, and align contracting and billing practices with your intended operating model.
Contact us to discuss your IoT product model and how connectivity may affect indirect tax and telecommunications compliance requirements.
Contact us
Plan for how IoT connectivity may impact indirect tax compliance early. Complete the form below to connect with CLA.