Register with our Knowledge Network to download this and other content...
Just 15 or so years ago Revenue Assurance was seen as an overhead; “How could our technology and processes fail”? Through hard-won experience, Revenue Assurance (RA) is now highly regarded as an essential business function to improve profitability and manage customer experience…
- Defining RA
- RA Scope
- Why RA?
- RA Functional Design Principles
- RA Operating Principles
- RA Solutions and Technology
- RA Process Summary
Revenue Assurance in Telecoms; Basic Principles v2
Publication format: PDF | A4 | 9 pages | English language.
This paper is a solid resource for anyone wishing to better understand the basic principles of RA in the Communications Service Provider (CSP)/Telecoms domain. Ideal for educating team members or senior management as a baseline for building an effective RA strategy.
Read more about the author here.
Join the Knowledge Network
Revenue Assurance Scope
One of the immediate challenges to address regarding the scope of Revenue Assurance activities is whether ‘Cost Assurance’ should be included. If you logically extend the definition above to include the provision and charging of products & services to your business, as well as by your business, then it would make sense. In effect, Revenue Assurance should be heavily focussed on margin and profitability, not just the top-line. There are many attributes that stem from a cost focus to be considered in any Revenue Assurance strategy and operations.
Other common scope questions arise in relation to Fraud Management and aspects of ...
Why Revenue Assurance?
The need for a Revenue Assurance function and process arises out of the many opportunities for revenue to be ‘lost’ or for costs to be unnecessarily inflated (revenue/cost leakage). Leakage can occur for many reasons. Communications Service Providers (CSPs) generally have a reasonably complex process and technical infrastructure (Network/OSS/BSS), with many points of data generation, input, enrichment, transformation, transit and output. Data types are also quite varied and include customer and service records, usage records and operational reference data such as dial-strings, tariffs and offers, business logic and rules. And the advent of digital services is adding even more with new types of transactions and interactions. With the complexity and often real-time nature of the environment, things can sometimes go awry in a big way. Common examples of issues include...
Basic Revenue Assurance Operating Principles
Revenue Assurance practices will vary but in general there are five main areas of operational focus:
- Usage – monitoring all forms of usage and reconciling with expected or normalised usage
- Subscription – examining the services contracted and supplied
- Reference data – assuring the integrity of the business DNA
- Asset – ensuring business assets and related costs are properly managed/optimised
- Receivables – timely and cost-effective management of receivables to drive cash-flow
This end-to-end perspective is sometimes referred to as ‘order-to-cash’ and Revenue Assurance practices may incorporate some or all of these elements.