MiFID II / EMIR Transaction Reporting
MIFID_IIfree10 data-quality rules for EU transaction reporting under MiFID II / MiFIR (RTS 22) and EMIR derivatives reporting. Covers required fields, LEI and ISIN format, ISO 4217 currency and MIC venue codes, buy/sell indicator, price/quantity validity, UTC timestamps, and transaction-reference uniqueness. Use it to validate reports before submission to an ARM / trade repository.
Checks included (10)
LEI Is 20 Characters(executing_lei)
The executing/submitting LEI must be a 20-character ISO 17442 identifier.
ISIN Is 12 Characters(instrument_isin)
The instrument ISIN must be a 12-character ISO 6166 identifier.
Buy/Sell Indicator Is Valid(buy_sell_indicator)
The buy/sell indicator must be BUYI (buy) or SELL (sell) per RTS 22.
Trading Date-Time Is UTC ISO 8601(trading_datetime)
Trading date-time must be reported in UTC ISO 8601 with a 'Z' suffix to the required precision.
Trading Venue Is a Valid MIC
The trading venue must be a valid ISO 10383 Market Identifier Code (MIC), or the 'XOFF'/'XXXX' codes where permitted.
Price Currency Is Valid ISO 4217
The price currency must be a valid ISO 4217 code.
Quantity Is Positive(quantity)
Reported quantity must be greater than zero.
Price Is Non-Negative(price)
Price must not be negative (where a numeric price applies).
Required Transaction Fields Present
Each transaction report must carry the executing-firm LEI, instrument identifier, trading date-time, quantity, and price.
Transaction Reference Is Unique(transaction_reference)
Each Transaction Reference Number must be unique per executing entity; duplicates are rejected by the ARM.