ClearingAccount (FIX tag 440)

StringFIX 4.2

ClearingAccount (tag 440) is a String field defined in FIX 4.2. It appears in 4 message types, always optionally.

At a glance

Tag: 440
Name: ClearingAccount
Datatype: String
Dialects: FIX 4.2
Messages: 4

What the specification says

Supplemental accounting information forwarded to clearing house/firm.

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

A real message using tag 440

OrderSingle · FIX 4.2

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.2
9	BodyLength	139
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
21	HandlInst	1	Automated execution order, private, no Broker intervention
55	Symbol	EUR/USD
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
440	ClearingAccount	EXAMPLE
10	CheckSum	091

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.2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 440 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
ExecutionReport	8	Optional	directly on the message body
OrderCancelReplaceRequest	G	Optional	directly on the message body
OrderList	E	Optional	directly on the message body
OrderSingle	D	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 440 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix42";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[440];field?.name;   // "ClearingAccount"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-fix42

Try the decoder Source on GitHub