Frequently Asked Questions

ChargeReport automatically generates tax-compliant charging reports for company car drivers who charge their electric vehicle at home using their own wallbox. The report is sent as a PDF via email directly to the employer — as proof for electricity cost reimbursement.

You connect your wallbox once to ChargeReport (cloud login or OCPP gateway). From then on, all charging sessions are automatically recorded. At your chosen interval (daily, monthly, quarterly or yearly), a PDF report is generated and sent to your employer. The report contains all sessions with kWh, date and the reimbursement amount.

ChargeReport supports 17 wallbox brands: Easee, go-eCharger, Wallbox (Pulsar/Commander), Zaptec, myenergi Zappi, V2C Trydan, Charge Amps, Ohme, Sungrow (iSolarCloud) and GoodWe (SEMS+) via cloud connection. Fronius Wattpilot, KEBA KeContact, Mennekes Amtron, ABL, Alfen Eve, cFos Power Brain and Elli (newer models) via OCPP gateway.

OCPP is an open standard for communication between wallboxes and backend systems. Many wallboxes that don't have a cloud API support OCPP 1.6J. ChargeReport runs an OCPP server — you simply enter a URL in your wallbox, and charging sessions are recorded automatically. No software installation needed.

Yes. A wallbox using OCPP talks to exactly ONE backend. As soon as it connects to ChargeReport, its link to the manufacturer backend ends — and that is what carried the app's control features such as pausing or charging windows. This is not a fault; it is how OCPP works. ChargeReport measures and documents, but deliberately does not control: if reporting fails, the report is late; if control failed, you would find an uncharged car in the morning. Schedule charging via the car instead — it knows its state of charge and handles preconditioning.

Yes, via an intermediate meter instead of OCPP. Your wallbox stays with the manufacturer backend and the app keeps working — a Shelly Pro 3EM handles the evidence, a DIN-rail energy meter installed in the distribution board on the wallbox supply line. It measures the wallbox alone and therefore satisfies the separate-meter requirement in para. 27 of the German BMF letter of 11 Nov 2025; MID calibration is explicitly not required. The device costs roughly EUR 100–130 depending on retailer, plus installation by an electrician. Let us know if you'd like this route — we'll set up the connection for you.

The first report is free. After that: €0.50 per charging day, €1.50/month, €3.50/quarter or €12.00/year — depending on your chosen interval. For employers, flat-rate packages start at €15/month for up to 10 employees.

Yes, at any time in the dashboard. The switch takes effect from the next billing cycle.

Yes. In the dashboard, you can create reports for past months or quarters at any time — at the respective plan price.

As an employer, you create a business account and invite your employees via email. Each employee connects their own wallbox. You receive all reports centrally in the dashboard, can download combined PDFs and get a single invoice.

€15/month for up to 10 employees, €20/month for 11–20, €25/month for 21–30. From 30 employees: +€5 per additional 10. This is a flat rate, not per person. 14 days free trial.

Per company and month you export a ready-made table with staff number, name, kWh and amount — as Excel, as a posting CSV, or in DATEV format for German payroll (LODAS or Lohn und Gehalt). Reimbursement then runs through payroll instead of individual bank transfers. We recommend running the first DATEV import as a trial with your tax advisor.

It cannot be ruled out completely — a fuel card for a combustion car doesn't do that either. What is required is a traceable, documented procedure with a plausibility check, and two routes lead there. The first is the private RFID card, and it works where the card number reaches us together with the session: via the OCPP gateway (KEBA, Mennekes, Fronius, ABL, Alfen, cFos, Elli) and with Charge Amps, Easee and GoodWe. A card reader on the box alone is not enough — the number also has to reach the evaluation, and not every manufacturer cloud hands it over; for further connections we are building that in right now. Which cloud passes the card on for your model, we tell you specifically — most providers only talk about “RFID support” and mean the card reader by it. Where it does work, the driver registers his private cards once (e.g. the family's second car) in his own account; their sessions then stay out of billing automatically, with nothing further to do. Otherwise per-session confirmation is the mechanism: each morning the driver receives an email and, if set up, a push notification about the previous day's sessions, and classifies every single one as business or private. Nothing is preselected — that is exactly what it is built for: one wallbox with the company car plugged in each morning and the private second car each evening. Sessions marked private drop out of billing immediately. As soon as at least one session is business, the odometer reading is mandatory (a photo of the dashboard stays optional); for purely private sessions neither is asked for. We are open about what the odometer reading does: it is a record that stays traceable later — no more, but no less either. It does not yield a consumption figure per 100 km, because we only see the wallbox at home; electricity charged on the road is missing from our kWh. One signal stays solid: energy flowed, but the vehicle was not moved — no public charging explains that. The larger effect is a human one anyway: the driver knows that odometer reading and charged energy are recorded and looked at together. That is a brake and a record, not a proof. Implausible readings are flagged automatically; if a driver confirms despite the warning, it is recorded on the session and shown to you. Sessions below 1 kWh are not asked about, the link is valid for 30 days and there is exactly one reminder, after three days. You switch the confirmation on for the organisation and set it per driver (on, off, or as the company) — only exempt someone whose connection passes the card on and who has registered it, otherwise no mechanism at all would be left for him. Conversely you can trial the process with a single driver first; for him it is then just as binding as fleet-wide, so his unconfirmed sessions are missing from his report. Unconfirmed sessions do not go into the report, but as a rule they are not lost: they appear in the next report as soon as they are confirmed. Two exceptions remain: sessions below 1 kWh are never asked about and therefore stay unconfirmed, and after 30 days the link expires — anyone who does not answer within that time can no longer submit that day.

Yes, as long as the limit is clear: a meter measures electricity, it does not see a vehicle. Behind a Shelly meter — and in any wallbox without a card reader — there is no technical separation between the company car and a private second car; anyone promising you one is promising too much. The same applies where the box does have a card reader but its manufacturer cloud does not hand the card over with the session — with go-e, for instance, the cloud interface returns no individual sessions at all, only totals per card. Whether the card arrives for your model, we tell you specifically beforehand. The mechanism there is per-session confirmation: the driver classifies each of the previous day's sessions individually as business or private, and sessions marked private drop out of billing immediately. On top of that comes the odometer reading entered along with it — a record and a plausibility check, but not a consumption figure. It does not give a consumption figure per 100 km: we only see the wallbox at home, and electricity charged on the road is missing from our kWh. It is, however, a record that stays traceable later, and one signal stays solid — energy flowed, vehicle not moved. Readings that run backwards and unrealistic jumps are flagged automatically; if a driver confirms despite the warning, it is recorded on the session and shown to you. The strongest effect is a human one: the driver knows that odometer reading and charged energy are recorded and looked at together. That is not infallibility, but nobody asks for it: a fuel card for a combustion car does not prevent a private tank of fuel either. What is required is a traceable, documented procedure with a plausibility check — and legally, para. 27 of the German BMF letter of 11 Nov 2025 states that a separate meter is sufficient; a calibrated MID meter is explicitly not required.

The admin sees all employees' charging sessions, grouped by company, with date, duration and kWh. Individual sessions can be excluded from billing with a stated reason, which remains documented for the employee. What a driver has declared private themselves cannot be reversed by the admin, and nothing is ever deleted: a month that has been billed stays reproducible for a payroll tax audit.