My trades are on the wrong day

Three different timezone settings decide which day a trade lands on. Which one to change, and why one of them needs the file uploaded again.

Same on every platform Updated 26 July 2026

What this does

Trades landing on the wrong calendar day, or a session labelled After-Hours when it was the middle of the session, come from a timezone mismatch. VEXA keeps three separate timezone ideas and they are easy to confuse.

	What it is	What it affects
Broker Server Timezone	The clock your broker’s export was written in	How a file is read at upload time. Changing it means uploading the file again.
Display timezone	The clock you want to read trades in	What you see, everywhere, immediately. Your data is untouched.
Storage	Always true UTC	Nothing you can change, and nothing you need to.

Before you start

Work out which of the two settings is wrong, because the fixes are different.

Every trade in one broker account is shifted by the same whole number of hours. That is the Broker Server Timezone. It was wrong when the file was read.
Everything in the app shifted together, across every broker. That is the display timezone.
Some trades are on the right day and some are not, usually around session boundaries or daylight saving changes. That is a display timezone that does not match the market you trade.

Which brokers need a server timezone

Five run on their own clock and need this set: MetaTrader 4, MetaTrader 5, Moomoo, Tiger Brokers and NinjaTrader.

MetaTrader is the one that catches people. VEXA defaults to GMT+2, which is the most common MetaTrader server offset and is far from universal. Check the clock in your terminal’s Market Watch panel against your own, and set the offset that matches. NinjaTrader exports in whatever timezone the platform itself is configured for, usually Central time for CME futures.

Every other broker writes a timezone into its export, or exports in a fixed known zone, so there is nothing to set.

Steps

Open Profile from the sidebar card that shows your name with View Profile under it.
Find the Display Preferences card.
Set Broker Server Timezone to your broker’s server clock.
Set Trade Display Timezone to the clock you want to read trades in.
If you changed the server timezone, upload the affected file again. The setting is applied when a file is read, so trades already imported keep the timezone they were imported with.

Tap the circular avatar at the top right of Home.
Open Settings.
Tap Broker Server Timezone and set your broker’s server clock.
Tap Display Timezone and set the clock you want to read trades in.
If you changed the server timezone, upload the affected file again.

Tap the profile chip at the bottom of the sidebar, then View Profile.
Open Settings.
Tap Broker Server Timezone and set your broker’s server clock.
Tap Display Timezone and set the clock you want to read trades in.
If you changed the server timezone, upload the affected file again.

Tap the circular avatar at the top right of Home.
Open Settings.
Tap Broker Server Timezone and set your broker’s server clock.
Tap Display Timezone and set the clock you want to read trades in.
If you changed the server timezone, upload the affected file again.

Android also puts a timezone selector on the upload screen itself, so you can set it at the moment you pick a file rather than going to your profile first.

On Android tablet both timezone settings live in the pane the Display Timezone row opens. They are stored on your account rather than on the device, so if that row does not respond you can change them on your phone or on the web and this tablet picks up the result.

Open VEXA on the web, or on your phone.
Set Broker Server Timezone and the display timezone there.
If you changed the server timezone, upload the affected file again.

What you should see

After a display timezone change, times across the journal, metrics and trade pages move immediately. Nothing is recalculated and nothing is at risk, because trades are stored in UTC and the display timezone is only a lens over them.

After a server timezone change plus a re-upload, the affected trades sit on the correct calendar day and their session labels make sense: Pre-Market, Regular, After-Hours or Overnight, relative to the market the symbol trades on.

Re-uploading is safe. Fills already imported are recognised and skipped.

Daylight saving

Markets change clocks and broker servers do not always change with them. If your trades were right for months and then shifted by an hour on a specific date, that date is a daylight saving boundary somewhere. The fix is the same: set the offset that matches your broker’s server clock now and re-upload anything that landed wrong.

If it doesn’t work

Only some trades moved. Those trades came from a different file or a different broker account, imported under a different setting. Re-upload the ones that are still wrong.
The day is right but the session label looks odd. Sessions are derived from the market the symbol trades on, not from your local clock. An overnight futures fill genuinely sits outside regular hours.
Daily totals disagree with your broker. Compare the same date range in the same timezone on both sides before treating it as a P&L problem. See Your P&L does not match your broker.

Some of my trades are missing Part of your history imported and part did not. Almost always the export covered less than you thought, or your broker splits its history across several files. Your P&L does not match your broker How VEXA calculates trade P&L, the three bases it uses in priority order, and the six reasons your number and your broker's number can legitimately differ. How forex and CFD trades are imported Lots, quote-currency P&L, broker symbol suffixes, hedged positions and swap. What VEXA does with a forex or CFD fill and what you have to set yourself.

Still stuck? Email support@vexatrade.ai.