CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/Telecom

πŸ“Ά Telecom Β· Data Flow

Telecom Billing and Rating Pipeline

How network usage becomes a customer bill: call detail records, mediation, rating against the plan, billing and invoicing.

More Telecom templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • Mediation cleans and de-duplicates raw usage records
  • Rating prices each record against the customer's plan
  • Bills are generated per billing cycle with taxes

Prompt used

Data flow for telecom billing: network elements (switches, packet core, SMSC) produce CDRs; mediation collects, validates, de-duplicates and normalises them; the rating engine prices each record using the customer's plan from the product catalog and applies allowances; at cycle end billing applies discounts and taxes (GST), produces invoices and posts them to the customer's account and the general ledger; disputes come back as adjustments. Number the processes.

Mermaid code
flowchart LR
subgraph EXT ["External entities"]
ne["Network Elements (Switches, Packet Core, SMSC)"]
cust["Customer"]
gl["General Ledger System"]
end
subgraph PROC ["Processes"]
p1("1.0 Collect and Validate CDRs")
p2("2.0 Rate Usage Records")
p3("3.0 Apply Discounts and Taxes")
p4("4.0 Generate and Post Invoices")
p5("5.0 Process Billing Disputes")
end
subgraph STORE ["Data stores"]
d1[("D1 Raw and Normalized CDRs")]
d2[("D2 Product Catalog")]
d3[("D3 Customer Account and Allowance Data")]
d4[("D4 Rated CDRs")]
d5[("D5 Billing and Invoice Data")]
d6[("D6 Dispute and Adjustment Data")]
end
ne -->|"Raw CDRs"| p1
p1 -->|"Validated and Normalized CDRs"| d1
d1 -->|"Normalized CDRs"| p2
d2 -->|"Customer Plan Details"| p2
d3 -->|"Allowance Data"| p2
p2 -->|"Updated Allowance Balances"| d3
p2 -->|"Rated CDRs"| d4
d4 -->|"Rated CDRs"| p3
p3 -->|"Discounted and Taxed (GST) CDRs"| d5
d5 -->|"Cycle-End Billing Details"| p4
p4 -->|"Invoice and Account Details"| cust
p4 -->|"General Ledger Entries"| gl
cust -->|"Billing Dispute Details"| p5
p5 -->|"Dispute Records"| d6
p5 -->|"Account Adjustment Data"| d3
p5 -->|"Invoice Adjustments"| d5
d5 -->|"Dispute History Context"| p5

Inside this diagram

A data flow diagram with 8 processes and outside parties, 6 data stores and 17 data flows.

Processes and outside parties

  • Network Elements (Switches, Packet Core, SMSC)
  • Customer
  • General Ledger System
  • 1.0 Collect and Validate CDRs
  • 2.0 Rate Usage Records
  • 3.0 Apply Discounts and Taxes
  • 4.0 Generate and Post Invoices
  • 5.0 Process Billing Disputes

Data stores

  • D1 Raw and Normalized CDRs
  • D2 Product Catalog
  • D3 Customer Account and Allowance Data
  • D4 Rated CDRs
  • D5 Billing and Invoice Data
  • D6 Dispute and Adjustment Data

Data flows

  • Network Elements (Switches, Packet Core, SMSC) β†’ 1.0 Collect and Validate CDRs: Raw CDRs
  • 1.0 Collect and Validate CDRs β†’ D1 Raw and Normalized CDRs: Validated and Normalized CDRs
  • D1 Raw and Normalized CDRs β†’ 2.0 Rate Usage Records: Normalized CDRs
  • D2 Product Catalog β†’ 2.0 Rate Usage Records: Customer Plan Details
  • D3 Customer Account and Allowance Data β†’ 2.0 Rate Usage Records: Allowance Data
  • 2.0 Rate Usage Records β†’ D3 Customer Account and Allowance Data: Updated Allowance Balances
  • 2.0 Rate Usage Records β†’ D4 Rated CDRs: Rated CDRs
  • D4 Rated CDRs β†’ 3.0 Apply Discounts and Taxes: Rated CDRs
  • 3.0 Apply Discounts and Taxes β†’ D5 Billing and Invoice Data: Discounted and Taxed (GST) CDRs
  • D5 Billing and Invoice Data β†’ 4.0 Generate and Post Invoices: Cycle-End Billing Details
  • 4.0 Generate and Post Invoices β†’ Customer: Invoice and Account Details
  • 4.0 Generate and Post Invoices β†’ General Ledger System: General Ledger Entries
  • Customer β†’ 5.0 Process Billing Disputes: Billing Dispute Details
  • 5.0 Process Billing Disputes β†’ D6 Dispute and Adjustment Data: Dispute Records
  • 5.0 Process Billing Disputes β†’ D3 Customer Account and Allowance Data: Account Adjustment Data
  • 5.0 Process Billing Disputes β†’ D5 Billing and Invoice Data: Invoice Adjustments
  • D5 Billing and Invoice Data β†’ 5.0 Process Billing Disputes: Dispute History Context

Boundaries

  • External entities: Network Elements (Switches, Packet Core, SMSC), Customer and General Ledger System
  • Processes: 1.0 Collect and Validate CDRs, 2.0 Rate Usage Records, 3.0 Apply Discounts and Taxes, 4.0 Generate and Post Invoices and 5.0 Process Billing Disputes
  • Data stores: D1 Raw and Normalized CDRs, D2 Product Catalog, D3 Customer Account and Allowance Data, D4 Rated CDRs, D5 Billing and Invoice Data and D6 Dispute and Adjustment Data

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

Related templates

NetworkTelecom

5G Core Network Topology

A simplified 5G standalone network: phones and radio sites, the 5G core network functions, and the connection out to the internet.

State MachineTelecom

SIM Activation Lifecycle

The states a mobile SIM goes through, from stock in the warehouse to active service, suspension, porting out and deactivation.

C4 ArchitectureProTelecom

Telecom OSS/BSS Architecture

The IT stack of a mobile operator: business support systems (CRM, billing, orders) and operations support systems (inventory, provisioning, assurance).

SequenceTelecom

Mobile Number Portability

How a subscriber moves their number to another operator: porting code, request through the clearing house, donor approval and cutover.

SequenceTelecom

Prepaid Recharge Sequence

What happens when a customer recharges a prepaid mobile: plan selection, payment, balance update in the charging system and confirmation.

Database ERDTelecom

Telecom Customer Data Schema

A schema for subscriber data: customers, accounts, subscriptions (numbers), plans, SIMs and bills.