Party Blocks
Party information is carried in the NoPartyIDs (453) repeating group. Each entry sets PartyID (448) to the party identifier and PartyRole (452) to the role value. There are three party block variants depending on message type.
PartyBlock-Inbound
Set by subscribers on all orders, quotes, and Summon requests.
| 452 = | Role Name | Required | Notes |
|---|---|---|---|
| 3 | Client ID | Y | Your assigned counterparty code (not MPID) |
| 4 | Clearing Firm | Y/O | Your MPID shown to contra firms. Optional if OpenYield can determine it via rules; mandatory if multiple MPIDs or if configured. |
| 5 | Investor ID | O | Account code, if configured for account segregation |
| 24 | Customer Code (FIX: Customer Account) | Y/O | Pass-through tag; returned unchanged on all responses and fills |
| 11 | Order Origination Trader | Y/O | Obfuscated trader code; reflected unchanged on all responses |
Clearing Firm (452=4): If your MPID has multiple accounts at the same DTCC clearing firm, add a NoPartySubIDs (802) repeating group to this entry: set PartySubID (523) to the clearing account code and PartySubIDType (803) to 10 (Securities Account Number).
Your own Clearing Firm entry (452=4) carries your MPID, while the contra's Contra Clearing Firm entry (452=18) on fills carries a DTCC participant number.
Customer Code (452=24): OpenYield returns this field unchanged on every response and fill. Use it for any internal tagging: account codes, strategy codes, algo order codes, portfolio codes, desk codes, and so on. If the order originated in the OpenYield UI, this field is set to ViaInterface.
Order Origination Trader (452=11): Carries an obfuscated trader identifier. If set on a FIX order, OpenYield reflects it on all responses. If you also receive Drop Copies of orders entered in the OpenYield UI, ask OpenYield to configure an obfuscated trader code for each UI login so that no personally identifiable information (PII) passes through the platform. Otherwise, the UI user's email address is sent in this field.
PartyBlock-Fill
Returned by OpenYield on fill execution reports (150=F) and fill corrections (150=G). Subscriber fields echo the original order; contra-party settlement details are added.
| 452 = | Role Name | Required | Notes |
|---|---|---|---|
| 3 | Client ID | Y | Matches Order |
| 4 | Clearing Firm | O | Matches Order |
| 5 | Investor ID | O | Matches Order |
| 24 | Customer Code (FIX: Customer Account) | O | Matches Order |
| 11 | Order Origination Trader | O | Matches Order |
| 17 | Contra Firm | Y | Bilateral: MPID of the settlement counterparty. Intermediated: OpenYield's MPID |
| 18 | Contra Clearing Firm | O | Bilateral: DTCC participant number of the contra's clearing firm. Intermediated: OpenYield's clearing firm DTCC participant number |
| 1 | Executing Firm | Y | OpenYield's MPID |
PartyBlock-Execution
Returned by OpenYield on non-fill execution reports: order acknowledgments, replaces, cancels, rejects, and fill cancels (150=H). Contra Firm (452=17) is omitted because an order may have filled against multiple counterparties across earlier messages.
| 452 = | Role Name | Required | Notes |
|---|---|---|---|
| 3 | Client ID | Y | Matches Order |
| 4 | Clearing Firm | O | Matches Order |
| 5 | Investor ID | O | Matches Order |
| 24 | Customer Code (FIX: Customer Account) | O | Matches Order |
| 11 | Order Origination Trader | O | Matches Order |
| 1 | Executing Firm | Y | OpenYield's MPID |