Intro

GreenFlux Billing Engines (more here) are equipped with a powerful validation system that identifies transactions containing missing, incorrect or suspicious data before ever creating a final Charge Detail Record (CDR). Flagged transactions can be viewed and actioned directly from the CDR table in EV Portal. This capability provides transparency into and control over transaction flows for CPOs and eMSPs.

Validation Categories

Validation Category	Description	Available Actions
Configuration	Checks if the information of the underlying entities related to the transaction is complete, such as Networks, Contracts, Agreements, Tokens, etc.	1. Retry 2. Drop
Feasibility	Checks if transaction details related to time, duration, energy and power are feasible.	1. Accept 2. Drop
Billing Rules	Checks if there is a single valid billing rule.	1. Retry 2. Drop
Final Cost Check	Checks if the cost(s) is/are feasible.	1. Accept 2. Drop

Each category has a set of validation criteria that it must pass, or the transaction will be flagged and then must be actioned from the CDR table.

Review & Action CDRs

Users can see all transactions in the Charge Detail Records table.

⚠️

It is the responsibility of the CPO operator to cyclically, recommended once a week, check the CDR validation tool and take action if any issue is detected.

Billing Status and Analysis

Each line item in the table can have 1 of 3 states in the Billing Status column: Calculated, Flagged or Dropped.

A flagged transaction means that the CDR has not yet successfully been created, and thus requires attentions from the user to progress. Flagged transactions are in an automatic daily retry queue for 90 days. If the transaction is not resolved within 90 days, it is dropped.

⚠️

A dropped transaction means the the user has reviewed the transaction and decided it cannot or should not be finalized as a CDR, and thus will never be published via any API or export, and thus never be invoiced. If you dropped a CDR by mistake, you can undrop it from the Actions button.

Besides the Billing Status, there are 3 other important columns for CDR Validation:

Billing Status Analysis: Provides information about the type of error on the transaction, a recommended action to take in order to resolve it, and a copyable message with all the relevant technical info to provide GreenFlux Support in case you need help.

Days Remaining: Days remaining in the automatic daily retry loop. When this number reaches 0, the CDR will be dropped.

Last Actioned: Details on which user last actioned the transaction.

Actioning Flagged Transactions

Each flagged transaction can be actioned individually from any view in the table using the Action button at the end of each line in the CDR table:

Depending on the state and the type of flag, different actions are available for each transaction.

Action	Description	Example
Accept	Accept the suspicious transaction	Transaction has a cost of 200 euros; you verify that the tariff on this charger is indeed very high, and so accept the transaction.
Retry	Retry processing the transaction, usually after fixing something	Flagged CDR was missing a Billing Rule; add the Billing Rule and retry.
Drop	Drop the transaction out of the invoicing cycle. A CDR is not created, and thus will not appear in any API, export, etc.	Transaction has volume of 5000kWh in 2 hours; something went wrong in the charger, so we Drop this CDR in order to avoid billing the driver.
Undrop	Send the transaction back to the Flagged state after it was dropped.	You drop the transaction on Row 1 when you intended to drop Row 2. Go to the Dropped view and undrop the Row 1 transaction.

Table Views and Bulk Actions

Each CDR can be actioned individually from any view in the table; however it is also possible to apply filters to the table and perform the same action on multiple transactions at once.

You can use the Views bar at the top of the table to select one of 5 views: All, Successful, Retriable, Suspicious, or Dropped.

The bulk actions available in each view are as follows:

View	Bulk Actions Available
All	None
Successful	None
Retriable	1. Retry2. Drop
Suspicious	1. Accept2. Drop
Dropped	1. Undrop

To perform bulk actions, go to the appropriate View, select the line items you wish to action in bulk, and use the drop down actions at the top right of the table.

ℹ️

Note: You cannot perform bulk actions from the "All" view, because the the possible actions are "mixed" so cannot easily be done in bulk. In the Retriable, Suspicious and Dropped views, the possible actions are uniform, so we can easily do bulk actions.

Validation Criteria

⚠️

This is not an exhaustive set of validation conditions but rather the most relevant ones.

Configuration Validation

Location info is complete (counter example: Missing or invalid connector)

Token info is complete

Valid Agreement found

eMSP entities can be resolved

CPO entities can be resolved

Feasibility Validation

Volume < 750kWh

Duration < 7 days

Duration > 2mins OR Volume > 0.2kWh

If Volume>1, Duration>1: Average Power [Volume(kWh)/Duration(h)] < 350kW

MeterValueStart < MeterValueEnd

StartDate > (Today - 180days)

StartDate < ReceivedDateTime + 24hrs

Billing Rule Validation

Valid Billing Rule is found

No conflicting billing rules are found

Cost Validation

WholesaleCost < 200 euros

WholesaleRetailDeltaHigh: retail cost should be less than 1.5x wholesale, or less than 5 euros when wholesale is zero

WholesaleRetailDeltaLow: retail cost should be at least 67% of total wholesale cost

Special Cases

When Duration < 2 minutes AND Volume < 0.2 kWh, we set cost to zero, but the CDR can still be generated as valid. Roaming contracts do not allow CPOs to invoice transactions that do not meet these criteria. We still create the CDRs in this case to facilitate specific technical flows, but by setting cost to zero we avoid invoicing issues. Furthermore, when required to have these CDRs exposed through Platform API subscriptions, this can be done, but it needs to be enabled (by default, these CDRs are not exposed)

These validation criteria are not applicable to CDRs involving chargers that belong to Mobi.E network, due to regulatory compliance reasons.