Xiva runs customer lifecycle, product catalog, billing, finance, resource inventory, and dealer-channel operations on one platform — built with TMF-style APIs and an ODA-inspired domain architecture, so your integration and systems teams recognize the shape of the system from day one.
Most operators don't lack systems — they lack one system that agrees with itself. Six patterns show up again and again in a BSS modernization review.
A pricing decision turns into a multi-week release because the catalog, ordering, and billing systems don't share a model.
A single TMF-style product catalog and a visual offering designer let commercial teams model plans, bundles, and pricing directly against what ordering and billing already read.
Usage, discounts, and manual adjustments drift out of sync with what's actually billed — and revenue leaks out through the gap.
Governed billing runs, rated-usage gating, and a rules-driven dunning workflow keep billing tied to what was delivered — and to what's been collected.
The general ledger closes independently of the billing system, so finance reconciles by spreadsheet instead of by design.
Billing and payment events post to a double-entry ledger automatically, with period lock and reconciliation runs that compare billed, collected, and posted totals.
Commission is calculated in a side spreadsheet and nobody can say with confidence which channel actually sold what.
A purpose-built dealer platform attributes every transaction to its channel, calculates commission by scheme, and settles it through a dealer wallet — auditable end to end.
SIMs, MSISDNs, eSIM profiles, and vouchers are tracked in separate tools that don't agree with each other.
SIM, MSISDN, eSIM, and voucher inventory live in one resource model, with dealer stock transfer and redemption tracked against the same records billing and provisioning use.
Configuration changes ship straight to production, and nobody can say with confidence who changed what, or when.
Role-based access, a dual-path audit log, and a scoped feature-flag system with an approval workflow give operations a governed way to change behavior without a redeploy.
Six layers carry a customer from first contact through to a governed, auditable revenue record — commercial, monetization, operational, channel, control, and integration.
Customer 360, onboarding, quoting, product catalog, prices, bundles, and benefit policies.
Billing runs, invoice production, deposits, presentment, payment allocation, and the dunning lifecycle.
SIM, MSISDN, eSIM, and voucher inventory, resource orders, shipping, and network-provisioning handoff.
Dealer hierarchy, wallet, commission schemes, stock transfers, risk, territory, and attribution.
RBAC, audit logging, scoped feature flags, notifications, agreements, consents, and platform configuration.
An adapter model for PSP, KYC, network, ERP, tax, messaging, shipping, and data ecosystems.
Each domain owns its own data model and API surface, following an ODA-inspired domain architecture — so your teams can integrate against the specific domain they need, without touching the rest of the platform.
Party and customer lifecycle, credit management, onboarding, quoting, and account structure.
Read more →Governed billing runs, invoicing, our visual Invoice Designer, dunning, deposits, and presentment.
Read more →Double-entry ledger, payment allocation, reconciliation, and period governance.
Read more →Plans, devices, bundles, pricing, and a visual Product Offering Designer.
Read more →SIM, MSISDN, eSIM, and voucher inventory, plus warehouse stock management, dealer transfer, resource ordering, and shipping.
Read more →Dealer hierarchy, wallet, commission engine, and channel attribution.
Read more →Tiered loyalty programs, points accrual and redemption, and account-level eligibility overrides.
Read more →Trouble-ticket lifecycle with SLA tracking, escalation, and customer-facing status visibility.
Read more →Anomaly detection on billing and payment patterns, recommendation patterns, and AI-ready service hooks.
Read more →Role-based access, audit logging, scoped feature flags, and notification administration.
Read more →A closer look at what each domain actually covers, and the operator outcome it's built to support.
| Domain | Representative capabilities | Business value |
|---|---|---|
| CRM & Customer | Customer 360, individual/organization profiles, customer hierarchy, credit profile, KYC document capture, consents, agreements, leads, opportunities, and quotes. | Faster subscriber activation and better account visibility. |
| Product Catalog & Offers | Catalogs, offerings, bundles, categories, rate plans, prices, commercial benefit policies, eligibility rules, and offering wizard. | Faster offer launch with pricing and benefit discipline. |
| Quote, Order & Fulfillment | Quote builder, quote-to-order conversion, product ordering, resource ordering, service fulfillment, and activation handoff. | Connects commercial sales to operational fulfillment. |
| Billing & Collections | Billing runs, customer bills, invoices, invoice PDFs, invoice designer, deposits, presentment, dunning, late fees, and service lifecycle actions. | Controls the revenue lifecycle and reduces leakage. |
| Finance & Accounting | GL, journals, accounting periods, payment allocation, reconciliation, tax, revenue recognition, ECL, and async posting. | Finance-grade traceability and revenue assurance. |
| Resource & Inventory | SIM, MSISDN, eSIM, voucher/ePIN, warehouses, vendors, stock movement, resource orders, and shipping. | Improves fulfillment visibility across assets. |
| Dealer Network | Dealer hierarchy, contracts, wallet, transactions, commissions, clawbacks, stock transfer, territory, risk, and analytics. | Grows indirect channels with operational accountability. |
| Platform | RBAC, audit, feature flags, notifications, email templates, agreement templates, currencies, compliance references, and integrations. | Operates with control, governance, and extensibility. |
Party, account, and credit data live in a single customer model, so onboarding, credit decisions, and quoting are all reading the same record — not three different ones that drift apart.
Individual and organization parties linked into a customer hierarchy that supports parent/child and family-member relationships for shared billing accounts.
Configurable credit profiles, scoring, and threshold monitoring, with an external credit-bureau connection where one is configured.
A multi-step flow covering identity capture, product selection, MSISDN assignment, and agreement signature in one pass.
Structured document capture and identification records attached to the customer, ready for a regional identity-verification integration.
Build quotes against the live product catalog and convert them into orders without re-keying anything.
Filterable views of credit exposure and risk across the customer base, for teams who need the number before the meeting, not after.
Billing history, active services, resources, credit standing, and account timeline are assembled from the same customer record — so a support agent, a credit analyst, and a billing lead are all looking at the same facts, not three exports that disagree.
Billing runs are a governed process, not a script someone remembers to run. Every run is tracked, every invoice is traceable, and collections acts on overdue accounts instead of just reporting on them.
Dry-run and execution modes, rating-run gating, and a governance record kept against every billing run.
Bill state, finalization, and lifecycle events tracked as an auditable trail, not a single mutable row.
PDF generation plus a visual invoice designer for building and publishing branded templates without a code release.
Invoices delivered by email on a configurable schedule, with a presentment pipeline and document retention policy.
Configurable rules and stages progress overdue accounts through notification, fee, suspension, and, as a last resort, termination.
Deposit wallets and refund policy management for prepaid and risk-managed accounts.
Build and publish branded invoice templates — logo, layout, and line-item bindings — without waiting on an engineering release. Every template is versioned, so a previous layout is never lost, and nothing reaches a customer until it's explicitly published.
Finance shouldn't have to take billing's word for it. Xiva posts billing and payment activity to a real double-entry ledger, with the governance controls a finance team expects from day one.
IFRS/GAAP-style account types and hierarchy, with balances maintained atomically as activity posts.
Every journal entry is enforced to balance before it posts — debits equal credits, by construction.
Billing and payment events post to the ledger asynchronously, with retry and reconciliation so a dropped message doesn't mean a dropped journal entry.
Payments are mapped directly to the bills they settle, with discounts and write-offs tracked as distinct allocation types.
Reconciliation runs compare billed, collected, and posted totals, and surface variance rather than bury it.
Open, preliminary, closed, and locked period states, so a closed period stays closed.
Recognition scheduling for multi-period obligations, tied back to the originating bill line.
Every account carries an IFRS/GAAP-style type and rolls into a hierarchy. Every journal entry is rejected unless its debits equal its credits. Balances update atomically as activity lands, so "what does the ledger say right now" is never a batch job away — and a closed period stays closed until someone with the authority to reopen it does.
Nine dedicated modules cover the full dealer lifecycle — hierarchy, wallet, commission, stock, risk, and analytics — so channel performance is a report, not an argument.
Dealer roles, contract terms, and a fallback commission rate for dealers without an active scheme assignment.
Flat, tiered, and product-based commission schemes, with accrual, clawback, and payout tracked per dealer.
Prepaid balance, reservations, and top-ups, with configurable low-balance alerting.
Activations, top-ups, and refunds are attributed to the selling dealer automatically, across the transactions that touch commission.
Requests, approvals, and inventory adjustments between warehouse and dealer stock.
Velocity rules and risk scoring to flag channel fraud early, plus daily performance snapshots per dealer.
Offerings, specifications, pricing, and terms are modeled as related entities in one TMF-style catalog, so ordering and billing are always reading the plan commercial teams actually published.
Product offerings, specifications, pricing, and terms as first-class, related entities.
Family & friends groups and benefit assignment applied at the account level.
Build and publish offerings without an engineering release, with a pre-publish validation check.
Control which offerings are available to which customers, at the point of ordering.
A guided offering builder walks a product team through specification, resource/service linkage, pricing, terms, and eligibility — then runs a pre-publish check before the offering goes live in the catalog your ordering and billing systems already read from.
Physical and digital resources are tracked in one model, so fulfillment status is never a guess.
Vendor batches, warehouse-level stock control, and duplicate-entry detection across incoming inventory.
Batch import, number ranges, and reservation handling for physical SIM stock.
eSIM profile and SM-DP+ configuration handling alongside physical SIM inventory.
Dealer transfer and point-of-sale redemption, reconciled against a configurable liability policy.
Resource orders linked directly to product orders, so fulfillment and commercial intent stay in sync.
Carrier configuration and webhook support for physical SIM and device fulfillment.
Vendor stock arrives into a warehouse, gets tracked at the batch and unit level, and moves out again through a request-and-approval transfer workflow to dealer stock — with every movement recorded, not just the current count.
A TMF621-aligned ticket model with real priority-based SLA deadlines, breach warnings, and escalation — so "we're on it" has a timestamp behind it.
State transitions, comments, attachments, watchers, and customer linkage on every ticket.
Priority-based SLA deadlines, breach warnings, and escalation actions, with support metrics for team leads.
Knowledge articles linked to tickets, customer satisfaction capture, and an approval flow for closure and credits.
Tickets route to an assignee and team, with watchers kept in the loop as status changes.
Tiered loyalty programs with real earning-rule and tier-assignment logic, plus a customer-level eligibility override for the support cases a general rule set can't anticipate.
Programs, tiers, loyalty accounts, points, transactions, and computed tier progress.
Promotion actions, eligibility rules, events, and bulk operations for retention campaigns.
Points history and program-level summary views for support and marketing teams.
Every loyalty program runs on a shared eligibility rule set — but a support case sometimes needs an exception. A customer-level override lets a CSR force a specific customer in or out of a program without touching the rules everyone else runs on.
Usage thresholds and billing-anomaly detection run as real, scheduled statistical checks. Recommendation and generative-AI hooks exist in the platform for teams ready to plug in a model provider.
Scheduled monitoring flags accounts approaching or exceeding usage allowances.
Statistical outlier checks on billing and payment patterns surface irregularities for review.
Rule-based product and pricing suggestions, with a service architecture ready for a trained model.
A generative-AI service layer (chat, email drafting, report summarization) ready to connect to your model provider of choice.
Governance isn't a compliance checkbox here; it's how operations actually makes changes day to day.
Role, group, and permission structures enforced at the API layer, not just the UI, across business functions.
Model-level and API-level audit records support traceability across every non-read operational action.
Scoped runtime flags support staged rollout, with an approval step required for changes that touch production billing.
Notification outbox, alert thresholds, email templates, email types, and send logs.
Agreement templates, digital agreement flow, consent records, and document-type references.
Languages, countries, currencies, credit profiles, KYC types, shipping, and integration settings.
Async batch jobs, an outbox pattern, idempotency keys, and end-to-end traceability — the patterns that keep a retried request or a dropped message from becoming a finance incident.
Xiva's APIs follow TM Forum Open API naming and resource conventions across product catalog, party, customer bill, trouble ticket, and related domains — TMF-style APIs that your integration and systems-integration partners will recognize on sight.
The platform's domains are organized around an ODA-inspired architecture: customer, product, billing, finance, resource, and channel management are separated as distinct domains, each with its own data model, so an integration or extension can target the specific domain it needs without pulling in the rest of the platform.
This is a foundation for TMF/ODA-aligned integration work. Where your compliance program requires a specific certified API surface, we scope that as part of solution design — ask your Xiva contact for the current alignment map for your target TMF APIs.
"Aligned" means Xiva's API paths and resource fields follow the naming and shape of that TM Forum Open API — not that Xiva holds formal TM Forum certification for it.
Xiva is built to sit inside your existing operator stack, connecting outward through adapters scoped to your environment.
Connect the PSP of your choice for card, wallet, and local payment methods.
Plug in a regional identity-verification provider for onboarding compliance.
Trigger activation, suspension, and resource actions against your network and provisioning layer.
Extend the ledger outward to a corporate ERP for group-level consolidation.
SMS, email, and push delivery through your preferred provider.
Carrier-specific integration for physical SIM and device delivery.
| Integration area | Xiva role | Typical operator counterpart |
|---|---|---|
| Payment & settlement | Payment records, allocation, deposit wallet, and settlement lifecycle structures. | PSP, bank, wallet provider, card acquirer. |
| KYC & compliance | Document capture, consent, profile, and compliance reference structures. | Identity verification provider, regulatory registry, compliance workflow. |
| Network provisioning | Provisioning trigger, action execution, and service/resource handoff structures. | HLR/HSS/UDM, OCS, PCRF/PCF, ESB, network provisioning gateway. |
| ERP & finance | GL posting, journal entries, reconciliation, and finance reporting structures. | ERP, corporate GL, tax system, revenue assurance platform. |
| Messaging & notification | Notification outbox, email templates, email delivery logs, and alert thresholds. | SMTP, SMSC, WhatsApp, push notification provider, campaign platform. |
| Logistics | Shipment, tracking, pickup request, and provider configuration structures. | Shipping carriers, courier aggregators, fulfillment partners. |
One operating system for the customer, revenue, and channel lifecycle — one platform to govern, not five to reconcile.
TMF-style APIs and a domain-separated architecture your integration team can map directly to your systems landscape.
A ledger that closes on your terms — double-entry, period-locked, and reconciled against billing and payments, not a spreadsheet.
A dunning engine that acts, not just reports — fewer manual write-offs, fewer silent losses.
Commission, wallet, and attribution in one system, so channel performance is a report, not an argument.
Through structured catalog, pricing, benefits, and quote/order flow.
Through billing, dunning, deposits, payment allocation, and reconciliation.
Through dealer wallet, commissions, stock movement, and attribution.
Through RBAC, audit history, feature controls, and notification governance.
Xiva BSS is a telecom operating platform for MNO and MVNO modernization, connecting customer lifecycle, product monetization, billing, finance, inventory, dealer channels, and platform control in one integrated capability layer.
Customer onboarding, product catalog, billing, inventory, support, and platform configuration for a new market proposition.
Dealer wallet, commissions, stock movement, voucher/ePIN, SIM/MSISDN, and channel attribution in one operating model.
Governed billing runs, invoice lifecycle, PDF templates, dunning, GL posting, payment allocation, and reconciliation.
Catalog, offers, bundles, rate plans, prices, benefits, eligibility, and quote-to-order controls for faster market response.
Traceability across bills, payments, allocations, deposits, credits, dunning events, and accounting periods.
RBAC, audit trail, feature flags, notification administration, agreement templates, and integration governance.
| Phase | Focus | Output |
|---|---|---|
| 1. Business capability alignment | Map operator priorities across customer, product, billing, finance, inventory, dealer, and support domains. | Target operating model and prioritized capability scope. |
| 2. Solution blueprint | Define data model, integrations, commercial flows, billing rules, finance controls, and operational workflows. | Architecture blueprint and delivery backlog. |
| 3. Configuration & integration | Configure catalogs, products, roles, workflows, templates, and integrate selected operator partners. | Configured environment connected to required ecosystem systems. |
| 4. Controlled rollout | Use operational controls, feature governance, audit history, and environment gates to manage phased adoption. | Operational readiness and phased go-live model. |
Delivery philosophy: Xiva is positioned as a configurable BSS capability layer, implemented around operator-specific commercial models, regulatory context, integration partners, and deployment priorities.
A BSS platform for operators that need commercial agility, billing accuracy, finance traceability, inventory visibility, and dealer-channel growth within one governed operating model.