From order to cash, on one platform.
B.O.S.S. runs the whole operator stack — subscriber lifecycle, service catalogue, provisioning, rating, invoicing, revenue assurance and customer care — without the middleware layer that usually sits between them.
- Prepaid & postpaid
- TRAI & GCC compliant
- Cloud or on-premise
The integration layer is where operator margin goes to die
Separate OSS and BSS products mean a permanent middleware project: adapters to maintain, reconciliations that never quite balance, and a launch cycle measured in quarters.
Revenue leakage
Usage recorded on the network never reaches the invoice. Services stay active after termination. Discounts outlive their campaign. Each gap is small; together they are a percentage of revenue.
Slow time-to-market
Launching a new plan means touching the catalogue, the rating engine, the provisioning scripts and the portal — four teams, four release cycles, one missed window.
Manual provisioning
Orders are re-keyed into network tools. Activation takes days, errors take longer, and the customer’s first experience of the brand is a delay.
Fragmented customer view
Care agents open three systems to answer one question. The subscriber repeats themselves, and the call takes four minutes longer than it should.
Six modules, one subscriber record
Every module reads and writes the same customer, service and usage objects. There is no synchronisation job between them because there is nothing to synchronise.
Subscriber lifecycle
Acquisition, activation, plan change, upgrade, suspension, reactivation and termination — each with its own rules, approvals and downstream network actions.
Service catalogue
Define the full portfolio once — pricing, eligibility, bundling rules, provisioning parameters — and launch a new plan as configuration rather than a release.
Order management & provisioning
Automated fulfilment straight to network elements over NETCONF, SNMP or REST, with real-time order status, rollback on failure and full activation history.
Convergent billing
One rating engine for prepaid and postpaid, recurring and usage-based, with taxation, proration, credit control, dunning and multi-currency invoicing.
Revenue assurance
Automated reconciliation between network usage records, mediation output and billing. Discrepancies surface as exceptions with an owner, not as a year-end write-off.
Customer care
One screen with the subscriber’s services, usage, invoices, payments and tickets. Agents resolve on the first call because nothing is in another system.
Five stages, no re-keying, no reconciliation gap
The same object travels the whole way. That is the difference between an integrated platform and two products with an adapter between them.
Capture
Order taken through portal, app, retail or partner API, with identity verified inline by H.A.R.T. eKYC.
Resolve
The catalogue turns the order into a priced, provisionable service instance with eligibility and bundle rules applied.
Provision
Network elements are configured automatically and the activation is confirmed back to the order — or rolled back cleanly.
Rate
Usage and recurring charges are rated in real time against the subscriber’s plan, balance and credit position.
Assure
Invoices are issued, payments reconciled, and network usage checked against billed usage before the cycle closes.
Find the leakage before the auditor does
Every operator loses revenue between the network and the invoice. B.O.S.S. treats that gap as a first-class object: measured continuously, attributed to a cause, and assigned to someone.
- Three-way reconciliation. Network usage records, mediation output and billed usage are compared on every cycle, not sampled quarterly.
- Orphan service detection. Services live on the network with no billing record — or billed with no network presence — are flagged automatically.
- Discount and promotion expiry. Time-bound pricing ends when it is supposed to, without a manual clean-up campaign.
- Auditable trail. Every rating decision, adjustment and write-off is recorded with the user, the reason and the before-and-after value.
Exceptions are routed to a named owner with an SLA. Nothing closes a cycle silently.
One stack instead of a stack of vendors
The typical operator estate is four or five products held together by custom integration. B.O.S.S. collapses that into a single platform, with the network-facing layers supplied by the same vendor.
- No middleware to own. Fewer adapters means fewer failure points and no integration team on permanent standby.
- Native access-layer link. SmartGuard supplies authentication and usage; NMS supplies network state; B.O.S.S. turns both into money and service records.
- Hyperscale ready. Architected to carry hundreds of thousands of subscribers, with horizontal scale-out per module.
- Open at the edges. REST APIs, webhooks and partner portals so retailers, aggregators and payment providers plug in without bespoke work.
Each layer is separately licensable — but when they come from one vendor, the integration is already done.
Operators of every shape run the same platform
Internet service providers
Fibre and wireless broadband with prepaid recharge, franchise hierarchies, self-care and automated dunning.
Cable & MSO operators
Bundled video, voice and data on one bill, with LCO settlement, regional pricing and franchise-level reporting.
Telecom operators
Convergent prepaid and postpaid rating, interconnect handling and regulatory reporting for licensed carriers.
Managed service providers
Recurring service billing across multiple client estates, with per-tenant catalogues and white-labelled portals.
Utilities & smart metering
Usage-based billing for metered services, with reconciliation between field readings and issued invoices.
Government network operators
Public broadband and civic connectivity programmes with subsidy handling, audit trails and localisation compliance.
Regulator-ready in the markets you actually operate in
Compliance is not a feature you bolt on before an audit. B.O.S.S. carries TRAI reporting for India and GCC regulatory requirements for the Gulf as part of the product, with data localisation supported by deployment model.
- Hyperscale growth — sized for hundreds of thousands of subscribers with horizontal scale-out per module.
- Direct engineering support — escalation reaches the team that owns the core architecture, not a partner tier.
- Migration handled — structured data migration from incumbent billing systems, with parallel-run validation before cutover.
| Billing models | Prepaid, postpaid, hybrid; recurring, usage-based, one-off, bundled; proration and mid-cycle changes |
|---|---|
| Taxation | GST (India), VAT (GCC and Africa), multi-jurisdiction rules, e-invoicing hooks |
| Provisioning | NETCONF SNMP TR-069 REST SSH / CLI adapters with rollback |
| Payments | Gateway integrations, auto-debit mandates, wallet and voucher recharge, partial payment and dunning |
| Revenue assurance | CDR-to-bill reconciliation, orphan service detection, exception workflow with ownership and SLA |
| Channels | Subscriber self-care, mobile app APIs, retailer and franchise portals, partner REST API |
| Compliance | TRAI reporting, GCC regulatory pack, configurable data residency, full audit trail |
| Deployment | On-premise, private cloud or XS-managed; high-availability pairs with database replication |
Billing software from a company that has been billing since 1995
Three decades of cycles
B.O.S.S. has closed billing cycles for operators through every generation of access technology since dial-up. The edge cases are already in the product.
Local regulatory depth
India, the UAE and African markets are home ground, not an export. Regulatory change is delivered as product updates, not as a consulting engagement.
The rest of the stack
Take B.O.S.S. alone, or add SmartGuard, NMS and H.A.R.T. and remove three integration projects from your roadmap at the same time.
Before you talk to sales
Yes. Standard practice is a structured migration with a parallel run: B.O.S.S. rates the same cycle alongside the incumbent, the two outputs are reconciled line by line, and cutover happens only once the variance is understood and closed. Migration of subscribers, plans, balances and open receivables is part of the engagement.
No. Modules are separately licensable, and many customers start with billing and subscriber management, then add provisioning or revenue assurance later. The advantage of taking more of the stack is that the integration between modules is already built and supported — but it is a commercial choice, not a technical requirement.
Through a single convergent rating engine rather than two parallel systems. The same subscriber can hold prepaid and postpaid services, share balances across a family or corporate group, and move between models mid-cycle with automatic proration.
Both are supported in-product. Indian deployments include TRAI-aligned reporting and record retention; Gulf deployments carry the GCC regulatory pack and VAT handling. Because XS Infosol operates in these markets directly, regulatory changes arrive as product updates rather than as a change request.
Yes — on-premise, private cloud or XS-managed, with the same build in each case. Operators with localisation obligations typically run on-premise in-country with XS providing remote support, version upgrades and annual maintenance.
A new plan is a catalogue configuration — pricing, eligibility, bundle rules and provisioning parameters — not a code release. Product teams typically build, test and launch a plan within the same working week, without involving engineering.
See your own plans rated in B.O.S.S.
Send us a sample of your tariff structure and usage data. We will configure it in the platform and walk you through a real cycle — catalogue to invoice to reconciliation.