FIX TAG 103
OrdRejReason
Definition
Code to identify reason for order rejection. Note: Values 3, 4, and 5 will be used when rejecting an order due to pre-allocation information errors.
Compare versions
Differences between the selected source snapshots, including wording and errata; not a migration guide.
FIX 5.0 SP2 FIX Latest · EP309
Values only in FIX Latest · EP309 15
19Reference price not available20Notional value exceeds threshold21Algorithm risk threshold breachedAdditional source detail
A sell-side broker algorithm has detected that a risk limit has been breached which requires further communication with the client. Used in conjunction with Text(58) to convey the details of the specific event.
22Short sell not permitted23Short sell rejected due to security pre-borrow restriction24Short sell rejected due to account pre-borrow restriction25Insufficient credit limitAdditional source detail
In the context of IA FX Reject codes, Trade Request Rejection Category C, order rejected due to credit limit exceeded or not in place.
26Exceeded clip size limit27Exceeded maximum notional order amount28Exceeded DV01/PV01 limit29Exceeded CS01 limit30Last lookAdditional source detail
In the context of IA FX Reject codes, Trade Request Rejection Category A-1, order rejected due to a "last look".
31Last look latencyAdditional source detail
In the context of IA FX Reject codes, Trade Request Rejection Category A-2, order rejected due to "last look latency", therefore price or liquidity is unavailable.
32Unavailable price or liquidityAdditional source detail
In the context of IA FX Reject codes, Trade Request Rejection Category B, the order was not subjected to last look but rejected due to pricing or liquidity being no longer available for execution.
33Invalid or missing entitlementsAdditional source detail
In the context of IA FX Reject codes, Trade Request Rejection Category D, order rejected due to static/reference data error where counterparty is not permissioned or entitled.
Value text or deprecation changed 4
| Value | FIX 5.0 SP2 | FIX Latest · EP309 |
|---|---|---|
1 | Unknown symbol | Unknown symbolAdditional source detailIn the context of IA FX Reject codes, Trade Request Rejection Category F, order rejected due to the product not being supported, e.g. by the specific venue, tenor restrictions on the market participant(s) involved. |
12 | Surveillence Option | Surveillance option |
15 | Unknown account(s) | Unknown account(s)Additional source detailIn the context of IA FX Reject codes, Trade Request Rejection Category D, order rejected due to static data when the account/fund is not setup or unknown. |
99 | Other | OtherAdditional source detailIn the context of IA FX Reject codes, Trade Request Rejection Category E, order rejected due to other exceptions. Further detail may be provided in RejectText(1328) or Text(58), with preference for RejectText(1328) if field is present in the message. |
Values 34
| Value | Meaning |
|---|---|
0 | Broker / Exchange option |
1 | Unknown symbol Additional detail from the official sourceIn the context of IA FX Reject codes, Trade Request Rejection Category F, order rejected due to the product not being supported, e.g. by the specific venue, tenor restrictions on the market participant(s) involved. |
2 | Exchange closed |
3 | Order exceeds limit |
4 | Too late to enter |
5 | Unknown order |
6 | Duplicate Order (e.g. dupe ClOrdID) |
7 | Duplicate of a verbally communicated order |
8 | Stale order |
9 | Trade along required |
10 | Invalid Investor ID |
11 | Unsupported order characteristic |
12 | Surveillance option |
13 | Incorrect quantity |
14 | Incorrect allocated quantity |
15 | Unknown account(s) Additional detail from the official sourceIn the context of IA FX Reject codes, Trade Request Rejection Category D, order rejected due to static data when the account/fund is not setup or unknown. |
16 | Price exceeds current price band |
18 | Invalid price increment |
19 | Reference price not available |
20 | Notional value exceeds threshold |
21 | Algorithm risk threshold breached Additional detail from the official sourceA sell-side broker algorithm has detected that a risk limit has been breached which requires further communication with the client. Used in conjunction with Text(58) to convey the details of the specific event. |
22 | Short sell not permitted |
23 | Short sell rejected due to security pre-borrow restriction |
24 | Short sell rejected due to account pre-borrow restriction |
25 | Insufficient credit limit Additional detail from the official sourceIn the context of IA FX Reject codes, Trade Request Rejection Category C, order rejected due to credit limit exceeded or not in place. |
26 | Exceeded clip size limit |
27 | Exceeded maximum notional order amount |
28 | Exceeded DV01/PV01 limit |
29 | Exceeded CS01 limit |
30 | Last look Additional detail from the official sourceIn the context of IA FX Reject codes, Trade Request Rejection Category A-1, order rejected due to a "last look". |
31 | Last look latency Additional detail from the official sourceIn the context of IA FX Reject codes, Trade Request Rejection Category A-2, order rejected due to "last look latency", therefore price or liquidity is unavailable. |
32 | Unavailable price or liquidity Additional detail from the official sourceIn the context of IA FX Reject codes, Trade Request Rejection Category B, the order was not subjected to last look but rejected due to pricing or liquidity being no longer available for execution. |
33 | Invalid or missing entitlements Additional detail from the official sourceIn the context of IA FX Reject codes, Trade Request Rejection Category D, order rejected due to static/reference data error where counterparty is not permissioned or entitled. |
99 | Other Additional detail from the official sourceIn the context of IA FX Reject codes, Trade Request Rejection Category E, order rejected due to other exceptions. Further detail may be provided in RejectText(1328) or Text(58), with preference for RejectText(1328) if field is present in the message. |
About the int data type
Sequence of digits without commas or decimals and optional sign character (ASCII characters "-" and "0" - "9" ). The sign character utilizes one byte (i.e. positive int is "99999" while negative int is "-99999"). Note that int values may contain leading zeros (e.g. "00023" = "23").
Used in messages 3
Includes nested components and repeating groups. Open a location to see its surrounding requirements.
35=8ExecutionReportMessage body35=NListStatusOrdListStatGrp35=DKMassOrderAckOrderEntryAckGrp