JouloDocs

Charging data delivery

Deliver charge sessions as CSV keyed on your customer number, or let customers link their own charger.

Charging data delivery

Each tenant has one charging data source, configured by Joulo:

  • Customer-linked (user) • the customer connects their own charger in the onboarding wizard and Joulo syncs the sessions from the charger backend. You deliver nothing; skip the rest of this page.
  • CPO-delivered (tenant) • you deliver the sessions, keyed on the customer number. The charger-link step is removed from onboarding and the customer dashboard shows the latest delivery date.

CSV delivery

Upload a session export in the admin portal under Imports (/admin/imports). One row per charge session, semicolon-delimited, with a header row:

contract;customer;MID;EVSE-Id;Manufacturer;Model;Serialnumber;"session start";"session stop";"total energy (kWh)";"session ID"
1707830;1706679;true;NL*XYZ*E0013982*001;Alfen;"Eve Single Pro-line 22kW cable";ace0013982;"2026-01-10 12:02:18";"2026-01-10 14:18:54";24.2000;82227874

Columns

ColumnRequiredDescription
customeryesYour customer number. Must match the number the customer registered with (SSO sub or the signup form).
MIDyestrue/false (also accepts 1, ja, yes). Whether the session was measured by a MID-certified meter.
session startyesYYYY-MM-DD HH:mm:ss. Determines the month the energy is booked in.
total energy (kWh)yesSession energy. Both 24.20 and 24,20 are accepted; European thousands formatting (1.234,56) is handled.
contractnoContract number, used as fallback matching key when the customer number does not match.
EVSE-IdnoCharge point id. Parsed per customer; not currently shown in the import report.
ManufacturernoCharger manufacturer, e.g. Alfen. Used to verify MID status against the charger catalog.
ModelnoCharger model.
SerialnumbernoMeter/charger serial number.
session stopnoIgnored for booking; the start timestamp determines the month.
session IDnoYour session reference.
StreetnoStreet of the charge point's location.
House Numberno, but send itHouse number of the location, for example 12.
House Number AdditionnoAddition, for example A. You may also put it in House Number (12A).
Postcodeno, but send itPostcode of the location, for example 6961 AB.
CitynoPlace of the location.

Practical notes:

  • Column order does not matter and header matching is tolerant of casing and punctuation.
  • A comma-delimited file also works; the delimiter is detected from the header row.
  • UTF-8, with or without BOM; any line-ending style.

Charge point location

The verifier wants proof for every charger that it stands at the address of its EAN. The address columns give Joulo that proof without asking the customer for anything. Joulo reads them when the House Number and Postcode headers are present. Street, City and House Number Addition are optional.

  • Per charge point, not per row. The address belongs to the charge point (EVSE-Id, or serial number when there is none). The first row with a value wins, so you may fill it on every row or on one row per charge point.
  • Postcode and house number decide. Joulo compares them, with the addition, with the address the customer registered with, which we checked against the EAN. A customer with more connections matches when the charge point stands at one of them. Street and city may stay empty, and spelling differences in them never cause a mismatch. 12A and 12B are different addresses. When only one side has an addition, nothing disagrees.
  • The address routes kWh. For a customer with more connections, a charge point goes to the connection at its address when no EVSE-Id was set for it.
contract;customer;MID;EVSE-Id;Manufacturer;Model;Serialnumber;"session start";"session stop";"total energy (kWh)";"session ID";Street;"House Number";Postcode;City
1707830;1706679;true;NL*XYZ*E0013982*001;Alfen;"Eve Single Pro-line 22kW cable";ace0013982;"2026-01-10 12:02:18";"2026-01-10 14:18:54";24.2000;82227874;Dorpsstraat;12;"6961 AB";Eerbeek

What happens on import

  1. Rows with MID = false are skipped: only MID-metered kWh counts toward ERE. The report shows how many rows were skipped for this reason.
  2. Sessions are rolled up to monthly totals per customer. You keep the raw sessions; Joulo books the month aggregate.
  3. Customers are matched on customer number first, contract number as fallback. Unmatched customers are listed in the import report so you can see who has kWh waiting but no registration yet.
  4. Re-importing a month overwrites that month for the customers in the file. Delivering a cumulative or overlapping export is safe; totals never double-count. Each delivery must contain the complete month, though: a re-import replaces the stored month total rather than adding to it, so a file with only part of a month would lower it.

The import report shows rows counted, rows skipped (non-MID and rows with missing or unreadable fields), matched and unmatched customers, the months written, and the charge points whose address is not the address of the customer's connection. Those kWh are still imported; Joulo reviews the charge point.

Deliver at least monthly. The dashboard shows customers the date of the latest delivery, and ERE submission follows the delivered months.

REST delivery

Programmatic session delivery over REST is available for CPOs on the Integrated API: push monthly kWh totals per account with POST /v1/sessions:batch, on the same data model as the CSV (MID-metered kWh, idempotent per month). Use it instead of CSV uploads when you run your own onboarding through the API.