What is revenue leakage for an ISP?
For an ISP, leakage is the gap between the service you deliver and the service you bill and collect. The network says a subscriber is online on a 1 Gbps plan with a rented router; the invoice says something else, or nothing at all.
It builds up quietly because every individual gap looks small and the bill still goes out. Nobody notices a $10 equipment fee that was never added, until the same omission has repeated across hundreds of accounts and many cycles.
Where does revenue leak in an ISP?
| Leak | How it happens | Where to look |
|---|---|---|
| Unbilled installs | Service goes live but the billing start date is never set or is set late | Accounts with live service and no invoice in the first cycle |
| Mis-rated plans | An upgrade happens on the network but the plan on the account never changes | Service profile vs billed plan, account by account |
| Promotions that never end | A three-month discount has no end date and keeps applying | Active discounts older than their offer terms |
| Missed equipment fees | Rented routers or ONUs are installed but the rental line is never added | Installed equipment vs recurring equipment charges |
| Suspended but still online | The account is suspended in billing but service keeps running | Suspended accounts with recent traffic or active sessions |
| Dunning gaps | Past-due accounts fall outside the rules and are never reminded or suspended | Aging buckets with no reminder or suspension history |
| Unapproved credits | Credits are issued to close calls, with no reason or approval | Credits by agent, reason and amount |
Almost every leak on this list is a handoff between two systems or two teams. The fewer systems a subscriber record passes through, the fewer places revenue can fall out.
Why do network and billing drift apart?
Drift happens when provisioning and billing are separate systems. A technician changes a speed profile on the OLT or in RADIUS to fix a problem, and the account never follows. A suspension is applied in billing but the network is never told. Each system is correct on its own, and together they disagree.
The structural fix is to drive network changes from the subscriber record, so a plan change, suspension or reconnection happens in one place and reaches the equipment automatically.
| ID | Event | Detail | Status | Value |
|---|---|---|---|---|
| #48201 | Auto-suspend | Past due · 4 days · policy DUNN-04 | Suspended | −1 service |
| #48202 | Auto-reconnect | ACH payment cleared · $74.00 | Reconnected | 2 min |
| #48203 | Cycle invoicing | Taxes, USF and E911 applied · emailed | Issued | 2,418 docs |
| #48204 | Payment reconciled | Paid via reminder link · matched to invoice | Cleared | +$74.00 |
How much leakage comes from collections?
Some of it is not a billing error at all: the invoice is right, it just never gets paid. Past-due balances that are never reminded, suspension rules that do not cover every plan, and reconnections that restore service before a payment actually clears all turn billed revenue into written-off revenue.
- DueSep 01
- ReminderSep 08
- SuspendedSep 15
- Paid via linkSep 18 14:02
- ReconnectedSep 18 14:04
Our collections and dunning playbook covers how to design the policy itself.
How do you run a revenue leakage audit and keep leaks from coming back?
Start with a one-time reconciliation, then turn the checks that found something into recurring reports.
| Check | Why it matters |
|---|---|
Every account with live service has an invoice this cycle. Catches installs that went live without billing starting. | Catches installs that went live without billing starting. |
The billed plan matches the service profile on the network. Catches upgrades delivered but never billed. | Catches upgrades delivered but never billed. |
Every active discount has an end date inside its offer terms. Catches promotions that outlived the promotion. | Catches promotions that outlived the promotion. |
Installed rental equipment matches recurring equipment charges. Catches routers and ONUs in homes with no fee attached. | Catches routers and ONUs in homes with no fee attached. |
Suspended accounts show no active sessions. Catches service delivered to accounts marked as suspended. | Catches service delivered to accounts marked as suspended. |
Every past-due account has a reminder or suspension on record. Catches balances that fell outside the dunning rules. | Catches balances that fell outside the dunning rules. |
Every credit has a reason and an approver. Catches credits used to end calls rather than fix problems. | Catches credits used to end calls rather than fix problems. |
- Set the billing start date from the turn-up event, not by hand after the install.
- Push plan changes, suspensions and reconnections from the subscriber record to the network.
- Require an end date on every promotion when it is created.
- Attach equipment fees to the equipment record, so installing the device adds the charge.
- Require a reason code and an approval threshold for credits.
- Review the audit checks every cycle, not once a year.
Who should own revenue assurance, and what signals help?
Leakage survives because it belongs to nobody. Billing assumes the network is right, the network team assumes billing will catch changes, and field techs assume someone else closes the order. Give one person ownership of the recurring checks, even at a small operator where it is a few hours a month.
That owner does not fix every issue personally. They run the audit reports each cycle, route what they find to the team that caused it, and track whether the same leak comes back. Over time the reports should shrink, and when one grows again it usually points to a new process that skipped a step, such as a new promotion, a new building or a new installer.
Give the owner read access to the network side, not only billing. Most of the checks in this guide compare what the network delivers with what the invoice says, and that comparison is impossible from one side alone.
Often, yes. Subscribers call when an invoice surprises them: a promotion ended without warning, a fee appeared that nobody explained, or a plan they upgraded never showed on the bill. Those calls are also where unapproved credits are issued to end the conversation.
Tagging billing calls by reason turns them into an early-warning system. A rising cluster of "bill line item unclear" contacts after a plan change or a new promotion usually means a rating or communication problem that will repeat every cycle until someone fixes it at the source.
Where does Inerxia fit?
The Inerxia Operating System puts subscribers, billing, dunning, inventory, ticketing and provisioning on one record, so a network change and the invoice come from the same place. Automated suspension and reconnection run on your dunning rules; reconnection fires when the payment your processor confirms is matched to the invoice. Inerxia does not process payments.
The billing and collections agent sends reminders with your own payment links and negotiates payment plans over voice and text.