Charging is only profitable if every kWh delivered turns into money in your account. That sounds obvious, yet billing is where many operators lose revenue: sessions without invoices, invoices without payments, roaming CDRs nobody checks and fleet customers waiting weeks for statements. This guide explains how to design billing for each customer type and how to automate it.
- Different customers need different billing flows: instant capture, wallet deduction, monthly invoices or partner settlement.
- Every invoice line should be traceable back to a session and a charge detail record.
- VAT and e-invoicing rules vary by country and customer type, so plan them early.
- Automating invoicing, payment collection and reconciliation is what makes billing scale.
Billing flows by customer type
| Customer type | Typical flow | Document |
|---|---|---|
| Ad-hoc driver | Card pre-authorised, final amount captured after session | Receipt or simplified invoice per session |
| App user with wallet | Prepaid balance topped up, session cost deducted | Receipt per top-up or session, statement |
| Contract or RFID customer | Sessions collected, charged monthly by card or direct debit | Monthly invoice with session list |
| Fleet or company | Postpaid, grouped by cost centre or vehicle | Monthly invoice with detailed report |
| Roaming eMSP | CDRs sent, settled per agreement or through a hub | Partner invoice or self-billing statement |
| Site host | Revenue share or energy reimbursement | Statement or credit note |
What an EV charging invoice should contain
- Seller and buyer details, invoice number and date, as required by local tax law.
- Session details: location, EVSE or charger ID, start and end time.
- Energy delivered in kWh and, if applicable, charging and idle time.
- Unit prices for each component and the tariff name.
- Net amount, VAT rate and VAT amount, total.
- Payment method and status.
Each line should link to the session's charge detail record, so that disputes can be resolved by looking at meter data rather than guessing.
Prepaid vs postpaid
Prepaid wallets remove credit risk and reduce payment fees, because one top-up covers many small sessions. They suit public networks and residential sites. Postpaid billing is expected by businesses and fleets, but requires credit checks, payment terms and dunning. Many operators offer both: prepaid for individuals, postpaid for companies.
VAT and tax considerations
Charging is generally treated as a supply of services or goods subject to VAT, but details differ between countries, for example on the place of supply for cross-border roaming and on how bundled parking is taxed. Agree with your tax adviser how to treat ad-hoc sales, roaming B2B settlements and site host payouts. Show VAT clearly to drivers, who increasingly expect a proper invoice for business mileage claims.
E-invoicing mandates
More countries require structured electronic invoices. Italy has used its SDI system for B2B invoices for years, Turkey uses e-Fatura and e-Arşiv, Germany requires businesses to be able to receive e-invoices and is phasing in issuing obligations, and France is rolling out a mandate from 2026. If you invoice businesses in these countries, your billing system must produce compliant formats or integrate with a certified provider.
Refunds, disputes and failed payments
- Refunds: issue a credit note linked to the original invoice, and a credit CDR for roaming sessions.
- Disputes: compare the driver's claim with meter values, charger logs and status history.
- Failed payments: retry automatically, notify the customer and block new sessions after a defined limit.
- Chargebacks: keep session evidence ready, including pre-authorisation and capture records.
Fleet and company billing
Fleet managers need invoices grouped by vehicle, driver or cost centre, plus exports for accounting and expense systems. Sessions at public chargers paid with a company card should appear in the same report as depot charging. Our fleet charging management guide covers this in more detail.
Automation checklist
- Generate invoices or receipts automatically when sessions close or at the end of each billing period.
- Collect payments by card on file, direct debit or wallet without manual steps.
- Reconcile payment provider payouts with invoices every week.
- Export to your accounting system with the correct VAT codes.
- Send reminders and statements automatically.
- Monitor key metrics: unbilled sessions, outstanding receivables and failed payments.
Common mistakes
- Billing from the CSMS session list without checking for open or duplicated sessions.
- Applying new tariffs retroactively to sessions that started under old ones, see tariff models.
- Issuing invoices in only one language or currency for an international customer base.
- Forgetting idle fees or session fees on invoices, which drivers then dispute.
- Not reconciling roaming income, so missing CDRs go unnoticed.
Frequently asked questions
Do drivers need an invoice for every session?
It depends on local tax law and the customer. Ad-hoc drivers usually get a receipt per session, while contract and business customers usually receive a monthly invoice with all sessions listed.
Can billing run in several currencies?
Yes, if your platform supports multi-currency tariffs and invoices. This is important for networks operating across borders.
How do I bill residents in an apartment building?
Typically by kWh measured per resident, at cost plus a service fee, invoiced monthly or deducted from a prepaid balance.
Üreticy automates receipts, invoices, wallets, fleet billing and reporting from the same session data. See billing features or contact us.