Why I’m writing this
A friend once sent me a screenshot of their phone bill: three pages of line items, a mysterious “proration,” a “bundle discount,” and something called “regulatory fees.” “How do they figure all this out?” they asked. That question led to this post. If you’ve ever wondered how a telco turns your calls, texts, and gigabytes into a monthly invoice—or a prepaid balance that ticks down in real time—this is your guide.
I’m keeping this beginner-friendly, conversational, and product-agnostic. You’ll learn the big pieces, how they talk to each other, and where common bill surprises come from. I’ll also include simple diagrams you can recreate in tools like diagrams.net/draw.io, Mermaid, or PlantUML, and I’ll suggest some diagramming toolkits that include telecom/BSS shapes.
The big picture: What “billing” really does
Think about telecom billing like running a restaurant that’s open 24/7:
- The kitchen (network) cooks up services: voice calls, data, messages.
- The waitstaff (mediation) keeps track of what each table consumed, corrects any scribbles, and makes sure the orders are legible.
- The cashier (rating/charging) applies the menu prices, happy-hour rules, and coupons to compute amounts.
- The accountant (billing/invoicing) adds taxes, splits the check, applies prepayments, and generates the bill.
- The collections clerk (payments/dunning) handles card payments, due dates, reminders, and suspensions if needed.
- The business manager (catalog/CRM) decides what’s on the menu and what promotions to run.
- The auditor (revenue assurance/fraud) makes sure nothing leaks—no free lobster walking out the door.
In Simple telecom terms
- Network: phone/data/sms service elements that produce usage records
- Mediation: normalizes and cleans usage data (CDRs/EDRs)
- Rating/Charging: calculates charges for usage (and often for allowances)
- Billing: consolidates one-time, recurring, and usage charges into a bill
- Invoicing: turns charges into a customer-facing document, with taxes and totals
- Payments/Collections: takes money, manages due dates and dunning
- CRM & Product Catalog: knows who the customer is and what’s been sold
- Revenue Assurance/Fraud: checks for leakage, anomalies, and fraud
Two charging styles you’ll hear a lot
- Offline (postpaid): the network writes logs (CDRs), then later the system rates them and invoices you monthly.
- Online (prepaid or hybrid): your device is granted credit in near real time; if you run out, the network stops the flow immediately.
Billing & associate systems component map
High-level mechanism
The four questions every bill answers
1) Who is it? Identity, account hierarchy, bill cycle, language, currency.
2) What did they use/consume? Calls, messages, data, value-added services, roaming.
3) How much does it cost? Tariffs, bundles/allowances, discounts, taxes, fees, proration.
4) How and when do we collect? Due dates, payments, refunds, adjustments, dunning.
Deep dive, one piece at a time
1) Usage: from the network to clean records
Analogy: The kitchen prints order tickets. Some tickets smudge; some duplicate; some arrive late. Mediation fixes that.
What gets recorded:- Voice: calling/called numbers, start time, duration, roaming flags.
- Messaging: sender/recipient, count, short codes.
- Data: session start/end, bytes up/down, APN, roaming.
- Normalizes units (MB vs bytes), time zones, codes.
- Enriches with subscriber/account IDs, offer IDs, roaming zones.
- De-duplicates and correlates (e.g., data start/stop pair).
- Aggregates when needed (e.g., batch micro-events into 15-minute blocks).
- Roaming note:
When you roam, the visited network creates records that the home operator receives via standardized settlement files (commonly TAP in legacy), then bills you after applying your plan’s roaming rules.
2) Charging: turning usage into money
Analogy: You ordered a burger, but it’s Tuesday—buy one get one half off—and you have a coupon. How much should it cost?
- Offline rating basics:
- Bundles/allowances: “10 GB included; extra at $X/GB.”
- Tiers: first 100 units at $A, next 900 at $B.
- Discounts: percentage or absolute, conditional (“family plan 10%”).
- Rollover: unused allowance carries into next cycle (with rules).
- Proration: you joined mid-cycle; you get a fraction of allowance and fee.
- Online charging basics (prepaid and hybrid):
- Before or during a session, the network asks the charging system: “Grant 5 MB?” If balance/allowance allows, it gets a “Yes” and a token; when consumed, it asks again.
- Immediate enforcement: if balance hits zero, service stops or slows (per policy).
- Converged charging: in modern networks, a single system handles both real-time and batch logic to keep rules consistent.
3) Product catalog and CRM: the rules of the game
Analogy: The menu and customer file.
- Product catalog:
- Defines offers/bundles: allowances, tiers, discounts, eligibility.
- Defines relationships: dependencies, incompatibilities, upsells.
- CRM:
- Stores subscriptions: which products/offers are active.
- Bill cycle:
- Prepaid: rolling validity windows and renewal dates.
4) Billing and invoicing: assembling the bill
Analogy: Printing the check, splitting it between diners, adding tax and service fees, and applying gift cards.
- Bill run stages:
- Rating/charging: usage rated; recurring/one-time charges generated.
- Billing: account-level rollups, discounts, taxes, currency conversion.
- Invoicing: document render (PDF/email/HTML), with detail pages.
- Posting: record revenue and receivables in financial systems.
- Taxes and fees:
- Applied per jurisdiction; often integrated via a tax engine that needs location and service codes.
- Adjustments:
- Payments and dunning:
- Dunning strategy: reminders, soft-block, hard-block, write-off.
5) Wholesale, interconnect, and roaming settlements (the other bills)
- Interconnect: When your customer calls someone on another operator’s network, you “buy” termination from that operator. Separate inter-operator billing handles this, using traffic volumes and contractual rates.
- Roaming: When your customer roams, the visited operator sends you usage details via clearinghouses. You settle B2B based on roaming agreements. Your retail bill to the customer is separate but related.
6) Revenue assurance and fraud: keeping the bucket from leaking
Analogy: Counting plates leaving the kitchen and comparing with what’s on the checks.
- Common leakage points:
- Rating rules missing or misconfigured (e.g., a new short code unpriced).
- Discounts applied out of scope or twice.
- Controls:
- Exception reports: zero-rated when shouldn’t be, sudden usage drops/spikes.
- Fraud watch:
7) Privacy and compliance, briefly
- Retention/archival rules: keep records long enough for disputes and regulation, not longer than needed.
- Why does my first month look weird? Proration. If you join mid-cycle, you get part of the monthly fee and sometimes part of the allowance. Often you’ll see a pro-rated partial month plus the next full month in advance.
- Why are my calls rounded to the minute? Some tariffs round per event (e.g., 60/60 billing: every call charged at least one minute). Others round to the second and aggregate for the month.
- Why did data stop suddenly on prepaid? Online charging granted a quota and later denied more because balance hit zero.
- Why do I get taxed more when I roam nationally? Taxes can depend on service type and location. When roaming, jurisdiction attribution can change, and some regions add surcharges.
Practical tips if you’re new to designing billing
- Keep the catalog clean: start with a few modular building blocks—one-time, recurring, usage, discount, allowance—and compose offers from them.
- Separate price from policy: define the price rule and the quota rule independently so you can evolve each without breaking the other.
- Version everything: catalog items, price plans, and rating rules evolve—keep effective dates and clear versioning.
- Build for traceability: every charge should trace to an input record and a rule; it makes disputes and audits far easier.
- Test like a customer: simulate common journeys—join mid-cycle, add an add-on, roam, exceed allowances, pay late.
Putting it all together: a tiny end-to-end story
Sara signs up for a postpaid plan on the 20th, with 50 GB/month and a 10% family discount. Her bill cycle is the 1st to 31st.
- On signup (20th): Billing generates a pro-rated recurring charge for 11 days, and a SIM activation one-time charge. The catalog tells rating how to pro-rate the 50 GB allowance to roughly 18.33 GB for that partial period.
- During the cycle: Mediation normalizes network data usage; rating subtracts from Sara’s pro-rated allowance. She uses 16 GB—no overage.
- Month end: Billing aggregates charges, applies the 10% discount on recurring charges, adds taxes based on Sara’s address, and produces the invoice.
- Next month: Full 50 GB allowance applies. If Sara roams internationally, roaming usage will arrive later, possibly generating a future invoice depending on timing.
Modern twist: how 5G changes Billing
- Converged charging: A unified brain handles both real-time and batch rules to keep prices consistent everywhere.
- Event vs session: Beyond data sessions, 5G adds new event types (e.g., API calls, slices) that still boil down to “events” for charging.
- Policy integration: Policy decisions (quality, speed) and charging decisions (quota, price) are more tightly coupled.
- B2B/B2B2X: Enterprises buying slices or QoS-backed services need clearer, often usage-based or outcome-based bills. Still the same four questions—who, what, how much, how to collect—just at different scales.
Summary
"Telecom billing isn’t magic; it’s a well-organized relay race"
- The network logs what happened.
- Mediation cleans it up.
- Charging/rating turns it into money.
- Billing and invoicing assemble and present it.
- Payments and collections close the loop.
- Catalog/CRM set the rules; assurance and analytics keep everyone honest.
"Once you see those pieces, bills become less intimidating. You can trace any line item back to an event and a rule."
may your bills always balance!
Comments
Post a Comment