Skip to content


Did a coding error crash the economy?

May 22, 2008

Posted by: Mike Simons


A problem in the code used by financial ratings firm Moody’s may have contributed to the banking industry's headlong rush into “complex financial instruments” that ultimately led to the current global credit crunch.

That is the amazing tale broken yesterday by the Financial Times.

It shows both the power of the systems IT professionals build and manage and the stupidity of anyone in suspending disbelief because a computer system tells them black is white. It also highlights the governance issues involved in rectifying mistakes.

The Financial Times tells how Moody’s gave its top rating, Triple A, to financial products that promised spectacular rates of return. Yet because of a coding error, the products should have had a significantly higher risk evaluation.

“It was nothing more than a mathematical typo – a small glitch in a line of computer code. The impact of the bug Moody’s analysts discovered was, nevertheless, significant,” said the FT.

As a result banks rushed to bring to market similar products, despite warnings from analysts and rival ratings agencies that “something was wrong” and the proposition was too good to be true.

So it proved. Moody’s spotted the flaw and set about correcting it –which has now led to a range of governance questions. The FT reported that senior managing directors at Moody’s discussed how to update the model and changes, “which had the effect of reducing the negative impact on the ratings of correcting the code error.”

Moody’s initial response was to say, “It would be inconsistent with Moody’s analytical standard and company policies to change methodologies in an effort to mask errors.”

This was followed up by a statement that, “The integrity of our ratings and rating methodologies is extremely important; as such … we retained the law firm of Sullivan & Cromwell and initiated a thorough external review of our … ratings process. Upon completion of the review, we will promptly take any appropriate actions.”

Quite right, but who wants to be in that position? Mistakes happen and the cost of putting them right in IT systems rises exponentially, the longer it is delayed.

So, a coding error probably didn’t bring the world economy to its knees, but it certainly contributed to the current problems. It could only do so because some in the financial services industry thought that IT systems were the tool of modern alchemists.

When something seems too good to be true, whether the message is delivered by a complex IT system or man selling Rolexes at your local street market, it is too good to be true.

Follow highlights from ComputerworldUK on Twitter
Sign up for our Daily Newsletter
The UK IT News widget Get it for your site!

<<newer entry | back to blogs indexolder entry>>

Advert

close

Email this article to a friend or colleague:




PLEASE NOTE: Your name is used only to let the recipient know who sent the story, and in case of transmission error. Both your name and the recipient's name and address will not be used for any other purpose.

close
  • This article is now being printed.
close

What are your views on this subject? Use the form below to post a comment on this article up to 1000 characters.


Characters remaining:

close

Click below to add 'Did a coding error crash the economy?' to your blog.



If you do not have a ComputerworldUK Account and would like to use this feature, please Register.

If you are a registered, logged-in user, this will post the title and first paragraph of this story to your blog to share with your readers.

What is this?

Advert

WHITE PAPERS

  • Legal risks: Employee use of the internet and email
    Exploring the challenges facing IT Mangers today and vital steps to ensure safe internet an email use by employees.
  • Phishing for victims
    This White Paper examines the phenomenon of phishing. It explains the potentially catastrophic threat it presents to all kinds of organisation. Exploding some widespread myths, it lights up the murky waters where phishing first emerged and where it continues to evolve. But it also highlights what your business can do to blunt the threat.
  • Challenges and opportunities of PCI
    The control framework implicit in the Payment Card Industry Data Security Standard (PCI DSS) provides an enterprise structure for improving operational, security, and audit performance.
  • Social CRM comes of age
    Who is this “social customer”? What strategies and tools does the new breed of CRM provide to do something about this?
  • Risk Management: Protect and Maximize Stakeholder Value
    What has held organisations back from a broader adoption of risk management programs?
*