How it works
1
Driver taps
A fleet driver starts a session with their assigned charge key at any compatible charger, on the Spirii network or a roaming partner’s.
2
Spirii records the session
The platform captures the CDR: session start and end, energy consumed, price, and the charge key that authenticated it.
3
Sessions are aggregated
Through the billing period, every session for that fleet or eMSP accumulates under a single billing document per country and currency.
4
The invoice is issued
At the end of the period, Spirii sends one invoice covering every session by every driver, with a specification attachment detailing each one.
5
CPOs are paid
Spirii pays the revenue on to the CPOs whose chargers were used, and settles with any roaming partners involved.
What the invoice covers
Every session authenticated with a charge key issued under that billing customer, whether it ran on a public or workplace charger on the Spirii network, or on a partner network reached over Hubject or a direct OCPI connection. Because the consumption is invoiced afterwards rather than paid at the charger, the monthly invoice is the VAT document. Individual sessions produce a statement instead of a receipt. See Receipts.Billing service levels
The billing service level set on the operator decides whether Spirii invoices the end customer or hands you the data to invoice them yourself.What each side sees
Fleet managers see every session their drivers ran in Spirii Connect, with live session status and historical CDR exports. Drivers tap, charge, and leave. The company’s monthly invoice handles the rest, whether they charged at the office, on a public charger, or at home with home charging reimbursement configured.Dependencies & limitations
- Autocharge charge keys do not work over roaming. A vehicle key is read by the charger itself, so it only works on chargers managed by Spirii’s platform — a driver relying on Autocharge needs an RFID or virtual charge key as well to charge on partner networks. See Charge keys.
- Physical charge keys need a reader. Usually that’s the charge box’s own RFID reader. On a charge box without one, a Spirii POS terminal can read the charge key instead, and the session is billed exactly as if it had been tapped at the charger. Virtual charge keys need no reader.
- Charge key sessions produce a statement, not a receipt. The statement carries no VAT details, because the monthly invoice is the VAT document for that consumption.
- CPO payout follows the month. Revenue from charge key sessions reaches the CPO the month after the sessions ran, in the same cycle as app and terminal revenue.
Related
Charge keys
How charge keys are issued, typed, and managed.
Billing automation
How the billing engine turns CDRs into invoices and payouts.
Roaming settlement
How sessions on other networks are invoiced and settled.
Home charging reimbursement
Automate reimbursement for employees charging at home.