Skip to content
FIXtags

FIX TAG 751

TradeReportRejectReason

intAdded FIX.4.4

Definition

Reason Trade Capture Request was rejected. 100+ Reserved and available for bi-laterally agreed upon user-defined values

Compare versions

Differences between the selected source snapshots, including wording and errata; not a migration guide.

FIX 4.4 FIX 5.0 SP2

Definition text changed

FIX 4.4

Reason Trade Capture Request was rejected. 4000+ Reserved and available for bi-laterally agreed upon user-defined values

FIX 5.0 SP2

Reason Trade Capture Request was rejected. 100+ Reserved and available for bi-laterally agreed upon user-defined values

Value text or deprecation changed 2

ValueFIX 4.4FIX 5.0 SP2
0Successful (Default)Successful (default)
1Invalid party informationInvalid party onformation

Values 6

ValueMeaning
0

Successful (default)

1

Invalid party onformation

2

Unknown instrument

3

Unauthorized to report trades

4

Invalid trade type

99

Other

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"). Examples: 723 in field 21 would be mapped int as |21=723|. -723 in field 12 would be mapped int as |12=-723| The following data types are based on int.

Used in messages 1

Includes nested components and repeating groups. Open a location to see its surrounding requirements.