MatchIncrement (FIX tag 1089)

QtyFIX 5.0 SP2

MatchIncrement (tag 1089) is a Qty field defined in FIX 5.0 SP2. It appears in 8 message types, always optionally.

At a glance

Tag: 1089
Name: MatchIncrement
Datatype: Qty (float)
Dialects: FIX 5.0 SP2
Messages: 8

What the specification says

Allows orders to specify a minimum quantity that applies to every execution (one execution could be for multiple counter-orders). The order may still fill against smaller orders, but the cumulative quantity of the execution must be in multiples of the MatchIncrement.

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

A real message using tag 1089

NewOrderSingle · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	124
35	MsgType	D	NewOrderSingle
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
1089	MatchIncrement	1000000
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	163

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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 1089 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
CrossOrderCancelReplaceRequest	t	Optional	directly on the message body
ExecutionReport	8	Optional	directly on the message body
MultilegOrderCancelReplace	AC	Optional	directly on the message body
NewOrderCross	s	Optional	directly on the message body
NewOrderList	E	Optional	inside the ListOrdGrp component
NewOrderMultileg	AB	Optional	directly on the message body
NewOrderSingle	D	Optional	directly on the message body
OrderCancelReplaceRequest	G	Optional	directly on the message body

Wire format

A decimal quantity. Fractional quantities are legal, which is why this is a float family rather than an integer. @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 1089 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1089];field?.name;   // "MatchIncrement"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-fix50sp2

Try the decoder Source on GitHub