A trade ticket can display a live price while the instrument behind it is configured incorrectly. The symbol name may look familiar, but order acceptance depends on a separate collection of records describing contract size, permitted quantities, trading status and price increments. Platforms must check those records before an instruction becomes an executable order.
For forex trading platforms, reference-data validation is an operational safeguard rather than a market forecast. Its failures can reject legitimate instructions, misstate exposure or allow orders whose economic meaning differs from what the customer intended.
Symbol Identity Must Match the Intended Contract
A label such as USD/JPY does not establish every contractual detail. Brokers may publish separate symbols for account types, execution arrangements or products with different settlement conventions. An order router must resolve the displayed name to the correct internal instrument identifier and verify that the instrument is active for that account.
An outdated symbol mapping can send an order toward a discontinued contract or the wrong product configuration. Checking the instrument description and account eligibility is particularly important after platform migrations, symbol renaming or changes to a broker’s product catalogue.
Quantity Rules Can Reject Otherwise Valid Orders
Minimum trade size, maximum size and permitted increments are independent of the current exchange rate. A platform may reject 0.15 lots when a particular instrument accepts only increments of 0.10 lots, even though the account has sufficient margin. The same order might be valid for another symbol.
A robust validation process checks quantities against the current contract specification before sending the request. Automatic rounding is not always harmless: increasing a quantity to the next permitted step can create more exposure than the customer authorized.
A Contract-Size Error Can Multiply Exposure
Imagine a hypothetical currency CFD labelled USD/PLN. An order-entry screen displays a request for 0.40 lots, and the customer expects one lot to represent USD 100,000. Intended exposure is therefore USD 40,000. Following a configuration update, the order service incorrectly reads a contract size of USD 10,000 per lot while the execution server still uses USD 100,000.
The service estimates USD 4,000 of notional exposure and understates the associated margin requirement. If the server accepts the 0.40-lot order, actual exposure is USD 40,000, ten times the service’s estimate. A proper pre-trade check reconciles contract size and margin parameters with the authoritative execution configuration, rejecting inconsistent requests rather than relying on a plausible-looking ticket.
Price Precision and Trading Sessions Require Separate Checks
Currency prices may use different decimal conventions, tick sizes and permitted order distances. A stop price rounded to the display precision can still violate the instrument’s actual tick increment or minimum stop distance. Meanwhile, a valid price cannot make an order executable when the symbol is closed for trading.
Reference records should distinguish quotation availability from order-entry availability. Some instruments continue showing indicative prices outside executable hours. A platform that treats every visible quote as tradable may create avoidable rejections or leave customers uncertain about pending-order behavior.
Stale Specifications Can Survive a Correct-Looking Interface
Validation is only as reliable as the version of reference data being checked. A mobile client, pricing service and execution server may update at different times. A local ticket can pass its own checks while the server rejects the instruction using newer restrictions.
For forex trading platforms, a server-side rejection can be safer than accepting an order under inconsistent rules. Before opening a currency CFD, inspect the current symbol specification for contract size, lot step, tick size, margin treatment and trading hours; then confirm the order preview reflects those values and that the platform reports any rejection without silently changing the requested quantity.