It’s been barely six weeks since the EMIR trade reporting obligations came into effect on 12 February and, as the regulatory dust begins to settle, parties to derivative transactions are still in the process of assessing their duties under the new regime.  In the lead up to the February deadline, bank and securities firms were busy implementing their client outreach programmes whilst we were busy putting out client alerts and blogging about the new requirements under EMIR.  We continue to help clients with their questions on this significant change to the EU regulatory landscape.

Two aspects of the new trade reporting regime in particular repay some close attention to avoid potential trip-ups.  First, the rules relating to what has been termed ‘backloading’, or, in other words, the requirement to transaction report historic trades.  After some uncertainty in the lead up to implementation, the requirements are now clearer.  Broadly, counterparties need to ensure that all historic trades that were either ‘live’ on 12 August 2012 (the date EMIR came into force), or subsequently became live prior to 12 February 2014 (the date the reporting requirements came into force), are reported.  For these trades, the deadline for reporting will range from just one day to a period of three years after the reporting obligations became effective, depending on the date of the trade and, if applicable, its termination date.  Our client alert sets out these timeframes in more detail.

Continue Reading Back(loading) to the Future – the Nuances of EMIR Transaction Reporting Requirements

EMIR’s trade reporting obligations come into effect on 12 February and counterparties to derivative transactions are currently scrambling to ensure they have all the appropriate systems in place to ensure compliance. For large financial institutions, this has already involved many months of hard work and, even still, many are not optimistic about meeting next month’s deadline. At the other end of the spectrum, the administrative burden on one-off or low volume commercial counterparties should be relatively light, and ensuring that the reporting obligations are covered not therefore too taxing.

What then of SPVs – which are neither operational goliaths like their derivative counterparties nor autonomous commercial entities capable of assessing the implications on cost, resources and time of each option open to them?
Continue Reading You Don’t Need EMIRacle – Trade Reporting for SPVs Made Easy

In times when banks are facing balance sheet pressure and rating downgrades, it seems sensible for their clients to review the Credit Support Annex (“CSA”) terms under which they have entered into (or are looking to enter into) interest rate swaps with such bank counterparties. This is the main protection for a swap counterparty against counterparty credit risk so it is important that the terms actually address the current state of play.

In the past, when the banks were seen as almost indestructible, it was not unusual for the CSA to be completely absent or one-sided, relieving the banks of the need to post collateral, eliminating their funding risk or shifting it entirely onto the other swap party in the case of a one-sided CSA.

Having witnessed the difficulties that highly rated banks can run into – in some cases without any warning – and the impact it can have on their swap positions, clients should again consider the credit risks that they face in terms of what they can, and should, do to protect themselves when negotiating the swap terms.
Continue Reading CSAs: when and why to negotiate?