SideComplianceID (FIX tag 659)
SideComplianceID (tag 659) is a String field defined in FIX 4.4. It appears in 2 message types, always optionally.
At a glance
- Tag
- 659
- Name
- SideComplianceID
- Datatype
- String
- Dialects
- FIX 4.4
- Messages
- 2
What the specification says
ID within repeating group of sides which is used to represent this transaction for compliance purposes (e.g. OATS reporting).
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 659
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 183 | |
| 35 | MsgType | s | New Order - Cross |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 548 | CrossID | EXAMPLE | |
| 549 | CrossType | 1 | Cross Trade which is executed completely or not. Both sides are treated in the same manner. This is equivalent to an All or None. |
| 550 | CrossPrioritization | 0 | None |
| 552 | NoSides2 entries | 2 | repeating group |
| 54 | Side | 1 | Buy |
| 11 | ClOrdID | ORD-10042 | |
| 659 | SideComplianceID | EXAMPLE | |
| 54 | Side | 1 | Buy |
| 11 | ClOrdID | ORD-10042 | |
| 659 | SideComplianceID | EXAMPLE | |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 40 | OrdType | 1 | Market |
| 10 | CheckSum | 149 |
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 659 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 |
|---|---|---|---|
| CrossOrderCancelReplaceRequest | t | Optional | inside the SideCrossOrdModGrp component |
| NewOrderCross | s | Optional | inside the SideCrossOrdModGrp 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 659 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[659];field?.name; // "SideComplianceID"field?.raw; // the verbatim wire stringfield?.value; // coerced to a stringOther String fields
- 655ContraLegRefID
- 654LegRefID
- 664ConfirmID
- 649QuoteStatusReqID
- 671LegAllocAccount
- 672LegIndividualAllocID
- 644RFQReqID
- 674LegAllocAcctIDSource
- 677LegBenchmarkCurveName
- 678LegBenchmarkCurvePoint
- 682LegIOIQty
- 635ClearingFeeIndicator
- 688LegStipulationType
- 689LegStipulationValue
- 628HopCompID
- 691Pool
- 625TradingSessionSubID
- 693QuoteRespID
- 620LegSecurityDesc
- 699BenchmarkSecurityID
- 617LegIssuer
- 703PosType
- 707PosAmtType
- 609LegSecurityType
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