MikroTik ISP billing software for connected subscriber operations.
XIMS connects MikroTik RouterOS with subscriber management, RADIUS AAA, PPPoE and hotspot access, bandwidth policies, billing, GST, payments, complaints and field operations. Customer, commercial and network actions work from one subscriber record instead of separate systems and manual scripts.
One subscriber record from onboarding to network access
Broadband operators often manage customers in one application, billing in another and MikroTik routers through scripts or separate utilities. This creates delays, duplicate records and uncertainty about which system holds the correct status.
XIMS connects the subscriber’s commercial account with the access workflow. The same record used for KYC, plan selection and billing can drive PPPoE or hotspot access, bandwidth policy, suspension, reconnection, payment updates and support operations.
When a plan changes, the authorised network policy can change with it. When an account becomes eligible for restoration, the operational workflow can restore access without manually updating multiple systems. Every permitted action remains associated with the subscriber and the operator who performed it.
MikroTik operations controlled from the ISP platform
Direct RouterOS integration with RADIUS working alongside it
XIMS can communicate with MikroTik RouterOS through the native API for supported configuration and operational actions. RADIUS handles authentication, authorization and session accounting, while the API supports approved router-management workflows.
- The customer is created or onboarded in XIMS.
- A broadband or hotspot plan is assigned.
- XIMS creates or updates the supported subscriber-access configuration.
- The subscriber authenticates through PPPoE, hotspot or another configured access method.
- RADIUS applies the authorised service policy and records session accounting.
- Billing and payment status remain associated with the same customer record.
- Approved plan changes, suspension, restoration or disconnect actions are sent through the appropriate integration path.
- Operators review customer, payment, session and support context from XIMS.
XIMS-native billing, CRM, support and workflow capabilities; native RADIUS/AAA; MikroTik RouterOS API integrations; device- or deployment-specific configurations; and roadmap or limited-availability functionality are distinguished clearly — an integration-dependent function is never described as universally native across every MikroTik deployment.
Commercial status and service access working together
XIMS supports prepaid, postpaid and hybrid ISP billing workflows. Invoices, renewals, adjustments, payment receipts and collection activity remain connected to the subscriber whose network access is being managed.
- Automated recurring invoicing
- Prepaid, postpaid and hybrid plans
- GST-ready invoicing for Indian operators
- Proration and plan changes
- Credit notes and adjustments
- Advance renewals and grace-period workflows
- Dunning and collection follow-up
- Payment receipts and account ledger
- Bank and gateway reconciliation
- Franchise and reseller settlement workflows
XIMS connects with supported payment gateways and UPI-enabled collection workflows. Once a payment is verified and posted to the subscriber’s account, the corresponding authorised restoration process can proceed without requiring the billing team to update separate network tools. See ISP billing software India for the complete billing platform.
Operate the wider ISP workflow from XIMS
MikroTik integration is one part of the operating platform. XIMS also supports the commercial and service workflows surrounding network access.
Compare complete operating workflows—not feature labels
Some systems record invoices but leave router configuration, RADIUS, customer support and fibre operations in separate tools. Others rely heavily on scripts or manual RouterOS administration. XIMS is designed to connect the commercial subscriber record with the authorised access workflow.
| Evaluation area | Conventional billing-only or script-driven setup | XIMS with MikroTik integration |
|---|---|---|
| Subscriber record | Customer information may be split between billing, router and support tools | CRM, billing, access and support context connected to one subscriber record |
| MikroTik integration | Manual RouterOS work, scripts or separate utilities may be required | Supported actions handled through native RouterOS API integration and RADIUS workflows |
| PPPoE operations | Credentials and profiles may be maintained separately | PPPoE access linked to subscriber plan and commercial status |
| RADIUS AAA | May require an independent RADIUS platform and manual synchronisation | Authentication, authorization and accounting connected with XIMS subscriber operations |
| Plan and speed changes | Billing update and router update may be separate tasks | Approved plan and policy workflow can update the commercial and access context together |
| Suspension and restoration | Manual coordination between accounts and network teams | Controlled workflow connects account status with supported access actions |
| Hotspot services | Often managed in a separate hotspot utility | Supported hotspot, voucher and customer workflows managed within the XIMS environment |
| GST and Indian payments | May require external customisation or accounting workarounds | GST-ready billing and supported UPI/payment-gateway workflows |
| Complaints and field service | Separate helpdesk with limited network context | Ticket, SLA, field assignment and subscriber context connected within XIMS |
| Franchise and reseller operations | Often handled through spreadsheets or add-on modules | Multi-tier partner workflows, wallets, commissions and scoped access |
| FTTH and OLT operations | Fibre access commonly remains in a separate NMS | Supported OLT/ONU and FTTH workflows available through the XIMS ecosystem |
| Audit trail | Actions may be distributed across router logs, scripts and billing records | Authorised platform and integration actions recorded against operational context |
| Reporting | Separate exports must be combined manually | Commercial, subscriber, payment and supported access information available for joined reporting |
| Customer self-care | May require a separate application | Supported white-labelled customer app and portal connected to XIMS |
| Migration | Subscriber and router data may be moved independently | Structured data mapping, trial migration, reconciliation and controlled cutover |
The important question is not whether a platform can create an invoice or add a PPPoE user. The real test is whether customer onboarding, payment status, RADIUS policy, MikroTik access, complaint handling and operational reporting work as connected parts of one controlled subscriber lifecycle.
XIMS is designed for operators that want MikroTik to remain an important network platform without forcing business and support teams to operate through disconnected systems.
Built for different MikroTik-powered service models
Network actions require operational control
Router-management capability should not mean unrestricted access. XIMS uses role-based permissions and operational audit history so sensitive actions can be limited to authorised users. Depending on the deployed configuration, the control model can cover:
- Role-based access
- Tenant and branch scope
- Approval-sensitive workflows
- Operator identity and timestamps
- Action reasons and subscriber context
- Integration-event history
- Authentication and accounting records
- Reviewable suspension and restoration activity
Move from disconnected billing and router operations with controlled reconciliation
- Discovery — document subscribers, plans, billing cycles, PPPoE identities, profiles, routers, IP pools, payment status, partner structures and current operating exceptions.
- Data mapping — map existing customer, plan, billing and access fields to the XIMS data model; resolve duplicates, missing identifiers and inconsistent plan names before cutover.
- Trial migration — import a controlled sample and validate subscriber totals, balances, plan assignments, access identities and reporting outputs.
- Shadow validation — run agreed checks against the existing environment; compare billing results, payment status and selected access workflows before switching production operations.
- Controlled cutover — move authorised workflows in an agreed sequence, with rollback criteria and responsible owners identified in advance.
- Hypercare — monitor authentication, billing, payments, suspensions, restorations and support exceptions through the first operational and billing cycles.
The full method is documented under ISP billing software migration.
Frequently asked questions
What is MikroTik ISP billing software?
MikroTik ISP billing software connects customer accounts, broadband plans, invoices and payments with subscriber-access operations on MikroTik RouterOS. XIMS adds CRM, RADIUS AAA, PPPoE and hotspot workflows, support, partner management and reporting around that connected subscriber lifecycle.
How does XIMS connect with MikroTik routers?
XIMS uses supported MikroTik RouterOS API integrations for approved router-management actions. RADIUS handles authentication, authorization and accounting for configured subscriber-access services. The available actions depend on the deployment design and enabled integrations.
Does XIMS support MikroTik PPPoE billing?
Yes. XIMS connects subscriber plans and billing status with supported PPPoE provisioning, authentication, policy and session workflows. Relevant subscriber, payment and access context can be reviewed through the XIMS operating environment.
Does XIMS include RADIUS AAA?
Yes. XIMS supports RADIUS authentication, authorization and accounting for configured broadband and hotspot deployments, including plan-based policy, session accounting and supported Change of Authorization or disconnect workflows.
Can XIMS manage MikroTik hotspot services?
Yes. Supported deployments can manage hotspot users, profiles, packages, vouchers and captive-portal workflows for public Wi-Fi, hospitality and prepaid-access use cases.
Can a payment restore a suspended subscriber?
XIMS can connect verified payment status with an authorised service-restoration workflow. The precise timing and access action depend on the ISP’s billing rules, grace policies and network configuration.
Does XIMS support bandwidth and FUP policies?
Yes. Broadband plans can carry supported bandwidth, fair-usage and policy attributes that are applied through the configured RADIUS or RouterOS integration workflow.
Can XIMS work with MikroTik and GPON OLTs together?
Yes. XIMS can support operators using MikroTik for routing or subscriber access alongside supported GPON/EPON OLT and ONU/ONT workflows through XIMS Access. Device compatibility and supported write operations should be confirmed during solution design.
Is XIMS suitable for Indian ISPs?
Yes. XIMS includes India-focused operational capabilities such as GST-ready billing, supported UPI and payment-gateway workflows, franchise and reseller management, PPPoE/RADIUS operations and support for mixed MikroTik and FTTH environments.
Can an ISP migrate existing subscribers and PPPoE users to XIMS?
Yes. Migration should follow discovery, data mapping, trial import, reconciliation, controlled cutover and hypercare. The exact migration plan depends on the source billing system, RouterOS configuration and quality of subscriber and access data.
Does XIMS require scripts for routine MikroTik operations?
XIMS is designed to use supported RouterOS API and RADIUS workflows for routine integrated operations. Any deployment-specific scripts or custom device configurations must be documented separately rather than presented as universal product behaviour.
How can an ISP evaluate XIMS with MikroTik?
Book a technical walkthrough with details of the current RouterOS versions, router roles, PPPoE or hotspot design, RADIUS setup, subscriber scale, plans and payment workflow. Xonware can then demonstrate the relevant operating flow and confirm integration scope.
See XIMS working with your MikroTik operating model
Bring your current RouterOS environment, subscriber-access method, broadband plans and billing workflow to a technical session. Xonware will map the customer, payment, RADIUS and MikroTik operations that apply to your network.