ISP billing software

ISP Billing Software

Run subscriber billing, payment matching, controlled access workflows, support context, and field work from one cloud operations layer.

See MikroTik integration
Operator console

Subscribers, devices, and access in one view

subscribers
4.2k
sites live
3
critical fails
0
LiveSubscriber + device identityMapped
ActionGuarded command previewApproved
AuditEvery change loggedTracked
One operator surface ties each subscriber to their devices, access, and history.
Page type
Solutions
Primary search
ISP billing software
Updated
2026-05-24

Billing should control the network state

Most ISP billing tools stop at invoices. Operators still need staff to confirm payments, find the subscriber, open the router, change a queue, check RADIUS, and then explain what happened to support.

ISPAgents is built for the full workflow:

  • Create prepaid and postpaid plans.
  • Match payments from mobile money, cards, bank transfers, or manual receipts.
  • Queue or restore service when payment is confirmed and access mapping is trusted.
  • Preview, approve, and audit overdue subscriber suspension or shaping through RADIUS or router control.
  • Show support the payment state, router state, CPE state, and ticket history.
  • Keep an audit trail for every billing-driven service change.

What operators can control

WorkflowWhat ISPAgents does
Payment receivedMatches the receipt, updates the account, and queues restore.
Invoice overdueSends reminders, applies dunning rules, and prepares suspension.
Subscriber restoredSends RADIUS CoA or router command only through a validated path and records proof.
Plan changedUpdates billing and access policy together after mapping is verified.
Support ticket openedShows payments, access state, CPE health, and outage context.

Built for small and growing ISPs

Small ISPs cannot afford a system that requires dedicated operations staff just to keep billing and routers aligned. ISPAgents is cloud-managed, so the ISP does not need to deploy and maintain a heavy billing server before seeing value.

The platform can start with one workflow, such as payment-to-restore, then grow into CRM, field service, inventory, RADIUS, CPE management, and AI-assisted support.

Key modules

  • CRM and subscriber records
  • Plans, orders, upgrades, downgrades, cancellations, and relocations
  • Prepaid and postpaid billing
  • Credits, refunds, deposits, statements, aging, and reconciliation
  • RADIUS, MikroTik, and custom connector access control
  • WhatsApp-first support context
  • Technician jobs, photos, signatures, and stock usage
  • Inventory, serialized assets, routers, CPEs, ONTs, and antennas
  • Operator-reviewed AI summaries and copilots

Migration path

Operators do not need to replace everything on day one. ISPAgents can coexist with the current stack first:

  1. Import customers, plans, and balances from CSV or Excel.
  2. Connect existing MikroTik routers or FreeRADIUS.
  3. Run payment matching and restore workflows in parallel.
  4. Move support, inventory, and field work when the team is ready.
  5. Make ISPAgents the operating source of truth after the first stable cycle.

FAQ

Can ISPAgents automatically cut off internet for unpaid invoices?

Only after the tenant proves subscriber identity, billing state, access mapping, command preview, approval rules, audit evidence, and rollback. The access action can use validated managed RADIUS, existing FreeRADIUS, MikroTik direct control, or custom agents depending on the network.

Can we keep our existing FreeRADIUS?

Yes. ISPAgents should integrate with an existing FreeRADIUS deployment first where that is the safest path, then move selected workloads to managed RADIUS only when the operator wants less infrastructure to maintain and has validated the cloud auth path.

Is this only for large ISPs?

No. The product is designed to be flexible for small operators while still supporting the accounting, inventory, field service, and network inventory depth needed as the ISP grows.

Next step

See how this works in your network.