MatchAlgorithm (FIX tag 1142)

StringFIX 5.0 SP2

MatchAlgorithm (tag 1142) is a String field defined in FIX 5.0 SP2. It appears in 8 message types, always optionally.

At a glance

Tag: 1142
Name: MatchAlgorithm
Datatype: String
Dialects: FIX 5.0 SP2
Messages: 8

What the specification says

The types of algorithm used to match orders in a specific security. Possilbe value types are FIFO, Allocation, Pro-rata, Lead Market Maker, Currency Calender.

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

A real message using tag 1142

TradingSessionList · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	115
35	MsgType	BJ	TradingSessionList
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
386	NoTradingSessions1 entry	1	repeating group
336	TradingSessionID	1	Day
340	TradSesStatus	0	Unknown
1235	NoMatchRules2 entries	2	repeating group
1142	MatchAlgorithm	EXAMPLE
1142	MatchAlgorithm	EXAMPLE
10	CheckSum	005

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 1142 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
DerivativeSecurityList	AA	Optional	inside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › MatchRules
DerivativeSecurityListUpdateReport	BR	Optional	inside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › MatchRules
SecurityDefinition	d	Optional	inside MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › MatchRules
SecurityDefinitionUpdateReport	BP	Optional	inside MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › MatchRules
SecurityList	y	Optional	inside SecListGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › MatchRules
SecurityListUpdateReport	BK	Optional	inside SecLstUpdRelSymGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › MatchRules
TradingSessionList	BJ	Optional	inside TrdSessLstGrp › TradingSessionRules › MatchRules
TradingSessionListUpdateReport	BS	Optional	inside TrdSessLstGrp › TradingSessionRules › MatchRules

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 1142 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[1142];field?.name;   // "MatchAlgorithm"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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