EV charging billing software: how sessions and tariffs work
EV charging platforms combine authorisation, charger events, meter readings and tariff rules to create a priced session, payment record or invoice.
From authorisation to a charging session
EV charging billing software does not usually calculate a price from one charger message. It follows a session from authorisation through to a final record, then applies the tariff and sends the result to payment, invoicing or reimbursement systems.
A driver may identify themselves with an app, RFID card or another credential. The charge point management system (CPMS) checks the relevant account or service, returns an authorisation decision and records which charger and connector are involved. The charger then reports the transaction start, meter values, status changes and the reason the session ended.
What a session record contains
The exact fields depend on the platform and protocol version. A useful record normally includes a session identifier, charger and connector, user or contract reference, start and end times, energy delivered, relevant meter readings and a stop reason. The platform also needs the tariff version and tax treatment used for the calculation.
Operational status and a billable session are not the same thing. A vehicle can remain connected after energy delivery stops, a session can pause, or messages can arrive late after a network outage. The CPMS must interpret the sequence without losing or duplicating chargeable data.
How tariff rules are applied
Tariffs can include a price per kWh, a time charge, a fixed session fee, an idle fee or a combination. Rules may vary by location, connector, customer group or time period. The platform should show which rule applied and retain the version used, rather than recalculating old sessions against a new price.
Published driver prices, contractual wholesale prices and internal cost allocations may differ. VAT, rounding, minimum charges, free periods and price changes during a session need explicit rules. Market-specific metering and consumer-pricing requirements must be checked separately.
How the session becomes a bill or payment
When the session is complete, the platform rates it and creates a final transaction or charge detail record. That record may be sent to a payment service for pay-as-you-go charging, added to a monthly account, passed to an employer for reimbursement or exported to finance software.
A CPMS may coordinate this flow without being the merchant, payment processor or invoicing system. Buyers should establish which system is the financial source of truth, who handles refunds and disputes, and how failed or missing records are reconciled.
EV charging management software: how CSMS and CPMS platforms work
What changes when roaming is involved
In a roaming session, the charge point operator (CPO) runs the charger while an e-mobility service provider (eMSP) holds the driver relationship. The CPO backend shares locations, tariffs, session updates and a final charge detail record with the eMSP, often through OCPI. The eMSP bills the driver, while commercial settlement between the businesses follows their agreement.
This is why OCPP and OCPI have different jobs. OCPP carries charger-to-CPMS operations. OCPI exchanges roaming information between business platforms.
Where billing errors usually appear
Common causes include missing final meter values, duplicate messages after reconnection, incorrect clocks, mismatched tariff versions, wrong tax settings and inconsistent rounding. A sound platform keeps the raw event history, calculation steps and operator changes needed to explain the result.
How amina fits into the flow
amina charging stations send transaction and measurement data over OCPP to the selected CSMS. The amina OCPP reference lists start and stop transactions and meter values, while the meter-value documentation describes readings such as current, active power and cumulative imported energy.
The charger supplies operational evidence. The CPMS and connected commercial systems decide the tariff, produce billing records and manage payments. Operators should test that complete path, including offline recovery, before treating a session record as invoice-ready.
Related
