Ask five European operators about their transformation priorities, and four will name cloud modernisation, AI, and network API exposure. Not one will name charging. That is precisely the problem.
Operators today face pressure on several fronts at once: modernising OSS and BSS, simplifying operations, launching digital services, exposing network capabilities through APIs, and building revenue beyond connectivity. Yet one capability sits quietly at the intersection of these ambitions: the ability to turn usage into revenue accurately, in real time and at scale.
Converged Charging Systems transformation deserve renewed attention. They connect network capability, customer usage and commercial value, and they determine whether new offers can be launched with confidence. If charging cannot evolve safely and quickly, new monetisation models cannot scale.
Transformation is not the outcome
Telco transformation is often described as a technology journey: cloud-native platforms, simpler architectures, automated delivery, and modernised customer channels. All of this matters. But it is not the outcome operators are measured against.
The real outcome is commercial and operational performance. Can the operator launch new propositions faster? Can they scale without adding unacceptable risk? Can they convert usage into revenue with high integrity and low friction? Can they protect customers’ trust while the underlying systems evolve?
This is where monetisation execution becomes a strategic execution layer. Commercial performance depends on how quickly and safely network and digital capabilities become billable offers across channels, partners and customer segments. That requires charging capabilities that support real-time decisions, product flexibility, enterprise services, API-based use cases and increasingly dynamic customer journeys.
CCS transformation is where ambition meets operational reality
CCS migration is not simply a platform replacement. It is a controlled move of live commercial logic, customer balances and operational dependencies into a future-ready charging environment.
The charging layer touches balances, usage events, rating rules, tariffs, product history, partner settlements, policy control, billing, customer care, self-service and revenue assurance. It sits deep within both OSS and BSS and carries years of commercial decisions, exceptions and workarounds. That makes CCS migration fundamentally different from replacing a standard IT system.
The decisive question is therefore not only which platform should we migrate to? The more important question is how do we move a live business into a more flexible monetisation environment without disrupting revenue, customers or operations?
The hidden risk is not the cutover. It is the unknown.
In many transformation programs, risk is associated with the final migration event. The cutover becomes the visible moment of pressure.
But the deeper risk sits earlier. It sits in incomplete product logic, undocumented rating rules, legacy integrations no one wants to touch, customer segments that behave differently from the standard case and assumptions about data quality, balance handling, tariff dependencies, policy behaviour or downstream processes.
In our work with European operators, we consistently see that the programs that struggle are rarely those with the most complex target architectures. They are those that entered execution with the most unexamined assumptions.
This is why discovery and validation are not administrative steps. They are core migration disciplines. A migration must prove that balances remain correct, usage is rated correctly, customers are treated consistently and services continue to work. That evidence cannot be assembled at the end. It must be designed into the migration approach from day one.
From migration project to migration factory
The most mature operators treat CCS migration as a controlled migration factory rather than a one-off cutover. A factory creates repeatable processes, structured migration waves, automated validation, reconciliation logic, clear governance and transparent decision points.
This factory model turns complexity into manageable units and reduces risk. Charging transformation usually involves large customer bases, complex product portfolios and multiple stakeholder groups. Commercial, technical and operational teams all need to see what is ready, what is blocked, and what requires a decision. Instead of moving complexity in one large step, operators manage migration in controlled waves -validating outcomes, remediating issues and building confidence wave by wave.
In a recent engagement with a Tier-1 European operator -one of the largest converged charging installations in the EU -this delivery-model shift reduced project duration by around 40% compared to a conventional migration approach. Automated validation, structured waves and reconciliation logic were built into the migration from day one, not bolted on at the end. The lesson is not the percentage. It is that migration risk becomes an engineered variable when the delivery model is designed for it.
Testing must become a strategic capability
Many telco transformations do not fail because the architecture is wrong. They fail because organisations cannot reliably prove that change still works across the full-service journey.
A product may be configured correctly in one system. An order may be captured correctly in another. A billing process may appear stable in isolation. But customers do not experience systems in isolation -they experience outcomes. If an order is captured but not provisioned, or if a product change is reflected in one layer but not in the charging system, the transformation has not been delivered.
For CCS migration, testing must go beyond interface checks. It must validate the commercial and operational journey end-to-end: from order capture through orchestration, provisioning, usage, charging, billing and customer communication. Automation is valuable, but automation alone is not enough. Operators need orchestration, traceability and decision-ready evidence – test results that map back to business journeys and migration readiness, not just isolated technical components.
Future offers will stress today’s charging models
The strategic importance of CCS rises as business models become more dynamic.
5G standalone use cases, enterprise services, private networks, network APIs, quality-on-demand, IoT, edge services, partner ecosystems, or AI-enabled service model, all require flexible product definition, real-time decisions, policy-aware execution and commercial experimentation.
That is why monetisation must be part of the transformation strategy early, not added later as an implementation detail. If charging cannot support the business model, promising use cases stay trapped in pilots or bespoke integrations.
This is already visible in the industry frameworks surrounding network exposure: the CAMARA API portfolio includes Quality on Demand and carrier-billing capabilities, while GSMA Open Gateway provides a route for exposing network capabilities through common APIs. The TM Forum’s Open Digital Architecture points in the same direction. Charging is no longer a downstream billing function. It is an execution layer for programmable, exposable commercial capability.
AI raises the bar for the monetisation stack – it does not lower it
AI is increasingly on the telco transformation agenda, but it does not remove the need for a strong monetisation foundation. It increases it. Agentic workflows and autonomous decisioning only create value when they are grounded in a reliable context – one that spans OSS, BSS, network, customer and commercial domains.
Without a coherent view of who is charged for what, under which policy, and against which product logic, an AI-driven service model just automates the confusion. The same principle applies to CCS migration: systems, data and dependencies must be visible, connected and explainable – otherwise both the human and the automated decisions lose their grounding.
Three questions before committing to a CCS migration path
| 1. What don’t we know? Discovery precedes decisions. The riskiest assumptions in charging transformation are the ones nobody has time to test. 2. What is our evidence model? Migration confidence comes from proof, not optimism. Define upfront how you will prove that balances, usage, product behaviour and customer outcomes remain correct. 3. What business capability are we building? Migration is not the goal. The goal is a monetisation environment that supports 5G, enterprise, API and AI-enabled propositions over the long term. |
Transformation only pays off when monetisation works
The telco industry is moving beyond experimentation. The next phase will be defined by measurable business value. For operators, the practical question is not whether to modernise, but where modernisation creates measurable commercial value first.
CCS migration sits directly at that point. Handled well, it gives the business a safer path to simplify legacy logic, validate customer outcomes, and prepare for API, enterprise and AI-enabled models. Handled poorly, it slows the very transformation it was meant to enable.
Operators reviewing their charging estate should begin with a focused readiness assessment: where does legacy logic create risk today, which migration paths are realistic, and what evidence is required before customers move? Charging may not be the most visible item on the transformation agenda. It is one of the places where that agenda becomes economically real.
