ISP billing automation works best when the billing system, RADIUS server, and router policies all read from the same subscriber state. The practical goal is simple: when a subscriber pays, their service should renew automatically; when a plan expires, the network should enforce that change without manual router edits.
Start with a single subscriber source of truth
Store each subscriber plan, expiry date, connection type, NAS assignment, and billing status in one CRM record. MikroTik should not be the master database for subscriber commercial state. It should receive authorization decisions through RADIUS.
Connect MikroTik through RADIUS
Point MikroTik PPPoE or Hotspot authentication to FreeRADIUS. The RADIUS layer should return plan speed, session limits, and vendor-specific attributes such as MikroTik-Rate-Limit. This keeps plan changes inside the billing platform instead of scattered across router profiles.
Automate renewals from payment events
When UPI, card, net banking, wallet, or manual payment is recorded, the billing system should match the payment to an invoice, extend validity, generate a GST invoice or receipt, and trigger CoA if the subscriber is online. This is the step that removes most daily manual work for collection teams.
Use clear exception queues
Keep dashboards for failed payments, expired subscribers, RADIUS authentication failures, and invoice mismatches. Automation does not remove operations work; it narrows the work to the few cases that need human attention.
NowaCRM combines these flows into one ISP billing workflow: subscriber CRM, invoice generation, FreeRADIUS authorization, MikroTik-friendly attributes, payment reconciliation, and support tickets are tied to the same customer record.