Skip to main content

Blog

Your broker CSV has dates but no times. Here is what the journal loses.

A date-only export puts every trade at midnight UTC. Formatted in US Eastern that is the evening before, so the whole journal runs a day early. What breaks, how to spot it, how TradeFlow Quantum now handles it.

Published by TradeFlow Quantum. Filed under import, csv, journal, measurement.

A broker export with a Date column and no Time column looks harmless. Every row still has a day on it. But a journal has to store each trade as an instant, and the convention for a bare date is midnight UTC. In US Eastern time, midnight UTC is 7 or 8 PM the evening before. From that one decision, a whole journal can run a day early without a single error message.

Quick check: open any trade in your journal and compare its date with the broker statement. If every trade is exactly one day early, or every trade shows a 7 PM or 8 PM time, your file had dates but no execution times.

What a date-only import breaks

  • The calendar. A P&L calendar that files trades by the market's day puts a Wednesday trade on Tuesday. Every daily total, every streak, every best and worst day shifts by one.
  • Day of week. Any journal that reports the weekday in US Eastern reports the previous weekday. Monday losses become Sunday losses, which no trader has.
  • Hour of day. Every trade lands at the same hour, 19:00 or 20:00 ET. The hour-of-day chart becomes a single bar at a time you were not trading, and any flag that reads hour of day fires on it.
  • Trade detail. The trade page shows a time the file never contained. Once a trader notices one invented timestamp, they stop trusting the numbers around it.

None of this shows up as an error. The import succeeds, the row count matches, and the trades are there. The only tell is that the dates disagree with the statement by exactly one day.

Why the time zone makes it worse, not better

A journal has to pick one clock for session questions like which hour and which weekday a trade belongs to, and the right clock is the market's, not the viewer's and not UTC. A 21:30 ET Tuesday fill is a Tuesday trade even though it is Wednesday in UTC. That rule is correct for every real timestamp and wrong for a bare date, because a bare date carries no instant to shift. The fix is not to abandon the market clock. It is to recognise that a date-only row is a different kind of value.

What changed in TradeFlow Quantum on November 8, 2026

A stored instant at exactly midnight UTC is now treated as date-only. It is filed on the date written in the file, its weekday is that date's weekday, and its hour is reported as unknown rather than 7 PM. The pattern flags leave those trades out of their hour windows, and the cohort view files them under "—" instead of plotting them at 7 PM. The trade list and trade page print the written date with a note that the time was not in the import.

The import summary on the brokers page now reports how many rows had a date but no time, next to rows read and trades inserted, so the gap is explained at import rather than discovered a week later in a chart.

What this does not do: it cannot recover the time. Expectancy by hour and anything else that needs the clock will stay blank for those trades until you re-export with execution times. Most brokers offer a time column or a per-execution export; the per-broker setup pages say which. Until November 10, 2026 this callout listed hold time among the blank figures, which the journal does not compute for any trade, and the paragraph above said hour-of-day views leave date-only trades out, where the cohort view files them under "—".

How to export with times

  1. Prefer the per-execution or activity export over the daily summary. Summaries are what usually drop the time.
  2. Look for a Time or Execution Time column before you upload. If the Date column already reads like 2026-11-04 09:31, you are fine.
  3. Check the import summary. Rows with a date but no time is the line to watch. Zero means every trade carries a clock.
  4. If you can only get dates, import anyway. The calendar, weekday and P&L views are correct; the hour views will say so rather than guess.

Why we are writing this down

A trial account imported 79 trades across seven days from a date-only file, spent about forty minutes in the journal, and cancelled the same session. We did not have the data to know why at the time. We do now, the fix is live, and the import tells you about it up front. If your journal, ours or anyone's, shows your trades a day early, this is the reason.

$15/month or $150/year, one tier, 7-day trial with a card at signup and $0 charged during it. The ten direct broker connections and CSV import work during the trial.

Related posts

Not financial advice. This post reflects the author’s opinion based on publicly-available information at the time of writing. Mention of third-party products is not an endorsement; product features and prices change over time. Past performance does not guarantee future results.