Skip to main content

MT5: Orders, deals and positions explained

Understand why an instruction, its execution and an open position are different records in MT5.

Understand why an instruction, its execution and an open position are different records in MT5.

Three different records

An order is an instruction to buy or sell. Sending or placing it does not by itself prove execution. A pending order can remain unexecuted, be cancelled or expire.

A deal records an actual execution. One order may produce more than one deal, including partial executions. Each execution can have its own volume and price.

A position represents open market exposure resulting from deals. Its treatment depends on the account’s position-accounting mode; do not assume every MT5 account uses the same mode.

Example: one instruction, several executions

Suppose you request a 1.00-lot Buy. Before execution, that request is an order, not an open position. If it executes as 0.40 lots followed by 0.60 lots, the history contains two deals associated with the order. Those deals create a total 1.00-lot Buy position. These figures illustrate record relationships; they are not a trading recommendation or a promised execution pattern.

If you subsequently use the closing function to close 0.25 lots of that selected Buy position, the closing execution is a Sell and 0.75 lots remain open. The closing deal does not mean the original trade was a Sell. Counting every execution row as a separate newly opened trade would also give a misleading result.

Match related records, not just identical numbers

Orders, deals and positions have their own identifiers and relationships. A deal’s ticket need not equal the order ticket or the position identifier. Use the related order/position information together with the account, symbol, volume and time. Never decide that a record is missing simply because two different record types show different numbers.

Cancelling an unexecuted pending order does not close an existing position. If an order was partly filled before its remaining quantity was cancelled, cancellation does not undo the already executed part. Check the deal records and remaining open position separately.

Why the account’s position mode matters

In netting mode, trades in the same symbol contribute to one net position. Same-direction executions can increase it; opposite-direction executions can reduce, close or reverse it depending on volume. In hedging mode, several positions in the same symbol can coexist, including opposite directions. A new Sell can therefore be a separate position rather than the closure of an existing Buy.

To close a particular position, use the appropriate closing function for that selected position. Do not assume that placing an ordinary opposite-direction order always closes it. MT5 supports both accounting models; this does not establish the model available on every FXT account. Your exact account configuration governs.


Why the history can look different

A buy position is normally closed with a sell execution. The closing deal’s direction therefore differs from the original position’s direction. A position-level trade summary and an execution-level history describe different things.

When comparing records, check the account, full symbol, ticket, volume, time and whether the row describes an order, a deal or a position. A displayed request or pending order is not proof that a trade was executed.

Before concluding that records disagree

Check the selected account, date range, time zone and record view first. A list of orders, a list of deals and a position summary have different scopes. A position summary may combine several executions, show weighted-average prices and aggregate results, while individual deals show their own execution volumes and prices. A narrow date filter can exclude information needed to reconstruct the whole position.

Compare like with like: an opening direction with another position summary, or a closing execution with the matching deal. Also distinguish requested volume from filled volume and the original position volume from the remaining volume. If the same type of record still conflicts after those checks, contact support through the authenticated Client Portal and explain which records you are comparing. Do not send passwords or verification codes.

Did this answer your question?