I have an MT4/5 client getting slipped on his SL/TP prices. Please can you look into it for me please

First, we need to find the orders in Compass.

To find them in Compass you'd try to locate the same orders in Echo. Match the MT4/MT5 login with the counterparty field in compass

https://echo.mahimarkets.com/execution/yieldProfiles

Then filter for instrument / time range

We can then narrow it down to an order and Mahi can provide the forensic details based on their trade id.

Clicking on the trade id in Echo, will show you the order book at the time etc. and we can support the inquiry with fix logs if it needs to go further

With your MT4/5 flow by the time the order reaches us, it is often passed with a FIX order type of market i.e. not proposed with a price

It is often felt better to guarantee the fill and slip vs reject the order

Slippage can occur where a stop loss or take profit is triggered in MT4/5 and there is a delay in getting that order to us. During which successive updates to the price may have occurred

Even a small delay of 10 ms can at certain times have multiple price ticks elapse.

Another factor here is that the price can move through the SL/TP price in a single tick.

Slippage can occur when MetaQuotes only sees the cost of a BUY or SELL in the Top of Book i.e. small order quantities. A VWAP price for the order may be not as attractive to the user

So alot of the time its a business tradeoff between whether you want to reject the proposed order if phrased as a limit price (i.e on arrival to us the price is gone), or slip them.

It is possible to manage the FIX order type used to propose these orders to Compass.

Its a common predicament across brokers. As part of our MT4/5 bridge we are enriching our order types with the SL/TP rate, so we can also govern order acceptance in relation to that

i.e. for good customers honour their SL/TP for bad ones take the business decision to slip them