Ask Flux
Help Center
How can we help?

Tariff and prices

Tariff management

Introduction to e-Mobility, Transaction Types and GreenFlux Billing (Tariff) Engines

The article explains the e‑Mobility ecosystem and the three primary transaction types—Ad‑hoc charging, CPO subscription, and eMSP (roaming) subscription—detailing how drivers pay, how payments flow among drivers, CPOs, eMSPs, and GreenFlux, and the associated billing models. It also introduces a fourth transaction type, fleet reimbursement, and outlines GreenFlux’s three billing engines that calculate retail, wholesale, and reimbursement costs for these use cases.

How to manage tariffs and pricing using GreenFlux platform - CPO and eMSP perspectives

The article explains how GreenFlux manages tariffs, data exchange, and financial clearing for different EV‑charging transaction types—ad‑hoc charging, CPO subscriptions, roaming, and reimbursement—detailing the roles of CPOs, eMSPs, drivers, and the platform in each scenario.

Redesign of currency support in GreenFlux platform

The article explains upcoming changes to GreenFlux’s handling of currency in both wholesale and retail billing. It outlines the timeline for when new retail and wholesale billing rules go live, describes the current and future behavior of currency assignment, and details four retail‑pricing options that determine how the currency is chosen or defined. It also clarifies that the platform does not perform currency conversion, so any needed conversion must be managed by eMSPs. Finally, it briefly covers how wholesale tariffs define their own currency.

Wholesale Billing Engine and wholesale tariff configuration

The article explains how to configure wholesale unit pricing (tariffs) for both GreenFlux‑managed and self‑managed roaming services, detailing use cases for creating and updating tariffs, the operating scenarios of the Wholesale Billing Engine, and the steps required to assign a default tariff to a charge station.

Tariff Codes - What is it and how to I assign it to chargers?

This article explains what tariff codes are in the GreenFlux EV platform and how they identify the charging tariff structure for each charge station. It guides users through adding or updating tariff codes—both at the charge‑station level and for individual connectors—by using the portal’s creation wizard or the edit interface, and notes that changes apply only to future sessions.

Tariffs and Billing: Page Overview and Billing Rule Details

The article explains the “Tariffs and Billing” page, which offers a comprehensive overview of billing rules and their associated tariffs. It highlights key features such as persistent filtering and the ability to view detailed billing rule information. The piece then breaks down the Billing Rule Details page, describing each section—Rule Identification, Tariff, Price, CPO, eMSP, and Validity—and outlines how exceptions (time‑based and location‑based) are managed. Overall, it serves as a guide to navigating and understanding tariff and billing configurations.

How to create a (wholesale) tariff or update an existing tariff

The article provides step‑by‑step guidance for creating and updating wholesale tariff pricing in the GreenFlux platform, covering both managed‑roaming and self‑managed CPO networks. It details use cases for adding new tariffs with specified unit prices (e.g., 0.40 €/kWh, 0.33 €/kWh) and for modifying existing tariffs (e.g., price increases to 0.42 €/kWh or 0.35 €/kWh), including navigation through the “Tariffs and billing” interface, required fields, handling of billing rules, price settings, lead‑time considerations, and the process for splitting overlapping rules. The content emphasizes default‑pricing setup, scope limitations, and coordination with CSMs.

Batch Update Charge Station Tariff Codes

This article explains how to perform a bulk (batch) update of the default tariff codes for charge stations using the Charge Station Importer tool. It outlines the necessary permissions, walks through the steps to select chargers, prepare a CSV file with the new tariff codes, and run the import wizard. The guide also clarifies that only the default tariff of each station is changed—connector‑specific overridden tariffs remain unaffected—and provides a concrete example illustrating the before‑and‑after state of a charge station’s tariff configuration.

Reimbursement Billing Engine and reimbursement tariff configuration

The article explains how GreenFlux’s reimbursement billing engine works—detailing the conditions under which it runs, how it calculates reimbursement costs, and the principles governing reimbursement tariffs. It provides step‑by‑step instructions for creating and managing reimbursement tariffs and billing rules (including adding new tariffs, configuring unit pricing, scheduling price changes, and assigning tariffs to charge stations), along with best‑practice guidance for default billing rules.

Retail Billing Engine and Retail tariff configuration

The article explains the retail billing engine used in GreenFlux, detailing how it calculates retail costs for token‑based charging sessions, the principles governing retail packages, and step‑by‑step instructions for configuring retail unit pricing and billing rules within the platform.

Parking/Idle Price Component

The article explains GreenFlux’s parking/idle price component, detailing how parking fees are defined, detected, and calculated within billing rules, the mandatory configuration requirements (including Time‑of‑Use or Dynamic Time‑Based tariffs), and the technical and exception handling aspects of implementing and charging for parking time.

Dynamic Time Based Pricing

The article explains Dynamic Time‑Based (DTB) pricing for electric‑vehicle charging, detailing how operators can apply multiple time‑of‑day price models (e.g., different rates for day and night) within a single charging session. It contrasts the legacy single‑price approach with the new DTB feature, outlines configuration steps, technical constraints (such as exclusion of energy‑based tariffs), and highlights how the billing engine calculates costs based solely on time. The piece also notes UI changes for drivers, exception handling, and app support for displaying upcoming rates.

Time of Use Pricing

The article explains Time‑of‑Use (ToU) pricing for electric‑vehicle charging, detailing how multiple price rates (peak and off‑peak) can be applied during a session, the required charger and platform configurations, the differences between using ToU and a single‑rate setup, and how costs are calculated—including handling of special cases like missing meter data or offline stations.

VAT support

The article explains how GreenFlux’s VAT support works, detailing how CPO operators can define VAT rates at three hierarchical levels—tariff, CPO contract, and CPO—along with the priority rules that determine which rate applies. It guides super‑admin users through the steps to add and configure VAT rates, outlines best‑practice considerations for single‑rate and multi‑rate countries, and includes examples for the Netherlands and France to illustrate proper configuration.

Home Charging VAT exemption

The article explains the Home Charging VAT exemption (HCC) feature for CPOs, detailing how to configure chargers and tokens to exclude VAT from home‑charging sessions, the resulting CDR flags (HCC_E or HCC_V), bulk‑update methods, and how VAT applicability is reflected in charge‑detail records and product‑type mappings.

Location-Based Price Exceptions (LBPE): Legacy Pricing Configuration

The article explains the legacy “Location‑Based Price Exceptions (LBPE)” feature, which lets GreenFlux CPO operators define special tariffs for specific locations and token groups (e.g., private or semi‑private charging). It outlines how LBPE works, typical use cases, setup steps, and details major limitations such as poor scalability, reliability issues, usability challenges, and its impact on future tariff‑management improvements. The piece also notes that LBPE is only available to certain tenants (primarily GreenFlux staff) and that no alternative pricing rules currently exist for its use cases.