How do I set up an invoicing system for EV charging sessions, tax handling, and multi-currency customer billing?

To set up an invoicing system for EV charging sessions, tax handling, and multi-currency billing, design it around three layers:

1. Charging session data
2. Billing and tax calculation
3. Invoice generation and payment collection

Here’s a practical setup.

---

1) Define the billing model

First decide what exactly is billed for a charging session:

• Energy-based: kWh consumed
• Time-based: minutes connected or actively charging
• Session fee: flat fee per session
• Idle / overstay fee: extra charges after charging ends
• Roaming / network fee: platform margin or partner fee
• Taxes: VAT/GST/sales tax depending on location

A session may generate multiple line items, for example:

• 18.42 kWh × €0.39
• 47 minutes × €0.05
• Parking overstay fee €3.00
• VAT 20%

---

2) Capture the right charging session data

Your billing engine needs a complete session record:

• Session ID
• Customer / account ID
• Charging station ID
• Start/end timestamps
• Energy delivered in kWh
• Duration
• Location of charger
• Country/state/region of charging
• Tariff plan applied
• Currency to bill in
• Customer billing country and tax status
• VAT/GST number if applicable
• Payment status
• Any discounts, promotions, or refunds

Make sure the charging location is stored accurately, because tax often depends on where the service was delivered, not where the customer lives.

---

3) Build pricing and tariff logic

Create a pricing engine that can calculate charges from a tariff structure. Common tariff components:

• Base fee
• Energy rate per kWh
• Time rate per minute
• Idle fee after a grace period
• Minimum charge
• Maximum daily cap
• Dynamic pricing by time of day / location / charger type

Example tariff:

• €1.00 connection fee
• €0.42/kWh
• €0.06/min after 30 minutes
• 20% VAT added afterward

Your system should calculate:

1. Pre-tax subtotal
2. Tax amount
3. Total due

---

4) Handle tax correctly

Tax rules can get complex, so make them data-driven.

Key tax considerations

• Tax jurisdiction: based on charger location in many cases
• Customer type: consumer vs business
• Tax registration: whether you’re VAT-registered in that region
• Tax-exempt customers: e.g. businesses with valid VAT IDs
• Reverse charge: for some B2B cross-border EU cases
• Inclusive vs exclusive pricing: whether displayed prices already include tax
• Tax rate changes: store historical tax rates used for each invoice

Best practices

• Store the tax rate applied at invoice time, not just a current rate lookup
• Keep a tax calculation breakdown per line item
• Support multiple tax components if needed:
  • federal
  • state/provincial
  • local

Example invoice tax breakdown

• Subtotal: €12.50
• VAT 20%: €2.50
• Total: €15.00

For multi-jurisdiction systems, use a tax engine or rules service rather than hardcoding rates.

---

5) Support multi-currency billing

You need to distinguish between:

• Charging currency: the currency used for pricing the session
• Settlement currency: the currency you receive from the payment processor
• Invoice currency: what the customer is billed in
• Reporting currency: what your finance team uses internally

Recommended approach

• Store the session amount in a base currency or the local charger currency
• Convert using a locked FX rate at billing time
• Save:
  • exchange rate
  • conversion timestamp
  • source currency
  • target currency

Important rules

• Never recalculate historical invoices using today’s FX rate
• Keep FX rates immutable once invoice is issued
• Show the currency clearly on all invoice totals and line items

Example

• Session amount: $21.00 USD
• FX rate at billing time: 1 USD = 0.92 EUR
• Invoice currency: EUR
• Invoice subtotal: €19.32

If taxes must be calculated in local currency, do tax calculation in the legally required order for that jurisdiction:

• Some systems calculate tax on the converted amount
• Others require tax in the transaction currency

---

6) Generate invoices from sessions

An invoice should typically contain:

• Invoice number
• Invoice date
• Billing period or session reference
• Customer name and address
• Tax ID if relevant
• Charging site / service location
• Line items
• Tax breakdown
• Currency
• Total amount due
• Payment due date
• Payment instructions
• Terms and conditions

Invoice types

• Per-session invoice: one invoice per charging event
• Periodic invoice: aggregate many sessions into a monthly invoice
• Prepaid wallet statement: top-up and usage history
• B2B consolidated invoice: grouped by fleet/customer account

For EV charging, monthly consolidated invoicing is common for fleets and roaming partners.

---

7) Manage payment collection

Integrate with a payment provider for:

• Card payments
• Direct debit
• Wallet balance
• Postpaid invoicing
• Bank transfer

Payment flow options

Immediate capture

• Charge customer right after session ends

Preauthorized / postpaid

• Authorize before charging
• Capture after session finalization

Invoice-based

• Generate invoice later
• Customer pays within terms

If you support businesses or fleets, invoice-based billing with credit terms is often preferred.

---

8) Data model suggestion

A simple schema might include:

Tables/entities

• customers
• vehicles
• charging_sessions
• tariffs
• tariff_rules
• invoice_batches
• invoices
• invoice_lines
• tax_rates
• fx_rates
• payments
• refunds
• credit_notes

Important fields

invoices

• id, invoice_number, customer_id, issue_date, due_date, currency, subtotal, tax_total, total, status

invoice_lines

• id, invoice_id, session_id, description, quantity, unit_price, amount, tax_rate, tax_amount

charging_sessions

• id, customer_id, location_id, start_time, end_time, kwh, currency, tariff_id, status

---

9) Handle corrections, refunds, and credit notes

EV charging sessions can be adjusted after the fact due to:

• meter corrections
• failed readings
• session disputes
• price adjustments
• idle fee disputes

Best practice:

• Don’t edit issued invoices directly
• Issue a credit note or adjustment invoice
• Keep an auditable ledger of all changes

---

10) Make it audit-ready

For accounting and compliance, keep:

• Original session data
• Tariff version used
• FX rate used
• Tax rate used
• Invoice version history
• Payment records
• Refund/credit note records

This is especially important if you operate across countries or regions.

---

11) Recommended processing flow

A common flow is:

1. Charging session starts
2. Meter and session data are recorded
3. Session ends
4. Billing engine computes charges
5. Tax engine determines taxes
6. FX conversion applied if needed
7. Invoice generated
8. Payment collected or invoice sent
9. Settlement and reconciliation
10. Adjustments handled via credit notes if needed

---

12) Practical implementation tips

• Use idempotent billing jobs so sessions are not invoiced twice
• Version tariffs and tax rules
• Store money in minor units where possible, e.g. cents
• Round carefully and consistently
• Use a ledger approach for payment and invoice state
• Separate:
  • raw session metering
  • pricing calculation
  • invoice presentation
• Add monitoring for:
  • duplicate invoices
  • failed FX lookups
  • tax calculation errors
  • incomplete sessions

---

13) If you’re building this for production

Consider using:

• A tax calculation service
• A payment processor with invoicing support
• FX rate provider
• Accounting integration
• A rules engine for tariffs and tax

If you’re in the EU or cross-border business, also check:

• VAT invoicing requirements
• Reverse charge rules
• B2B vs B2C distinctions
• Local receipt/invoice formatting rules

---

If you want, I can also provide:

1. a sample database schema,
2. a billing workflow diagram,
3. or example invoice JSON/API payloads for EV charging sessions.