Waiting for EMIR

Safe to say the general gestalt of the industry is DOUBT.

Officially, companies are supposed to be sending trades over to a “Trade Repository” or TR by January 2014.  We are considering taking spread bets.

Waiting for EMIR

Here’s what we learned from Dodd Frank in the US:

TR submission is inextricably linked to the Electronic Confirm Process.  If you have to report OTC trades staying with a manual confirm process is a ticket to pain.  Plan for some re-design work around how OTC trades are confirmed and submitted.

Like Dodd Frank there are a pile of TR “contenders.”   Most likely won’t make it.  Why?  Well, like the US, there is operational efficiency in a confirmation + TR reporting.  Likewise, there is just not market (read money) mass for 9 TRs.

Firms should have a decent amount of skepticism around “easy” when it comes to both initial reporting on ongoing changes.  Take a look at Commissioner O’Malia’s comments here under the section “Attacking the Data Dilemma”.  Essentially he articulates that data non-standardization is the Achilles heel of trade reporting.  Many in the US selected an SDR that was easy to report to because the SDR did not standardize values.  We see this as mortgaging the workload.  If you picked an SDR that does a poor job of standardization you are just going to overhaul everything when they are forced to standardize.

What we think is going to be different under EMIR is that it is firms will likely report to multiple SDRs.  The product coverage under EMIR and REMIT is very wide and the ability for TRs to accommodate every single possible trade permutation is doubtful.  But here’s who we think are the major contenders.

EFET > DTCC COMBO: EFET already has a lot of confirm volume in Europe.  But, we are not expecting a target TR test environment to EFET until August.  This leaves 4 sweet months to meet compliance.  Somewhat doubtful that EFET will be able to incorporate FX deals into the commodity mix.  So it could be that firms may have to send some trades to EFET and FX trades over to DTCC directly.

ICE ECONFIRM > TRADE VAULT:  The feedback from participants in the US have been happier with the ICE/Trade Vault Combo than any other SDR.  Part of this could be because many firms were already somewhat familiar with the eConfirm process. But also the platform was more stable and ICE employees more familiar with complex commodity trades.  (I’m not suggesting there were no challenges…there were.  But they were far lower than other SDRs).   We are expecting ICE to expand its product footprint for EMIR to at least include FX trades.  This is a big plus.  Likewise we are expecting them to get fully underway and ready for TR connectivity by late July.

CME: A bit of a dark horse in the US.  CME was a little late to the game and under-marketed.  This is a mistake we don’t expect them to make twice.  Not only is CME a TR in and of itself, but they can also route submitted trades to DTCC.  Furthermore, product coverage is large out of the box.  There is also some natural advantage the futures exchanges have over others.  EMIR has a much wider reporting footprint than Dodd Frank.  So if your company is doing a significant volume on ICE or CME then it is likely that they can facilitate reporting of these products.

OTHERS:  I am not suggesting that others won’t show for TR reporting.  But our current read is that if they show for EMIR they will be loss leaders.

Our final bet.  When is EMIR going to go “Live?”   Mid Q1 2013.  We think that betting on anything later is overly optimistic.

Share on TwitterShare on LinkedInShare via email

Your End-User Dodd-Frank Checklist

Sharing information is important.  If you have any questions about any of these, don’t hesitate to email me.

In Texas it’s illegal to graffiti someone’s cow.  Seriously, you can’t make this stuff up.  So at some point someone in Texas took branding a bit too far.  And a legislature got into a knot and viola we have a law.

Speaking of fun laws, Dodd-Frank is upon us.  Here is a rundown to go live:

End User Requirements BY APRIL 10th:

Get Your CICI!  (The precursor to a Legal Entity Identifier (LEI)).

You’ve got to register.  Every party to a OTC financial transaction MUST register by April 10th.  It’s easy.  Get it done!  The CFTC may not be able to make heads or tails of trade submission (see below).  But they will be able to tell if a company has properly registered.  See the registration link here: www.ciciutility.org

Load All Historic Financial Deals into an SDR

If you are a party to any financial transaction in energy or commodity open as of July 21, 2010 to April 10th, you need to load EVERY historical deal into a Swaps Data Repository.

Yes, your counterparty may do this for you.  (Such as if you were dealing with a bank) But you need to make sure they either did it or intend to do it by April 10th.  The proof positive is by getting the USI (Universal Swap Identifier) from your counter-party .

Embedded Options are Reportable.  So say you did a physical fixed price deal.  But let’s further say the deal had some swing optionality.  The physical fixed part of the deal is not reportable…but the swing? Yep, that’s reportable.  It can get dicey here because sometimes your counterparty may disagree as to whether an embedded deal is reportable.  It’s worth spending some time examining contracts and determining whether there is any embedded optionality and reaching out to your counterparty.

Don’t Assume That the Exchange Will Send Historical Trades to the SDR for You.

Although exchanges are required to report deals as of April 10th, DO NOT assume that they will send over your historical financial deals.  This is particularly true if they were “facilitated” OTC deals.  It is a mistake to assume that your cleared and un-cleared “exchange facilitated deals” will be sent to an SDR.

EOD Reporting

On April 10th you’ve got to make sure that every new fin deal is reported to an SDR by end of day.  Are all your counterparties doing the reporting?  Yes?  Great!  Don’t forget your Part 45 obligations around recordkeeping.  Yes, even if you do not do the reporting there is a lot of mandatory requirements around how you keep these deals in house.

Let’s say you are a oil and gas producer.  To hedge production you entered into a 3 way collar.  Is this reportable?  You bet.  Odds are that a swaps dealer is your counterparty.  Just know that these are subject to “in house” inspections and they need to be complete.

Be Prepared for it all to Change

So Interest Rate and FX has been reporting since January.  How has it gone?  Terrible!  While most banks and market participants sent these trades have been sent over to the DTCC SDR and a handful over to ICE Trade Vault, the start of the Dodd-Frank market turned out to be a near total missed approach.   The data sent over to the SDR’s was so incomprehensible, that the CFTC admitted they couldn’t find the London whale even if they wanted to.   See this article.

Gensler’s comments in this doc highlight the CFTC lack of resources being part of the problem.

The net result of this is all that work you have done so far is going to change.  The CFTC will certainly be rolling out new requirements on how products are reported.  Be prepared.

ICE E-Confirm

I don’t mean to shamelessly plug ICE.  But if you are not using eConfirm you are in for a world of pain.  I don’t mean to suggest that you have to use Trade Vault as your SDR.  Let’s say you are the reporting counterparty and use DTCC as a SDR.  Your counterparty needs to know that you reported the deal.  Easily solved by sharing the USI.  The EASIEST way to get USI on both sides of the trade is eConfirm.    Rumor is that ICE has on-boarded hundreds of new users into eConfirm and it looks like the better part of the market is going to go there for confirmations.

 

Share on TwitterShare on LinkedInShare via email

Extract, Transform and Load – Same Syntax, Different Semantics

Our customers use K3 to connect systems efficiently and to consolidate data across a number of systems.  Often when evaluating options, they say to us “Of all the ETL (Extract, Transform and Load) software options, yours is by far the easiest and most cost-effective!”  Music to my ears you would think, right?

Well, kinda…see, there are hundreds of tools out there ‘extracting’, ‘transforming’ and ‘loading’ data.  But the term ‘ETL’ has generally meant something way way bigger.

ETL tools are typically gigantic, expensive and proprietary frameworks with tons of bells and whistles meant for developers.

For many firms that just want to consolidate data across systems or move data between a few systems, biting off a giant ETL tool is the technology equivalent of using a chainsaw to slice your bread.  

It’s going to make a mess.

We took a different approach.  After struggling with ETL tools for years we came to recognize that the ETL juggular is that it’s nearly impossible to keep the big ‘ol ETLs current with the business requirements.

Enter K3 where developers build the interfaces but then business users manage the logic of how the interface should transform the data.  Not the developers.  So while I love hearing clients tell me our software is the easiest way to extract, transform and load their data, I always feel a like someone just called our light, agile precision tool a giant chainsaw.

Share on TwitterShare on LinkedInShare via email

Next Named Storm – No SQL

This post is actually a response to a very thoughtful article by Merv Adiran and Ted Friedman over at Gartner.  Their point, which is a very important one, is that a platform does not make a solution.  For example, some keen developers are using Hadoop as an integration tool.  I mean it’s awesome!  I remember using MS SQL as an integration tool.  Cool?  Yes.  But a solution?  No.  It’s a bag of snakes.  Pretty much poison for a well-functioning enterprise.

A bit naughty as it may be this is really important stuff.  Why?  Disruption is happening here.  Technology-wise we have seen this again and again.  And, the No SQL technology, although somewhat slow moving, is a whopper which has a very high probability of changing the status quo.

To me it looks like this:

Data Integration: System to System
MDM: Master Data Management
ETL: Extract, Transform, Load
B.I.: Business Intelligence “a-la Cube”

The United States of Data Applications is our neighborhood.   Most vendors in the space play seriously in some and dabble in others.  There’s always a lot of confusion about what K3 does versus Informatica  versus Mule, Versus Biz Talk, etc etc.  Widely differing approaches here…that’s another blog post.

The challenge is this disruption is coming straight to the United States of Data Applications.  It is still uncertain where the No SQL hurricane will hit.  Could curve left…could curve right.  But when No SQL starts taking shape from a platform to solutions…it’s going to be a different world.

Share on TwitterShare on LinkedInShare via email

MxR – Announcing Multi-SDR “Drop Off Service”

Today we are announcing our “Drop Off Service” for SDRs with MxR.

For the last year or so we have been very active connecting deploying K3 to connect some of the world’s largest trading organizations to US Swaps Data Repositories.  What we noticed is that many times deals are captured in Excel spreadsheets and operations need a way to quickly and easily drop their trades into the SDR and eConfirm Service.

We have now gone live with several deployments of MxR.   With MxR you simply drop an Excel sheet into a folder and viola, it is automatically shipped into the SDR of your choice.  Whether you are standardizing on Trade Vault, DTCC, CME or any combination thereof, getting trades to the SDR has never been more simple.

What do you need to run MxR?  Technically nothing.   MxR runs on the Amazon Cloud (AWS) with full encryption.  Alternatively, one can run MxR internally behind your firewall.  Even if you have a built out solution for Dodd Frank, this is a great backstop.  Likewise, MxR’s user interface for configuring mapping and rules allows users to simply produce a minimal spreadsheet instead of one with hundreds of columns.

Email Andrew Byrnes if you would like to find out more.

Share on TwitterShare on LinkedInShare via email

The Year of the Snake…and Trade Break

I’m not big on New Year resolutions or on predictions.  But in the case of Dodd-Frank and EMIR in Europe it’s hard to resist.  The die has been cast and SDRs are a real thing now.

Here Come the Trade Breaks

Here Come the Trade Breaks

Setting aside for the moment the master strokes about what DF and EMIR are supposed to be about, let’s talk for a moment about the hands on, down in the trenches  effect of what these rules are actually causing.

A trade clean up of epic proportion.

It sounds like a great and practical idea.  Perhaps an idea that many firms agree have been put off too long.  But there is a problem.  A big one actually…this is the commodities business.

In the commodities business we have legacy systems.  No I don’t mean just in-house built systems.  I mean vendor systems that were architected in the 80′s and 90s.   Lots of them out there, sold as new, patina upon patina, with the same fundamental architecture they started with.  I was working with a vendor system at a client.  One of our younger developers was pulling his hair out asking why, why did they do this?!   The answer unfortunately is the same as the reasoning for popped collars and hair gel in the 80s.  “It was the thing at the time.”

Immediately on everyone’s plate is how to get trades out of these old architectures and get them properly into the SDRs.  This turns out to be, at best, like data gymnastics.  At worst mad contortion.  If the data is a spaghetti-works to begin with the probability of a trade break goes through the roof.  Surveying the dozen or so systems we have connected to the SDRs better than 3/4 of those have a significant amount of transactions that have been “shoehorned” into the system.  This is a recipe for a trade break downstream with ICE/DTCC/CME or whatever SDR has been chosen.  These systems are somewhat unforgiving, and as a result unless they come across perfect they bounce.

Forget the Year of the Snake.  This is the year of the Trade Break.

Share on TwitterShare on LinkedInShare via email