PosAmt (FIX tag 708)

AmtFIX 4.4

PosAmt (tag 708) is an Amt field defined in FIX 4.4. It appears in 4 message types, always optionally.

At a glance

Tag: 708
Name: PosAmt
Datatype: Amt (float)
Dialects: FIX 4.4
Messages: 4

What the specification says

Position amount

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

A real message using tag 708

TradeCaptureReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	217
35	MsgType	AE	Trade Capture Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
571	TradeReportID	EXAMPLE
570	PreviouslyReported	N	not reported to counterparty
32	LastQty	1000000
31	LastPx	1.09210
75	TradeDate	20240101
753	NoPosAmt2 entries	2	repeating group
707	PosAmtType	FMTM	Final Mark-to-Market Amount
708	PosAmt	125000.00
707	PosAmtType	FMTM	Final Mark-to-Market Amount
708	PosAmt	125000.00
60	TransactTime	20240101-12:00:00.000
552	NoSides1 entry	1	repeating group
54	Side	1	Buy
37	OrderID	ORD-10042
10	CheckSum	002

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 708 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
AssignmentReport	AW	Optional	inside the PositionAmountData component
PositionMaintenanceReport	AM	Optional	inside the PositionAmountData component
PositionReport	AP	Optional	inside the PositionAmountData component
TradeCaptureReport	AE	Optional	inside the PositionAmountData component

Wire format

A decimal monetary amount, in the currency named by the message's currency field. @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 708 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[708];field?.name;   // "PosAmt"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-fix44

Try the decoder Source on GitHub