Back to packs

MiFID II / EMIR Transaction Reporting

MIFID_IIfree

10 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.

10 rules 0 downloadsNo ratings yet
mifidemirmifirtransaction-reportingrts22regulatory-reporting
0.0(0 ratings)

Sign in to rate this pack

Test this pack with your data

Download the template, fill in your data, and see quality results instantly.

Test This Pack

Download & Install

Choose your tool — get a ready-to-run file

Run this on your data? Upload your CSV — we'll auto-map the columns, validate, and report the bad rows.Test my dataWant this certified on your data? Book a 30-min demo.Book a demo
Or use the CLI
$ npx dqhub install mifid-emir-transaction-reporting --format soda --table YOUR_TABLE

Reference data required

This contract's checks join against 2 reference tables. Load them into your warehouse — DQHub ships the public ones, the rest link to their source. All reference data →

Bundled — download
Customer-loaded — source

About this pack

10 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.

What's included

4format rules
2referential integrity rules
2range rules
1completeness rules
1uniqueness rules

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.