BusinessRejectReason (FIX tag 380)

intFIX 4.4FIX 4.2

BusinessRejectReason (tag 380) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 1 message type and is required in 1 of them. It is an enumerated field with 8 defined values.

At a glance

Tag: 380
Name: BusinessRejectReason
Datatype: int
Dialects: FIX 4.4 and FIX 4.2
Messages: 1
Valid values: 8

What the specification says

FIX 4.4

Code to identify reason for a Business Message Reject message

FIX 4.2

Code to identify reason for a Business Message Reject message.

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

A real message using tag 380

BusinessMessageReject · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	81
35	MsgType	j	Business Message Reject
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
372	RefMsgType	EXAMPLE
380	BusinessRejectReason	0	Other
10	CheckSum	215

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	Dialects
0	Other	OTHER / Other	FIX 4.4, FIX 4.2
1	Unknown ID	UNKOWN_ID / UnknownID	FIX 4.4, FIX 4.2
2	Unknown Security	UNKNOWN_SECURITY / UnknownSecurity	FIX 4.4, FIX 4.2
3	Unsupported Message Type	UNSUPPORTED_MESSAGE_TYPE / UnsupportedMessageType	FIX 4.4, FIX 4.2
4	Application not available	APPLICATION_NOT_AVAILABLE / ApplicationNotAvailable	FIX 4.4, FIX 4.2
5	Conditionally Required Field Missing	CONDITIONALLY_REQUIRED_FIELD_MISSING / ConditionallyRequiredFieldMissing	FIX 4.4, FIX 4.2
6	Not authorized	NOT_AUTHORIZED	FIX 4.4
7	DeliverTo firm not available at this time	DELIVERTO_FIRM_NOT_AVAILABLE_AT_THIS_TIME	FIX 4.4

Where tag 380 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	FIX 4.4	FIX 4.2	Where in the message
BusinessMessageReject	j	Required	Required	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 380 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 businessRejectReason = message.fields[380]?.raw;// e.g. "0" — Other// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(380)  ?.enumValues?.find((e) => e.value === businessRejectReason)  ?.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