DeliveryForm (FIX tag 668)

intFIX 4.4

DeliveryForm (tag 668) is an int field defined in FIX 4.4. It appears in 11 message types, always optionally. It is an enumerated field with 2 defined values.

At a glance

Tag: 668
Name: DeliveryForm
Datatype: int
Dialects: FIX 4.4
Messages: 11
Valid values: 2

What the specification says

Identifies the form of delivery

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

A real message using tag 668

AllocationInstruction · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	135
35	MsgType	J	Allocation Instruction
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
70	AllocID	EXAMPLE
71	AllocTransType	0	New
626	AllocType	1	Calculated (includes MiscFees and NetMoney)
857	AllocNoOrdersType	0	Not specified
54	Side	1	Buy
668	DeliveryForm	1	BookEntry
53	Quantity	1000000
6	AvgPx	1.09215
75	TradeDate	20240101
10	CheckSum	136

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.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

Value	Meaning	Symbolic name
1	BookEntry	BOOKENTRY
2	Bearer	BEARER

Where tag 668 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	Requiredness	Where in the message
AllocationInstruction	J	Optional	inside the InstrumentExtension component
AllocationReport	AS	Optional	inside the InstrumentExtension component
Confirmation	AK	Optional	inside the InstrumentExtension component
DerivativeSecurityList	AA	Optional	inside RelSymDerivSecGrp › InstrumentExtension
SecurityDefinition	d	Optional	inside the InstrumentExtension component
SecurityDefinitionRequest	c	Optional	inside the InstrumentExtension component
SecurityList	y	Optional	inside SecListGrp › InstrumentExtension
SecurityListRequest	x	Optional	inside the InstrumentExtension component
SecurityStatus	f	Optional	inside the InstrumentExtension component
SecurityStatusRequest	e	Optional	inside the InstrumentExtension component
TradeCaptureReportRequest	AD	Optional	inside the InstrumentExtension component

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 668 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 deliveryForm = message.fields[668]?.raw;// e.g. "1" — BookEntry// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(668)  ?.enumValues?.find((e) => e.value === deliveryForm)  ?.description;

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