Goldman Sachs' Expensive Typo

ft.com/alphaville All times are London time

News

The following is the formula for a properly structured warrant tied to Japan’s Nikkei index — which would (we presume) be easy enough to hedge for its issuer:

(Closing Level "“ Strike Level) x Index Currency Amount / Exchange Rate.

What follows is the formula attached to four recent warrants tied to Japan’s Nikkei index issued by Goldman Sachs:

(Closing Level "“ Strike Level) x Index Currency Amount x Exchange Rate.

Spot the difference?

In one, the index currency amount is divided by the exchange rate, in the other it is multiplied by the exchange rate.

It may be a small error, but according to the Economist (hat tip to our FT Tilt colleague Stacy-Marie Ishmael for flagging the story up), the typo is fast becoming a costly headache for Goldman Sachs in Asia.

As the magazine noted last week, having spotted the error, Goldman Sachs offered a 10 per cent premium to buy the contracts back from the market. Investors, however, have not budged easily. Most are insisting that the bank honours its typo-ridden terms.

That, needless to say, would be a blow for Goldman.

The Economist estimates the typo could expose the bank to as much as HK$350m instead of the HK$10m initially offered on the warrants, which are basically a type of derivative with a limit on losses, similar to options.

On the investors’ side is also the fact that Goldman may not have conducted itself in a forthright manner upon discovering the mistake.

As the Economist noted:

Holders also allege that after it notified the exchange of the problem but before trading was frozen, Goldman continued to bid to buy back the warrants while ceasing sell offers that would have meant disclosing the real price based on the prospectus. Goldman merely says it made offers at the "correct" price.

Understandably, while the two sides wrangle over the conclusion to the saga, the notes themselves have been suspended by the exchange.

Whatever it is, though, may have important implications for the wider market.

First, the Hong Kong exchange-traded warrant market is vastly popular — much more so than it is in the United Kingdom and the United States, where the products never really took off because they were seen as more expensive than rival products.  According to the Economist, some 14,400 warrants were issued in Hong Kong last year alone.  Each series would have carried its own phonebook-sized prospectus.

Not only does the Goldman case make you wonder about the attention to detail paid to the former prospectuses that are out there, it raises questions about what classifies reneging in the first place.

As the Economist notes:

"If it was possible to renege even on what was written down in black and white, how can we possibly be an international financial centre any more?" asked James To, a member of the Legislative Council (Legco), at a hearing in April; another Legco hearing was held this week and a further one is due in June. Perhaps the biggest question of all concerns the complexity of these instruments. What other risks might be lurking in the market undergrowth?

Furthermore, in the event that Goldman does get to backtrack on the prospectus, there’s the question if the same would apply to anyone else making a similar mistake.

Many in the market are not so sure.

One last thing. The saga may also finally shed some light on warrant pricing practices, and specifically to what degree they are potentially mis-priced versus rival products in the market.

Related links: Trader admits manipulating price of warrants – Straits Times Banks devise new structures that bet on the markets - FT All eyes on broker-dealer internalisation – FT Alphaville

WP Cumulus Flash tag cloud by Roy Tanck and Luke Morton requires Flash Player 9 or better.

Or select a previous briefing:

© The financial Times Ltd 2011 FT and 'Financial Times' are trademarks of The Financial Times Ltd.

var oob = new Advert(AD_OOB);oob.init(); var adPop = new Advert(AD_CORPPOP);adPop.init(); var adRefresh = new Advert(AD_REFRESH);adRefresh.init(); clientAds.fetch(AD_MACROAD); clientAds.render(AD_MACROAD); clientAds.fetch(AD_MARKETINGRIB); clientAds.render(AD_MARKETINGRIB); clientAds.fetch(AD_TLBXRIB); clientAds.render(AD_TLBXRIB); clientAds.fetch(AD_DOUBLET); clientAds.render(AD_DOUBLET); clientAds.fetch(AD_INTRO); clientAds.render(AD_INTRO); clientAds.fetch(AD_HLFMPU); clientAds.render(AD_HLFMPU); clientAds.fetch(AD_HMMPU); clientAds.render(AD_HMMPU); clientAds.fetch(AD_TRADCENT); clientAds.render(AD_TRADCENT); clientAds.fetch(AD_MARKETING); clientAds.render(AD_MARKETING); clientAds.fetch(AD_BANLB); clientAds.render(AD_BANLB); clientAds.fetch(AD_MPUSKY); clientAds.render(AD_MPUSKY); clientAds.fetch(AD_MPU); clientAds.render(AD_MPU); clientAds.fetch(AD_WDESKY); clientAds.render(AD_WDESKY); clientAds.fetch(AD_NRWSKY); clientAds.render(AD_NRWSKY); clientAds.fetch(AD_ARTBOX); clientAds.render(AD_ARTBOX); clientAds.fetch(AD_FTHBOX); clientAds.render(AD_FTHBOX); clientAds.fetch(AD_TLBX); clientAds.render(AD_TLBX); clientAds.fetch(AD_FMBUT2); clientAds.render(AD_FMBUT2); clientAds.fetch(AD_LHN); clientAds.render(AD_LHN); clientAds.fetch(AD_MKTBX); clientAds.render(AD_MKTBX); clientAds.fetch(AD_OOB); clientAds.render(AD_OOB); clientAds.fetch(AD_POP); clientAds.render(AD_POP); clientAds.fetch(AD_BXBAR); clientAds.render(AD_BXBAR); clientAds.fetch(AD_DKTALRT); clientAds.render(AD_DKTALRT); clientAds.fetch(AD_DSKTICK); clientAds.render(AD_DSKTICK); clientAds.fetch(AD_PRNT); clientAds.render(AD_PRNT); clientAds.fetch(AD_INV); clientAds.render(AD_INV); clientAds.fetch(AD_MBATOP); clientAds.render(AD_MBATOP); clientAds.fetch(AD_MBABOT); clientAds.render(AD_MBABOT); clientAds.fetch(AD_MBALINK); clientAds.render(AD_MBALINK); clientAds.fetch(AD_SBHEAD); clientAds.render(AD_SBHEAD); clientAds.fetch(AD_FTNT); clientAds.render(AD_FTNT); clientAds.fetch(AD_1x1); clientAds.render(AD_1x1); clientAds.fetch(AD_CURRCON); clientAds.render(AD_CURRCON); clientAds.fetch(AD_CURRBOX); clientAds.render(AD_CURRBOX); clientAds.fetch(AD_CORPPOP); clientAds.render(AD_CORPPOP); clientAds.fetch(AD_REFRESH); clientAds.render(AD_REFRESH); clientAds.render(); setCurrentTime(1232358020000) Assanka.wp.processClipThis(); var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www."); document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E")); try { var pageTracker = _gat._getTracker("UA-1874623-1"); pageTracker._trackPageview(); } catch(err) {} if (typeof Inferno == 'undefined') { var eid = (document.cookie.match(/EID=(\d+)/)) ? document.cookie.match(/EID=(\d+)/)[1] : 'unknown'; pageTracker._trackEvent('Debug events', 'sr23715', 'Load failure for '+eid); setTimeout(function() { var d = new Date(); document.getElementById('infdebug23715').innerHTML = (''); }, 1000); } var _sf_async_config={uid:14181,domain:"ft.com"}; _sf_async_config.sections = "alphaville"; _sf_async_config.authors = "Izabella Kaminska"; (function(){ function loadChartbeat() { window._sf_endpt=(new Date()).getTime(); var e = document.createElement('script'); e.setAttribute('language', 'javascript'); e.setAttribute('type', 'text/javascript'); e.setAttribute('src', (("https:" == document.location.protocol) ? "https://a248.e.akamai.net/chartbeat.download.akamai.com/102508/" : "http://") + "static.chartbeat.com/js/chartbeat.js"); document.body.appendChild(e); } var oldonload = window.onload; window.onload = (typeof window.onload != 'function') ? loadChartbeat : function() { oldonload(); loadChartbeat(); }; })(); Read Full Article »


Comment
Show comments Hide Comments


Related Articles

Market Overview
Search Stock Quotes