Revenue assurance and charge records
Charge records your finance team can stand behind
Every completed session becomes one charge record that is never changed afterwards, priced with the connector’s tariff and the site’s VAT. Roamed sessions carry Getz Hub’s tariff-check decision, and everything flows into files for your accounting tool.
Charge detail records (CDRs) for every session, in each site’s currency.
- What you see: every CDR with energy, tariff and amount
- Why it matters: immutable once issued; export to Xero, QuickBooks or Sage files
What it does
From session to statement
A locked record of each session
One immutable record per completed session, created once. Late messages never reopen a finished session; late meter data is kept as flagged evidence.
Hub tariff-check decisions
For roamed sessions, Getz Hub re-prices the record against your agreed tariff. Its decision (held, released or rejected, by whom and why) appears on your record.
Accounting files
CSV, Xero journals, bank statements or sales-invoice drafts, QuickBooks Online journal entries or invoices, and Sage journals.
Scheduled reports
Run exports on demand or on a schedule in your time zone, with the data window you choose, delivered by download or e-mail.
Audit trail
Every change in the back office is written to an audit record, and downloads of report files are audited too.
Card-terminal sessions stay yours
Sessions paid at a card terminal on the charger are recorded but never roamed to an app.
Direct accounting push
Records land in your accounting system with no file to import.
Coming soon
Leakage and calibration workflows
Workflows that act on leakage, calibration and compliance evidence.
Coming soon
In the product
What Hub’s tariff check does, and what it does not
Getz Hub checks every roamed charge record against the tariff you agreed with the partner and holds mismatches for finance to release or reject. It does not verify that the charger’s meter measured energy correctly; that is a matter of meter certification. It also cannot catch a tariff that was agreed wrongly in the first place.
Revenue assurance: exceptions found in sessions and CDRs, with their root causes.
- What you see: open exceptions by age and root cause
- Why it matters: leakage is found by rules, not by month-end reconciliation
Interactive: from session to statement
Follow one session to the reports
Select each stage to see what happens to a fictional session’s record, from the charger to your accounting files and the owner’s portal.
The charger reports the session’s end
Meter values arrive over OCPP while the car charges. When the transaction stops, the session closes. Late messages never reopen it; late meter data is kept as flagged evidence.
| Site | Demo Mall – Rosebank |
|---|---|
| Connector | Rosebank DC 1 · CCS2 |
| Energy | 18.4 kWh |
| Charging time | 41 min |
Questions
Revenue assurance and charge records: questions
Does Getz Network issue invoices?
No. It produces records and accounting files. Invoice layouts create drafts in your accounting tool, where your finance team issues them.
How is a disputed session resolved?
The operator looks up the session’s charge record, its OCPP message history and, for a roamed session, Getz Hub’s tariff-check decision. The record itself is never edited: any correction is made in the billing or accounting tool of whoever billed the driver, and a charge record is evidence of the session, not proof that money was received.
What does an owner or funder see, compared with the exports?
The read-only portal shows operations and energy per site, never prices. Charge records with amounts reach owners and funders only as exports that the operator’s finance team chooses to share. See the host and investor portal.
Does assurance prove our meters are accurate?
No. Assurance checks prices against the agreed tariff and the consistency of records. Meter accuracy depends on the charger’s certified meter. Meter-calibration workflows are coming soon.
Show your finance team the records
Request a demonstration of charge records, Hub decisions and exports with demonstration data.