eMSP prepares the driver's invoice

Advanced · 4 min

OCPI 2.1.1, 2.2.1 and 2.3.0

Showing OCPI 2.2.1. Physical and billing-system events are authored examples.

Step 4 of 4 · Tariff and billing
EventeMSPsendsDriverreceives
EventCPOActoreMSPsendsDriverreceives
Legend

The line follows the selected step. Actor dots identify the parties; they show no conformance verdict.

Step 4 of 4 · Paused

Selected step

All 3 actors

CPO · eMSP · Driver

Selected exchange

In this authored example, the eMSP's billing system uses the captured CDR data to prepare the driver's invoice. Its customer pricing and tax treatment are business-system choices.

eMSP → Driver · Authored event

Sources (2)
"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 should contain enough information (dimensions) to allow the eMSP to validate the total cost. It is advised to send enough information to the eMSP so that they can calculate their own costs for billing their customers. An eMSP might have a very different contract/pricing model with their EV drivers than the tariff structure of the CPO. If the CPO, for any reason, wants to view a CDR it has posted to an eMSP's system, the CPO can retrieve the CDR by performing a GET request on the eMSP's CDRs endpoint at the URL returned in the response to the POST."OCPI 2.2.1 CDRs module · #mod_cdrs_push_model
Why this matters

This billing event is an authored business-system observation, rather than an OCPI message or conformance result.

Test this flow

Test this flow runs against an eMSP endpoint you have registered.