How a Small ISP Should Choose Billing Software
Use workflow tests, tenant boundaries, network failure and total operating cost to select a platform that can grow safely.
Use workflow tests, tenant boundaries, network failure and total operating cost to select a platform that can grow safely.
Buy for the operation you can prove
A small ISP needs fast collection and simple customer management, but early shortcuts become structural limits when resellers, staff and devices grow. Selection should begin with real workflows and failure cases rather than a feature checklist or a dashboard demonstration.
Money
Trace invoice, payment, adjustment, receipt and ledger evidence.
Access
Test RADIUS, MikroTik, suspension, restoration and unavailable devices.
Delegation
Enforce group, operator, sub-operator and staff boundaries everywhere.
Exit
Retain ownership of data, backups, configurations and credentials.
Write acceptance scenarios first
Use a representative customer from creation through package assignment, payment, expiry, recharge, migration and closure. Include partial payment, duplicate callback and a correction that must not change validity.
Test direct URLs, autocomplete, exports and API calls under every role. Menu visibility is not an authorization control.
Evaluate operations under stress
Make a router slow or unreachable during bulk work. Disconnect a gateway callback, exhaust SMS balance and restore a backup in a test environment. Ask what remains queued, uncertain or reversible.
Inspect mobile screens used by field and collection staff and measure list performance with realistic data volume.
Calculate total operating cost
Include migration, setup, gateway work, messaging, support, backups, training and internal reconciliation time. A low subscription price can coexist with expensive manual repair.
Review support ownership, security updates, incident communication and export format in the contract.
Evidence before rollout
| Signal | Required proof |
|---|---|
| Lifecycle | A customer completes the full commercial and access journey. |
| Isolation | Cross-tenant URLs, searches and exports are blocked. |
| Failure | Gateway, SMS and router uncertainty is visible and recoverable. |
| Reconciliation | Financial and service state can be independently checked. |
| Portability | Data and configuration exports are usable. |
Put the plan into operation
- Define. Write critical workflows and non-negotiable controls.
- Shortlist. Reject products with architectural gaps.
- Demonstrate. Run identical scripted cases.
- Pilot. Use a bounded customer cohort.
- Reconcile. Compare money, sessions, messages and audit logs.
- Decide. Score evidence, cost and recovery together.
The decision standard
The right platform lets a small team explain every charge and access change, limits each user to authorized data, degrades visibly under dependency failure and provides a credible path to recover or leave.
Research basis: NIST software supply-chain guidance; OWASP ASVS; TM Forum billing concepts. Validate implementation details against the releases, contracts, and local regulations governing your network.