PosMaintRptID (FIX tag 721)

StringFIX 4.4FIX 5.0 SP2

PosMaintRptID (tag 721) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 3 message types and is required in 3 of them.

At a glance

Tag: 721
Name: PosMaintRptID
Datatype: String
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 3

What the specification says

Unique identifier for this position report

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

A real message using tag 721

RequestForPositionsAck · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	107
35	MsgType	AO	Request For Positions Ack
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
721	PosMaintRptID	EXAMPLE
728	PosReqResult	0	Valid Request
729	PosReqStatus	0	Completed
1	Account	ACCT-11223
581	AccountType	1	Account is carried on customer Side of Books
10	CheckSum	253

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.

Where tag 721 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 5.0 SP2	Where in the message
AdjustedPositionReport	BL	—	Required	directly on the message body
PositionMaintenanceReport	AM	Required	Required	directly on the message body
PositionReport	AP	Required	Required	directly on the message body
RequestForPositionsAck	AO	Required	Required	directly on the message body

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 721 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 field = message.fields[721];field?.name;   // "PosMaintRptID"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-fix44

Try the decoder Source on GitHub