trade reporting - TRAction

Trade Reporting Field of the Week: Buyer First Name Seller First Name

Find out more about the Buyer First Name/ Seller First Name MiFIR reporting field in this weeks Trade Reporting Field of the Week.

Trade Reporting Field of the Week: Buyer ID/Seller ID

For this week’s MiFIR Trade Reporting Field of the Week, TRAction explores the Buyer and Seller ID field.

Trade Reporting Field of the Week: Investment Firm Indicator

This week’s Trade Reporting Field of the Week looks at the Investment Firm Indicator field in MiFIR reports.

Trade Reporting Field of the Week: Report Executing Entity ID

For this Friday’s Trade Reporting Field of the Week, TRAction reviews the Executing Entity ID field in MiFIR reports.

Trade Reporting Field of the Week: Venue Transaction ID

For today’s Trade Reporting Field of the Week, TRAction is exploring the Venue Transaction ID field.

EMIR Refit: Unique Product Identifier (UPI)

EMIR Refit will see the introduction of a new field – the Unique Product Identifier (UPI). The UPI is being added to EMIR, as well as other regimes such as ASIC, MAS and CFTC derivative reporting so as to more closely align regulation worldwide.

We All Know About EMIR Refit But What About The Next MiFIR Changes?

EMIR Refit has been receiving a lot of press recently with its upcoming changes to the format of reporting and additional data elements. Alongside this, ESMA has been working on changes to MiFIR given that the regime commenced over five years ago.

What Is An XSD File And Why Is It Important for Your Regulatory Reporting?

With the upcoming ASIC Rewrite changes fast approaching, the transition to XML submissions will pose a massive challenge for many reporting entities in the jurisdiction. An XSD file is a text file (in XML format) that defines the schema (structure, content, and data types) of another XML file.