> ## Documentation Index > Fetch the complete documentation index at: https://docs.spirii.com/llms.txt > Use this file to discover all available pages before exploring further. # Token billing > Consolidated monthly invoicing for fleet drivers using RFID cards or virtual keys. Token billing gives fleet companies and eMSPs a single, consolidated invoice each month for all charging done by their drivers — across the Spirii network and roaming partners — instead of individual receipts per session. Drivers tap and charge; the billing is handled automatically in the background. ## How it works 1. **Driver taps.** A fleet driver uses their assigned RFID card or virtual token to start a session at any compatible charger on the Spirii network or a roaming partner network. 2. **Spirii records the session.** The platform captures the CDR — session start and end, energy consumed, price, and the token used to authenticate. 3. **Sessions are aggregated.** Throughout the billing period, all sessions for a given fleet company or eMSP are accumulated under a single billing document per currency and country. 4. **Invoice is issued.** At the end of the billing period, Spirii sends one invoice to the fleet company or eMSP covering every session by all their drivers. 5. **CPOs are paid.** Spirii pays the revenue to the CPOs whose chargers were used. ```mermaid theme={null} flowchart TD D1[Driver A] -->|Tap key| L1[Charger – Site 1] D2[Driver B] -->|Tap key| L2[Charger – Site 2] D3[Driver C] -->|Tap key| L3[Roaming charger] L1 -->|CDR| S[Spirii Billing Engine] L2 -->|CDR| S L3 -->|CDR| S S -->|Single monthly invoice| F[Fleet Company / eMSP] S -->|Self-billing payout| C1[CPO 1] S -->|Self-billing payout| C2[CPO 2] S -->|Settlement| R[Roaming Partner] ``` ## What the invoice covers A token billing invoice covers every session authenticated with a token issued under that billing customer: * Sessions on the Spirii network (public chargers, workplace chargers) * Roaming sessions on partner networks (Hubject, OCPI direct connections) ## Billing service levels The billing service level configured for the operator determines whether Spirii invoices the end customer directly or provides the data for the operator to invoice themselves. | Service level | What Spirii does | | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Full Service** | Spirii invoices the driver or fleet company directly and reports VAT, since Spirii is the party invoicing the consumer | | **Invoice Data Service** | Spirii generates the billing data and makes it available in an aggregated format; the eMSP invoices their own customers and Spirii settles roaming sessions | | **No service** | Spirii records the session; no billing action is taken by Spirii apart from settling roaming sessions | ## Fleet manager view Fleet managers can see all sessions for their drivers in Spirii Connect, including real-time session status and historical CDR exports. ## Driver experience Drivers do not submit expense claims for charging. They tap their RFID card or virtual key, charge, and leave. Their company's invoice handles the billing. This applies whether they charge at the office, on public chargers, or at home (with home charging reimbursement configured). ## Related How tokens are issued and managed. How sessions on other networks are invoiced and settled. Automate reimbursement for employees charging at home.