Skip to content
Blog

Why ISP billing and RADIUS belong in the same data model

When authentication and billing live in separate systems, every package change becomes a synchronization problem. Here is how we approached it in Netora.

E-Net Engineering

Most ISPs we speak with run authentication and billing as two separate systems. A RADIUS server decides who gets online. A billing tool decides who has paid. Somewhere between them sits a script, a CSV export, or a person.

That arrangement works while the subscriber base is small. As it grows, the gap between the two systems turns into a steady source of operational problems.

The synchronization problem

Consider what happens when a subscriber’s package expires:

  1. The billing system marks the account as unpaid.
  2. Something must tell the RADIUS server to reject the next authentication.
  3. Something must disconnect the current session, or the subscriber stays online until their router reconnects.
  4. When payment arrives, all of this must happen in reverse.

Each step is a chance for the two systems to disagree. The subscriber who stays online for weeks after non-payment is not a billing bug or a RADIUS bug. It is an integration bug, and integration bugs are the hardest to notice because neither system reports an error.

One subscriber, one state

In Netora, the subscriber is a single record with an explicit lifecycle state: active, suspended, expired, terminated. Both the AAA path and the billing path read and write that same state.

  • When the RADIUS service receives an Access-Request, it evaluates the subscriber’s current state and plan — not a copy exported from somewhere else.
  • When a billing rule suspends an account, the same transaction can trigger a Change-of-Authorization or disconnect for any active session.
  • When a payment is recorded, the ledger entry and the state change happen together.

There is nothing to synchronize because there is only one copy of the truth.

The ledger is part of the model

A related decision was to treat the customer ledger as a first-class part of the subscriber model rather than a reporting feature. Charges, payments and adjustments are recorded as entries; the balance is derived from them.

This matters operationally. When a subscriber calls support asking why they were disconnected, the answer is visible in one place: the ledger shows the unpaid charge, the state history shows the suspension, and the session log shows the disconnect.

What this does not mean

Keeping one data model does not mean everything must run in one place. The AAA services in Netora are designed to run close to the network edge, where latency and availability matter most, while management interfaces can run elsewhere. The point is shared state, not shared hardware.

Takeaway

If your team regularly reconciles “who is online” against “who has paid”, the problem is usually not either system on its own. It is the boundary between them. Removing that boundary is one of the most effective reliability improvements an ISP can make.

Get started

Ready to see it on your own setup?

Tell us what you run today. An engineer will walk you through the right E-Net Communication product for your network, infrastructure or AI workload.