Telecom Billing Software Development

CDR (Call Detail Record) mediation is the pipeline that sits between network elements and the rating engine. Network elements -- SMSC, MMSC, GGSN, P-GW, SBC, and third-party wholesale gateways -- produce usage records in formats including ASN.1 BER, CSV, XML, and proprietary binary formats specific to each vendor. Format normalisation converts every incoming record format into a consistent internal CDR schema so the rating engine receives a uniform input regardless of source. Duplicate detection uses a combination of record sequence numbers, IMSI, MSISDN, and timestamp matching to identify and discard records received more than once from the same source -- a common occurrence when network elements retransmit on timeout.

Gap detection identifies missing record sequences by comparing expected sequence continuity against received records: gaps indicate either network element failures or file transfer failures between the network element and the mediation system. When a gap is detected, the mediation layer triggers a re-request to the source element or marks the sequence as irrecoverable and creates an exception record for revenue assurance review. Failed records that cannot be normalised (unrecognised format, missing mandatory fields) are placed in a quarantine queue with the reason for failure, allowing the mediation team to inspect and reprocess after format correction rather than silently dropping records. Revenue assurance controls compare CDR volume received from the network against CDR volume rated by the billing engine by time period -- volume discrepancies exceeding a configurable threshold generate an alert for the revenue assurance team to investigate before the billing run closes. Reference platforms such as TeleOSS, BSCS iX, and Cerillion handle this layer for large carriers; custom mediation is appropriate for MVNOs and smaller operators where those platforms are over-specified and over-priced.

Usage-based charging for voice, SMS, MMS, and data with per-unit rates by service and destination. Bundle consumption logic tracking included units against customer plan entitlements -- data allowances, voice minutes, SMS bundles -- with correct out-of-bundle charging when thresholds are crossed. Tiered pricing where per-unit rate changes at consumption thresholds. Promotional discount application by customer segment, campaign code, or date range. Roaming rate tables by zone and destination with zone override logic. Rate effective dates ensuring historical usage is always rated against the rates that applied at the time of use. The rating layer that handles your real plan complexity, not a simplified approximation of it.

Convergent billing for voice, SMS, data, and IoT services rates all service types within a single customer account and invoice -- a requirement for MVNOs offering bundled service packages and for operators with IoT SIM portfolios billed on the same account as consumer mobile services. Prepaid plan management uses a real-time balance deduction model: each usage event checks the subscriber's balance before service is authorised, and the balance is decremented at call or session end based on the rated charge. Postpaid plan management accumulates charges during the billing cycle and generates an invoice at cycle end. MVNO billing with wholesale rate handling applies two-pass rating: the first pass rates the subscriber at the retail rate for invoice generation; the second pass rates the same usage at the MVNE or MNO wholesale rate for cost calculation, producing the per-subscriber margin that the MVNO finance team uses to evaluate product profitability. For tax calculation in the US market, the engine applies USF (Universal Service Fund) surcharges, PICC (Presubscribed Interexchange Carrier Charge) contributions, TRS (Telecommunications Relay Service) levies, and 911/E911 surcharges by jurisdiction; in EU markets, VAT is applied at the rate applicable in the customer's member state along with any national regulatory levies. Wholesale settlement for MVNE/MVNO relationships generates the monthly settlement statement reconciling retail revenue, wholesale costs, and any revenue share arrangements between the parties.

Itemised bill generation grouping charges by service, date range, and charge type. Configurable bill presentation -- summary view for residential customers, itemised view for business accounts. PDF invoice generation with your branding. Email delivery to customer on bill date with a link to the online bill. Online bill view in the customer portal with drill-down to individual usage events for dispute resolution. Paper bill output for customers who require printed invoices. Invoice version control so customers and agents can always retrieve any historical bill in its original form.

E-bill presentment is delivered in both PDF and HTML format: the PDF version is attached to the bill notification email and available for download; the HTML version renders in the customer self-service portal with drill-down to individual usage events, supporting charge dispute without a call to the support team. For business accounts with multiple lines, the bill consolidates charges across all subscriptions on the account with a per-line breakdown and account total. Dunning management for failed payments uses a configurable retry and escalation sequence: on payment failure, the system retries the payment method at 3 days and 7 days, sends automated customer notifications at each retry with a direct payment link, applies a suspension flag if payment has not been received by day 14, and triggers disconnection at a configurable threshold (typically 30-45 days). Each step in the dunning sequence is configurable by customer segment -- business accounts may have a longer dunning window than prepaid residential accounts, and high-value customers may bypass automated suspension in favour of a collections team contact. The dunning sequence, retry results, and customer notifications are all recorded in the account audit trail.

Card payment processing via Stripe, Braintree, or your preferred payment gateway. Direct debit collection via BACS, SEPA, or ACH depending on your market. ACH collection in the US uses NACHA-compliant ACH debit entries originated through a payment processor or directly through an ACH originator -- NACHA rules govern return codes, timing, and retransmission limits that the billing system enforces automatically. Bank transfer matching against outstanding invoices. Automated dunning sequences for failed payments -- retry logic, customer notification, suspension threshold, and final disconnection trigger -- all configurable by customer segment and product.

Partial payment recording tracks balances where a customer pays less than the full invoice amount, applying the payment to the oldest outstanding balance first (or to the current invoice, depending on your configured allocation rule) and carrying the remainder as an aged balance. Refund processing is linked back to the original payment method and transaction -- refunds via Stripe credit the original card; ACH refunds are processed as a separate ACH credit to the originating bank account. Payment reconciliation reports match collected payments against invoiced amounts by billing period, identifying invoices paid in full, invoices with partial payments, invoices with no payment, and any payments received without a matching invoice. This reconciliation report is the primary input for the revenue assurance review of the billing cycle, confirming that billed revenue and collected revenue agree within the tolerance defined by your finance team.

Gross revenue by product, plan, and customer segment by billing period. Adjustments and credits applied in the period with reason codes and agent attribution. Collections performance showing billed revenue vs. collected revenue and outstanding balance by age. Revenue by geographic region, sales channel, and customer tenure. Churn impact on recurring revenue -- customers lost and revenue lost by month. Plan migration reporting showing customers moving between plans and revenue impact of those moves. The revenue dashboard your finance and commercial teams can use without building it manually in spreadsheets.

Revenue assurance controls are embedded in the reporting layer rather than treated as a separate audit process. The controls compare CDR volume processed by the mediation layer against CDR volume rated by the billing engine by service type and time window -- discrepancies indicate records lost between mediation and rating, a form of leakage that does not appear in billing reports because the charge was never generated. A second control compares billed revenue per subscriber against the expected revenue given their plan and recorded usage -- subscribers whose billed amount differs from expected by more than a configurable tolerance are flagged for review. These leakage detection controls surface revenue recovery opportunities that manual billing reviews miss because they are embedded in individual account records rather than visible at the aggregate level. MVNE/MVNO wholesale settlement produces the monthly settlement statement showing retail revenue, wholesale cost per service type, and net margin by MVNO -- the document the host MNO and MVNO use to reconcile the commercial relationship. For operators using TeleOSS or Cerillion as their primary BSS platform, the custom reporting layer can be built as an overlay that pulls data from those platforms via their APIs rather than replacing the billing core.

Itemised billing transparency meeting regulatory requirements for your jurisdiction -- bill summary, usage detail, and charge breakdown presented to the standard required. Disputed charge handling workflow with audit trail of the original charge, customer dispute, investigation, and outcome. Cooling-off period credit automation for customers exercising cancellation rights within the regulated window. Billing complaint logging and resolution tracking for regulatory reporting. Tax calculation and invoice presentation for VAT, GST, or jurisdiction-specific telecom taxes. Billing data retention policy applied automatically to meet your regulatory obligation without manual archiving.

US telecom tax compliance involves multiple surcharge types applied at federal and state levels: USF contributions (Federal Universal Service Fund assessed as a percentage of interstate and international revenue), PICC charges (Presubscribed Interexchange Carrier Charge applied to multi-line business accounts), TRS (Telecommunications Relay Service) surcharges, and 911/E911 surcharges levied at state and local level with rates that vary by jurisdiction and change quarterly. The billing system maintains a tax rate table that is updated at each rate change cycle and applies the correct combination of surcharges to each invoice based on the customer's service address and the service type being billed. EU regulatory compliance addresses VAT application under the EU VAT Directive for digital and telecommunications services -- for B2C services, VAT is charged at the rate applicable in the customer's member state; the billing system stores the customer's verified country of residence and applies the correct VAT rate. E-bill presentment meets the transparency requirements of EU electronic communications regulations by displaying all charges, surcharges, taxes, and fees in the bill summary with itemised detail available on request. Billing data retention is enforced automatically per jurisdiction: typically six years for EU operators under GDPR and applicable sector regulations, and varies by state for US operators.