ExecPriceAdjustment (FIX tag 485)
ExecPriceAdjustment (tag 485) is a float field defined in FIX 4.4. It appears in 1 message type, always optionally.
At a glance
- Tag
- 485
- Name
- ExecPriceAdjustment
- Datatype
- float
- Dialects
- FIX 4.4
- Messages
- 1
What the specification says
For CIV the amount or percentage by which the fund unit/share price was adjusted, as indicated by ExecPriceType (484)
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 485
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 141 | |
| 35 | MsgType | 8 | Execution Report |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 37 | OrderID | ORD-10042 | |
| 17 | ExecID | EXEC-88117 | |
| 150 | ExecType | 0 | New |
| 39 | OrdStatus | 0 | New |
| 54 | Side | 1 | Buy |
| 151 | LeavesQty | 0 | |
| 14 | CumQty | 1000000 | |
| 6 | AvgPx | 1.09215 | |
| 485 | ExecPriceAdjustment | 1.0 | |
| 10 | CheckSum | 134 |
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.
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 485 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 |
|---|---|---|---|
| ExecutionReport | 8 | Optional | directly on the message body |
Wire format
A decimal number. The wire form keeps its trailing zeros, which is why decoders expose the raw string alongside the parsed number. @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 485 in TypeScript
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[485];field?.name; // "ExecPriceAdjustment"field?.raw; // the verbatim wire stringfield?.value; // coerced to a numberOther float fields
- 469RoundingModulus
- 520ContAmtValue
- 436UnderlyingContractMultiplier
- 389DiscretionOffsetValue
- 614LegContractMultiplier
- 623LegRatioQty
- 656SettlCurrBidFxRate
- 657SettlCurrOfferFxRate
- 253LegFactor
- 246UnderlyingFactor
- 231ContractMultiplier
- 228Factor
- 211PegOffsetValue
- 811PriceDelta
- 155SettlCurrFxRate
- 850TargetStrategyPerformance
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