Charging sessions

A session is the platform's record of a single charge. It ties together the pieces from the earlier pages: a token authorised at a connector on an EVSE Controller, owned by an Account, priced by a tariff, and turned into a billable record.

For the end-to-end flow across the protocols (plug in, authorise, meter, stop), see anatomy of a charging session in the primer. This page is about the session as a record.

Two sides of one charge

A single charge is recorded twice, once from each side:

  • a CPO session, the operator's record of a charge on its station, and
  • an MSP session, the driver's provider's record of the same charge.

The two are separate records that hold different data: the CPO session carries the operator and OCPP side of the charge, the MSP session the driver and payment side. They are kept apart because the two sides are usually different companies. The CPO session is the source: when a charge finishes the operator turns it into a CDR, the billable record, and for a roaming charge pushes that CDR to the driver's network. The MSP session is built from a received CDR. The CDR is what connects the two. For how the CPO and eMSP sides fit together, see the platform model.

The rest of this page describes the CPO session, the record an operator works with.

What a session references

A session does not stand alone. It links back to:

  • the token that authorised it,
  • the EVSE Controller, Connector and Location it ran on,
  • the tariff that priced it, and the resulting cost and energy delivered.

The token resolves to an Account and a driver only when it belongs to the platform. A roaming token belongs to another network, so the CPO session records it but the driver sits off-platform, and there is no matching MSP session on our side.

The cost is kept broken down, energy, time, a session fee and idle, alongside the total, in the session's currency and with VAT recorded against the rule that applied.

Lifecycle

A session is not driven by a single status field. It opens when a token is authorised and a transaction starts on the station; it runs as meter values stream in over OCPP and cost is tracked against the tariff; it ends when the charge stops and the final energy and duration are known; and it is then settled into its billable figures. Whether a session is live, finished or settled is read from its timestamps and its billing state, not from one label.

Valid, and billable

Two separate questions decide what becomes of a finished session, and the platform records each.

Is it valid? A session is invalid when it was not authorised, or when its measurement is missing or not credible. An invalid session is never billed or reimbursed.

Is it reimbursed? A valid session can still be left out of reimbursement because no money is owed through the platform: free charging, a payment collected elsewhere, or one still waiting on an external funder to confirm before it can be included. That last case is left undecided on purpose until the funder answers.

Keeping the two apart matters for reconciliation, because a session that will not be billed is not necessarily a broken one. Either outcome is recorded with a reason, set automatically by the platform's checks or applied by hand.

When the checks run

The checks run at three moments. A session already marked invalid when charging starts skips the checks at the end of charging.

  1. When charging starts. The charging station asks the platform whether the token may charge. If the platform says no and the charging station charges anyway, the session is invalid.
  2. When charging ends. The charging station sends a StopTransaction message with the final meter reading and the end time. The platform checks that the reading is present, that the session is not a duplicate, that energy and duration are within limits, and that there is a cost to bill.
  3. Afterwards. Payment results, late data and manual actions can still change the outcome.

Each session shows one reason. A session that fails several checks shows the last one that ran.

Validity limits

Energy is the final meter reading minus the start reading. Duration runs from the start time to the end time. The charging station reports all four values.

CheckLimitReason shown
Energy and duration, minimumunder 0.2 kWh (or none) and under 2 minutesLOW_ENERGY_USAGE
Energy, negativefinal meter reading lower than the start readingLOW_ENERGY_USAGE
Energy, maximumover 1,000 kWh in one sessionHIGH_ENERGY_USAGE
Charging speedover 10 kWh per minute on averageIMPROBABLE_ENERGY_USAGE
Start or end timemore than 5 years ago, more than 1 day in the future, or ending before it startedINVALID_START_TIME, INVALID_END_TIME

By default the minimum applies only when both conditions hold: a session of 90 seconds that delivered 3 kWh is valid. A provider can be set up with stricter minimums where either condition alone is enough, and a session that is only too short then shows LOW_DURATION.

Shore power on an IEC 60309 socket runs for days, so it is checked against the socket's rated power in place of the energy and duration limits.

These limits apply to sessions that were authorised and have a final meter reading. A session that passes them can still be invalid for another reason.

Reason codes

Invalid sessions:

ReasonDescription
NON_ACCEPTED_AUTHThe platform answered that this token may not charge here, and the charging station charged anyway. Typical causes are a blocked token, or a roaming token its issuer refused. Nobody has agreed to pay for the session.
MISSING_OR_INVALID_SESSIONThe platform refused the start, so no session was opened, and the charging station charged anyway. Typical causes: an unknown token, a token already charging at another charging station, or a charging station that is not fully set up, is private or is disabled. There is no known payer or no tariff to apply.
UNKNOWN_METER_VALUESThe platform closed the session without a final meter reading, so the energy delivered cannot be confirmed. Either the charging station sent the start twice, which opens a second, empty session, or the StopTransaction never arrived or arrived without a reading. Any kWh shown is the last reading received while charging. This check runs before the validity limits. The platform later looks for the final reading in the charging station's next messages, and the session becomes valid if it finds one and the session passes the limits.
LOW_ENERGY_USAGEThe session delivered less than the minimum energy, or none at all. Usually a vehicle that was plugged in and did not charge.
LOW_DURATIONThe session was shorter than the minimum duration. SHORT_DURATION in validity.invalidReason.
HIGH_ENERGY_USAGEMore than 1,000 kWh in one session. Almost always a wrong meter reading from the charging station.
IMPROBABLE_ENERGY_USAGEMore than 10 kWh per minute on average, which no charging station can deliver. The charging station reported a wrong meter reading or wrong times.
INVALID_START_TIMEThe charging station reported a start time that cannot be right: more than 5 years in the past or more than 1 day in the future. Usually its clock was not set.
INVALID_END_TIMEThe charging station reported an end time that cannot be right: more than 5 years in the past, more than 1 day in the future, or before the start.
DUPLICATEDThe charging station reported the same charge twice. The first session is billed and only the copy is excluded, so the driver is not charged twice.
MANUAL_CANCELLATIONA user force-closed a session that was stuck as active, with a hard cancellation. This closes the platform's record without contacting the charging station, so there is no final meter reading and no real end time. A soft cancellation sends a stop to the charging station, and the session ends and is billed as usual.
MAINTENANCE_TOKENStarted with a maintenance token, used to test a charging station before it goes live. A test, not a customer charge.
REPLACED_WITH_CORRECTED_SESSIONThe session was corrected (for example, its cost was recalculated) and replaced by a new one. The new session is the one that is billed.
FAILED_TO_STARTThe session was opened but charging never began.

Valid sessions left out of reimbursement:

ReasonDescription
NO_COSTEvery price in the tariff that applied was zero, as with free charging.
AUTHORIZED_NON_BILLABLE_RFIDThe token belongs to an access group member set to charge for free, or it is the operator's own internal token. The session is priced and not billed.
EXTERNAL_PAYMENT_SOLUTIONThe driver paid at a payment terminal where the operator, not Road, is the merchant. The money reached the operator directly.
EXTERNAL_PAYMENT_FAILEDThe payment terminal reported that the driver's payment failed, so there is no money to reimburse.
EXTERNAL_REIMBURSEMENTReimbursement is handled outside the platform.
TEMPORARILY_EXCLUDED_WAITING_FOR_MISSING_DATAWaiting for data needed to settle the session, such as a payment receipt sent after the stop, or the driver's MSP confirming who pays. Checked again when the data arrives.
NO_AUTO_REIMBURSEMENTThe platform lacks the payment information to reimburse automatically.
HISTORICAL_ENDThe charging station never closed the session. By the time the platform closed it, it was too old to bill: it ended more than two months earlier or started more than six months earlier.
MANUAL_EXCLUSIONThe session has been manually excluded.
UNSPECIFIEDNo specific reason was recorded.

From session to CDR

A settled session's authoritative billable form is a Charge Detail Record (CDR): the final statement of what was delivered and what it cost. Billing runs on the CDR, not on the live session, and where a charge crosses networks the CDR is also what the operators exchange to settle with each other, the roaming side covered in the roaming section.

A CDR can be repriced while it is still being processed, but once it has been billed its price is fixed, and a later change is made as a credit rather than an edit. This is why a session from months ago still shows the price that was in force when it ran.