Turning raw telecom CDR files into rated, explainable billing records_
We designed an ingestion and mediation layer that accepts controlled file uploads and transfer endpoints, maps source fields into a canonical event, submits rating work to CGRateS, and preserves the tariff and transforma
- Telecom CDR rating
- CGRateS event mediation
- CSV, XML, fixed-width, and API ingestion
Operators receive CDRs from switches, carriers, and partners in incompatible formats. A row can be syntactically valid and still be commercially wrong because prefixes, time zones, rounding, or tariff versions do not match.
We designed an ingestion and mediation layer that accepts controlled file uploads and transfer endpoints, maps source fields into a canonical event, submits rating work to CGRateS, and preserves the tariff and transformation trail.
The platform establishes a reviewable route from source file to normalized CDR, rated amount, exception queue, and report—without making finance teams reverse-engineer a black box.
Overview
Operators receive CDRs from switches, carriers, and partners in incompatible formats. A row can be syntactically valid and still be commercially wrong because prefixes, time zones, rounding, or tariff versions do not match.
We designed an ingestion and mediation layer that accepts controlled file uploads and transfer endpoints, maps source fields into a canonical event, submits rating work to CGRateS, and preserves the tariff and transformation trail.
The engineering decision
Raw files are immutable evidence. Mapping templates are versioned, rejected rows are quarantined with reasons, and re-rating creates a new auditable result rather than silently overwriting history.
How the system works
The implementation separates intake, validation, state changes, side effects, and reporting. That separation makes failures visible and allows one layer to change without rewriting the entire workflow.
Operational users see explicit statuses and exceptions; technical teams retain identifiers, timestamps, versions, and logs needed to reproduce a result.
Outcome
The platform establishes a reviewable route from source file to normalized CDR, rated amount, exception queue, and report—without making finance teams reverse-engineer a black box.
Project highlights
- CGRateS event mediation
- CSV, XML, fixed-width, and API ingestion
- Versioned tariff and mapping rules
- Duplicate and late-file detection
- Exception queues and re-rating
- Tenant-scoped reporting