CashOutstanding (FIX tag 901)

AmtFIX 4.4

CashOutstanding (tag 901) is an Amt field defined in FIX 4.4. It appears in 5 message types, always optionally.

At a glance

Tag: 901
Name: CashOutstanding
Datatype: Amt (float)
Dialects: FIX 4.4
Messages: 5

What the specification says

Starting consideration less repayments

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

A real message using tag 901

CollateralResponse · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	139
35	MsgType	AZ	Collateral Response
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
904	CollRespID	EXAMPLE
902	CollAsgnID	EXAMPLE
895	CollAsgnReason	0	Initial
905	CollAsgnRespType	0	Received
60	TransactTime	20240101-12:00:00.000
901	CashOutstanding	125000.00
10	CheckSum	119

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 901 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
CollateralAssignment	AY	Optional	directly on the message body
CollateralInquiry	BB	Optional	directly on the message body
CollateralReport	BA	Optional	directly on the message body
CollateralRequest	AX	Optional	directly on the message body
CollateralResponse	AZ	Optional	directly on the message body

Wire format

A decimal monetary amount, in the currency named by the message's currency field. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.

Read tag 901 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 field = message.fields[901];field?.name;   // "CashOutstanding"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

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