Friday, 20 November 2026 · Free. No paywall. No subscription.
Search The MidPoint News

Search articles, videos and sections. Press / to open, Esc to close.

FIX 4.4Field

BusinessRejectReason <380>

Tag
380
Type
int · code set BusinessRejectReasonCodeSet
FIXML name
BizRejRsn
Pedigree
Added FIX 4.2
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

This page shows BusinessRejectReason <380> as defined in FIX 4.4. For the current standard, see tag 380 BusinessRejectReason in FIX Latest.

BusinessRejectReason <380> in plain English

Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).

BusinessRejectReason gives the reason code for a BusinessMessageReject, such as an unknown ID, an unknown security or an unsupported message type.

Common values

ValueNameMeaning (from the Orchestra file)
380=0OtherOther
380=1UnknownIDUnknown IDUnknown ID
380=2UnknownSecurityUnknown SecurityUnknown Security
380=3UnsupportedMessageTypeUnsupported Message TypeUnsupported Message Type
380=4ApplicationNotAvailableApplication not availableApplication not available
380=5ConditionallyRequiredFieldMissingConditionally Required Field MissingConditionally Required Field Missing
380=6NotAuthorizedNot authorizedNot authorized

A selection. The full list of values is in the table further down.

Where it is used

BusinessMessageReject (35=j) . In all, 1 message in FIX 4.4 can carry it. Full list.

Example message

8=FIX.4.4|9=111|35=j|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|45=12|372=D|379=ORD-1001|380=2|58=Unknown security|10=019

Illustrative example, not real orders or market data. A BusinessMessageReject (35=j) in FIX 4.4, shown with BeginString FIX.4.4. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.4 dictionary, but it is not a complete specification of the message.

Description (from the Orchestra file)

Code to identify reason for a Business Message Reject message

Values (8)

ValueNameDescriptionPedigreeIn LatestIn 4.2
0 Other Other Added FIX 4.2 ✓✓
1 UnknownIDUnknown ID Unknown ID Added FIX 4.2 ✓✓
2 UnknownSecurityUnknown Security Unknown Security Added FIX 4.2 ✓✓
3 UnsupportedMessageTypeUnsupported Message Type Unsupported Message Type Added FIX 4.2 ✓✓
4 ApplicationNotAvailableApplication not available Application not available Added FIX 4.2 ✓✓
5 ConditionallyRequiredFieldMissingConditionally Required Field Missing Conditionally Required Field Missing Added FIX 4.2 ✓✓
6 NotAuthorizedNot authorized Not authorized Added FIX 4.3 ✓–
7 DeliverToFirmNotAvailableAtThisTimeDeliverTo firm not available at this time DeliverTo firm not available at this time Added FIX 4.3 ✓–

Used in

Messages (1)

MessageMsgTypePresence
BusinessMessageRejectjRequired