Match EV Charging Records and Document Energy Differences

The short answer

Two charging records can only be compared when they cover the same charging session, or the same set of sessions, and their energy figures are measured the same way. Matching the unit is not enough. Two values both labeled kWh (kilowatt-hours, the standard unit of electrical energy) can measure different things. First confirm that the records refer to the same event. Then confirm what each energy figure represents. Keep both original totals unchanged, and record the gap as a plain arithmetic difference. If the issuers have not explained why the numbers differ, label the gap unresolved rather than calling it a loss, a fault or a billing error.

Terms used in this guide

• Session: one continuous charging event, from the moment a record says charging started to the moment it says charging ended.
• Issuer: the company that produced a document, such as a charging network, a roaming provider, a vehicle maker's app or a home energy app.
• Scope: what a record covers, whether one session, one day or a selected period.
• Measurement definition: what an energy figure actually represents. Examples include energy billed at the station, a live reading during charging, a meter register, or an app's estimate of energy added.
• Meter register: a cumulative reading on a station's energy meter, recorded at the start and end of a session.
• Roaming: charging on one network while paying through another provider's account or app.

Why the same unit does not mean the same measurement

ChargePoint's European metering documentation for its CP6000 AC station shows how many distinct energy and power figures a single station can produce. That documentation separates the following:
• the theoretical maximum power of a port;
• the dispensed energy billed in kWh, which it describes as compensated;
• the station meter's starting and ending register values, also in kWh.
It also distinguishes uncompensated live readings shown during charging from compensated values in the session summary. As a result, a live figure noted mid-session and a session-summary total from the same station are not interchangeable, even though both are in kWh.

That documentation applies to the EU version of that one model. Other stations, markets and networks may define their figures differently. If you need to know exactly what a station's compensation accounts for, ask the issuer for the field definition. Do not assume one.

Identify each document's issuer and scope

Before treating two documents as records of the same transaction, establish who issued each one and what it covers. ChargePoint's driver support describes account session details that show the date, time, kWh and station address. It treats individual session receipts as separate from monthly statements, so a statement total should not be compared with a single receipt. ChargePoint also notes that when you charge through a roaming provider, that provider issues its own receipt and sets its own charging terms and prices. A network receipt and a roaming provider's receipt for what seems to be the same charge are therefore two issuers' records, each with its own definitions.

Check session, day and period boundaries

Vehicle apps often summarize charging instead of listing sessions one by one. Tesla documents that its app's charge stats group charging by day and by charging-location type, with totals for a selected period. A session that crosses midnight can therefore show up in two daily bars. Tesla's graph also switches between energy in kWh and estimated cost. For the Work and Other location types, the default cost figures use regional estimates.

In practice, decide whether you are comparing a session with a session, a session with a day, or a session with a period. A single station receipt for an overnight charge will not line up with either daily bar on its own. Compare it with the combined coverage of both days, and only if no other charging falls inside that coverage. Treat estimated cost views as estimates, not as substitutes for billed amounts.

Battery percentage is not a kWh figure

Some apps report energy as battery percentage added rather than kWh. ev.energy describes session views that can show either kWh or battery percentage added, along with session summaries that include plug-in times and location. Record which view each value came from. A percentage figure cannot be turned into kWh without a stated conversion rule. It also cannot be equated with a station receipt without knowing where each figure is measured, so leave it in its own column.

Build a reconciliation worksheet

Create one row per source record. Do not merge records into a single row. Link candidate matches with a shared match ID so the originals remain intact. Useful columns include:

• Document ID and issuer
• Vehicle reference, and where that reference came from (account, app or receipt)
• Session ID, if the record has one
• Station and port identifiers
• Original start and end times, exactly as printed
• Timezone stated or implied by the record
• Duration label, for example plug-in time or charging time
• Scope: session, day or period
• Energy label as written on the record
• Reported value and unit
• Measurement definition, if documented
• Normalized value and conversion rule, kept in separate columns
• Match ID and match status

Decide whether two records match

• 1. Match explicit references first. A shared session ID is the strongest link. On the CP6000 described in ChargePoint's EU documentation, the session ID also appears in the OCMF (Open Charge Metering Format) record, and station and port identifiers serve as additional references.
• 2. Cross-check vehicle, location and times. If no shared ID exists, these become the main evidence of a match, so all of them should agree.
• 3. Pause on conflicts. If the vehicle or location conflicts, or the timezone or start and end events are unclear, mark the pair as awaiting clarification instead of forcing a match.
• 4. Align coverage. If one record combines several sessions or days, gather the records that together cover the same span before comparing totals.
• 5. Confirm units and measurement definitions. If you convert any value, put the result in a separate column and record the rule you used.
• 6. Record the difference and its status. Compute it only after the steps above are settled.

Worked example (hypothetical)

The figures below are illustrative. Suppose record A and record B have been confirmed to share the same session boundaries, unit and measurement definition. Record A reports 24.80 kWh and record B reports 24.10 kWh. Define the difference as A minus B: 24.80 − 24.10 = +0.70 kWh. Fixing the direction of subtraction keeps the sign consistent across your log.

Field	Record A	Record B
Reported energy	24.80 kWh	24.10 kWh
Boundaries confirmed	Yes	Yes
Measurement definition confirmed	Yes	Yes
Difference (A − B)	+0.70 kWh	—
Status	Unresolved reported difference	—

Both original totals stay on the worksheet. The subtraction shows the size of the gap but not its cause. Until an issuer explains it, the correct label is an unresolved reported difference.

Ask the issuer the right questions

When a match or a difference needs clarification, contact the issuer of the record in question. Ask precise questions:

• What event starts and ends this record: plug-in, authorization, energy flow, or unplugging?
• Which timezone do the printed times use?
• What does this energy field measure, and where is it measured?
• Is the value measured or estimated?
• Does this document cover one session, or does it aggregate several?

Keep a follow-up and closure log

For each open item, record:
• the exact question asked;
• the issuer contacted;
• the document references supplied;
• the response date;
• any field definition the issuer gave, quoted word for word.
Close only the specific issue the response settles. For example, a confirmed timezone resolves a boundary question but not an energy-definition question. Any difference that remains unexplained stays on the log as reported, without being labeled a charging loss, a vehicle fault, a billing error or a safety finding.