🧭✨Future Charges (NEW)

✨ NEW TABLE - November 2025

🛠️ Partner API Alignment Migration

🧭 This table represents the post-migration state for charges.

1️⃣ Migrate to this table by April 2026

2️⃣ Between April 2026 and July 2026, remove FUTURE__ prefix 3

Charge session records enriched with charge point, team, and operator data. Contains detailed information about charging sessions including timing, energy consumption, pricing, and operational state.

SQL: FUTURE__charges

Schema

Changes from Last Version

Added columns:

• operator_role: ('owner' (of CP), 'payer', or 'both)
• type: ()Classification of the charging session type ('sponsored', 'operator', 'external')
• new IDs: paying_team_id, promotion_code_id, cost_price_group_id, price_group_id, smart_charge_id, sponsor_team_id,
• new timestamps: paying_team_deleted_at charge_point_deleted_at ,
• Operator matching filters
  • paying_team_is_main_operator_match
  • paying_team_is_parent_operator_match
  • charge_point_is_parent_operator_match
  • charge_point_is_sponsor_operator_match,
  • charge_point_is_sponsor_parent_operator_match
  • charge_point_is_main_operator_match,
• new pricing columns: price_limit, cost, price, payment_method
• other: avg_renewable, charge_auth_identifier, note

Renamed columns:

• charge_point_group_id → charge_point_site_id
• co2 → avg_co2_kwh

Data inclusion criteria

• either the charge_point_id is among ids of the operator's FUTURE__charge_points
• or the paying_team_id is among the id's of the operator's FUTURE__teams'

select charges.*
from FUTURE__charges as charges
left join FUTURE__charge_points as cp
    on charges.charge_point_id = cp.id
left join FUTURE__teams as teams
    on charges.paying_team_id = teams.id
where
    -- Filter by operatorRole: 'owner' filters by charge_point_id, 'payer' filters by paying_team_id
    -- Include charges where:
    --   1. The charge point is owned by the partner (operatorRole='owner')
    --   2. OR the charge is paid by a team belonging to the partner (operatorRole='payer')
    cp.id is not null
    or teams.id is not null

Data flow

Alignment

Partner API

• Aligns with Partner API get/charges endpoint
• This endpoint has a mandatory operatorRole param, so the SQL table has to be subset to match the API
• use operator_role column along with operator_match columns to align the API with the SQL table
• operatorRole = 'payer' → sql operator_role in ('payer', 'both') and paying_team_is_main_operator_match=true
• operatorRole = 'owner' → sql operator_role in ('owner', 'both') and (charge_point_is_main_operator_match=true or charge_point_is_parent_operator_match=true)

The charges table

• To match charges one needs to align charge_pointsand teams

              where (
                -- For owner/both roles: charge_point must exist in OLD charge_points table
                (operator_role in ('owner', 'both')
                 AND charge_point_id IN (SELECT id FROM FUTURE__charge_points WHERE integration_deleted_at is null))
                OR
                -- For payer role: paying_team must not be deleted
                (operator_role = 'payer' AND paying_team_deleted_at is null)
              )