Errors in Forex.com / CityIndex Instrument Data

[kevinenergy]

Hi there,

There there are mistakes in the instrument data for UK100 and JAPAN225 CFDs on Forex.com/CityIndex





UK100 has a point value of £1 per contract, not £0.10 as listed. This is a serious issue because it has caused me to open up positions that are 10x bigger than they should be, based on my calculated projected Risk and Reward. It may also be the cause of Ninjatrader failing to compute my position PNL or Realised PNL correctly since this value will be used internally to calculate PNL based on the number of Points PL in my execution data.

I have confirmed this error by taking a Market Order for 1 CFD Contract with a 10 Point target and a 10 Point Stop in Ninjatrader. This produced a loss of £10.20, both in Ninjatrader and verified in the City Index ATPro Platform. This conclusively proves that each point has a value of £1.



Furthermore, UK100 does not move in 0.01 ticks it moves in 0.1 Ticks. You can observe this by bringing up a UK100 chart when connected to Forex.com and observing that the second decimal place is always zero. You can also validate this by checking the instrument on other platforms, which present the data to one decimal place: https://www.tradingview.com/chart/?s...GBP&interval=5

This is a problem because when coding a strategy that places an order a Tick above or below a bar you get triggered into a trade too early.

[NinjaTrader_Jason]

Hello kevinenergy,

Thank you for reporting.

I have contacted our server team regarding the UK100 instrument settings.

For now, you can manually change it in the instrument settings (if you did not already).

[kevinenergy]

Hi There,

I noticed an update has been pushed out to fix the incorrect Point Value on UK100 CFDs.
However, the Tick Value is incorrect - as I explained at the end of the original message it is supposed to be 0.1, not 0.01. I've attached a screenshot from CityIndex's ATPro Platform that shows this.

[NinjaTrader_Jason]

The tick size was left to 0.01 as prices are reported in 2 decimals when connected to FXCM. I'm not sure why CityIndex uses 1 decimal. I suggest to check with them for clarification.

You can change it manually in the instrument settings if you like.