Definition
CPO Payment Reconciliation and Billing refers to the process where the charging service operator reconciles the charging session billing at the charge point with its own platform orders, payment institution transaction records, interconnection clearing results, and, if applicable, peripheral systems such as parking, membership, and invoicing. The core of reconciliation is that fields like start, stop, energy, amount, discounts, and profit sharing are consistent, and the timeline can be restored; any discrepancy in standards will manifest as overcharges or undercharges in daily or settlement batches.
CPO frequently interfaces with payment institutions, interconnection platforms, parking systems, and invoicing services. Billing generated at the charge point is uploaded to the platform via the network, and packet loss, duplicate reports, or clock drift between device and platform can all lead to reconciliation differences. When charging terminals are widely distributed and the on-site electromagnetic environment is complex, it is even more necessary to agree on unified timing and alert standards in the networking strategy with business systems like orderly charging and time-of-use pricing to reduce data discrepancies caused by 'parameter changes on-site without the platform being aware.'
Technical Features
On the IoT side, TLS, certificate updates, and domain reachability should be ensured; on the platform side, idempotency and deduplication should be applied to uploaded records, and weak network retransmission and retry strategies should be designed; operations need to monitor alerts such as "pile online but records missing" and "same session closed repeatedly." For cross-province roaming piles, attention should also be paid to the impact of carrier NAT and private network policies on long connections and reporting latency.
SimtoLink IoT SIM cards provide terminals with wide-area, manageable, and controllable cellular access capabilities, supporting strategies such as private network, public network, multiple APNs, and VPDN, facilitating unified authentication, whitelisting, and traffic management on the platform side. When implementing the project, capacity planning should consider heartbeat cycles, record reporting granularity, and data plan tiers, and operational methods for roaming, weak network reconnection, and log retention should be reserved. During the integration phase, it is recommended to retain end-to-end samples (dialing, DNS, TLS, business transaction ID) as a reference for troubleshooting; after launch, iteration should be driven by observability metrics.
Use Cases
Applicable to public charging networks, interconnection operations, and multilateral reconciliation with third-party clearing institutions. SimtoLink provides stable access and card management visibility, reducing manual reconciliation costs and shortening the time to identify discrepancies.
In delivery and operations, it is advisable to distinguish between "connection online" and "business success": in addition to card status and successful dialing, end-to-end DNS resolution, TLS certificate chain, application ports, and session stability need to be verified. It is recommended to configure dual cards with dual carriers or cellular plus wired backup for key nodes, and to specify record reporting success rate, latency percentiles, and cumulative downtime in the SLA; troubleshooting should be correlated using ICCID, APN, session, and domain dimensions. For sensitive data, classify and grade it, define minimal necessary collection, retention period, access auditing, and third-party sharing boundaries.
Key points for cooperation with IoT SIM cards
CPO Payment reconciliation highly depends on traceability of "which card, which EV charging station, which session"; the stability of cellular links and the accuracy of card management records directly affect call detail record completeness and adjustment efficiency.
- Establish ledger: Bind ICCID (and MSISDN if necessary) with pile number, station, and interconnection asset code. Console changes, on-site card replacement, and pile transfer should be updated synchronously, preventing mismatches between card numbers and piles on the clearing side.
- Divide by business APN / private network / VPDN: Separate transaction call detail records, operation & maintenance telemetry, and OTA logs to reduce retransmission backlog and reconciliation delay caused by bandwidth contention.
- Standardize time reference: Agree on NTP/time zone strategies between the pile, platform, and payment side. End-of-day cut-off and discount period boundaries should be aligned to reduce batch misalignment caused by clock drift.
- For weak network scenarios, design local buffering, breakpoint resume, and idempotent keys for call detail records. The platform can safely discard or merge duplicate submissions, avoiding simultaneous duplicate billing and missing records.
- Combine "pile online rate" and "call detail record arrival rate" alarms to quickly distinguish wireless side issues from application layer failures; roaming piles should separately monitor PLMN switching and tariff policies.
- SIM full lifecycle (activation, transfer, suspension, reactivation, cancellation) should be linked with pile removal, station merger/cancellation, and interconnection termination, implementing card-device binding and resource recovery to reduce reconciliation noise caused by idle cards and improper use.
At the scaling stage, it is recommended to maintain a terminal ledger (IMEI, SIM, firmware version, installation location), an alarm grading and change management process, and to reconcile traffic, SMS, and value-added services separately; align SLAs with the client's IT, network security, and business operations to ensure risk is controllable and costs are predictable from pilot to replication.