RECORDS / TERMS / THE NEXT APPOINTMENT

Keep EV Charging Session Records and Link Original Receipts

Build an EV charging log that records each session's date, vehicle, kWh, duration and station, links the original PDF receipt, and keeps costs in a separate expense table.

6 min readRunning-cost notes1 viewsKeep EV Charging Session Records and Link Original Receipts
— · 0 votes
Contents
  1. The short answer
  2. What different sources actually give you
  3. Getting the original receipts
  4. Treating Tesla charging data correctly
  5. Set up the session log
  6. File documents and expenses separately
  7. Worked example (hypothetical)
  8. Check your own provider before mapping its data

The short answer

Keep one row per charging session in a log, and save every original document that supports it: a PDF receipt, a monthly statement, an app history screen or an export. Copy each value exactly as the source reports it, including its unit and label. Then link each row to its documents by an ID you assign. Track money in a separate expense table. That way an overlapping statement and receipt never count the same charge twice, and an estimated cost never passes for a billed one.

A charging session is one continuous connection between a vehicle and a charger port. The energy value is the electricity reported for that session, usually in kilowatt-hours (kWh). Whether that number is a billed meter reading, an estimate or a daily total depends on the source, so the source decides how you label it.

What different sources actually give you

Charging records differ in what they contain and in what they can prove. The descriptions below come from each company's own support material for the products named. Your account, region, charger model or app version may show different fields.

SourceWhat it recordsHow to treat it in your log
ChargePoint account session (US-style driver account)Date, time, kWh, cost breakdown, payment method, station address; individual receipts can be shared as PDF; monthly statements are separate documentsIndividual receipt supports one session row; statement is a second document that may repeat the same sessions
ChargePoint CP6000 receipt (EU metering configuration)Station ID, invoice number and date, session time, rated power, total dispensed energy in kWh, fees, starting and ending meter registers in kWhUse dispensed energy as the session's billed energy; rated power is the port's theoretical maximum, not what the car drew
Roaming-card session on a public networkReceipt issued by the roaming service provider, which also sets the terms and priceRecord the roaming provider as the receipt issuer, not the station operator
ev.energy charge historySession history filtered as Standard, Smart, Boost or Away from Home; energy shown in kWh or battery percentage; plug-in times and location; cost when availableNote which unit view you copied from; away-from-home sessions appear only when the vehicle itself is connected to the service
Tesla app charging statsGraphs for a selected period, grouped by location type and by day, with estimated spendingA period summary, not a receipt; an overnight session can appear across two daily bars; costs are estimates

Getting the original receipts

  • ChargePoint account holders: open the Activity section to view a session and share its receipt as a PDF. Monthly statements are available as separate documents.
  • ChargePoint guest payments by card: use the receipt lookup instead of an account history. Some European operators issue receipts through their own websites.
  • Roaming cards: request the receipt from the roaming service provider that issued the card.
  • CP6000-type downloads: the downloaded receipt PDF drops any links that were attached to the receipt. If a receipt references a link, save that link as its own document entry rather than relying on the PDF to keep it.

Treating Tesla charging data correctly

Tesla's in-app charging stats show charging for a selected period, grouped by day and by location type (Home, Work and Other). The spending figure is an estimate. Home uses the rate you select or enter, and Work and Other default to regional electricity estimates unless you change them. A session that runs past midnight can split across two daily bars, so a day's bar is not one session. Access depends on your Tesla account, app and vehicle software versions, and data-sharing settings.

If you capture this view, file it as a period summary with its date range. Record its cost as estimated. Don't split a daily bar into invented session rows. Where a Supercharger or third-party network issues an actual per-session receipt, that receipt is the document to link to a session row.

Set up the session log

Use one row per session. Fill only what a document actually states. Write "not supplied" for missing values, never zero. A blank duration and a zero-minute session mean very different things.

record_id,vehicle_ref,vehicle_ref_origin,provider,session_ref,station_port_id,station_address,date,start_time_original,end_time_original,timezone_stated,duration_value,duration_label,energy_value,energy_unit,energy_label_original,document_ids,verification_status
  • vehicle_ref_origin: whether the vehicle reference is one you assigned (for example V01) or one the provider reported.
  • start_time_original and end_time_original: copy timestamps as shown, and record the timezone only if the source states it.
  • duration_label: keep plug-in time and charging time in separately labeled fields when a source supplies both. A car can stay plugged in long after it stops drawing power.
  • energy_label_original: keep the source's wording, such as "total dispensed energy". If an app shows battery percentage instead of kWh, record the percentage with its unit rather than converting it.
  • verification_status: whether you have checked the row against its original document.

File documents and expenses separately

  • Save each original receipt, statement, history screenshot or export unaltered.
  • Give each document its own ID and record its issuer, document type, the date you captured it and the period it covers.
  • Link documents to session rows through the document_ids field. One session can link to several documents.
  • Keep money in a separate expense table: amount, currency, document reference, and whether the amount is billed or estimated.
  • Before you add expenses from a monthly statement, match its lines to receipts you have already filed, and enter only the charges not yet recorded.

Worked example (hypothetical)

This example is illustrative, not drawn from a real account. Session S01 is for your vehicle V01, which you labeled yourself. Receipt R01 reports 12.40 kWh and a billed amount of 4.96 in the stated currency. Later, monthly statement M01 also lists that charge. You keep both R01 and M01 as documents and link both to S01. The session log still has one row for S01, and the expense table has one billed entry of 4.96 referencing R01. M01 is noted as also covering that charge, not entered as a second expense. R01 shows no duration, so S01's duration reads "not supplied".

Check your own provider before mapping its data

Field names, history depth and export formats vary by provider, account type, region and app version. If you need older records, such as sessions from 2022, confirm how far back your provider's history reaches before you rely on it. Before you build your log around any source, check the following.

  • How far back the session history goes, and whether older sessions are still accessible.
  • Which vehicle and session identifiers appear.
  • What the timestamps mean, plug-in or charging start, and which timezone they use.
  • How energy is defined: billed meter energy, estimated energy or battery percentage.
  • Where receipts are retrieved and whether they download as PDF.
  • What export option exists, if any. Open an actual export and confirm its columns, units and date coverage before mapping them into your log.

Related articles