Account (FIX tag 1)

StringFIX 4.4FIX 4.2

Account (tag 1) is a String field defined in FIX 4.4 and FIX 4.2. 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 and FIX 4.2
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.

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

A real message using tag 1

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	124
35	MsgType	D	Order – Single
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
1	Account	ACCT-11223
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	164

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.

Message	MsgType	FIX 4.4	FIX 4.2	Where in the message
AssignmentReport	AW	Optional	—	directly on the message body
BidRequest	k	Optional	Optional	inside the BidCompReqGrp component
CollateralAssignment	AY	Optional	—	directly on the message body
CollateralInquiry	BB	Optional	—	directly on the message body
CollateralInquiryAck	BG	Optional	—	directly on the message body
CollateralReport	BA	Optional	—	directly on the message body
CollateralRequest	AX	Optional	—	directly on the message body
CollateralResponse	AZ	Optional	—	directly on the message body
CrossOrderCancelReplaceRequest	t	Optional	—	inside the SideCrossOrdModGrp component
ExecutionReport	8	Optional	Optional	directly on the message body
MassQuote	i	Optional	—	directly on the message body
MassQuoteAcknowledgement	b	Optional	—	directly on the message body
MultilegOrderCancelReplace	AC	Optional	—	directly on the message body
NewOrderCross	s	Optional	—	inside the SideCrossOrdModGrp component
NewOrderList	E	Optional	Optional	inside the ListOrdGrp component
NewOrderMultileg	AB	Optional	—	directly on the message body
NewOrderSingle	D	Optional	Optional	directly on the message body
OrderCancelReject	9	Optional	Optional	directly on the message body
OrderCancelReplaceRequest	G	Optional	Optional	directly on the message body
OrderCancelRequest	F	Optional	Optional	directly on the message body
OrderMassStatusRequest	AF	Optional	—	directly on the message body
OrderStatusRequest	H	Optional	Optional	directly on the message body
PositionMaintenanceReport	AM	Required	—	directly on the message body
PositionMaintenanceRequest	AL	Required	—	directly on the message body
PositionReport	AP	Required	—	directly on the message body
Quote	S	Optional	—	directly on the message body
QuoteCancel	Z	Optional	—	directly on the message body
QuoteRequest	R	Optional	—	inside the QuotReqGrp component
QuoteRequestReject	AG	Optional	—	inside the QuotReqRjctGrp component
QuoteResponse	AJ	Optional	—	directly on the message body
QuoteStatusReport	AI	Optional	—	directly on the message body
QuoteStatusRequest	a	Optional	—	directly on the message body
RegistrationInstructions	o	Optional	—	directly on the message body
RegistrationInstructionsResponse	p	Optional	—	directly on the message body
RequestForPositions	AN	Required	—	directly on the message body
RequestForPositionsAck	AO	Required	—	directly on the message body
TradeCaptureReport	AE	Optional	—	inside the TrdCapRptSideGrp component
TradeCaptureReportAck	AR	Optional	—	directly 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

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

Try the decoder Source on GitHub