PositionCurrency (FIX tag 1055)

StringFIX 5.0 SP2

PositionCurrency (tag 1055) is a String field defined in FIX 5.0 SP2. It appears in 9 message types, always optionally.

At a glance

Tag
1055
Name
PositionCurrency
Datatype
String
Dialects
FIX 5.0 SP2
Messages
9

What the specification says

The Currency in which the position Amount is denominated

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

A real message using tag 1055

TradeCaptureReport · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength147
35MsgTypeAETradeCaptureReport
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
32LastQty1000000
31LastPx1.09210
753NoPosAmt2 entries2repeating group
707PosAmtTypeCASHCash amount (corporate event)
1055PositionCurrencyEXAMPLE
707PosAmtTypeCASHCash amount (corporate event)
1055PositionCurrencyEXAMPLE
552NoSides1 entry1repeating group
54Side1Buy
10CheckSum136
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 1055 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 PositionAmountData component
AllocationInstructionAlertBMOptionalinside the PositionAmountData component
AllocationReportASOptionalinside the PositionAmountData component
AssignmentReportAWOptionalinside the PositionAmountData component
PositionMaintenanceReportAMOptionalinside the PositionAmountData component
PositionMaintenanceRequestALOptionalinside the PositionAmountData component
PositionReportAPOptionalinside the PositionAmountData component
TradeCaptureReportAEOptionalinside the PositionAmountData component
TradeCaptureReportAckAROptionalinside the PositionAmountData component

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 1055 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[1055];field?.name;   // "PositionCurrency"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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