Most small fiber ISPs run billing in one tool, subscriber data in a spreadsheet, router details in a third system and line assignments in someone's notes. Each handoff is a place where an invoice goes out for the wrong plan, a suspended line stays active or a new customer waits a week to get online.
Fiber ISP billing software works best when it is not a separate island. The line, the router, the subscriber and the invoice should be one record.
The problem: data split across tools
When the subscriber lives in the billing system, the PPPoE account lives on the network, and the router lives in an inventory sheet, nobody has a complete picture. A plan change means three updates. A cancelled customer means a manual check across every system. Errors do not show up as one obvious failure. They show up as a disputed invoice two months later.
One record for each subscriber
A single subscriber record should link:
- the customer and their contact details
- the fiber line and the OLT port it runs on
- the customer router and its configuration
- the active plan and the invoices generated from it
When these are linked, a question like "what is this customer paying for, and is it actually active?" has one answer. You do not need to reconcile three lists to find out.
What billing needs from the network
Billing and network state have to agree. Three events matter most:
- Plan changes. A customer upgrades from 100 Mbps to 500 Mbps. The billing change and the PPPoE or RADIUS profile change should come from the same action.
- Suspensions. An unpaid account should be suspended on the network from the same record that marks it as overdue.
- Reactivations. When payment arrives, the line should come back without a manual step in a second system.
If these run from separate tools, the gap between them is where billing disputes begin.
Running billing in production
Once the records are unified, day-to-day billing gets simpler:
- Renewals are generated from the active plan on the subscriber record.
- Failed payments trigger the same suspension workflow every time, not one run by whoever remembers.
- Reconciliation becomes a routine check: do the active subscribers on the network match the subscribers being billed? Any mismatch is a finding to fix, not a surprise at month end.
Getting started without an outage
Moving off spreadsheets does not need to happen in one weekend. A practical sequence:
- List every place a subscriber, line or invoice is recorded today.
- Pick one system as the source of truth for each of the four data types.
- Import existing subscribers and check a sample of 20 against the network and your current invoices.
- Switch new sign-ups to the new process first, then move existing accounts in batches.
- Run one full billing cycle in parallel with your old process before you retire it.
The goal is not a perfect migration on day one. It is a single record your team trusts more than the spreadsheet it replaces.
Fiber OS brings the line, the router, the subscriber and the invoice into one platform, so billing and network operations run from the same record.