# Common mistakes auditing telecom and connectivity bills > What to check on telecom and connectivity invoices: zombie circuits, eroded discounts, tax basis errors, and unclaimed SLA credits, with checkable steps for. Source: https://valuexpa.com/insights/common-mistakes-when-auditing-telecom-and-connectivity Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-06 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. In telecom and connectivity spend, that gap hides inside a bill that looks stable month over month, which is exactly why it survives audit longer than volatile categories like freight. This page covers what a telecom invoice audit should actually check: circuit inventory against what is billed, discount schedules against what is applied, tax and surcharge lines against their stated basis, and SLA credits against outage logs. Each item below is checkable against documents you already have. ## Executive Summary Telecom bills survive audit longer than almost any other vendor category because they are boring in a specific way: the total barely moves month to month, so nobody opens the detail. Margin drift here is not one large error. It is a stack of small ones, a disconnected circuit still billing, a promotional discount that expired quietly, a regulatory fee recalculated on the wrong base, an outage credit nobody filed for, that together compound over a multi-year contract term. The mechanism is the same across all of them: telecom invoices separate the commercial terms (the contract, the discount schedule, the SLA) from the billing system that actually charges you, and the two are reconciled rarely, if ever. A circuit inventory built at contract signing goes stale the moment a site closes or a line gets replaced. A discount tied to a spend commitment erodes as usage shifts. Nothing forces either side to catch up. What changes it is treating the telecom bill like a contract compliance exercise, not a bill-pay function: reconcile the billed inventory against what is actually in service, check tax and surcharge lines against their own basis, and confirm every credit the contract promises was actually applied. None of this needs new tooling. It needs someone to open the detail. ## 1. What should you look for in telecom and connectivity invoices? **Check four things on every telecom invoice: whether every billed circuit, line, and device is still in active service; whether the discount rate on the bill matches the rate in the current contract amendment; whether tax and regulatory surcharges are calculated on the correct charge base; and whether any service outage during the period triggered an SLA credit that was actually applied. Each is a line-item comparison against a document you already hold, not an estimate.** Start with the circuit and line inventory. Pull the carrier's billed inventory report and compare it, line by line, against your own asset register or telecom expense management export. Every mismatch is either a circuit you are paying for that no longer exists, or a circuit in service that nobody is tracking. Next, pull the current contract amendment, not the original master agreement, and check the discount percentage or fixed rate against what the invoice actually applies. Contracts get amended through addenda and side letters; billing systems do not always pick up the latest one. Then check the tax and surcharge section against the contract's stated fee schedule, and check the SLA clause against any outage tickets logged during the billing period. Each is expanded below. - **Inventory reconciliation:** Match every billed circuit or line against your own active asset register, not against last year's inventory file. - **Discount schedule check:** Compare the invoiced rate against the current signed amendment, since side letters change rates the master agreement never mentions. - **Tax and surcharge basis:** Confirm regulatory fees are calculated on the discounted charge, not the pre-discount rate card amount. - **SLA credit filing:** Match outage tickets against the SLA clause's uptime threshold and claim window before that window closes. ## 2. Where do zombie circuits keep costing money after they're disconnected? **A zombie circuit is a line, trunk, or device that was physically disconnected or replaced but never removed from the carrier's billing system, so it keeps generating a monthly recurring charge with no service behind it. It survives because disconnect requests go through a different workflow than the invoice review, and nobody closes the loop by checking the next bill against the disconnect order.** Site closures, office moves, and equipment refreshes generate a disconnect order that goes to the carrier's provisioning team, not to accounts payable. The provisioning team closes the physical circuit; the billing system, run by a separate department on a separate schedule, does not always pick up the change in the same cycle, or at all. The checkable fix is a disconnect log. Every site closure, circuit swap, or device return should generate a dated ticket. Match that ticket against the next three billing cycles for the same account number, not just the next one, because carriers frequently take more than a month to process a disconnect internally. A circuit that keeps billing for a service that no longer exists sits inside the six categories where indirect spend drift accumulates without anyone noticing until the contract renewal forces a full inventory reconciliation. ## 3. How do bundled discounts erode without anyone changing the contract? **A bundled telecom discount is tied to a spend commitment, a line count, or a specific mix of services purchased together. When the mix shifts, a line is dropped, a service is downgraded, a device is moved to a different plan, the discount tier can drop with it even though the master contract was never renegotiated. The invoice keeps the old discount label while applying a lower effective rate.** Carriers structure telecom pricing around tiers: a certain number of lines, a certain committed spend, a certain bundle of data and voice services, qualifies for a specific discount percentage. The contract states the tier and the rate that applies at that tier, but it rarely states what happens automatically when the mix changes. When a business unit cancels a service, migrates users to a different plan, or consolidates lines during a reorganization, the qualifying volume for the discount tier can drop below the threshold. The billing system may or may not reprice the remaining services at the lower tier's rate, and either outcome, silent repricing or a stale discount held past its qualifying threshold, is a compliance question the contract can answer. The check is straightforward: recompute the qualifying volume from the current billed inventory, find the tier that volume actually supports in the discount schedule, and compare that rate against what the invoice applies line by line. ## 4. What taxes and regulatory fees actually belong on a telecom bill? **A telecom invoice separates into three layers: the service charge itself, carrier-imposed surcharges the contract discloses (administrative fees, cost-recovery charges), and government-mandated taxes and regulatory fees calculated on a specific base. Each layer has a different source document to check it against, and errors cluster where a fee is calculated on the wrong base, often the pre-discount charge instead of the post-discount one.** The service charge is the easiest layer to audit because it maps directly to the rate card and discount schedule already covered above. The carrier-imposed surcharge layer is next: administrative recovery fees and similar charges should be disclosed somewhere in the contract or the carrier's published rate sheet, and the invoice should cite the same percentage or flat amount. The regulatory layer, universal service fund contributions and similar mandated fees, is calculated as a percentage of a specific charge base defined by the underlying rule, not by the carrier. A common error is applying that percentage to the full pre-discount charge rather than the discounted amount actually billed, which overstates the fee on every line it touches. Where to verify each layer of a telecom invoice against a source document. Where to verify each layer of a telecom invoice against a source document. | Layer | What it covers | Verify against | Service charge | Recurring circuit, line, or device fee | Rate card and current discount schedule | Carrier surcharge | Administrative or cost-recovery fee set by the carrier | Contract disclosure or published carrier rate sheet | Regulatory fee | Government-mandated contribution calculated on a defined base | The stated charge base, checked against the discounted amount billed ## 5. Why do SLA outage credits go unclaimed on telecom contracts? **Telecom SLA clauses generally require the customer to file a claim within a stated window after an outage; the carrier does not calculate and apply the credit automatically. If nobody matches the outage ticket log against the SLA clause's uptime threshold and claim deadline within that window, the credit right expires unused, invoice after invoice, contract after contract.** The SLA clause defines an uptime commitment, a formula for the credit owed when the commitment is missed, and a deadline for filing the claim, often 30 to 60 days from the outage. None of that is applied by the carrier's billing system on its own; it depends on the customer noticing the outage, calculating the shortfall against the contracted threshold, and filing before the deadline closes. The checkable process is a standing reconciliation: pull the network monitoring or ticketing log for the period, calculate actual uptime against the contracted threshold for each affected circuit, and file a claim for every shortfall before the contract's own deadline. This is the same discipline covered on the page about SLA credits you are entitled to and never claimed, applied specifically to telecom uptime clauses rather than maintenance response-time clauses. ## 6. How does a telecom audit differ from auditing freight or MRO invoices? **Freight and MRO invoices vary by shipment or purchase order, so an error shows up as an outlier the moment someone scans the detail. Telecom invoices barely change month to month, so an error hides by blending into a stable total rather than standing out against it. The audit method has to change accordingly: reconcile against an inventory and a contract amendment, not against a per-transaction rate card.** A freight invoice audit checks each shipment against a rate card and an accessorial schedule; the transaction count is high and each one is a discrete check. A telecom invoice audit checks a small number of recurring line items against an inventory that changes slowly and a contract that gets amended irregularly, so the review cadence and the documents involved are both different. That difference is why telecom belongs among the indirect spend categories where drift hides: the review habits built for high-transaction-volume categories do not transfer, and a telecom line can run for years without anyone applying the checks in the sections above. [The accessorial charge audit approach](/guides/accessorial-charge-audit-the-surcharges-nobody-validates) used in freight, checking each surcharge against a published schedule, translates directly to the carrier surcharge layer covered here. For the wider pattern this sits inside, start with the [margin drift guide](/guides/indirect-spend-audit-categories). See also the six categories drift hides in and duplicate freight billing and the multi-carrier consolidation problem. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. ## 7. Frequently Asked Questions (People Also Ask) ### How often should we run a telecom invoice audit? There is no universal cadence in the proof registry to cite, so set it by contract events instead: run a reconciliation whenever a site closes, a contract is amended, or at least once before each renewal. Waiting for the renewal alone lets zombie circuits and eroded discounts accumulate for the full contract term. ### Can telecom expense management software catch these errors on its own? A telecom expense management tool tracks the inventory and billing data you feed it, but it enforces whatever rules and current contract terms it was configured with. If the amendment or disconnect order was never entered, the software has no way to flag the mismatch. It needs the same document reconciliation described here. ### What documents do we need before starting a telecom audit? The carrier's billed inventory report, your own asset register or TEM export, the current signed contract amendment (not just the master agreement), the SLA clause text, and any outage or disconnect tickets logged during the period under review. ### Is a stale discount the carrier's error or ours? Usually neither party flags it deliberately. The contract sets a discount tier tied to volume or spend, and when that volume shifts, neither the carrier's billing system nor the customer's AP team is obligated to recalculate the tier unless someone checks. It is a compliance gap, not a fraud. ### How far back can we claim a missed SLA credit? That depends entirely on the claim window stated in your specific SLA clause, which is not a figure this page can generalize. Read the clause's filing deadline directly and treat any outage past that window as unrecoverable, which is why the reconciliation needs to run inside the window, not after. ### Do these checks apply to mobile device plans as well as fixed circuits? The same four checks, inventory, discount schedule, tax basis, SLA credit, apply to mobile lines, though mobile plans typically substitute a device or line count for a circuit count. A disconnected employee's phone line is the mobile equivalent of a zombie circuit. ### Who inside the company should own this reconciliation? It sits between IT asset management, which knows what is actually in service, and accounts payable, which sees the bill. Neither owns it by default, which is exactly why the reconciliation described in this page often does not happen unless someone is explicitly assigned it. ### What is the difference between a carrier surcharge and a regulatory fee? A carrier surcharge, such as an administrative or cost-recovery fee, is set by the carrier itself and should be disclosed in the contract or its published rate sheet. A regulatory fee is government-mandated and calculated on a base defined by the underlying rule, not by the carrier, which is why the two need separate verification. ### Is contract complexity quietly draining your operating margin? A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit. **[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)** ## Executive Summary Telecom bills survive audit longer than almost any other vendor category because they are boring in a specific way: the total barely moves month to month, so nobody opens the detail. Margin drift here is not one large error. It is a stack of small ones, a disconnected circuit still billing, a promotional discount that expired quietly, a regulatory fee recalculated on the wrong base, an outage credit nobody filed for, that together compound over a multi-year contract term. The mechanism is the same across all of them: telecom invoices separate the commercial terms (the contract, the discount schedule, the SLA) from the billing system that actually charges you, and the two are reconciled rarely, if ever. A circuit inventory built at contract signing goes stale the moment a site closes or a line gets replaced. A discount tied to a spend commitment erodes as usage shifts. Nothing forces either side to catch up. What changes it is treating the telecom bill like a contract compliance exercise, not a bill-pay function: reconcile the billed inventory against what is actually in service, check tax and surcharge lines against their own basis, and confirm every credit the contract promises was actually applied. None of this needs new tooling. It needs someone to open the detail. ## 1. What should you look for in telecom and connectivity invoices? Check four things on every telecom invoice: whether every billed circuit, line, and device is still in active service; whether the discount rate on the bill matches the rate in the current contract amendment; whether tax and regulatory surcharges are calculated on the correct charge base; and whether any service outage during the period triggered an SLA credit that was actually applied. Each is a line-item comparison against a document you already hold, not an estimate. Start with the circuit and line inventory. Pull the carrier's billed inventory report and compare it, line by line, against your own asset register or telecom expense management export. Every mismatch is either a circuit you are paying for that no longer exists, or a circuit in service that nobody is tracking. Next, pull the current contract amendment, not the original master agreement, and check the discount percentage or fixed rate against what the invoice actually applies. Contracts get amended through addenda and side letters; billing systems do not always pick up the latest one. Then check the tax and surcharge section against the contract's stated fee schedule, and check the SLA clause against any outage tickets logged during the billing period. Each is expanded below. - Inventory reconciliation: Match every billed circuit or line against your own active asset register, not against last year's inventory file. - Discount schedule check: Compare the invoiced rate against the current signed amendment, since side letters change rates the master agreement never mentions. - Tax and surcharge basis: Confirm regulatory fees are calculated on the discounted charge, not the pre-discount rate card amount. - SLA credit filing: Match outage tickets against the SLA clause's uptime threshold and claim window before that window closes. ## 2. Where do zombie circuits keep costing money after they're disconnected? A zombie circuit is a line, trunk, or device that was physically disconnected or replaced but never removed from the carrier's billing system, so it keeps generating a monthly recurring charge with no service behind it. It survives because disconnect requests go through a different workflow than the invoice review, and nobody closes the loop by checking the next bill against the disconnect order. Site closures, office moves, and equipment refreshes generate a disconnect order that goes to the carrier's provisioning team, not to accounts payable. The provisioning team closes the physical circuit; the billing system, run by a separate department on a separate schedule, does not always pick up the change in the same cycle, or at all. The checkable fix is a disconnect log. Every site closure, circuit swap, or device return should generate a dated ticket. Match that ticket against the next three billing cycles for the same account number, not just the next one, because carriers frequently take more than a month to process a disconnect internally. A circuit that keeps billing for a service that no longer exists sits inside the six categories where indirect spend drift accumulates without anyone noticing until the contract renewal forces a full inventory reconciliation. ## 3. How do bundled discounts erode without anyone changing the contract? A bundled telecom discount is tied to a spend commitment, a line count, or a specific mix of services purchased together. When the mix shifts, a line is dropped, a service is downgraded, a device is moved to a different plan, the discount tier can drop with it even though the master contract was never renegotiated. The invoice keeps the old discount label while applying a lower effective rate. Carriers structure telecom pricing around tiers: a certain number of lines, a certain committed spend, a certain bundle of data and voice services, qualifies for a specific discount percentage. The contract states the tier and the rate that applies at that tier, but it rarely states what happens automatically when the mix changes. When a business unit cancels a service, migrates users to a different plan, or consolidates lines during a reorganization, the qualifying volume for the discount tier can drop below the threshold. The billing system may or may not reprice the remaining services at the lower tier's rate, and either outcome, silent repricing or a stale discount held past its qualifying threshold, is a compliance question the contract can answer. The check is straightforward: recompute the qualifying volume from the current billed inventory, find the tier that volume actually supports in the discount schedule, and compare that rate against what the invoice applies line by line. ## 4. What taxes and regulatory fees actually belong on a telecom bill? A telecom invoice separates into three layers: the service charge itself, carrier-imposed surcharges the contract discloses (administrative fees, cost-recovery charges), and government-mandated taxes and regulatory fees calculated on a specific base. Each layer has a different source document to check it against, and errors cluster where a fee is calculated on the wrong base, often the pre-discount charge instead of the post-discount one. The service charge is the easiest layer to audit because it maps directly to the rate card and discount schedule already covered above. The carrier-imposed surcharge layer is next: administrative recovery fees and similar charges should be disclosed somewhere in the contract or the carrier's published rate sheet, and the invoice should cite the same percentage or flat amount. The regulatory layer, universal service fund contributions and similar mandated fees, is calculated as a percentage of a specific charge base defined by the underlying rule, not by the carrier. A common error is applying that percentage to the full pre-discount charge rather than the discounted amount actually billed, which overstates the fee on every line it touches. Where to verify each layer of a telecom invoice against a source document. Where to verify each layer of a telecom invoice against a source document. | Layer | What it covers | Verify against | | --- | --- | --- | | Service charge | Recurring circuit, line, or device fee | Rate card and current discount schedule | | Carrier surcharge | Administrative or cost-recovery fee set by the carrier | Contract disclosure or published carrier rate sheet | | Regulatory fee | Government-mandated contribution calculated on a defined base | The stated charge base, checked against the discounted amount billed | ## 5. Why do SLA outage credits go unclaimed on telecom contracts? Telecom SLA clauses generally require the customer to file a claim within a stated window after an outage; the carrier does not calculate and apply the credit automatically. If nobody matches the outage ticket log against the SLA clause's uptime threshold and claim deadline within that window, the credit right expires unused, invoice after invoice, contract after contract. The SLA clause defines an uptime commitment, a formula for the credit owed when the commitment is missed, and a deadline for filing the claim, often 30 to 60 days from the outage. None of that is applied by the carrier's billing system on its own; it depends on the customer noticing the outage, calculating the shortfall against the contracted threshold, and filing before the deadline closes. The checkable process is a standing reconciliation: pull the network monitoring or ticketing log for the period, calculate actual uptime against the contracted threshold for each affected circuit, and file a claim for every shortfall before the contract's own deadline. This is the same discipline covered on the page about SLA credits you are entitled to and never claimed, applied specifically to telecom uptime clauses rather than maintenance response-time clauses. ## 6. How does a telecom audit differ from auditing freight or MRO invoices? Freight and MRO invoices vary by shipment or purchase order, so an error shows up as an outlier the moment someone scans the detail. Telecom invoices barely change month to month, so an error hides by blending into a stable total rather than standing out against it. The audit method has to change accordingly: reconcile against an inventory and a contract amendment, not against a per-transaction rate card. A freight invoice audit checks each shipment against a rate card and an accessorial schedule; the transaction count is high and each one is a discrete check. A telecom invoice audit checks a small number of recurring line items against an inventory that changes slowly and a contract that gets amended irregularly, so the review cadence and the documents involved are both different. That difference is why telecom belongs among the indirect spend categories where drift hides: the review habits built for high-transaction-volume categories do not transfer, and a telecom line can run for years without anyone applying the checks in the sections above. [The accessorial charge audit approach](/guides/accessorial-charge-audit-the-surcharges-nobody-validates) used in freight, checking each surcharge against a published schedule, translates directly to the carrier surcharge layer covered here. For the wider pattern this sits inside, start with the [margin drift guide](/guides/indirect-spend-audit-categories). See also the six categories drift hides in and duplicate freight billing and the multi-carrier consolidation problem. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. ## Common questions ### How often should we run a telecom invoice audit? There is no universal cadence in the proof registry to cite, so set it by contract events instead: run a reconciliation whenever a site closes, a contract is amended, or at least once before each renewal. Waiting for the renewal alone lets zombie circuits and eroded discounts accumulate for the full contract term. ### Can telecom expense management software catch these errors on its own? A telecom expense management tool tracks the inventory and billing data you feed it, but it enforces whatever rules and current contract terms it was configured with. If the amendment or disconnect order was never entered, the software has no way to flag the mismatch. It needs the same document reconciliation described here. ### What documents do we need before starting a telecom audit? The carrier's billed inventory report, your own asset register or TEM export, the current signed contract amendment (not just the master agreement), the SLA clause text, and any outage or disconnect tickets logged during the period under review. ### Is a stale discount the carrier's error or ours? Usually neither party flags it deliberately. The contract sets a discount tier tied to volume or spend, and when that volume shifts, neither the carrier's billing system nor the customer's AP team is obligated to recalculate the tier unless someone checks. It is a compliance gap, not a fraud. ### How far back can we claim a missed SLA credit? That depends entirely on the claim window stated in your specific SLA clause, which is not a figure this page can generalize. Read the clause's filing deadline directly and treat any outage past that window as unrecoverable, which is why the reconciliation needs to run inside the window, not after. --- ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us