Charge-record assurance
Check roamed charge records against agreed tariffs
Hub re-prices every charge record a CPO sends from that CPO’s own tariff and compares the result with the CPO’s total. Mismatches are held before they reach the app, until finance staff release or reject them with a reason.
Charge records checked against agreed tariffs: mismatches are held until released. Synthetic demo data.
- Overcharged records are held from the eMSP
- Hub staff release a held record with a reason; every decision is audited
The challenge
Where roaming bills go wrong
Most disputes between operators and apps start with a charge record that does not match what was agreed, found weeks later.
Stale tariffs
A charger still bills last month’s price after the tariff changed.
Missing or extra fees
Idle, session or reservation fees left out or added by mistake.
Tax errors
VAT computed on the wrong amount, or at the old rate for a session after VAT moved to 15.5% on 1 January 2026.
How it works
How a record is checked
Step 1: Re-price
Hub prices the session from the CPO’s tariff, in the location’s local time, with fixed-point arithmetic, including tax, idle and reservation fees.
Step 2: Check consistency
Totals, periods, energy and times are checked against each other and against what the charger could deliver.
Step 3: Hold mismatches
A record that fails, or cannot be priced because there is no tariff, is held from the app.
Step 4: Release or reject
Finance staff release or reject with a reason. Both sides are told; every decision is audited.
Interactive illustration
Tariff check and mismatch handling
See how a charge record is re-priced, and what happens when it does not match.
Tariff check and mismatch handling
Pick what the operator’s charge record says. Hub re-prices the same session from the agreed tariff and compares totals. Synthetic numbers in US dollars.
| Energy | US$0.42 per kWh |
|---|---|
| Session fee | US$0.50 |
| Idle time | US$0.10 per min |
| VAT | 15.5% |
| Line | Hub re-priced | CPO’s record |
|---|---|---|
| Energy, 32.4 kWh × US$0.42 | US$13.61 | US$14.90 |
| Session fee | US$0.50 | US$0.50 |
| Idle time, 10 min × US$0.10 | US$1.00 | US$1.00 |
| Subtotal excluding VAT | US$15.11 | US$16.40 |
| VAT 15.5% | US$2.34 | US$2.54 |
| Total including VAT | US$17.45 | US$18.94 |
Price mismatch of US$1.49: held
The CPO’s total is higher than the tariff gives. Hub holds the record before it reaches the app. The record itself is never changed.
Finance staff review the held record and decide, with a reason:
Illustration with invented numbers. Hub’s check compares the record with the agreed tariff; it does not test the charger’s meter or the app’s own driver price.
Capabilities
What finance teams get
Records never altered
The verdict is stored beside the charge record. The record itself stays exactly as the CPO sent it.
OCPI 2.3.0 tax model
2.3.0 records are checked in their own tax-inclusive model, not forced through an older one.
Held-record alerts
Staff are alerted when a record stays held too long.
Decision notices
Partners that offer the Getz assurance notice module receive each decision over OCPI.
Sync and count checks
Health per partner and module, and count comparison where the sender reports its counts.
Audit trail
Every assurance decision with who decided, when and why.
Limits
What assurance checks, and what it does not
Assurance is a tariff and reconciliation check. It is valuable, and it has limits we state up front.
| Capability | Checked by Hub | Where it belongs |
|---|---|---|
| The agreed tariff applied to each roamed record | Yes | Hub assurance |
| Tax, idle and reservation fees | Yes | Hub assurance |
| Totals, periods and energy consistent with each other | Yes | Hub assurance |
| Record counts between sender and Hub | Partlywhere the sender reports its counts | Hub sync health |
| Accuracy of the charger’s meter | No | Meter certification (hardware and CPMS) |
| Whether the tariff itself was agreed correctly | No | The operator and the app |
| The app’s driver price, markups and refunds | No | The app |
| Settling money between the parties | No | The partners’ own invoicing |
In the product
Delivery health per OCPI module
What was delivered, what is waiting and what failed, per module. Captured with synthetic demonstration data.
- Degraded modules are flagged with the reason; staff can requeue failed deliveries
- Inbound counts are compared only where the sender reports its own counts
Partner health per OCPI module: what was delivered, what is waiting and what failed, so problems surface per module. Synthetic demo data.
Coming soon
More reconciliation, and the assurance tier billed from Hub.
- Coming soon
The assurance tier as a paid subscription, packaged and billed
The tariff checks themselves run on every roamed record.
- Coming soon
Record-count reconciliation with every sender, for every OCPI module
Extends today’s count checks to every module.
Questions
Charge-record assurance: questions
Does assurance verify the charger’s meter?
No. Assurance is a tariff and reconciliation check. Meter accuracy is a matter for meter certification, the charger hardware and the operator’s CPMS.
Does it check what the driver paid?
No. The app’s driver price, markups, card charges and refunds happen after Hub and are outside the check.
Is assurance a paid tier?
The tariff checks run on every roamed record today. The assurance tier, with reconciliation reports and the audit trail as evidence for finance teams, is coming soon as a paid subscription. Pricing on request. See the pricing model.
Who resolves a held record?
A held record waits until a finance user releases it or rejects it with a reason. The operator and the app are both told, and the decision is audited. Fixing the cause, such as a stale tariff, is the operator’s job; the commercial dispute, if any, stays between operator and app. Complaints and settlement questions about Hub’s handling go to support@getzcharging.com.
Do late charge records still arrive after an agreement ends?
Yes, for 90 days. Session updates and charge records of sessions that started under the agreement are still delivered for 90 days after it ends; after that they are refused, with a recorded reason both partners can see. Discovery and commands stop when the agreement ends.
What does this mean for a driver’s bill?
A charge record that does not match the agreed tariff can be held for review before it is passed on to the app that bills the driver. The app’s own driver price is outside the check.
Give your finance team the same evidence as your partners
Talk to us about assurance for your roamed sessions.