Billing automation

Spirii’s billing engine reads every CDR as it arrives and works out who owes money, who is owed money, and which document each session belongs on. What lands at the end of the month is a reconciled set of invoices, self-billing invoices, and expense reports — with no billing infrastructure for you to build.

​

How it works

The engine runs continuously. As sessions complete and their CDRs are finalised, it evaluates each one against the billing configuration for your account and adds it to the document it belongs on for that period.

​

What the engine decides

​

The documents it produces

Charge key sessions aggregate per billing customer across the period, so one invoice covers every session their drivers ran, with a specification attachment itemising each. Roaming sessions are billed from the CDR data exchanged with the partner over Hubject or OCPI.

​

Dependencies & limitations

• A session is billed once its CDR is final. The engine works from finalised records, so a session still running is not on any document yet.
• Late sessions land in the earliest open period. A charger that was offline syncs its sessions later. Those join the earliest billing period still open, which is the current one if their own has closed.
• Not every CDR earns revenue. Sessions below the energy threshold, sessions running past seven days, free and voucher charging, and several other cases are excluded from the payout. See Understanding your payout.
• Documents split by country and currency. Each supplier receives one document per country and per currency, rather than a single combined document across markets.
• What Spirii invoices depends on the billing service level. At Full Service Spirii invoices your customers directly; at the other levels it produces the data and you invoice them. See Charge key billing.

​

Related