EFPTrackingError (FIX tag 405)
EFPTrackingError (tag 405) is a Percentage field defined in FIX 4.4 and FIX 4.2. It appears in 1 message type, always optionally.
At a glance
- Tag
- 405
- Name
- EFPTrackingError
- Datatype
- Percentage (float)
- Dialects
- FIX 4.4 and FIX 4.2
- Messages
- 1
What the specification says
FIX 4.4
Eg Used in EFP trades 2% (EFP – Exchange for Physical ). Represented as a percentage.
FIX 4.2
Eg Used in EFP trades 12% (EFP – Exchange for Physical ). Represented as a percentage.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 405
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 141 | |
| 35 | MsgType | k | Bid Request |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 391 | ClientBidID | EXAMPLE | |
| 374 | BidRequestTransType | N | New |
| 393 | TotNoRelatedSym | 1 | |
| 394 | BidType | 1 | "Non Disclosed" Style (e.g. US/European) |
| 398 | NoBidDescriptors2 entries | 2 | repeating group |
| 399 | BidDescriptorType | 1 | Sector |
| 405 | EFPTrackingError | 0.05 | |
| 399 | BidDescriptorType | 1 | Sector |
| 405 | EFPTrackingError | 0.05 | |
| 418 | BidTradeType | R | Risk Trade |
| 419 | BasisPxType | 2 | Closing Price at morning session |
| 10 | CheckSum | 239 |
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 405 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 4.2 | Where in the message |
|---|---|---|---|---|
| BidRequest | k | Optional | Optional | inside the BidDescReqGrp component |
Wire format
A decimal rate where 1.0 means 100%, not 1%. @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 405 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[405];field?.name; // "EFPTrackingError"field?.raw; // the verbatim wire stringfield?.value; // coerced to a numberOther Percentage fields
- 403LiquidityPctHigh
- 407OutsideIndexPct
- 402LiquidityPctLow
- 410WtAverageLiquidity
- 413CrossPercent
- 435UnderlyingCouponRate
- 512DistribPercentage
- 516OrderPercent
- 252LegRepurchaseRate
- 245UnderlyingRepurchaseRate
- 236Yield
- 227RepurchaseRate
- 223CouponRate
- 615LegCouponRate
- 632BidYield
- 633MidYield
- 634OfferYield
- 158AccruedInterestRate
- 765AllowableOneSidednessPct
- 849ParticipationRate
- 869PctAtRisk
- 898MarginRatio
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