Tag forty two (OrigTime) specifies the timestamp of the original buy request, ordinarily Utilized in modification or cancellation messages. It helps avert processing stale orders by confirming the timing context of the original ClOrdID. Any time a cancel or replace ask for is distributed, together with OrigTime makes certain the broker applies the improve to the correct instance, specifically in superior-frequency environments where several variations might exist.
Tag 142 (SenderLocationID) identifies the Bodily or sensible locale of the sender, such as a knowledge center or buying and selling desk. It supports latency monitoring and routing optimization. SenderLocationID improves auditability and it is Utilized in high-frequency trading to research geographic effectiveness.
Tag 594 (UnderlyingLocaleOfIssue) specifies the town or neighborhood location wherever the fundamental security was issued. It provides supplemental geographic context past state and point out.
Tag 438 (ContraTradeTime) specifies the timestamp (in UTC) at which the counterparty executed their aspect of a trade. It's used in Execution Studies to supply synchronization among counterparties in matched or crossed trades. This area is particularly crucial in block buying and selling, EFPs, and internal crossing networks where timing consistency is significant for confirmation and regulatory reporting. ContraTradeTime enables both sides to verify that the trade transpired at a similar instant, lessening disputes and reconciliation problems. It can be formatted as YYYYMMDD-HH:MM:SS.
Tag 437 (ContraTradeQty) specifies the quantity of shares or contracts traded through the counterparty within a matched or crossed trade. It's Employed in Execution Reports and affirmation messages to supply complete transparency on either side of the transaction, specially in block trades, Trade-for-physical (EFP) transactions, or inner crosses. ContraTradeQty makes certain that both equally get-togethers can reconcile their data correctly. In the cross-trade scenario, where by two counterparties conform to trade right, Each and every may possibly report marginally distinct portions because of rounding or timing; ContraTradeQty allows for comparison and determination.
Tag 304 (TotNoQuoteEntries) specifies the total quantity of estimate entries throughout all messages inside a quotation response. It supports reconciliation and makes certain completeness. TotNoQuoteEntries is used in multi-information quotation workflows to substantiate all entries have been been given.
Tag 704 (LongQty) specifies the quantity of a security held in a long situation. It signifies possession and upside exposure to price raises. LongQty is used in Posture Experiences and allocations to reflect invest in-aspect holdings.
This subject assists receivers distinguish concerning event-pushed alerts and query responses. UnsolicitedIndicator supports genuine-time industry monitoring and is also significant for timely dissemination of trading halts or company actions.
90 suggests ninety% of the original notional stays. It supports correct valuation, margining, and possibility modeling. LegFactor is tag168 essential for instruments with evolving notional values and makes sure right posture monitoring and performance attribution in complicated derivatives.
Tag 200 (MaturityMonthYear) specifies the maturity of a futures or choice in YYYYMM format. It identifies the deal thirty day period and is particularly essential for derivatives buying and selling.
Tag 157 (NumDaysInterest) specifies the number of days accustomed to estimate accrued interest on set-revenue securities. It's used in bond trades to find out interest owed from the final coupon date to settlement.
This subject delivers auditability and transparency. TradSesOpenTime supports latency Investigation and compliance with exchange reporting regulations. It assures accurate timestamping of the beginning of trading activity.
Tag 508 (RegistRefID) is usually a reference identifier assigned to your registration ask for, used to backlink requests and responses. It guarantees information correlation in Registration Instructions and acknowledgments. RegistRefID enables monitoring of registration lifecycle situations and supports reconciliation.
This industry enables precise correlation among rejection notices and original requests. BusinessRejectRefID is essential for troubleshooting buy rejections because of business logic, for example credit limitations or invalid parameters.