Skip to main content

Risk Reward tool and the Profit are not matching

The Risk Reward tool and the Profit are not matching. The profit recorded is higher than the real. In the example below I am risking $147,83 with a R:R 2,62, so the profit should be $387, 31. However, the profit of this trade was recorded as $415,71. This is happening in many trades.

How does this impact your experience?
2 comments

Comments2

  • Diana Zhoshko

    Team•

    Oct 24

    Hi Luhem,

    We reviewed the project and were able to reproduce the result of $415.71.

    The difference between the expected RR target ($387.90) and the recorded profit is caused by positive slippage. The trade was filled at a better price than the levels defined by the Risk Reward tool:

    • Entry: 2722.406 instead of 2722.408

    • Exit: 2723.835 instead of 2723.741

    This is valid behavior for limit orders, which may be executed at a more favorable price when market conditions allow.

    Please also note that:

    • The Risk Reward tool calculates the theoretical result based on the planned entry, stop loss, and take profit levels.

    • The actual profit is calculated using the real execution prices and commission ($0.12 in this case).

    • The displayed RR value of 2.62 is rounded, so multiplying the risk amount by 2.62 will not necessarily produce the exact expected profit.

    Such price improvement on both limit entries and exits is standard market behavior and is described by brokers such as IG and OANDA.

    However, it is important to understand that this is a possible execution outcome, not a guaranteed one with every broker. In live trading, the final execution depends on factors such as available liquidity, execution delays, and the broker's execution policies. Partial fills may also occur.

    Therefore, based solely on historical quotes, it is not possible to prove that the entire 2.91-lot position would have been filled at exactly the same price in a live market environment.

  • Diana Zhoshko

    Team•

    Oct 23

    Hi @Luhem Oliveira,

    Thank you for reporting this. I've already informed our developers about the issue.

    Could you please provide the project link where this occurs?