Skip to main content
← All answers

Checked 2026-11-10

Why does my trading journal show my trades on the wrong day, or at 7 PM?

Usually because the export had a date and no execution time. A bare date is stored as midnight UTC, and midnight UTC is 7 PM the previous evening in New York in winter and 8 PM in summer, so a journal that reads trades on the market's clock moves every one of them back a day, onto the wrong weekday, at an hour you never traded. Since November 8, 2026 TradeFlow Quantum treats an instant at exactly midnight UTC as date-only: it keeps the date written in the file, gives the trade that date's weekday and reports the hour as unknown. The other case is a real fill late in the evening, which is already the next day in UTC; here it stays on the market's day.

Midnight UTC is the evening before in New York

A journal has to store every trade as an instant. A row that says only "2026-11-04" becomes 2026-11-04T00:00:00Z, midnight UTC. Session questions (which day, which weekday, which hour) are answered on the market's clock, US Eastern, so that a Tuesday evening fill counts as Tuesday. On that clock, 2026-11-04T00:00:00Z is 7 PM on November 3, because New York is five hours behind UTC in winter. A date-only row from summer, "2026-07-06", reads as 8 PM on July 5, four hours behind. Every trade in the file moves back one day and lands at the same evening hour.

Nothing errors. The import succeeds, the row count matches, and the one sign is that every date is one day earlier than the statement. The reconciliation answer lists this among six reasons a journal disagrees with the broker; this page is the long version of that one.

Which case you have

Compare a few trades with the broker statement:

  • Every trade is exactly one day early and shows 7 PM or 8 PM: the file had dates and no times. In TradeFlow Quantum, the import summary on the brokers page says so on a line headed "Rows with a date but no time", with the count.
  • Only trades taken late in the evening differ, and only from a log kept in UTC: those are real fills on the market's day. A fill at 21:30 ET on Tuesday, November 3 is 02:30 UTC on Wednesday; the journal files it on Tuesday, the session it was traded in.
  • Dates match but some trades are missing or doubled: that is a different problem, covered in the reconciliation answer above.

What TradeFlow Quantum does with a date-only row

Since November 8, 2026, a stored instant at exactly midnight UTC, to the millisecond, is treated as date-only. The journal keeps the date written in the file for the calendar and daily P&L, gives the trade that date's weekday, and reports the hour as unknown, so hour-of-day views leave those trades out, or file them under "—", instead of stacking them at 7 PM. The trade page prints the date with a note, for example "Nov 4, 2026 · time not in import".

The rule has one edge: a real fill at exactly midnight UTC, to the millisecond, is read as date-only too. A fill one millisecond later is not.

What it cannot do is recover the time. Hour-of-day figures stay blank for those trades until you re-export with execution times. The post on exports without times walks through finding a per-execution export, and the supported broker pages that list a broker's CSV columns include the column the importer reads the trade's date and time from.

Questions traders ask

Why 7 PM in winter and 8 PM in summer?

Midnight UTC is 7 PM in New York on Eastern Standard Time and 8 PM on Eastern Daylight Time. A journal reading a date-only row on the market's clock shows whichever applies on that date.

Will my calendar and daily P&L be right for a date-only import?

In TradeFlow Quantum, yes for the date: a date-only row stays on the date written in the file. The hour is reported as unknown, not guessed.

Can the journal work out the missing times?

No. A file with dates only carries no time to recover. Re-export from the broker with execution times. The timed rows carry a different open time, so they do not match the date-only rows already imported; remove those first, or the trades are counted twice.

A trade I took at 9:30 PM shows on the day before my UTC log. Is that the same bug?

No. That fill is on the market's day: 21:30 ET is already the next day in UTC, and the journal files it on the session it was traded in.

Sources

Related

TradeFlow Quantum is a $15/month trading journal: 10 direct broker connections that work during the 7-day trial, nightly sync for paid accounts, a prop-evaluation copilot, and a P&L-free weekly discipline grade. Descriptive analytics only — nothing in the analytics edits your trades.

Start your 7-day free trial →