CFTC cannot cope with SDR data


In their efforts to implement Dodd-Frank, it would appear that the CTFC are guilty of not thinking about the data they would receive as part of the SDR requirements. Commissioner Scott O’Malia gave a speech to the SIFMA Compliance and Legal Society on March 19 where he said:

“Since the beginning of 2013, certain market participants have been required to report their interest rate and credit index swap trades to an SDR.

Unfortunately, I must report that the Commission’s progress in understanding and utilizing the data in its current form and with its current technology is not going well.

Specifically, the data submitted to SDRs and, in turn, to the Commission is not usable in its current form. The problem is so bad that staff have indicated that they currently cannot find the London Whale in the current data files. Why is that?

In a rush to promulgate the reporting rules, the Commission failed to specify the data format reporting parties must use when sending their swaps to SDRs. In other words, the Commission told the industry what information to report, but didn’t specify which language to use. This has become a serious problem. As it turned out, each reporting party has its own internal nomenclature that is used to compile its swap data.

The end result is that even when market participants submit the correct data to SDRs, the language received from each reporting party is different. In addition, data is being recorded inconsistently from one dealer to another. It means that for each category of swap identified by the 70+ reporting swap dealers, those swaps will be reported in 70+ different data formats because each swap dealer has its own proprietary data format it uses in its internal systems. Now multiply that number by the number of different fields the rules require market participants to report.

To make matters worse, that’s just the swap dealers; the same thing is going to happen when the Commission has major swap participants and end-users reporting. The permutations of data language are staggering. Doesn’t that sound like a reporting nightmare?

Aside from the need to receive more uniform data, the Commission must significantly improve its own IT capability. The Commission now receives data on thousands of swaps each day. So far, however, none of our computer programs load this data without crashing. This would seem odd with such a seemingly small number of trades. The problem is that for each swap, the reporting rules require over one thousand data fields of information. This would be bad enough if we actually needed all of this data. We don’t. Many of the data fields we currently receive are not even populated. ”

Wow! (or words to that effect). I can recall a conversation with my colleague Paul Blank where we discussed the likely impact of the new reporting rules on the regulator & the consequent need for (1) more staff & (2) more compute & storage capability. It would appear that the CFTC has not been pro-active in forecasting this impact. Funny but I don’t recall the NASD having these sorts of issues when they implemented TRACE. Maybe the CFTC should have spoken to the NASD to get some advice?

Commissoner O’Malia’s full speech is here

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: