MDEntryForwardPoints (FIX tag 1027)

PriceOffsetFIX 5.0 SP2

MDEntryForwardPoints (tag 1027) is a PriceOffset field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally.

At a glance

Tag: 1027
Name: MDEntryForwardPoints
Datatype: PriceOffset (float)
Dialects: FIX 5.0 SP2
Messages: 2

What the specification says

Used for an F/X entry. The forward points to be added to or subtracted from the spot rate to get the "all-in" rate in MDEntryPx. Expressed in decimal form. For example, 61.99 points is expressed and sent as 0.006199

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

A real message using tag 1027

MarketDataSnapshotFullRefresh · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	107
35	MsgType	W	MarketDataSnapshotFullRefresh
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
268	NoMDEntries2 entries	2	repeating group
269	MDEntryType	0	Bid
1027	MDEntryForwardPoints	0.00010
269	MDEntryType	0	Bid
1027	MDEntryForwardPoints	0.00010
10	CheckSum	046

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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 1027 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
MarketDataIncrementalRefresh	X	Optional	inside the MDIncGrp component
MarketDataSnapshotFullRefresh	W	Optional	inside the MDFullGrp component

Wire format

A signed decimal price delta. Negative values are legal and meaningful. @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 1027 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1027];field?.name;   // "MDEntryForwardPoints"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

Other PriceOffset 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-fix50sp2

Try the decoder Source on GitHub