FIX Protocol Tag 20: ExecTransType

Transaction type of an Execution Report: new, cancel, correct or status. It exists in FIX 4.0 to 4.2; from FIX 4.3, ExecType (150) carries trade cancel and trade correct events instead.

Tag number: 20
Data type: CHAR
FIX versions: FIX 4.0 to 4.2
Used in: 1 message type

Practical notes on ExecTransType

ExecTransType said whether an Execution Report was new, a cancel, a correction or a status report. It exists only in FIX 4.0 to 4.2.

Values: 0 New, 1 Cancel (a bust of an earlier report), 2 Correct, 3 Status.
In FIX 4.2 it is required on every Execution Report.

Common mistakes

Sending it on a FIX 4.4 session, where strict engines reject it as a tag not defined for the message.

Changes between FIX versions

Removed in FIX 4.3. Its meanings moved into ExecType (150): Trade Cancel (H), Trade Correct (G) and Order Status (I).

Tag 20 in each FIX version

Values and message usage as defined in a specific version.

Data type

CHAR: A single character.

Valid values

4 enumerated values across all FIX versions.

Value	Meaning
0	New
1	Cancel
2	Correct
3	Status

Example

20=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 20

Execution Report 35=8

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.