ZagTrader

FIX Protocol Tag 829: TrdSubType

TrdSubType is an integer field used in 11 FIX message types, including Execution Report (35=8), Trade Capture Report (35=AE) and Market Data Snapshot Full Refresh (35=W). It is defined in FIX 4.4 to 5.0 SP2 and has 52 enumerated values.

Tag number
829
Data type
INT
FIX versions
FIX 4.4 to 5.0 SP2
Used in
11 message types

Tag 829 in each FIX version

Values and message usage as defined in a specific version.

Data type

INT: A whole number without a decimal point. It may be negative.

Valid values

52 enumerated values across all FIX versions.

ValueMeaningFIX versions
0CMTAAll
1Internal transfer or adjustmentAll
2External transfer or transfer of accountAll
3Reject for submitting sideAll
4Advisory for contra sideAll
5Offset due to an allocationAll
6Onset due to an allocationAll
7Differential spreadAll
8Implied spread leg executed against an outrightAll
9Transaction from exerciseAll
10Transaction from assignmentAll
11ACATSAll
14AiAll
15BAll
16KAll
17LcAll
18MAll
19NAll
20NmAll
21NrAll
22PAll
23PaAll
24PcAll
25PnAll
26RAll
27RoAll
28RtAll
29SwAll
30TAll
31WnAll
32WtAll
33Off hours trade5.0 SP1, 5.0 SP2
34On hours trade5.0 SP1, 5.0 SP2
35OTC quote5.0 SP1, 5.0 SP2
36Converted swap5.0 SP1, 5.0 SP2
37Crossed trade5.0 SP1, 5.0 SP2
38Interim protected trade5.0 SP1, 5.0 SP2
39Large in scale5.0 SP1, 5.0 SP2
40Wash trade5.0 SP2
41Trade at settlement5.0 SP2
42Auction trade5.0 SP2
43Trade at marker5.0 SP2
44Credit default5.0 SP2
45Credit restructuring5.0 SP2
46Merger5.0 SP2
47Spin off5.0 SP2
48Multilateral compression5.0 SP2
50Balancing5.0 SP2
51Basis trade index close5.0 SP2
52Trade at cash open5.0 SP2
53Trd submit venue clr settl5.0 SP2
54Bilateral compression5.0 SP2

Example

829=0

Illustrative value. In a message, fields are separated by the SOH character (0x01), often shown as | or ^ in logs.

Decode a message with this tag

Message types that use tag 829

Covers every version from FIX 4.0 to 5.0 SP2, including fields reached through components and repeating groups. The version pages above show whether the tag is required in each message.

Field and message data comes from the QuickFIX data dictionaries for FIX 4.0 to 5.0 SP2 and FIXT 1.1, used under the QuickFIX Software License. This product includes software developed by quickfixengine.org (http://www.quickfixengine.org/). Enumerated value names are converted to plain text for reading.