comarch billing quality assurance - leaflet
TRANSCRIPT
-
8/6/2019 Comarch Billing Quality Assurance - Leaflet
1/2
Seek & destroy every crack in your revenue pipe
Comarch Billing Quality Assurance
Figure 1. The revenue assurance process
Functional overview
Comarch Billing Quality Assurance (BQA) is a modern tool dedicated to detecting revenue
leakage in operators order-to-cash processes. The solution identifies revenue leaks by
monitoring and verifying all critical stages of rating and billing processes.
File- and field-level validation
To work effectively, Comarch Billing Quality Assurance requires proper input data,
representing rating and billing configuration and usage records. If this data is too limited,
certain errors may pass unnoticed. In order to obtain a representative sample, CDRs/EDRs
are filtered with specific testing assumptions, such as a subscriber control group, products
or timestamp of call/event (at the turn of the year, month, day, billing period, peak time, at
the end of a subscription).
During the file / field verification process, various correlation and deduplication errors can
be detected, e.g. missing CDRs, uncorrelated CDRs representing one call or duplicates(originating in the network, mediation or IN itself). Furthermore, the system performs other
off-the-shelf processes such as feed validation, file name checking and data enrichment.
Rating / billing verification
Comarch BQA is based on components that support multi-service, multi-industry
convergence, which allows to perform advanced rating and billing verification. Such
flexibility enables modelling all the elements of the product catalog from the legacy
system. Thanks to an intuitive GUI any changes in configuration can be performed by QA
departments, improving time-to-market for new products.
Benefits
Shorter testing processes of products,
tariff plans and bundles (from weeks to
days)
Reduction in revenue leakage
6-fold increase in RA departments
productivity
Increased efficiency of discrepancies
recovery
Reduction of customer service costs
Decrease of over-billing resulting in
improved customer satisfaction and
reduced churn
Key features
Convergent on 3 levels: account, invoice,
system
xDRs filtering and discarding
Validation of xDR data
List of all of the events related to
a chosen discrepancy
Alarm generation and prioritization
according to user settings
Discrepancy aggregation
Notification mechanisms
On-line testing
Discrepancies statistics, drill-down
navigationMass management of conflicting records
Verification of guiding and invoicing
file/field levelvalidations
Rating/billingcomparison
Alarmsand reportsgeneration
CDR
ExternalCDR
sources
CDRM
ediation
Rating
&billing
en
gine
Verif
ication
en
gine
Analysingand
reportingengine
Legacy billingExternal
push scripts
Legacy-ratedCDRs
CDR CDR Bills Diff Rep
Local storageBQA pull
scripts
Filestorage
IN
Filestorage
OUT
ValidatedCDRs
Bill positionsand summary
Detecteddifferences
Discrepancyreports/alarms
Ratingand billingcalculation
Legacy-ratedCDRs
Local storage
-
8/6/2019 Comarch Billing Quality Assurance - Leaflet
2/2
Comarch Spka Akcyjna with its registered seat in Krakw at
Aleja Jana Pawa II 39A, entered in the National Court Register
kept by the District Court for Krakw-rdmiecie in Krakw, the
11th Commercial Division of the National Court Register under no.
KRS 000057567. The share capital amounts to 8,051,637.00 z. The
share capital was fully paid, NIP 677 00 65 406
Copyright Comarch 2010. All Rights Reserved.
EN-2011.05
Comarch SA
Al. Jana Pawa II 39 a
31-864 Krakw
Poland
phone: +48 12 64 61 000
fax: +48 12 64 61 100
e-mail:[email protected]
About Comarch:
Comarch is a global supplier of IT products and
services for the telecommunication industry.
The companys flexible solutions are industry
standard compliant and developed in-house.
Comarch solutions constantly evolve based on
customer demand. Since 1993, the company
has accumulated experience and knowledge
in the fields of designing, implementing, and
integrating IT solutions. Comarch serves some
of the markets largest players - such as Telekom
Deutschland (former T-Mobile Germany), T-Mobile
Austria, E-Plus Germany, Vodafone Germany and
Telefnica O2 Germany, as well as companies from
the KPN and France Telecom groups. Comarch
provides COTS products in the areas of BSS,
CRM, OSS as well as a range of comprehensive
services.
comarch.com comarch.pl comarch.de
www.telecoms.comarch.com
Depending on the scope of the data available in the rated xDRs, the system can perform
automated verification of a final price, usage (in seconds, bytes or units), call/event cost
before discount, included/free units requested and assigned, used discount, amount of
tax (the final amount, but also the method of calculating tax), extension prefix, as well as
whether the consumption has been done within peak time or not.
Comarch Billing Quality Assurance also enables verification of guiding (matching usage
data to subscribers), subscriber data such as balance (amount and continuity), contracted
products/bundles and generated invoices.
Analyzing and reporting discrepancies
All discrepancies detected during verification are analysed in order to recognize the most
important ones and accordingly prioritize corrective actions. To support this sub-process,
many statistics are available in Comarch BQA, that show sums of aggregated differences
according to several dimensions, helping pinpoint the source of the discrepancy:
Service (voice, SMS, MMS, data)
Tariff/Option/Concession/Bundle
Recurring/Usage-based charge
Any other xDR field
These statistics are available to users via dedicated screens, and provide flexible, context-
based navigation between various objects in the configuration, in order to facilitate the
search for the root cause of the discrepancy.
After distinguishing the cause of a single discrepancy, it is possible to mark all the
discrepancies related to this cause (e.g. every record that was rated with the use of a faulty
rating element) as dealt with, in order to speed up the entire process. Also, if the identified
root cause cannot be fixed (immediately or in the near future), application configuration
can be easily changed, to treat such recognized errors in a specific manner, so they do
not interfere with tracking further problems.
Figure 2. Aggregated differences