Explanations use OCPI 2.2.1. Physical and billing-system events are authored examples.
CPO POSTs the CDR and the eMSP stores it
Advanced
4 min
CPO POSTs the CDR and the eMSP stores it
A charge finishes. The CPO, NL-FPN, sends CDR CDR-NL-GCH-88401 for Session session-7710 to the eMSP, which stores it.
Sandbox run · OCPI 2.2.1
Run this exchange in the sandbox
CPO
EMSP
"A *Charge Detail Record* is the description of a concluded charging session. The CDR is the only billing-relevant object. CDRs are sent from the CPO to the eMSP after the charging session has ended. Although there is no requirement to send CDRs in (semi-) realtime, it is seen as good practice to send them as soon as possible. But if there is an agreement between parties to send them, for example, once a month, that is also allowed by OCPI."OCPI 2.2.1 CDRs module · #mod_cdrs_cdrs_module"CDRs are created by the CPO. They most likely will be sent only to the eMSP that needs to pay the bill of the underlying charging session. Because a CDR is for billing purposes, it cannot be changed or replaced once sent to the eMSP. Changes are simply not allowed. Instead, a Credit CDR can be sent. CDRs may be sent for charging locations that have not been published via the Location module. This is typically for home chargers."OCPI 2.2.1 CDRs module · #mod_cdrs_flow_and_lifecycle
Message FlowStep 1 of 2