LastParPx (FIX tag 669)

PriceFIX 4.4

LastParPx (tag 669) is a Price field defined in FIX 4.4. It appears in 4 message types, always optionally.

At a glance

Tag
669
Name
LastParPx
Datatype
Price (float)
Dialects
FIX 4.4
Messages
4

What the specification says

Last price expressed in percent-of-par. Conditionally required for Fixed Income trades when LastPx (3) is expressed in Yield, Spread, Discount or any other type. Usage: Execution Report and Allocation Report repeating executions block (from sellside).

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

A real message using tag 669

ExecutionReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength145
35MsgType8Execution Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
17ExecIDEXEC-88117
150ExecType0New
39OrdStatus0New
54Side1Buy
669LastParPx1.09210
151LeavesQty0
14CumQty1000000
6AvgPx1.09215
10CheckSum090
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 669 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.

MessageMsgTypeRequirednessWhere in the message
AllocationInstructionJConditionalinside the ExecAllocGrp component
AllocationReportASConditionalinside the ExecAllocGrp component
ExecutionReport8Conditionaldirectly on the message body
TradeCaptureReportAEConditionaldirectly on the message body

Wire format

A decimal price. Precision is a venue convention, not a protocol rule, so compare the raw string when exactness matters. @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 669 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[669];field?.name;   // "LastParPx"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

Other Price fields

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