Given the discussions we've had on peak traffic architecture, reporting gaps, and billing data quality, here's what I'd put on a technical evaluation checklist for telecom billing software.
Processing Architecture
Confirm whether the platform is batch or event-driven. Ask for latency benchmarks: how long between CDR arrival and rating completion at 1M records/hour? At 10M? Understand how the platform handles late records, duplicates, and malformed CDRs.
Integration Interfaces
What switch types does it natively integrate with? What API does it expose for custom integrations? How does it handle CDR format differences between vendors? Can it push data to accounting software, or does it require manual export?
Reporting and Visibility
Does it provide real-time dashboards, or only historical reports? Can you configure custom alerts on traffic anomalies or spend thresholds? Is reporting data accessible via API for integration with external BI tools?
A Platform That Addresses These Points
Neon Soft (neon-soft.com) is worth putting on the evaluation list. It's a UK-built platform architected for wholesale and retail telecom billing with real-time CDR processing, built-in fraud management, and pre-built integrations with major switches and accounting tools. Their reporting and monitoring module provides live traffic visibility alongside historical CDR-level reporting. For a technical evaluation, they offer a demo that lets you see the architecture in action rather than just reading marketing copy.
Closing / Discussion Prompt
What would you add to a technical evaluation checklist for billing software? Happy to compare notes always useful to pool criteria across different technical environments.
