Subscriber identity
Maintain a clear relationship between the customer account and network access identity.
AAA & subscriber access
Keep authentication and billing policy aligned with the subscriber account.
RADIUS and subscriber billing are most effective when identity, package, authorization policy and account state are managed as part of the same operational lifecycle.
WORKFLOW FOCUSRADIUS & ISP Billing Software
Evaluate this use case together with customer lifecycle, finance and network ownership—not as an isolated feature.
What to evaluate
Operational questions that matter in this workflow.
These are practical considerations for comparing software and designing your deployment.
Package policy
Keep service package and access policy changes understandable to both billing and network teams.
Accounting context
Use session/accounting information as operational context around the subscriber.
PPPoE and Hotspot
Support access models where centralized subscriber policy is useful.
Expiry handling
Coordinate account state and service policy when a package becomes due or is restored.
Auditability
Keep changes and financial events easier to trace during support or collection review.
Why the connection matters
Subscriber state affects more than one department.
A payment can change service state. A support issue can depend on session or ONU context. A reseller collection belongs to a financial hierarchy. Sweet Billing is structured around those relationships.
Billingcycle & ledger
AccessPPPoE / Hotspot
NetworkMikroTik / OLT
Customerportal / support
MikroTik operations
MikroTik PPPoE Billing: From Customer Expiry to Session Visibility
Understand the operational pieces behind MikroTik PPPoE billing: provisioning, package control, session visibility, expiry, reconnection, logs and customer communication.
Read practical guide