CustOrderCapacity (FIX tag 582)

intFIX 4.4

CustOrderCapacity (tag 582) is an int field defined in FIX 4.4. It appears in 13 message types, always optionally. It is an enumerated field with 4 defined values.

At a glance

Tag: 582
Name: CustOrderCapacity
Datatype: int
Dialects: FIX 4.4
Messages: 13
Valid values: 4

What the specification says

Capacity of customer placing the order Primarily used by futures exchanges to indicate the CTICode (customer type indicator) as required by the US CFTC (Commodity Futures Trading Commission).

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

A real message using tag 582

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
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
582	CustOrderCapacity	1	Member trading for their own account
10	CheckSum	004

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	Member trading for their own account	MEMBER_TRADING_FOR_THEIR_OWN_ACCOUNT
2	Clearing Firm trading for its proprietary account	CLEARING_FIRM_TRADING_FOR_ITS_PROPRIETARY_ACCOUNT
3	Member trading for another member	MEMBER_TRADING_FOR_ANOTHER_MEMBER
4	All other	ALL_OTHER

Where tag 582 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
Quote	S	Optional	directly on the message body
QuoteResponse	AJ	Optional	directly on the message body
QuoteStatusReport	AI	Optional	directly on the message body
TradeCaptureReport	AE	Optional	inside the TrdCapRptSideGrp component
TradeCaptureReportAck	AR	Optional	directly on the message body

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 582 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 custOrderCapacity = message.fields[582]?.raw;// e.g. "1" — Member trading for their own account// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(582)  ?.enumValues?.find((e) => e.value === custOrderCapacity)  ?.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