Session Validation and Revenue Protection

The Problem

Why does this extension exist?

A charger that reports 0 kWh for a 40-minute session, a meter that resets mid-session, a CDR that arrives with a duration but no energy — none of these announce themselves. They pass through billing quietly, and the loss only shows up months later as a gap between what the meters delivered and what the invoices collected. By then the partner has closed the period and the money is gone.

The Solution

What you get

Validation rules per charger model and per location, so a known quirk of one manufacturer does not have to become a rule for the whole network
Automatic anomaly flagging with severity levels, so a rounding oddity and a lost session are not treated the same
Energy consistency checks: what the session reported against what the meter actually measured
Revenue leakage estimated per charger, per location and per roaming partner
Bulk validation across a period, with a trend dashboard that shows whether the problem is growing
Alert recipients and thresholds configurable, so the right person hears about it while it can still be fixed
A full audit trail of every check performed, kept as evidence for partner disputes

🎯 Who is this for?

CPOs and hub operators whose revenue depends on data produced by hardware they do not control, and finance teams that have to explain the gap between energy delivered and revenue collected.

Enable This Extension Browse All Addons

🔌 Modular by design

Enable or disable per tenant. Pay only for what you use. All addons integrate seamlessly.

Key Capabilities

Everything included

Rules You Configure

Build validation rules from the available types and scope them by charger model and location. A quirk in one manufacturer's firmware stays a rule for that manufacturer.

Severity, Not Just Alarms

Every flagged session carries a severity, so a €0.02 rounding difference and a completely lost 60 kWh session appear in different places on the list.

Revenue Leakage Estimates

The estimated loss is attributed to a charger, a location and a roaming partner — which turns 'something is wrong somewhere' into a work order for a specific asset.

Energy Consistency

Compare the energy the session reported with the energy the meter measured. A drift between the two is the earliest sign that a charger is misreporting.

Bulk Validation and Trends

Validate a whole period at once and watch the trend. A rising line tells you a firmware update or a new site is introducing errors before the invoices do.

Audit Trail

Every check that ran, on what, and what it concluded — kept in full. When a partner disputes a CDR, you answer with a record instead of a recollection.

Use Cases

See it in action

How operators around the world can use this extension to solve real problems and grow their business.

The charger that bills for nothing

One charger reports sessions of 30 to 50 minutes and 0.0 kWh. Validation flags them the same day at high severity, the site engineer finds a failed meter board, and the unit is swapped before it produces another month of unbillable sessions.

A meter that quietly disagrees

A location's site meter and the sum of its session energy drift apart by 4%. The consistency check surfaces the gap, the cause turns out to be one dual-connector charger reporting a single connector, and the tariff engine stops undercharging.

A roaming partner's period, defended with evidence

A partner disputes 3,200 CDRs at settlement. The leakage report shows which sessions were flagged, why, and when — and the dispute is closed on the record instead of on the phone.

Simulated Case Study

Network operator recovers 2.1% of annual revenue that was leaking through bad session data

An operator with 420 chargers knew that energy delivered and revenue collected did not match, but could not say where. After turning on session validation, rules per charger model flagged three firmware versions that under-reported energy and a batch of units that occasionally closed sessions with no meter value at all. Fixing those, and re-billing what was still in period, recovered 2.1% of annual revenue — and the flag rate has fallen every quarter since.

2.1%

Of annual revenue recovered

420

Chargers under validation

Firmware versions found at fault

Same day

From bad session to alert