EncodedIssuer (FIX tag 349)

dataFIX 4.4FIX 4.2FIX 5.0 SP2

EncodedIssuer (tag 349) is a data field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 59 message types, always optionally. It is length-prefixed — tag 348 carries the byte count, so the value may contain the SOH separator without breaking the message.

At a glance

Tag
349
Name
EncodedIssuer
Datatype
data
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
59
Length field
tag 348

What the specification says

FIX 4.4

Encoded (non-ASCII characters) representation of the Issuer field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Issuer field.

FIX 4.2

Encoded (non-ASCII characters) representation of the Issuer field in the encoded format specified via the MessageEncoding field. If used, the ASCII (English) representation should also be specified in the Issuer field.

FIX 5.0 SP2

Encoded (non-ASCII characters) representation of the Issuer field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Issuer field.

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

A real message using tag 349

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength129
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
348EncodedIssuerLen7
349EncodedIssuerEXAMPLE
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum247
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 349 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
AdjustedPositionReportBLOptionalinside InstrmtGrp › Instrument
Advertisement7ConditionalOptionalOptionalinside the Instrument component
AllocationInstructionJConditionalOptionalOptionalinside the Instrument component
AllocationInstructionAlertBMOptionalinside the Instrument component
AllocationReportASConditionalOptionalinside the Instrument component
AssignmentReportAWConditionalOptionalinside the Instrument component
CollateralAssignmentAYConditionalOptionalinside the Instrument component
CollateralInquiryBBConditionalOptionalinside the Instrument component
CollateralInquiryAckBGConditionalOptionalinside the Instrument component
CollateralReportBAConditionalOptionalinside the Instrument component
CollateralRequestAXConditionalOptionalinside the Instrument component
CollateralResponseAZConditionalOptionalinside the Instrument component
ConfirmationAKConditionalOptionalinside the Instrument component
ContraryIntentionReportBOOptionalinside the Instrument component
CrossOrderCancelReplaceRequesttConditionalOptionalinside the Instrument component
CrossOrderCancelRequestuConditionalOptionalinside the Instrument component
DerivativeSecurityListAAConditionalOptionalinside RelSymDerivSecGrp › Instrument
DerivativeSecurityListUpdateReportBROptionalinside RelSymDerivSecUpdGrp › Instrument
DontKnowTradeQConditionalOptionalOptionalinside the Instrument component
EmailCConditionalOptionalOptionalinside InstrmtGrp › Instrument
ExecutionAcknowledgementBNOptionalinside the Instrument component
ExecutionReport8ConditionalOptionalOptionalinside the Instrument component
IOI6ConditionalOptionalOptionalinside the Instrument component
ListStrikePricemConditionalOptionalOptionalinside InstrmtStrkPxGrp › Instrument
MarketDataIncrementalRefreshXConditionalOptionalOptionalinside MDIncGrp › Instrument
MarketDataRequestVConditionalOptionalOptionalinside InstrmtMDReqGrp › Instrument
MarketDataSnapshotFullRefreshWConditionalOptionalOptionalinside the Instrument component
MassQuoteiConditionalOptionalOptionalinside QuotSetGrp › QuotEntryGrp › Instrument
MassQuoteAcknowledgementbConditionalOptionalOptionalinside QuotSetAckGrp › QuotEntryAckGrp › Instrument
MultilegOrderCancelReplaceACConditionalOptionalinside the Instrument component
NewOrderCrosssConditionalOptionalinside the Instrument component
NewOrderListEConditionalOptionalOptionalinside ListOrdGrp › Instrument
NewOrderMultilegABConditionalOptionalinside the Instrument component
NewOrderSingleDConditionalOptionalOptionalinside the Instrument component
NewsBConditionalOptionalOptionalinside InstrmtGrp › Instrument
OrderCancelReplaceRequestGConditionalOptionalOptionalinside the Instrument component
OrderCancelRequestFConditionalOptionalOptionalinside the Instrument component
OrderMassActionReportBZOptionalinside the Instrument component
OrderMassActionRequestCAOptionalinside the Instrument component
OrderMassCancelReportrConditionalOptionalinside the Instrument component
OrderMassCancelRequestqConditionalOptionalinside the Instrument component
OrderMassStatusRequestAFConditionalOptionalinside the Instrument component
OrderStatusRequestHConditionalOptionalOptionalinside the Instrument component
PositionMaintenanceReportAMConditionalOptionalinside the Instrument component
PositionMaintenanceRequestALConditionalOptionalinside the Instrument component
PositionReportAPConditionalOptionalinside the Instrument component
QuoteSConditionalOptionalOptionalinside the Instrument component
QuoteCancelZConditionalOptionalOptionalinside QuotCxlEntriesGrp › Instrument
QuoteRequestRConditionalOptionalOptionalinside QuotReqGrp › Instrument
QuoteRequestRejectAGConditionalOptionalinside QuotReqRjctGrp › Instrument
QuoteResponseAJConditionalOptionalinside the Instrument component
QuoteStatusReportAIConditionalOptionalinside the Instrument component
QuoteStatusRequestaConditionalOptionalOptionalinside the Instrument component
RFQRequestAHConditionalOptionalinside RFQReqGrp › Instrument
RequestForPositionsANConditionalOptionalinside the Instrument component
RequestForPositionsAckAOConditionalOptionalinside the Instrument component
SecurityDefinitiondConditionalOptionalOptionalinside the Instrument component
SecurityDefinitionRequestcConditionalOptionalOptionalinside the Instrument component
SecurityDefinitionUpdateReportBPOptionalinside the Instrument component
SecurityListyConditionalOptionalinside SecListGrp › Instrument
SecurityListRequestxConditionalOptionalinside the Instrument component
SecurityListUpdateReportBKOptionalinside SecLstUpdRelSymGrp › Instrument
SecurityStatusfConditionalOptionalOptionalinside the Instrument component
SecurityStatusRequesteConditionalOptionalOptionalinside the Instrument component
SettlementObligationReportBQOptionalinside SettlObligationInstructions › Instrument
StreamAssignmentReportCDOptionalinside StrmAsgnRptGrp › StrmAsgnRptInstrmtGrp › Instrument
StreamAssignmentRequestCCOptionalinside StrmAsgnReqGrp › StrmAsgnReqInstrmtGrp › Instrument
TradeCaptureReportAEConditionalOptionalinside the Instrument component
TradeCaptureReportAckARConditionalOptionalinside the Instrument component
TradeCaptureReportRequestADConditionalOptionalinside the Instrument component
TradeCaptureReportRequestAckAQConditionalOptionalinside the Instrument component
TradingSessionStatushOptionalinside the Instrument component

Wire format

Raw bytes, length-prefixed by a partner field. The value may legally contain the SOH separator, which is why the length matters. @boarteam/fix reads the partner length field first and takes exactly that many bytes, so an embedded separator does not truncate the value.

Read tag 349 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);// Length-prefixed: tag 348 carries the byte count, so the// value may contain the SOH separator without breaking the message.const length = message.fields[348]?.value;const encodedIssuer = message.fields[349]?.raw;

Other data 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