Use interval energy when you have it
A typical supported row has an interval timestamp and an amount of imported energy in kWh. Set the interval duration and identify whether the timestamp is the start or the end. The tool converts supported readings to interval starts internally.
Wh can be converted to kWh. A kW column can be converted only when it represents average power over a known duration. An instantaneous demand reading cannot be treated as interval energy.
Make dates unambiguous
An ISO timestamp with a UTC offset is the clearest input, for example 2026-07-01T17:00:00-07:00. The offset identifies the instant; the utility’s time zone identifies the applicable local hour.
For dates such as 03/04/2026, choose month/day/year or day/month/year yourself. My Power Rates does not silently decide whether you meant March 4 or April 3. A repeated fall clock hour needs an explicit offset to distinguish its two occurrences.
Check the preview and meter
Comma and semicolon delimiters and quoted fields are supported. Select the decimal separator separately. Review the timestamp and consumption columns before confirming.
If the file includes multiple meters, select one. Adding them together automatically could mix service conditions or double-count a whole-premise reading. Fix rejected rows in the source text or mapping and run the review again.
What this release does not import
PDF bills, OCR and utility account connections are outside this release. Green Button XML is not enabled: a safe implementation needs separately verified ESPI export profiles, including multipliers, directions and quality codes.
Export readings, solar and battery profiles require a different billing model. Removing their negative rows would create a misleading import-only history, so those inputs are not a supported shortcut.
Next at the desk
Continue reading
Sources & reference
Product behavior is documented for this edition. The source register contains dated tariff evidence and its verification notes.