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

# Revenue sharing & automated payouts

> How Spirii distributes charging revenue to CPOs, site owners, and subsidiaries — automatically, every month.

Spirii collects revenue from drivers and eMSPs across all payment channels and pays it out each month. The payout can go to a single account, or Spirii can split it between multiple parties — the CPO, the site owner, or regional subsidiaries — based on the configuration you set.

## How payouts work

At the end of each billing period, Spirii issues a self-billing invoice on your behalf covering the sessions Spirii collected revenue for during that month. Payment arrives in your registered bank account shortly after the billing cycle closes.

The payout covers:

* Sessions paid via the Spirii app or a branded app
* Sessions paid at a Spirii-managed payment terminal (turnkey acquiring mode)
* Token (RFID) sessions where Spirii invoices the fleet or eMSP
* Inbound roaming sessions — drivers from other networks charging on your stations

<Note>
  Payouts cover revenue Spirii collected. For sessions where you hold your own acquiring agreement (PAAS terminal mode), funds come directly from your PSP and are not included in the Spirii payout.
</Note>

## Revenue sharing with site owners

If you operate chargers on behalf of other businesses — landlords, retailers, hotel chains — you can configure Spirii to pay the site owner directly, rather than routing everything through you first.

**How it works:**

1. You configure a revenue split for the relevant locations in Spirii Connect, specifying the share that goes to the site owner.
2. After each billing period, Spirii issues a self-billing invoice to the site owner for their share and a separate document to you for the remainder.
3. Each party receives their payout independently — no manual transfers required.

This model is also used when the CPO and site owner are different legal entities within the same group — for example, a CPO with separate national subsidiaries that each need their own invoice.

```mermaid theme={null}
flowchart LR
    D[Driver] -->|Pays| S[Spirii]
    S -->|Self-billing invoice\nCPO share| C[CPO]
    S -->|Self-billing invoice\nSite owner share| CSO[Site Owner]
    C -.->|Optional: further\ndistribution| SUB[Subsidiary / BU]
```

## What you see

Your monthly payout is accompanied by a self-billing invoice and an attached CSV of all the CDRs included in the payment. You can reconcile this against the session data in Spirii Connect. Sessions are attributed to the period in which they occurred, not the period in which they were invoiced.

<Note>
  Roaming revenue is paid out in the same month Spirii invoices the roaming partner. App, terminal, and token billing revenue is paid out the following month.
</Note>

## Related

<CardGroup cols={3}>
  <Card title="Billing and payout flows" icon="building-2" href="/capabilities/billing-payouts/billing-and-payout-flows">
    How money flows between drivers, Spirii, CPOs, and site owners.
  </Card>

  <Card title="Understanding your payout" icon="file-text" href="/capabilities/billing-payouts/payouts">
    How to read a self-billing invoice and reconcile it with Connect data.
  </Card>

  <Card title="Setting up revenue sharing" icon="split" href="/guides/revenue-sharing-setup">
    Step-by-step guide to configuring site owner splits.
  </Card>
</CardGroup>