> ## 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.

# Charge key billing

> Consolidated monthly invoicing for fleet drivers using RFID cards or virtual charge keys.

Charge key billing gives a fleet company or eMSP one consolidated invoice each month covering every session their drivers ran, on the Spirii network and on roaming partners alike. Drivers tap and charge. Nobody files an expense claim.

## How it works

<Steps>
  <Step title="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.
  </Step>

  <Step title="Spirii records the session">
    The platform captures the CDR: session start and end, energy consumed, price, and the charge key that authenticated it.
  </Step>

  <Step title="Sessions are aggregated">
    Through the billing period, every session for that fleet or eMSP accumulates under a single billing document per country and currency.
  </Step>

  <Step title="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.
  </Step>

  <Step title="CPOs are paid">
    Spirii pays the revenue on to the CPOs whose chargers were used, and settles with any roaming partners involved.
  </Step>
</Steps>

```mermaid theme={null}
flowchart TD
    D("Drivers tap charge keys") --> N("Spirii network and roaming partners")
    N -->|"CDRs"| S("Billing engine")
    S -->|"one monthly invoice"| F("Fleet or eMSP")
    S -->|"self-billing payout"| C("CPOs")
    S -->|"settlement"| R("Roaming partners")
```

## 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](/capabilities/compliance/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.

| Service level | What Spirii does | Choose it when |
| - | - | - |
| **Full Service** | Invoices the fleet company or driver directly, and reports the VAT as the invoicing party | You want the billing relationship off your books entirely |
| **Invoice Data Service** | Produces aggregated billing data for you to invoice from, and settles roaming sessions | You hold the customer relationship and issue the invoices under your own brand |
| **No service** | Records the session and settles roaming sessions, nothing further | You bill from your own systems and need Spirii only for the session data |

## 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](/capabilities/billing-payouts/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](/components/access/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](/capabilities/payments/in-person-payments) 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

<CardGroup cols={2}>
  <Card title="Charge keys" icon="key-round" href="/components/access/charge-keys">
    How charge keys are issued, typed, and managed.
  </Card>

  <Card title="Billing automation" icon="zap" href="/capabilities/billing-payouts/billing-automation">
    How the billing engine turns CDRs into invoices and payouts.
  </Card>

  <Card title="Roaming settlement" icon="globe" href="/capabilities/billing-payouts/roaming-settlement">
    How sessions on other networks are invoiced and settled.
  </Card>

  <Card title="Home charging reimbursement" icon="house" href="/capabilities/billing-payouts/home-charging-reimbursement">
    Automate reimbursement for employees charging at home.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.