SettlInstReqRejCode (FIX tag 792)

intFIX 4.4

SettlInstReqRejCode (tag 792) is an int field defined in FIX 4.4. It appears in 1 message type, always optionally. It is an enumerated field with 4 defined values.

At a glance

Tag: 792
Name: SettlInstReqRejCode
Datatype: int
Dialects: FIX 4.4
Messages: 1
Valid values: 4

What the specification says

Identifies reason for rejection (of a settlement instruction request message)

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

A real message using tag 792

SettlementInstructions · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	112
35	MsgType	T	Settlement Instructions
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
777	SettlInstMsgID	EXAMPLE
160	SettlInstMode	1	Standing Instructions Provided
792	SettlInstReqRejCode	0	unable to process request (e.g. database unavailable)
60	TransactTime	20240101-12:00:00.000
10	CheckSum	178

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	unable to process request (e.g. database unavailable)	UNABLE_TO_PROCESS_REQUEST
1	unknown account	UNKNOWN_ACCOUNT
2	no matching settlement instructions found	NO_MATCHING_SETTLEMENT_INSTRUCTIONS_FOUND
99	other	OTHER

Where tag 792 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
SettlementInstructions	T	Conditional	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 792 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 settlInstReqRejCode = message.fields[792]?.raw;// e.g. "0" — unable to process request (e.g. database unavailable)// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(792)  ?.enumValues?.find((e) => e.value === settlInstReqRejCode)  ?.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