Revenue leakage in telecom: reconcile usage and billing

Revenue leakage in telecom is delivered, authorized service that is omitted from billing or charged at less than the agreed amount. Find it by rebuilding the expected charge from service records, usage and effective contract terms, then comparing that result with invoice lines. A difference is a candidate exception until someone checks timing, allowances and approved adjustments.

Start with services rather than invoices

An invoice-only review cannot reveal an active circuit that never reached billing. Begin with the service activation export for the service period, including services activated or disconnected during it. Attach usage and invoice records to that population using stable service and account identifiers.

Keep unmatched records in the review. A service without an invoice, usage without a recognized service ID and an invoice without an active service each require a different investigation. Blank matches must remain visible rather than disappearing from a summary.

This work is narrower than general B2B ledger leakage checks: telecom needs explicit treatment of service activation, metered units, allowances and rate-effective dates. Once billing is reconciled, telecom revenue analysis compares the resulting revenue across services and customers.

Assemble the export rows

Use a common service period and one currency. Keep minutes, data units and recurring service fees distinguishable; combining quantities from different unit types produces a meaningless total.

For telephone bills, the FCC's truth-in-billing requirements require clear descriptions that let customers assess whether billed services match what they requested and received. That makes identifiable service descriptions useful evidence in the reconciliation, alongside the underlying contract.

For covered broadband offerings, the transparency rule requires disclosure of commercial terms and accurate consumer labels. Where applicable, the relevant published label can provide a further cross-check; use the customer's effective agreement to calculate the contractual expectation for this review.

Rebuild the expected bill

The following simplified calculation assumes a separate allowance per service, no tiered rates, no pooled allowances and a full month of recurring fees:

Chargeable units = Maximum of zero and usage minus included allowance

Expected charge = Recurring fee + Chargeable units × Contract unit rate

Candidate underbilling = Maximum of zero and expected charge minus billed charge

A US connectivity provider reviews September service charges. All services were authorized and active throughout the month. Taxes, pass-through fees and equipment sales are outside this defined population, and there are no approved credits in the example.

Put those columns in A through F, with headers in row 1. In G2, calculate chargeable units; in H2, calculate expected charges; in I2, retain the signed difference; and in J2, isolate candidate underbilling:

=MAX(0,B2-C2)
=E2+G2*D2
=H2-F2
=MAX(0,I2)

Fill each formula through row 5. These formulas operate on already matched, period-aligned rows. First confirm that a service has only one applicable rate for each covered date; a rate change within the period requires separate subperiod rows.

Voice A's expected usage charge is (12,000 - 2,000) × 0.04 = $400. Adding the $250 recurring fee gives $650, leaving an $80 gap against the $570 invoice amount. Circuit C demonstrates why zero usage cannot be treated as zero expected revenue: its recurring fee is still due under the example's terms.

Prove the gap before calling it lost revenue

The charge bridge must reconcile:

Expected charges - Billed charges = Net signed difference

Here, $2,100 - $1,470 = $630, matching $80 + $0 + $500 + $50. Expected charges also equal $1,350 in recurring fees plus $750 in usage charges. Each of those totals can be rebuilt from the service rows.

Candidate underbilling is 630 / 2,100 = 30% of expected charges, exact in this example. It describes this selected review population, not a company-wide leakage benchmark. If there were overbilled services, report those amounts separately rather than netting away the customer correction required.

Tie the $1,470 billed amount to the corresponding invoice export subtotal. Record the service population's count, usage subtotals by unit type and invoice amount before and after matching; these control totals expose missing records and duplicated matches.

Then assign each exception to an owner. Billing checks missing or duplicated invoice lines. Commercial operations confirms rates, allowances and amendments. Finance checks cutoffs and credits. Review credit notes and returns in revenue measures when a billing correction crosses reporting periods.

Retain the original expected amount, explanation, confirmed correction and later invoice reference. Only the reviewed difference should enter a confirmed-leakage report; a proposed rebill is not collected cash.

Where it goes wrong

• One allowance applied more than once. Shared account allowances need a contract-defined allocation before calculating service-level excess usage.
• Usage period confused with invoice date. Usage billed in arrears can appear missing until the appropriate billing cycle closes.
• Mismatched units or rounding rules. Seconds, minutes and billed increments are different quantities. Apply the contract's conversion and rounding before comparing charges.
• Partial service months treated as full months. Activation, suspension and disconnection dates can change both recurring fees and allowances.
• An unmatched invoice treated as permission to bill. Verify authorization and the effective terms. The cited truth-in-billing rule also prohibits unauthorized telephone charges.

Reconcile your telecom exports in Covirage

Bring service, usage, effective-rate and invoice records in a file or Google Sheet, with the periods and units identified. Covirage maps the columns; its tools compute and check the figures, and the external AI model explains the differences with every figure traced to its rows. Create a free Covirage account and bring a sample of your own export.

See Covirage for telecom teams for the supporting industry workflow.