Skip Ribbon Commands
Skip to main content
Navigate Up

FAQs

KDPW TR. WHO ARE WE?
KDPW TR is an EU trade repository based in Warsaw, Poland. It is authorised by the European Securities & Markets Authority (ESMA) and the Polish Financial Supervision Authority (KNF) to provide EU regulatory reporting services under:
  • EMIR - All asset classes (ESMA authorisation)
  • SFTR- All eligible SFTs (ESMA authorisation)
  • MiFID2/MiFIR (KNF authorisation)

PORTING FROM OTHER TR:

WHAT IS PORTING?
Porting is the process of transferring data held in your current trade repository to a new trade repository, such as KDPW TR.

HOW DO I ARRANGE FOR MY TRANSACTIONS TO BE PORTED TO KDPW TR?
Easy. Clients obliged to perform regulatory reporting under EMIR can move their reporting to KDPW TR from another EU trade repository.

DO YOU CHARGE FOR THE PORTING ITSELF?

No. KDPW TR does not charge for the porting process. However, please check if your current TR charges a fee for the data transfer at its end.

WHAT DATA NEEDS TO BE PORTED?

1. Active trades – i.e. the last trade state for trades previously reported to a TR that have not expired and for which no amending Action Types “E”, “C”, “P” or “Z” have been submitted. The data is ingested directly into the KDPW TR system and from that moment are available to all TR processes (validation, reconciliation, reporting to supervisory bodies).
2. Historic data – at the client’s request or in the event of a TR withdrawal. This data is sent by TRs in CSV format and are not included in TR processes.

HOW DOES THE PORTING PROCESS WORK?

1. Only data for active trades that meet current EMIR technical standards can be ported between TRs.
2. Only the last trade state of trades are ported, as well as lifecycle events – although these lifecycle events are not involved in KDPW TR processes.
3. Ported trades include own trades, counterparty trades and 3rd party trades (delegated reporting).
4. KDPW TR agrees the porting details and timetable with the client and the client’s current TR, from which the data are to be ported.
5. Porting takes place over a weekend to minimise disruption to TR production systems.
6. The client’s current TR needs to confirm with the client the scope of the data to be ported (including UTIs, and LEIs). Some data may need to be updated to the latest EMIR technical standards.
7. Once the details of the porting have been agreed between KDPW and the client’s TR, KDPW TR provides the client with a
TR Portability Form, which forms a legal basis for the transfer. The TR Portability Form needs to be signed by the client’s authorised representative.
8. The client’s TR provides the client with a timetable for the porting.
9. The client will need to be available on the porting date to its TR and to KDPW in case of any outstanding issues that need to be resolved.
10. Once data porting has been successfully completed, any further porting queries need to be addressed to the client’s new TR, KDPW TR.

For more detailed information on porting, please see the ESMA Final Guidelines, available here:
Final Report. Guidelines on transfer of data between Trade Repositories.

SOUNDS GOOD. WHERE CAN I GET MORE INFORMATION ON PORTING TO KDPW TR?
Please contact us at repository@kdpw.pl or call us on + 48 22 537 94 60 and we’ll help you get started.
Last modified:08-12-2020 Go up