Boar Team
GitHub

NewOrderSingle (MsgType D)

applicationFIX 4.4FIX 4.2FIX 5.0 SP2

NewOrderSingle is the FIX message with MsgType D, defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It is an application-level message: it carries a business event rather than managing the session. Its body has 78 top-level members once the standard header and trailer are counted. Earlier dialects call it OrderSingle; the MsgType value is unchanged.

MsgType is case-sensitive
D is NewOrderSingle, but d is a different message entirely — SecurityDefinition. Forty-six FIX message types differ from another only by letter case.
Also known as OrderSingle
FIX 4.2 calls MsgType D OrderSingle. Same value on the wire, different name in the spec.

A real NewOrderSingle

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength111
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum240
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.

Message body — FIX 4.4

Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.

Message body — FIX 4.2

Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.

Message body — FIX 5.0 SP2

Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.

What changed between the dialects

Present in FIX 4.2 only (34)

tag 109, tag 76, group 78, group 386, tag 55, tag 65, tag 48, tag 22, tag 167, tag 200, tag 205, tag 201, tag 202, tag 206, tag 231, tag 223, tag 207, tag 106, tag 348, tag 349, tag 107, tag 350, tag 351, tag 38, tag 152, tag 12, tag 13, tag 47, tag 204, tag 211, tag 388, tag 389, tag 439, tag 440

Present in FIX 5.0 SP2 only (16)

tag 1089, tag 1090, DisplayInstruction, tag 1133, tag 1092, TriggeringInstruction, tag 1091, StrategyParametersGrp, tag 1028, tag 1029, tag 1030, tag 1031, tag 1032, TrdRegTimestamps, tag 1080, tag 1081

Handle NewOrderSingle 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);​if (message.msgType === "D") {  message.name;            // "NewOrderSingle"  // fields are keyed by tag; repeating groups live on message.groups}​// Problems come back as data, never as exceptions:issues;                    // FixIssue[]fix.validate(message);     // dictionary-level problems

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 decoderSource on GitHub