BookingUnit (FIX tag 590)

charFIX 4.4

BookingUnit (tag 590) is a char field defined in FIX 4.4. It appears in 8 message types, always optionally. It is an enumerated field with 3 defined values.

At a glance

Tag: 590
Name: BookingUnit
Datatype: char
Dialects: FIX 4.4
Messages: 8
Valid values: 3

What the specification says

Indicates what constitutes a bookable unit.

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

A real message using tag 590

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	117
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
590	BookingUnit	0	Each partial execution is a bookable unit
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	002

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
0	Each partial execution is a bookable unit	EACH_PARTIAL_EXECUTION_IS_A_BOOKABLE_UNIT
1	Aggregate partial executions on this order, and book one trade per order	AGGREGATE_PARTIAL_EXECUTIONS_ON_THIS_ORDER_AND_BOOK_ONE_TRADE_PER_ORDER
2	Aggregate executions for this symbol, side, and settlement date	AGGREGATE_EXECUTIONS_FOR_THIS_SYMBOL_SIDE_AND_SETTLEMENT_DATE

Where tag 590 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
CrossOrderCancelReplaceRequest	t	Optional	inside the SideCrossOrdModGrp component
ExecutionReport	8	Optional	directly on the message body
MultilegOrderCancelReplace	AC	Optional	directly on the message body
NewOrderCross	s	Optional	inside the SideCrossOrdModGrp component
NewOrderList	E	Optional	inside the ListOrdGrp component
NewOrderMultileg	AB	Optional	directly on the message body
NewOrderSingle	D	Optional	directly on the message body
OrderCancelReplaceRequest	G	Optional	directly on the message body

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 590 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 bookingUnit = message.fields[590]?.raw;// e.g. "0" — Each partial execution is a bookable unit// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(590)  ?.enumValues?.find((e) => e.value === bookingUnit)  ?.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