Party Blocks
Party information is carried in a repeating group (tag 453 NoPartyIDs). Each entry sets tag 448 PartyID to the party identifier and tag 452 PartyRole to the role value. There are three party block variants depending on message type.
PartyBlock-Inbound
Set by subscribers on all orders, quotes, and RFO requests.
| 452 = | Role Name | 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 | 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 PartySubID block (802) to this entry: set PartySubID (523) to the clearing account code and PartySubIDType (804) to 10 (Securities Account 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, etc. 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. Recommended for any firm that also receives Drop Copies from the OpenYield UI — set this to a consistent obfuscated code per UI login so no Personally Identifiable Information passes through the platform. If unset, the user's email address is used.
PartyBlock-Fill
Returned by OpenYield on fill execution reports (ExecType=F). Subscriber fields echo the original order; contra-party settlement details are added.
| 452 = | Role Name | Notes | |
|---|---|---|---|
| 3 | Client ID | Y | Matches Order |
| 4 | Clearing Firm | O | Matches Order |
| 5 | Investor ID | O | Matches Order |
| 24 | Customer Code | 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 code of the contra's clearing house. Intermediated: OpenYield's clearing DTCC code |
| 1 | Executing Firm | Y | OpenYield's MPID |
PartyBlock-Execution
Returned by OpenYield on non-fill execution reports: order accepts, cancels, completions, and post-trade messages. Contra Firm (452 = 17) is omitted because a completed order may have filled against multiple counterparties across earlier messages.
| 452 = | Role Name | Notes | |
|---|---|---|---|
| 3 | Client ID | Y | Matches Order |
| 4 | Clearing Firm | O | Matches Order |
| 5 | Investor ID | O | Matches Order |
| 24 | Customer Code | O | Matches Order |
| 11 | Order Origination Trader | O | Matches Order |
| 1 | Executing Firm | Y | OpenYield's MPID |