
Trading, clearing, custody, settlement
Industry domain brief
COBOLpro documents provisioning, mediation, rating, billing, subscriber, and OSS/BSS dependencies for telecom documentation.
3
Legacy estate
Systems and data surfaces to inspect
9
Workflows
Business workflows grouped by capability
3
Risks
Business impacts with control focus
4
Deliverables
COBOLpro assessment artifacts
Executive summary
Telecom legacy estates often sit between network systems, subscriber records, product catalogs, mediation feeds, billing cycles, tax logic, partner settlement, and customer care. The hard part is proving how service states and usage charges stay synchronized.
COBOLpro builds a domain brief that makes OSS/BSS dependencies visible before product launches, billing migrations, network updates, or vendor replacement.
Legacy systems in scope
Each row is structured for executive review: where the COBOL behavior sits, what it touches, and what the documentation must prove.
Subscriber and service operations
Legacy estate
Subscriber, order, service catalog, provisioning, activation, number management, device, and network inventory systems
Documentation focus
Service qualification, activation states, plan changes, inventory updates, and network handoffs
Mediation, rating, and billing
Legacy estate
Usage mediation, CDR processing, rating, taxation, discounts, billing, invoicing, collections, and dispute systems
Documentation focus
Usage transformations, pricing rules, tax calculations, invoice generation, credits, and adjustments
Partner and regulated interfaces
Legacy estate
Wholesale, roaming, partner settlement, finance, customer care, SLA, regulatory, and tax feeds
Documentation focus
Partner reconciliation, regulated billing evidence, dispute handling, and downstream reporting
Operational workflows
COBOLpro groups source behavior around the operating workflows buyers need to preserve, explain, or replace.
01
02
03
Risk and control priorities
The assessment narrows risk to business impact and source-backed control evidence instead of treating documentation as a generic code inventory.
01
Business impact
Rating, mediation, and billing defects can create revenue leakage, customer disputes, and regulatory exposure.
Control focus
Trace usage records from network events through mediation, rating, invoice, tax, and finance outputs.
02
Business impact
Subscriber, service, catalog, and network states can diverge across OSS, BSS, vendors, and care systems.
Control focus
Map service state transitions, file timing, transaction handoffs, and recovery paths.
03
Business impact
Wholesale, roaming, tax, and partner interfaces can block billing or network documentation.
Control focus
Inventory partner feeds and settle each dependency against source programs, jobs, and reconciliation controls.
COBOLpro assessment output
Outputs are written for shared use across business, audit, architecture, application, data, and delivery teams.
01
Provisioning and subscriber lineage
Order, service qualification, activation, inventory, subscriber, and network handoffs tied to source.
02
Usage and billing rule catalog
Plans, usage, rating, taxes, discounts, credits, adjustments, disputes, and exceptions in buyer-readable form.
03
OSS/BSS interface inventory
Network, customer-care, partner, wholesale, roaming, finance, regulatory, and tax feeds organized by workflow.
04
Launch and migration impact package
Evidence for product launches, billing migration, network documentation, and partner changes.
Domain assessment