MarginRatio (FIX tag 898)

PercentageFIX 4.4

MarginRatio (tag 898) is a Percentage field defined in FIX 4.4. It appears in 26 message types, always optionally.

At a glance

Tag
898
Name
MarginRatio
Datatype
Percentage (float)
Dialects
FIX 4.4
Messages
26

What the specification says

The fraction of the cash consideration that must be collateralized, expressed as a percent. A MarginRatio of 02% indicates that the value of the collateral (after deducting for "haircut") must exceed the cash consideration by 2%.

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

A real message using tag 898

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength120
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
898MarginRatio0.05
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum154
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 898 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
AllocationInstructionJOptionalinside the FinancingDetails component
AllocationReportASOptionalinside the FinancingDetails component
CollateralAssignmentAYOptionalinside the FinancingDetails component
CollateralInquiryBBOptionalinside the FinancingDetails component
CollateralInquiryAckBGOptionalinside the FinancingDetails component
CollateralReportBAOptionalinside the FinancingDetails component
CollateralRequestAXOptionalinside the FinancingDetails component
CollateralResponseAZOptionalinside the FinancingDetails component
ConfirmationAKOptionalinside the FinancingDetails component
ExecutionReport8Optionalinside the FinancingDetails component
IOI6Optionalinside the FinancingDetails component
NewOrderSingleDOptionalinside the FinancingDetails component
OrderCancelReplaceRequestGOptionalinside the FinancingDetails component
OrderCancelRequestFOptionalinside the FinancingDetails component
OrderStatusRequestHOptionalinside the FinancingDetails component
QuoteSOptionalinside the FinancingDetails component
QuoteCancelZOptionalinside QuotCxlEntriesGrp › FinancingDetails
QuoteRequestROptionalinside QuotReqGrp › FinancingDetails
QuoteRequestRejectAGOptionalinside QuotReqRjctGrp › FinancingDetails
QuoteResponseAJOptionalinside the FinancingDetails component
QuoteStatusReportAIOptionalinside the FinancingDetails component
QuoteStatusRequestaOptionalinside the FinancingDetails component
SecurityListyOptionalinside SecListGrp › FinancingDetails
SecurityListRequestxOptionalinside the FinancingDetails component
TradeCaptureReportAEOptionalinside the FinancingDetails component
TradeCaptureReportRequestADOptionalinside the FinancingDetails 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 898 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[898];field?.name;   // "MarginRatio"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

Other Percentage 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