The Complexities of ISO 20022 XML for Transaction Reporting



ESMA went live with SFTR in accordance with the ISO 20022 XML methodology in July 2020. This is the first time an EU transaction reporting regulation went live with XML being the only format available for submission. This XML structure was created to provide an industry-wide framework to be used by all financial standards initiatives. Coming into effect in 2023, the European Markets Infrastructure Regulation (EMIR) REFIT will be adding ISO 20022 XML as part of the requirement for submissions.

The objective

One of ESMA’s goals of introducing ISO 20022 is to improve reporting quality. Where each trade repository has had its own unique submission format to date, it has caused difficulties in data sharing and matching between repositories.

By unifying the submission format to the ISO 20022 XML schema, this should eliminate the risk of discrepancies between reporting parties and repositories due to inconsistent data and allow generation of cleaner data with less variation of file formats for matching among repositories.


While data sharing is expected to improve under the ISO 20022 standard, the major drawback is that creating these files in XML format is not easily done. Transforming data into the right format to report via XML offers operational challenges and additional costs. Firms are required to develop in-house capabilities that they have not had before.  Firms will need to build test harnesses, then build the platforms, test systems and processes around it. This will require a full technology build and a solid base before firms are able to complete their transaction reporting.

Whilst it is not recommended to use excel to create trade reports, the ability to create or edit XML manually will be extremely difficult compared to old SCSV reports.

The XML outputs and response files from the trade repository are not easily human readable like CSV files, so the ability to perform a quick visual check is also lost.


TRAction’s regulatory trade reporting solution is built to cover multiple reporting regimes so that the cost and resource burden for investment firms can be reduced.

TRAction can ingest any client file or data format and convert it to XML for submission to the trade repository. TRAction also provides an easy to read summary of the TR response in its industry leading handback and confirmation files.

Please contact us if you would like to know more about how to simplify your reporting for multiple regimes.

Recent Articles:


What is an NFC-?

Entering into derivative transactions, you become a ‘counterparty’.
EMIR introduces two types of counterparties: Financial Counterparties (FC) or Non-Financial Counterparties (NFC).

Repo Agreements
About TRAction

How Are Repurchase Agreements Reported for SFTR?

A repurchase agreement (repo) is a form of short-term secured loan where one party sells securities to another and agrees to repurchase those securities later at a higher price with the securities serving as collateral for the borrower.


Refit, Rewrite, RTS, EMIR II; Navigating the Maze of EMIR Version Names

Regulatory reporting is hard enough without the confusion over which version of each regime is the latest. EMIR has gone through a number of variations since it was first implemented in 2012. We thought it would be a great time to outline what the EMIR version names relate to and where we are currently at as we anticipate further changes to the regime.


Reminder: Daylight Saving Time Ends this Weekend for New York

Are you reporting trades by New York (NY) time or following NY close of business? If so, it is important to check your trades/transactions are still reported at the correct time now that daylight saving time (DST) has started in the US (13 March 2022).