FirmTradeID (FIX tag 1041)

StringFIX 5.0 SP2

FirmTradeID (tag 1041) is a String field defined in FIX 5.0 SP2. It appears in 7 message types, always optionally.

At a glance

Tag
1041
Name
FirmTradeID
Datatype
String
Dialects
FIX 5.0 SP2
Messages
7

What the specification says

The ID assigned to a trade by the Firm to track a trade within the Firm system. This ID can be assigned either before or after submission to the exchange or central counterpary

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 1041

TradeCaptureReport · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength110
35MsgTypeAETradeCaptureReport
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
1041FirmTradeIDEXAMPLE
32LastQty1000000
31LastPx1.09210
552NoSides1 entry1repeating group
54Side1Buy
10CheckSum095
Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 1041 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

MessageMsgTypeRequirednessWhere in the message
AllocationInstructionJOptionalinside the ExecAllocGrp component
AllocationInstructionAlertBMOptionalinside the ExecAllocGrp component
AllocationReportASOptionalinside the ExecAllocGrp component
TradeCaptureReportAEOptionaldirectly on the message body
TradeCaptureReportAckAROptionaldirectly on the message body
TradeCaptureReportRequestADOptionaldirectly on the message body
TradeCaptureReportRequestAckAQOptionaldirectly on the message body

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 1041 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1041];field?.name;   // "FirmTradeID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other String fields

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix50sp2