REMIT Reporting Services and Solutions - July 2015 updated March 2016
6.2.6.4 Communication with regulatory destination
A regulatory package will offer built in and supported connections to different reporting destinations, such as EMIR
Trade Repositories, REMIT RRMs, TR/RRMs and others such as Dodd Frank SDRs. In the case of REMIT the package
will need at least one mechanism to send data to ACER, which could be via a dedicated adapter to an RRM, the
support of a direct link to ACER (which would require the user to become an RRM themselves), by offering their own
RRM service (which at least one vendor is offering) or another mechanism. One connection to a TR/RRM is also
possible.
By offering a connection to a specific destination, the vendor will need to undertake to support that destination
going forward. Any change made by the destination will need to be supported by the package. The package will be
able to support the specific language of the destination, turning whichever data is loaded into the correct set of
events, whether in ACER XML or another, required by the destination.
When considering a package, it is important to consider the destinations supported – if a package only offers certain
destinations, the user will need to subscribe to that one and pay ѡ