Tag 144 (OnBehalfOfLocationID) specifies The situation on the agency on whose behalf a message is sent. It complements OnBehalfOfCompID and supports granular area monitoring in routed messages. It is useful for functionality Evaluation and regulatory reporting in multi-site buying and selling environments.
Tag 570 (PreviouslyReported) implies irrespective of whether a trade has previously been reported to a regulator or trade repository (Y/N). It can be Utilized in Trade Seize Report messages to avoid duplicate submissions. PreviouslyReported supports compliance with trade reporting regimes by signaling the reporting standing.
Tag 283 (LocationID) identifies the physical or reasonable location of the investing desk or gateway. It supports latency checking and regulatory reporting.
Tag 181 was employed for phone number but is changed. Deprecated in favor of structured conversation fields.
Tag one hundred forty five (DeliverToLocationID) identifies the final delivery site in a multi-hop message chain. It assures precise routing to the correct data center or system. DeliverToLocationID supports complex network topologies and is also critical for very low-latency buying and selling infrastructure.
Tag 254 (LegRedemptionDate) was made use of to indicate the redemption day of the leg in a multi-leg instrument but is tag168 deprecated. It's been replaced by MaturityDate and SettlDate.
Tag 704 (LongQty) specifies the amount of the safety held in a protracted posture. It represents ownership and upside exposure to cost boosts. LongQty is Employed in Posture Stories and allocations to reflect invest in-side holdings.
This industry aids receivers distinguish between party-pushed alerts and question responses. UnsolicitedIndicator supports real-time market place monitoring and is particularly vital for timely dissemination of trading halts or corporate actions.
Tag 499 (CashDistribAgentCode) is a unique identifier to the income distribution agent, for instance a BIC or proprietary code. It enables specific routing and validation of payment instructions.
This field supports interoperability amongst techniques with different buffer restrictions. MaxMessageSize makes sure dependable transmission of enormous messages, which include mass offers or complex allocations, without having fragmentation or failure.
TradeDate is useful for accounting, overall performance measurement, and regulatory reporting. It is actually crucial for accurate trade lifecycle monitoring and makes certain suitable date attribution in economic data.
This field enhances transparency and supports troubleshooting. It allows shoppers to regulate their procedures or resubmit requests properly. CxlRejReason is significant for strong buy management and makes sure precise responses in significant-frequency trading environments.
AllocAvgPx makes sure exact Price foundation assignment for each account. It's Employed in Allocation messages and supports exact effectiveness measurement and tax reporting throughout various portfolios.
This subject supports regulatory compliance and Trader safety regulations. It can help brokers disclose materials conditions. CancellationRights is particularly suitable in UCITS or retail fund distributions. The field boosts transparency in subscription workflows.