# One trusted source of truth for all ESME / A2P SMS traffic. - Canonical URL: https://www.broadnet.me/platforms/esme-cdr - Language: en - Last updated: 2026-10-20 - Publisher: BroadNet (https://www.broadnet.me) - Markdown version of the page above, generated from the rendered page. Platforms · ESME CDR Intelligence CDRs live in different systems with different field names, different status codes, different time zones. Reconciliation becomes a spreadsheet exercise — and revenue leaks every billing cycle. The ESME CDR Intelligence Suite is the vendor-agnostic correlation layer that consolidates them, matches them intelligently, and produces dispute-ready evidence packages. [Request CDR reconciliation audit](https://www.broadnet.me/contact?topic=cdr-reconciliation-audit&product=esme-cdr) [Talk to a telecom intelligence engineer](https://www.broadnet.me/contact?topic=intelligence-engineer&product=esme-cdr) Vendor-agnostic Dispute-ready evidence Real-time + batch ![The BroadNet snow leopard before two ledgers of call records sliding into one reconciled column](https://www.broadnet.me/marketing/art/pf-esme-cdr.webp) BroadNet · ESME + CDR CDR reconciliation 300M+ records / day 1,000+ operator routes 99.99% SLA Operators and aggregators that run BroadNet as their reconciliation layer Tier-1 GCC operator MENA carrier group Pan-African operator South Asian MNO Regional aggregator Caribbean operator Hub aggregator Multi-country MVNO The operating shape ## Independent. Vendor-agnostic. Trusted by every team that touches the data. One correlation layer that catches what single-vendor reporting misses — and produces evidence the next team can act on. Sources 6+ CDR feeds in one view SMSC, firewall, billing, partner CSVs — DB, SFTP, API. Match window ±2s fuzzy time tolerance Clock-drift safe matching across vendor systems. Categories 5 reconciliation buckets Matched · status-mismatch · only-int · only-op · variance. Throughput M/day CDRs processed Millions per day with configurable retention. CDR reconciliation console ## Every CDR, reconciled down to the last record. The reconciliation view RA and finance teams open each morning — five variance buckets, one match rate, every discrepancy attributable. Below is an illustrative run built from sample data. broadnet · reconciliation Example ### Reconciliation run #4821 2026-08-28 · 00:00–24:00 UTC 99.2% matched Window 24h Records processed 4,821,096 Match rate 99.2% Run time 3m 42s Variance report records by reconciliation bucket 99.2% matched 40,684 exceptions Matched baseline 4,780,412 99.2% Exceptions · 40,684 bars scaled to largest exception Rated diff 21,904 0.45% Missing in A 9,120 0.19% Missing in B 6,540 0.14% Duplicate 3,120 0.06% A = internal SMSC · B = partner billing ESME / SMPP binds live session status ACME-A2P TRX 1,200 TPS Bound PayFlow-OTP TX 640 TPS Bound Gulf-AGG TRX 880 TPS Bound Retail-BULK TRX 0 TPS Idle Test-ESME RX — Unbound Illustrative example — sample data, not an audited SLA or a live feed. Five-layer architecture ## From six scattered feeds to one reconciliation report. Collection, normalisation, intelligent matching, reconciliation and reporting — each layer scoped, scalable, and replaceable independently from the others. 1. 01 · Collect Multi-source collector Direct DB read, SFTP polling, REST APIs, file-drop monitoring. Scheduled per source — 5 min for real-time, hourly or daily for batch. every 5 min 2. 02 · Normalise Canonical schema Source ID, sender ID, ESME account, status code, timestamps — all mapped to a single canonical model. Time zones standardised to UTC. ≈1ms / CDR 3. 03 · Match Intelligent matching Multi-key matching on message-id, MSISDN, sender-ID and timestamp — with a ±2-second fuzzy window for clock drift. M / batch 4. 04 · Reconcile 5-category buckets Matched · status-mismatch · only-internal · only-operator · volume-variance. Root-cause flagged per bucket. auto-categorise 5. 05 · Report Dashboards · evidence Live dashboards for NOC and RA; scheduled reports for finance; CSV / JSON / PDF evidence packs for legal and partner disputes. real-time + sched 6. ← evidence packages · CSV · JSON · PDF 01 · Collect Multi-source collector Direct DB read, SFTP polling, REST APIs, file-drop monitoring. Scheduled per source — 5 min for real-time, hourly or daily for batch. every 5 min 02 · Normalise Canonical schema Source ID, sender ID, ESME account, status code, timestamps — all mapped to a single canonical model. Time zones standardised to UTC. ≈1ms / CDR 03 · Match Intelligent matching Multi-key matching on message-id, MSISDN, sender-ID and timestamp — with a ±2-second fuzzy window for clock drift. M / batch 04 · Reconcile 5-category buckets Matched · status-mismatch · only-internal · only-operator · volume-variance. Root-cause flagged per bucket. auto-categorise 05 · Report Dashboards · evidence Live dashboards for NOC and RA; scheduled reports for finance; CSV / JSON / PDF evidence packs for legal and partner disputes. real-time + sched Why an independent reconciliation layer ## The verification layer your vendor reports never include. Four reasons operators and aggregators choose ESME CDR over relying on the SMSC vendor's own dashboards. 01 · NETWORK ### Vendor-agnostic by design. We hold our own SMPP and SS7 binds with destination operators in 86 countries, and every other route is a labelled partner route. No grey routes, no surprise re-routing, no opaque price markups in the middle. 0 Vendor lock-in 02 · HERITAGE ### Evidence packages the next team can act on. Operating since 2003, headquartered in Dubai. We carry 300M+ application-to-person messages a day for banks, governments, airlines, and the platforms that power the modern internet. 3 Export formats 03 · REACH ### Start small, scale to four teams. Local presence across the Middle East and North Africa, plus pan-African, South Asian, and South-East Asian operator relationships that make global rollouts feel like a single market. Phased Roll-out 04 · COMPLIANCE ### 5-minute ingestion. Daily reconciliation. Both, at once. ISO 27001 / 9001 / 22301, SOC 2 Type II, GSMA Associate Member, HIPAA-aligned, GDPR-aligned. Sender-ID registrations handled by an in-region compliance team in every regulated market. 5min Live cadence Multi-source collector ## Whatever your SMSC vendor. Whatever the partner format. We have integrated with dozens of SMSC platforms across many generations of telecom kit. If a system can export records — via database, file, or API — the collector can read them. ### SMSC CDRs Both MT and MO records. Direct read-only DB access or scheduled CSV export via SFTP. ### Firewall logs Allowed, blocked, modified — the firewall view of the same traffic, correlated with what the SMSC saw. ### ESME gateway logs Direct SMPP connections from ESME clients — captured at the gateway for end-to-end attribution. ### Billing exports Rating and invoicing data pulled from the billing platform for cross-validation against routed traffic. ### Partner files CSV / XLSX from operators and aggregators — pulled via SFTP, dropped to a watched folder, or pushed via API. ### Internal pipeline data Reads from internal pipeline stores when available — used to enrich correlation and confirm routing decisions. Reconciliation buckets ## Every CDR lands in one of five buckets. Discrepancies are categorised so the right team owns the right bucket — RA owns phantom CDRs, ops owns status mismatches, commercial owns volume variance, legal owns dispute escalation. 01 · Matched ### In both systems, same status The healthy case. Records present in internal and partner data with consistent delivery status. The baseline against which the rest are measured. 02 · Status mismatch ### Present in both — different status We say DELIVRD, partner says EXPIRED. Indicates DLR-timing drift, error-code mapping differences, or genuine delivery disputes. 03 · Only-internal ### We have it, partner does not Potential missing billing on the partner side. Cross-check against firewall logs and routing to confirm send-completion. 04 · Only-operator ### Partner has it, we do not Phantom-CDR candidate. Possible duplicate count, test-traffic inflation, or data corruption upstream. Strongest revenue-recovery lever. 05 · Volume variance ### Same count, different mix Aggregate volume matches but the per-status distribution differs. Usually a sign of segment / concatenation handling drift between the two systems. Teams served ## One platform. Four critical functions. ### NOC · Operations Live traffic dashboards by ESME, operator, and route. Quality KPIs with delivery rates and error distributions. Threshold and anomaly alerts. ### Revenue Assurance · Finance Automated reconciliation against partner CDRs. Leakage analysis identifying unbilled traffic and phantom charges. Billing-rule validation. ### Commercial Teams Volume trends per partner and destination. Campaign and partner behavior patterns across operators. Margin visibility per route. ### Legal · Dispute Evidence-ready CDR exports with full correlation. Forensic drill-down by message-id, MSISDN, or sender. Structured packages for arbitration. Customer stories ## What an independent CDR layer changes. Tier-1 GCC operator Telecom · Gulf SA **Challenge** Monthly invoices from one A2P partner consistently exceeded internal SMSC counts, but no team had a defensible way to challenge the difference. **Approach** Multi-source collection across SMSC, firewall, and partner files; fuzzy ±2-second matching surfaced a structured pattern of only-operator records. Head of revenue assurance (reference under NDA) Attributable Per-record evidence Pan-African operator Telecom · East Africa KE **Challenge** Operations and finance were arguing over what counted as a delivered SMS — each team trusted a different system and discrepancies were dismissed as 'tooling noise'. **Approach** Every team was given the same dashboard and reconciliation buckets; status-mismatch and only-internal records were investigated case-by-case in a recurring weekly review. Director, network operations (reference under NDA) 1 Source of truth Weekly Reconciliation rhythm Root-cause Driven fixes Regional aggregator A2P aggregator · MENA AE **Challenge** A partner enterprise customer disputed delivery on a high-volume campaign; without independent evidence the conversation was a stand-off. **Approach** Forensic drill-down by sender-ID, MSISDN window and timestamp produced an evidence package showing per-message status across SMSC, firewall, and operator records. Commercial lead (reference under NDA) Per-message Evidence depth Re-usable Pack template On-premise or private-cloud, audit-ready, regulator-recognised across MENA. ISO 27001 ISO 9001 ISO 22301 GDPR Ready TDRA UAE CST KSA NTRA EG Companion platforms ## Pair with the rest of the intelligence stack. [Signaling & CDR Intelligence The companion product. ESME CDR covers A2P SMS records; Signaling CDR adds SS7 / SIGTRAN / SIP capture and court-ready forensic packages. Learn more](https://www.broadnet.me/platforms/signaling-cdr) [SMSC Gateway Carrier-grade messaging core. ESME CDR is the natural reconciliation layer on top of SMSC and partner billing. Learn more](https://www.broadnet.me/operators/smsc-gateway) [What is a CDR? Plain-English answer to the most common question for teams new to telecom CDR work. Learn more](https://www.broadnet.me/answers/edr-vs-cdr) Questions buyers ask ## Eight questions RA and ops teams ask. It gives operators, aggregators and enterprises one trusted view of A2P SMS traffic, independent of any single vendor's reporting. CDRs from SMSC, firewall, billing, and partner sources are consolidated, normalised to a canonical schema, intelligently matched, and categorised into reconciliation buckets — so disputes have attributable evidence and revenue leakage gets caught before it becomes a recurring loss. Multiple alternatives are supported: CSV / XLSX export to a polled SFTP folder, REST or SOAP API integration, or working with the SMSC vendor to expose a read-only view. We have integrated with dozens of SMSC platforms across many generations of telecom kit. If the system can export records, the collector can read them. Matching combines multiple keys — message-id, MSISDN, sender-ID, and timestamp — with a fuzzy time window (typically ±2 seconds) to account for clock drift between systems. Concatenated messages are reassembled before matching so that a single logical message is not double-counted across its segments. A summary report with totals per bucket — matched, status-mismatch, only-internal, only-operator, volume-variance — and detailed exception lists exportable as CSV for analysis, JSON for system integration, or PDF for formal reports and partner disputes. Forensic drill-down is available on every record. All timestamps are normalised to UTC on ingestion and stored in UTC. When displayed in dashboards or reports, they are converted to the user's preferred timezone (configurable per account). For reconciliation, the fuzzy time window absorbs both clock drift and small timezone-conversion errors. Raw timezone metadata is preserved for forensic work. It provides strong fraud indicators rather than full fraud management. Volume-based alerts surface traffic spikes from specific ESME accounts, behavioural analysis flags suspicious sender-ID patterns, velocity checks identify repeat-to-same-destination patterns, and integration with firewall data correlates blocked traffic with CDR patterns. Teams who already run a fraud system feed those indicators into it; teams who do not often start there. On-premise or in private cloud, on Linux or Windows servers. Data residency is fully under your control — nothing is sent to BroadNet or third parties without explicit approval. Retention is configured per table to match internal IT and compliance policy. A typical engagement runs in phases: discovery workshop, pilot deployment against the first data source (usually SMSC), full integration of remaining sources (firewall, billing, partners), and production rollout with dashboards, alerts, and team training. End-to-end timelines vary by environment complexity — most operators are in production inside a quarter. Question not here? [Ask our engineering team](https://www.broadnet.me/contact) ![The BroadNet snow leopard walking past holographic network dashboards in a night city](https://www.broadnet.me/marketing/art/band-platforms.webp) Carrier-grade platform ## Infrastructure engineered since 2003. The same platform that carries 300M+ messages a day, available as building blocks for your stack. 300M+ Msgs·day 99.99% SLA 23+ Years [Talk to sales](https://www.broadnet.me/contact) Vendor-agnostic · independent verification layer ## Find the discrepancies your single-vendor reports never surface. We will run a reconciliation audit against your existing SMSC, firewall, billing and partner data — and show you what an independent correlation layer would have caught in the last billing cycle. [Request CDR reconciliation audit](https://www.broadnet.me/contact?topic=cdr-reconciliation-audit&product=esme-cdr) [Talk to a telecom intelligence engineer](https://www.broadnet.me/contact?topic=intelligence-engineer&product=esme-cdr) Related guides & answers Go deeper on the concepts behind this product. [What is SMPP Read](https://www.broadnet.me/answers/what-is-smpp) [How does the SMPP protocol work Read](https://www.broadnet.me/answers/smpp-protocol) [What is an SMSC Read](https://www.broadnet.me/answers/what-is-smsc) [What is an ESME Read](https://www.broadnet.me/answers/what-is-esme)