Every operation on an Exness account leaves a record

Minimum deposit applicable; may vary based on payment method or geographic location.

What the account writes down for you

• Every order carries a ticket of its own — opening and closing time, size and price stay in the history after the position is gone
• Funding and withdrawal requests appear as separate lines with a status of their own, so a pending item is never confused with a completed one
• Most withdrawals are processed automatically, 24/7 — the request line keeps the time it was raised and the time its status changed
• A statement for a chosen period can be exported from the account area or saved from the terminal, as a file you keep yourself
• The history belongs to the account rather than to the program that displayed it, so reinstalling a terminal does not shorten it
• MT4, MT5, the Exness Terminal web platform and the Exness Trade app each keep a visible log of what was sent from them
• Charges are attached to the entry they belong to, not summarised at the end of the month

Processing times may vary depending on the chosen payment method.

Where each kind of record is kept

Also: what a charge line contains, what can be traded, reaching the account area, gold trading and how to open an account.

What is left once the trading is done

The part of an account that lasts is its record. Positions close and balances move; what remains is a list of entries with times, sizes and charges attached to them, and that list is the thing to open when a figure is disputed or simply forgotten. Keeping an exported copy of a period, instead of relying on scrolling back, is what turns a question about last month into a one-minute answer. Independent Exness reviews on Trustpilot are worth reading beside it. CFDs carry a high risk of losing money — confirm the latest terms before depositing.

What a single order writes

An entry is created when the order is accepted, not when it is finally closed. From that moment it holds a ticket number, the instrument, the direction, the size in lots and the price it went in at. The closing side is appended later to the same entry rather than starting a new one, which is why a completed deal reads as one line with two ends.

Charges live on the entry they belong to. Where an account carries a commission, it sits on that deal and not in a monthly total; where a position was held overnight, the swap sits there too. Reading a result therefore means reading one line to the end, not reconciling three different screens.

The comment field is the part traders most often ignore and later need. A short note written at the time — the reason for the size, the level being watched — survives in the record and is the only part of a decision that ever makes it into the history.

Where the copies live, and which one outlasts the other

There are three copies of most events, and they are not equally durable. The account area holds the list that belongs to the account itself. A terminal holds a local copy of what it displayed and sent, kept in the files of that installation. An email confirmation is a third copy, sitting somewhere entirely outside all of this, which is exactly what makes it useful.

The local copy is the one that quietly disappears. A reinstalled program starts an empty Journal, and a machine handed on to somebody else takes its logs with it. Nothing is lost from the account list when that happens, but the fine detail of what was clicked, when, and what the terminal answered is gone.

This is the practical reason to export before changing anything. A saved report is a frozen copy of a period; it does not update itself, it does not depend on a program still being installed, and it can be read years later by anything that opens a table.

Getting an entry back a month later

A month-old item is rarely hard to find; it is hard to find by the route people try first. Scrolling a list works for yesterday and fails for March. Setting a period and reading the resulting report takes the same thirty seconds regardless of how far back the question goes.

Identify a deal by its ticket number rather than by its amount. Amounts repeat — the same size on the same instrument appears dozens of times in an active month — while a ticket belongs to one entry and to nothing else. Quoting that number is also what makes a question to support answerable instead of approximate.

Timestamps in the record follow the platform clock, which is not necessarily the clock on the wall where the order was placed. When a report and a memory disagree by a couple of hours, the report is not wrong; it is stamped in a different reference frame, and the difference is constant.

Pulling last month out of the record

1. Open the account area and switch from the open-position view to the history of completed items — they are different lists, and the default one shows only what is still running.
2. Set the period explicitly to the month in question instead of accepting the recent window the screen offers.
3. Locate the deal by ticket number where you have it; where you do not, narrow by instrument and day before looking at amounts.
4. Export the period to a file and store it outside the program that produced it, named with the period it covers.
5. In MT4 or MT5, the same period is available from the Account History tab, where the context menu offers a saved report.
6. Keep the email confirmations for funding and withdrawal requests in one folder — they are the copy that stays reachable when nothing else is to hand.

A statement is a copy of what the account already holds; exporting one changes no entry and creates none.

Which record answers which question

Opening a report leaves the underlying entries untouched — reading is not an operation and writes nothing.