MT5 netting — what happens to SL and TP when a position changes?

On an MT5 netting account, stop loss and take profit belong to the combined position for a symbol, rather than to each addition separately. A subsequent deal can therefore change protection for the entire remaining quantity. Before increasing or reversing a position, check both the volume and the levels carried by the order. These examples describe MT5 netting; do not automatically apply them to MT4, a hedging account or another platform.

What do the SL and TP levels protect?

Think of two records: executed deals and the current position. History retains individual executions, while netting combines their current effect into one direction and volume. Our article on long and short positions explains that distinction. An order ticket does not create a separately protected slice of the position. If you want to close only part, you need an appropriate instruction and a check of the quantity actually remaining.

A position's stop loss and take profit are exit conditions. They do not represent cash reserved for a future loss or a guaranteed execution price. Establish whether you are reading the current position, a pending order's parameters or a historical deal. Those three views can legitimately contain different numbers. An old deal showing a stop does not establish that the current position still has that stop.

When are the levels retained or replaced?

MetaQuotes distinguishes an increase or reversal, which adopts the latest executed order's levels, from a partial close, which retains the position's levels. A full close removes them with the position. Zero values in an increasing or reversing order can remove the corresponding SL or TP. This is a platform rule, not advice to remove protection. Source: MT5 inheritance rules.

The order window can automatically insert existing levels. According to MT5 documentation, One Click Trading through the chart panel or Market Watch preserves current SL/TP for an existing symbol position. Missing fields in a quick panel do not mean an instruction to delete stops. Compare the actual execution route: a custom EA request does not necessarily reproduce the quick-trading button's behaviour.

Separate the executed deal from a later modification of protection. If a robot first adds volume and then sends revised SL/TP, the intermediate position can differ from its target state. A log saying that a modification was sent does not resolve that exposure. You need confirmation and a fresh reading of accepted server levels, especially when another program is operating on the same account.

How do addition, reduction and reversal work?

This is a hypothetical USD account and EUR/USD contract: one lot represents 100,000 EUR, with no commission, financing or slippage. Initially, 0.20 lot was bought at 1.1000, with SL 1.0970 and TP 1.1060. Each step below assumes the stated quantity was executed and the appropriate parameters accepted. The prices support arithmetic, not a market recommendation or a universal broker specification.

Addition: buying 0.10 lot at 1.1030 with SL 1.0990 and TP 1.1080 produces one 0.30-lot position. Its weighted entry price is (0.20 × 1.1000 + 0.10 × 1.1030) ÷ 0.30 = 1.1010. The new levels cover all 0.30 lot, including the earlier 0.20. There are no independently retained stops for the two purchases.

Reduction: selling 0.05 lot reduces the position to 0.25 lot. Because this operation partially closes it, the existing SL 1.0990 and TP 1.1080 remain. Zero parameters in a partial-closing order are a different situation from zero parameters in an addition. Identify the quantity change first, then assess inheritance. A sale need not mean a new short position.

Reversal: selling 0.40 lot at 1.1040 against the remaining 0.25-lot buy closes that 0.25 and opens a 0.15-lot sell position. In this model the reversing order carries SL 1.1070 and TP 1.0980. Those levels apply to the new short exposure. Selling 0.25 instead of 0.40 would fully close the position without leaving a new direction.

The diagram's conclusion: the change to the combined position determines protection, rather than the label Buy or Sell alone. The sale can reduce a buy position or establish short exposure. Use the current volume to distinguish these outcomes; an amount remembered before the latest execution is insufficient. When another order fills, recalculate the intended next instruction before sending it.

Why recalculate risk after adding volume?

Initially the model has a 0.0030 distance on 20,000 EUR: the price difference represents 60 USD of planned loss to the SL level. After addition, 30,000 × (1.1010 − 1.0990) also equals 60 USD. That equality comes from these particular numbers, not from netting itself. Keeping the old 1.0970 stop would mean 120 USD. A larger quantity changes the weight of every price movement.

After reduction, the remaining position gives 25,000 × 0.0020 = 50 USD from the weighted entry to the retained stop. After reversal, the new short position gives 15,000 × (1.1070 − 1.1040) = 45 USD. These are separate measures of remaining exposure; do not add previously realised profit to the calculation. Actual losses can include costs and a different fill. Account currency and contract specifications also matter.

The same stop price can represent a different cash exposure after volume changes. Checking the level and checking risk are two separate steps.

What should you check after the server response?

Read the symbol, direction, remaining volume, weighted entry and current S/L and T/P. Compare them with the plan recorded before the operation. For an EA, OrderSend returning true does not confirm execution: check the result, events and account state. An unclear response is not a reason to repeat the trade on an assumption. The MT4 and MT5 order-error guide helps identify rejection and technical restrictions.

If protection is missing, assess present exposure and available ways to reduce it. Do not move a stop further away merely to obtain acceptance. Record the rejection reason, current quote and symbol conditions. A request changing only SL/TP still requires checking the other field: do not accidentally replace an existing TP with zero while trying to modify SL. A valid modification can still conflict with your risk plan.

For your journal, preserve before-and-after states plus order and deal identifiers. In MQL5, POSITION_IDENTIFIER helps link history: it persists through a netting reversal although POSITION_TICKET can change. A different ticket alone does not establish an entirely separate position history. This is a technical distinction; read identifiers and values from the same account and server. A screenshot from a different login is not a useful state comparison.

What to do tomorrow on demo?

1. Choose confirmed netting demo and small permitted volumes. Record the symbol, current direction, quantity and both protection levels. Prepare a table containing state before, instruction, expected state, server reply and the actual observed state afterwards.
2. Practise addition, reduction and reversal separately. After each confirmed fill, inspect remaining volume and SL/TP. Distinguish the order dialog, quick panel and your own EA; do not run this experiment on a live trading account.
3. Explain each discrepancy and recalculate remaining exposure before the next operation. Do not assume a stop survived merely because it existed previously. Use the MT5 overview linked earlier to confirm the wider account and tester context.