Account (FIX tag 1)

StringFIX 4.4FIX 4.2FIX 5.0 SP2

Account (tag 1) is a String field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 38 message types and is required in 5 of them.

At a glance

Tag
1
Name
Account
Datatype
String
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
38

What the specification says

FIX 4.4

Account mnemonic as agreed between buy and sell sides, e.g. broker and institution or investor/intermediary and fund manager.

FIX 4.2

Account mnemonic as agreed between broker and institution.

FIX 5.0 SP2

Account mnemonic as agreed between buy and sell sides, e.g. broker and institution or investor/intermediary and fund manager.

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

A real message using tag 1

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength124
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
1AccountACCT-11223
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum164
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 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 1 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.

MessageMsgTypeFIX 4.4FIX 4.2FIX 5.0 SP2Where in the message
AssignmentReportAWOptionalOptionaldirectly on the message body
BidRequestkOptionalOptionalOptionalinside the BidCompReqGrp component
CollateralAssignmentAYOptionalOptionaldirectly on the message body
CollateralInquiryBBOptionalOptionaldirectly on the message body
CollateralInquiryAckBGOptionalOptionaldirectly on the message body
CollateralReportBAOptionalOptionaldirectly on the message body
CollateralRequestAXOptionalOptionaldirectly on the message body
CollateralResponseAZOptionalOptionaldirectly on the message body
CrossOrderCancelReplaceRequesttOptionalOptionalinside the SideCrossOrdModGrp component
ExecutionReport8OptionalOptionalOptionaldirectly on the message body
MassQuoteiOptionalOptionaldirectly on the message body
MassQuoteAcknowledgementbOptionalOptionaldirectly on the message body
MultilegOrderCancelReplaceACOptionalOptionaldirectly on the message body
NewOrderCrosssOptionalOptionalinside the SideCrossOrdModGrp component
NewOrderListEOptionalOptionalOptionalinside the ListOrdGrp component
NewOrderMultilegABOptionalOptionaldirectly on the message body
NewOrderSingleDOptionalOptionalOptionaldirectly on the message body
OrderCancelReject9OptionalOptionalOptionaldirectly on the message body
OrderCancelReplaceRequestGOptionalOptionalOptionaldirectly on the message body
OrderCancelRequestFOptionalOptionalOptionaldirectly on the message body
OrderMassStatusRequestAFOptionalOptionaldirectly on the message body
OrderStatusRequestHOptionalOptionalOptionaldirectly on the message body
PositionMaintenanceReportAMRequiredOptionaldirectly on the message body
PositionMaintenanceRequestALRequiredOptionaldirectly on the message body
PositionReportAPRequiredOptionaldirectly on the message body
QuoteSOptionalOptionaldirectly on the message body
QuoteCancelZOptionalOptionaldirectly on the message body
QuoteRequestROptionalOptionalinside the QuotReqGrp component
QuoteRequestRejectAGOptionalOptionalinside the QuotReqRjctGrp component
QuoteResponseAJOptionalOptionaldirectly on the message body
QuoteStatusReportAIOptionalOptionaldirectly on the message body
QuoteStatusRequestaOptionalOptionaldirectly on the message body
RegistrationInstructionsoOptionalOptionaldirectly on the message body
RegistrationInstructionsResponsepOptionalOptionaldirectly on the message body
RequestForPositionsANRequiredOptionaldirectly on the message body
RequestForPositionsAckAORequiredOptionaldirectly on the message body
TradeCaptureReportAEOptionalOptionalinside the TrdCapRptSideGrp component
TradeCaptureReportAckAROptionalOptionaldirectly 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 1 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1];field?.name;   // "Account"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-fix44