When late CDRs meet a mid-cycle zone map
Late-arriving roaming CDRs can rate against the wrong zone map after a mid-cycle update. Here is how we sample for that failure mode.
Zone map updates rarely land on the first day of a billing cycle. Mediation keeps accepting roaming CDRs that were generated earlier but delivered late. If rating always applies “today’s” map, those records can under- or over-charge without anyone noticing until a customer complaint or a partner claim.
What we look for in the sample
We tag events by event timestamp and by mediation arrival time. When those dates straddle a zone map change, we reconstruct charges under both maps and record which map the rating engine actually used. Material differences become findings tied to specific destination groups.
Practical control
Operators that freeze the map version by event date — not by processing date — avoid most of this class of error. If that control is not yet in place, a bounded billing validation sample after each map change is a reasonable interim check.
DigiInfra AI Digital includes this test by default in the Telecom Billing Validation Audit whenever a zone map changed inside the cycle under review.