FIX TAG 2670
TrdRegPublicationReason
Definition
Additional reason for trade publication type specified in TrdRegPublicationType(2669).
Reasons may be specific to regulatory trade publication rules.
Compare versions
Differences between the selected source snapshots, including wording and errata; not a migration guide.
FIX 5.0 SP2 FIX Latest · EP309
This tag is not present in the FIX 5.0 SP2 source. There is no definition or value list to compare.
Values 25
| Value | Meaning |
|---|---|
0 | No preceding order in book as transaction price set within average spread of a liquid instrument Additional detail from the official sourcePer MiFIR Article 4(1)(b)(i) the obligation to place a public order can be waived for transactions of liquid instruments on "systems that formalise negotiated transactions which are made within the current volume weighted spread reflected on the order book or the quotes of the market makers of the trading venue operating that system, subject to the conditions set out in Article 5" of MiFIR on volume caps. "Liquid markets" as per MiFIR Article 2(17)(b) are assessed by the regulator for the purposes of MiFIR Articles 4, 5 and 14. For ESMA RTS 1, RTS 6 and RTS 22 this is the waiver "NLIQ" flag. |
1 | No preceding order in book as transaction price depends on system-set reference price for an illiquid instrument Additional detail from the official sourcePer MiFIR Article 4(1)(b)(ii) the obligation to place a public order can be waived for "negotiated transactions which are in an illiquid share, depositary receipt, ETF, certificate or other similar financial instrument that does not fall within the meaning of a liquid market, and are dealt within a percentage of a suitable reference price, being a percentage and a reference price set in advance by the system operator." For ESMA RTS 1, this is the "OILQ" flag. |
2 | No preceding order in book as transaction price is for transaction subject to conditions other than current market price Additional detail from the official sourcePer MiFIR Article 4(1)(b)(iii), the obligation to place a public order can be waived in "systems that formalise negotiated transactions which are subject to conditions other than the current market price of that financial instrument." For ESMA RTS1, RTS 6 and RTS 22 this is the waiver flag "PRIC". |
3 | No public price for preceding order as public reference price was used for matching orders Additional detail from the official sourcePer MiFIR Article 4(1)(a) the obligation to place a public order can be waived for "systems matching orders based on a trading methodology by which the price of the financial instrument is derived from the trading venue where that financial instrument was first admitted to trading or the most relevant market in terms of liquidity, where that reference price is widely published and is regarded by market participants as a reliable reference price." For ESMA RTS 1, RTS 6 and RTS 22 this is the waiver flag "RFPT". |
4 | No public price quoted as instrument is illiquid Additional detail from the official sourceAccording to MiFIR Article 4(1)(b)(ii) and Article 14(1) the obligation to publish the quote prior to closing the trade may be waived if it was made in an illiquid instrument. However, according to MiFIR Article 14(1) and Article 18(2), systematic internalisers shall still disclose quotes to their clients upon request. This obligation may also be waived in case of bonds, structured finance products, emission allowances and derivatives. For ESMA RTS 1, RTS 2, RTS 6 and RTS 22 this is the waiver flag "ILQD". |
5 | No public price quoted due to "Size" Additional detail from the official sourceIn the context of ESMA, as per MiFIR Article 4(1)(c) and Article 14(2), the systematic internaliser was not obliged to quote prior to closing the trade as the trade was above the standard market size. In accordance to MiFIR Article 9(1)(b) and Article 18(10), market operators, investment firms and systematic internalisers may be waived, in accordance to guidance from the Competent Authorities, from making public prices for derivative instruments which are above a side specific to the instrument. For ESMA RTS 1, RTS 2, RTS 6 and RTS 22 this is the waiver flag "SIZE". |
6 | Deferral due to "Large in Scale" Additional detail from the official sourcePer MiFID Article 14, publication deferral is permitted if the transaction is large in scale compared to a standard market size, as set in RTS 1/Annex II (thresholds for "large in scale") and RTS 2/Annex III ("LIS and SSTI thresholds"). For ESMA RTS 1 and RTS 2, this is the "LRGS" flag. |
7 | Deferral due to "Illiquid Instrument" Additional detail from the official sourcePublication deferral is permitted if the transaction's instrument is illiquid, as defined by regulator's stipulation. For ESMA RTS 2, this is the "ILQD" flag. |
8 | Deferral due to "Size Specific" Additional detail from the official sourcePer MiFIR Article 11, publication deferral is permitted if the transaction is greater than the stipulated 'Size Specific to the financial instrument' threshold. For ESMA RTS 2, this is the "SIZE" flag. |
9 | No public price and/or size quoted as transaction is "large in scale" Additional detail from the official sourceIn the context of ESMA, as per MiFIR Article 4(1)(c) and Article 9(1)(a), the trading venue was not obliged to quote prior to closing the trade as the order size was above normal market size. |
10 | No public price and/or size quoted due to order being hidden Additional detail from the official sourceIn the context of ESMA, as per MiFIR Article 4(1)(d) and Article 9(1)(a), a transaction arising from an order that was not fully pre-trade transparent due to all or part of it being held in a trading venue order management facility, such as a reserve order. |
11 | Exempted due to securities financing transaction Additional detail from the official sourcePer ESMA RTS 22, Annex I, Table 2, Field 65: a transaction which "falls within the scope of activity but is exempted from reporting under Securities Financing Transaction Regulation". |
12 | Exempted due to European System of Central Banks (ESCB) policy transaction Additional detail from the official sourcePer ESMA RTS2, Article 14(1), and Article 15(1): "A transaction shall be considered to be entered into by a member of the European System of Central Banks (ESCB) in performance of monetary, foreign exchange and financial stability policy [is exempted from publication] … [The regulation] shall not apply to the following types of transaction entered into by a member of the ESCB for the performance of one of the tasks referred to in Article 14: transaction entered into for the management of its own funds; transaction entered into for administrative purposes or for the staff of the member of the ESCB which include transactions conducted in the capacity as administrator of a pension scheme for its staff; transactions entered into for its investment portfolio pursuant to obligations under national law." |
13 | Exception due to report by paper Additional detail from the official sourceIncomplete report due to submission by paper (form). In the context of US CAT this is Form T pursuant to FINRA Trade Reporting Rules. |
14 | Exception due to trade with non-reporting party Additional detail from the official sourceIncomplete report due to counterparty of the reporting party being absent. In the context of US CAT this is when a trade was executed by a non-FINRA member and reported to the TRF by the FINRA member counterparty. |
15 | Exception due to intra-firm order Additional detail from the official sourceIncomplete report due to intra–firm order filled from firm’s proprietary account. |
16 | Reported outside of reporting hours Additional detail from the official sourceIn the context of ESMA, trades published after the trade reporting facility being used (e.g. APA for trades brought onto a trading venue) closes, will be reported the following business day and not flagged as deferred (as the MiFID deferral regime is not applicable). This value distinguishes these types of trades from trades executed (and published) on the same business day. It is recommended that this value be set by the trade reporting facility, e.g. APAs, (as opposed to publishing investment firms) to ensure the most accurate use of this value. |
17 | No public price quoted due to usage of a pre-trade transparency waiver Additional detail from the official sourcePer FCA policy statement PS23/4, this is the "NETW" flag for negotiated trades in accordance to MiFIR Article 4(1)(b). |
18 | Deferral due to medium liquid instrument Additional detail from the official sourceIn the context of the EU Consolidated Tape, this is used for the post-trade deferral flag MLF1. |
19 | Deferral due to medium illiquid instrument Additional detail from the official sourceIn the context of the EU Consolidated Tape, this is used for the post-trade deferral flag MIF2. |
20 | Deferral due to large liquid instrument Additional detail from the official sourceIn the context of the EU Consolidated Tape, this is used for the post-trade deferral flag LLF3. |
21 | Deferral due to large illiquid instrument Additional detail from the official sourceIn the context of the EU Consolidated Tape, this is used for the post-trade deferral flag LIF4. |
22 | Deferral due to very large liquid instrument Additional detail from the official sourceIn the context of the EU Consolidated Tape, this is used for the post-trade deferral flag VLF5. |
23 | Deferral due to very large illiquid instrument Additional detail from the official sourceIn the context of the EU Consolidated Tape, this is used for the post-trade deferral flag VIF5. |
24 | Deferral due to asset class Additional detail from the official sourceIn the context of the EU Consolidated Tape, this is used for the post-trade deferral flag DEFF. |
About the int data type
Sequence of digits without commas or decimals and optional sign character (ASCII characters "-" and "0" - "9" ). The sign character utilizes one byte (i.e. positive int is "99999" while negative int is "-99999"). Note that int values may contain leading zeros (e.g. "00023" = "23").
Used in messages 9
Includes nested components and repeating groups. Open a location to see its surrounding requirements.
35=8ExecutionReportTrdRegPublicationGrp35=DNewOrderSingleTrdRegPublicationGrp35=JAllocationInstructionExecAllocGrp / TrdRegPublicationGrp35=WMarketDataSnapshotFullRefreshMDFullGrp / TrdRegPublicationGrp35=XMarketDataIncrementalRefreshMDIncGrp / TrdRegPublicationGrp35=AETradeCaptureReportTrdRegPublicationGrp35=AKConfirmationExecAllocGrp / TrdRegPublicationGrp35=ASAllocationReportExecAllocGrp / TrdRegPublicationGrp35=BMAllocationInstructionAlertExecAllocGrp / TrdRegPublicationGrp