United States: The Iheart Communications Credit Event And What It Means For The CDS Contract

Why We Still ❤ CDS

As has been the case now for three years running1, 2016's December 20 roll date again triggered a set of novel questions for the credit default swap market, this time related to the decision by iHeart Communications, Inc. ("iHeart") to fail to pay principal on bonds held by one of its subsidiaries. Although the iHeart questions turned out to be easier to resolve than those raised in Caesars or Novo Banco (which both required External Review2), they again strained market participants' tolerance for the complexity of the product and the opacity of the process required to manage it. In this memo, we summarize the analytical issues raised by the iHeart event, consider a few market-management issues highlighted by the determinations process in this case and offer some recommendations for the design of the product going forward.

Nevertheless, we think both the product and the process, as complex and opaque as they may be, once again delivered an outcome that was predictable, swift and certain. We hope the guardians of the product keep these principles in mind as ISDA prepares to hand over administration of the product to ICE Benchmark Association.3

Despite these latest bumps, we think financial market professionals who want to see analytical effort rewarded should still find CDS worth ♥-ing.

The iHeart event generated two analytical questions under the Definitions, each sub-mitted to the International Swaps and Derivatives Association ("ISDA") Determinations Committee (the "DC") for consideration:

(1) whether a Failure to Pay Credit Event had occurred with respect to certain of iHeart's outstanding notes (the "Notes") held by Clear Channel Holdings, Inc. ("CCH"), an iHeart wholly-owned subsidiary (the "FTP issue"), and

(2) how accrued interest on the Deliverable Obligations likely to be delivered in the Auction should affect the timing of the Auction and, therefore, the Auction Final Price for CDS referencing iHeart the ("Auction Date issue").

Both issues reinforced the lesson that CDS is a highly technical product governed by objective rules and standards, not one whose performance will be determined by general views of fairness or broad market expectations. Nevertheless, as well-worn as the product is, we think the iHeart event shows there are still technical improvements to be made.

The iHeart event also expanded and tested the market's reliance on the product's unique governance structure. While the FTP issue was well-briefed and telegraphed by market participants and observers; the Auction Date issue was not. We think the difference in the way the Determinations Committee dealt with each issue suggests areas for improvement here as well.

IHEART'S TACTICAL FAILURE TO PAY

Analyzing the performance of iHeart CDS was initially challenging because of an unusual "springing lien" provision contained in certain of iHeart's outstanding debt obligations requiring the company to grant additional collateral to certain of its creditors once the outstanding principal amount of specified iHeart bonds falls below a specific level. Specifically, the "springing lien" would have been triggered if the Company had redeemed all of the outstanding Notes on December 15, 2016 as required under the relevant indenture. Prior to December 12, 2016, market participants had been speculating as to whether iHeart would retire the Notes as scheduled and allow the lien to spring. Market participants were aware, however, that enough of the Notes ($57.1 mil-lion) were held by CCH to allow iHeart to avoid that outcome if it could manage to leave the CCH-held Notes outstanding while retiring all of the Notes held by non-affiliates. (Because the cross-default threshold in iHeart's other debt obligations is $100million, this would also avoid a wider iHeart cross-default). It was not clear to market participants, however, exactly how iHeart would achieve that result. Would iHeart somehow direct payment to some beneficial owners of the Notes but not to others? Would iHeart amend the indenture to split the obligations and establish that the CCH-held Notes were not due? Would the company pursue some other tactic?

On December 13, 2016, iHeart ended the speculation when it disclosed4 that, although it intended to repay in full the Notes held by non-affiliated holders on December 15, 2016 as required under the indenture, it had informed CCH that it would not repay the $57.1 million of Notes held by it on the maturity date but would continue to pay inter-est on those notes as long as they remained outstanding. CCH, in turn, informed iHeart that, while it retains its right to exercise remedies under the Notes in the future, "it does not currently intend to, and it does not currently intend to request that the trustee, seek to collect principal amounts due or exercise or request enforcement of any remedy with respect to the non payment of such principal amount under the Legacy Notes Indenture."5 It went on to state that, in its view, the CCH-held Notes would re-main "outstanding," and the lien would not spring. In an effort to create greater certainty as to that outcome, iHeart also initiated litigation in Texas state court6 seeking a declaratory judgment that the CCH-held Notes were still outstanding and would re-main outstanding until cancelled or repaid.

THE CREDIT EVENT QUESTION

While the status of the springing lien remains unresolved, CDS market participants sought a quick resolution as to whether iHeart's actions nevertheless constituted a Failure to Pay under the standard CDS contract. The DC concluded on December 21, 2016 that a Failure to Pay Credit Event had occurred on December 20, 2016 with respect to iHeart as a result of a Failure to Pay in respect of the Notes held by CCH.7 While this was not a typical Credit Event, with an issuer clearly in default on its debt obligations generally, the decision was reached unanimously and without the need for postponement for further deliberation. This may in part have been due to the fact that the question had already been debated in public filings submitted to the DC by law firms on either side of the question8 —a development that has increasingly become part of the CDS determination process for questions of controversy in the market.

In keeping with past practice, the DC did not detail its reasoning. In our view, once the facts were disclosed by iHeart, the FTP issue became straightforward. Under Section 4.5 of the Definitions, a Failure to Pay occurs when the Reference Entity fails to make a payment when and where due in accordance with the terms of the relevant Obligation. The key question in this case, then, was whether the terms of the Notes could have been considered to have been amended as a result of any agreements between, or other conduct of, iHeart and CCH, as holder of the remaining Notes, such that either the Notes were no longer outstanding or the $57.1 million was no longer due on the original due date.

On the first point, available public information continued to show that iHeart, CCH and the Notes trustee were treating the Notes as being outstanding.9 Had the Notes been held by iHeart itself, this might have been a more complex question, as an argument could have been made that the Notes would not be considered outstanding in bankruptcy (or, indeed, for certain other purposes); though we believe that, even then, the DC would likely have made the determination as to whether the Notes were still outstanding on the basis of a reading of the technical terms of the Notes.

On the second point, which was the one more directly argued in the Paul Weiss Memorandum and the Linklaters Memorandum, the DC apparently concluded that there was no evidence that the terms of the indenture had actually been amended, and there was therefore no reason to conclude that a Failure to Pay had been avoided. Although Linklaters argued that the agreement by CCH not to pursue remedies in respect of iHeart's non-payment should be read as a waiver of the Note holders' rights and there-fore a constructive amendment of the terms of the Notes, such forbearance agreements have never been construed by the DC as being equivalent to an amendment to the terms of the relevant obligation, except where there was an express agreement by all the relevant parties to do so.10 In this case, it appears that the DC adopted the view espoused by Paul Weiss, that a Failure to Pay could have been avoided had iHeart and the Notes trustee formally agreed to a supplemental indenture amending the maturity date of the CCH-held Notes. As iHeart's 8-K filings would have had to disclose any such amendments, the DC apparently concluded that no such amendment was made.11

Footnotes

1 See, e.g., the Failure to Pay question with respect to Caesars Entertainment Corporation, available at http://dc.isda.org/cds/caesars-entertainment-operating-company-inc-4/, and the Succession Event question with respect to Novo Banco, available at http://dc.isda.org/cds/novo-banco-s-a/, both of which led to External Review.

2 Capitalized terms used but not otherwise defined in this alert shall have the meanings given to them in the 2014 ISDA Credit Derivatives Definitions (the "Definitions").

3 News Release: "ISDA Selects Benchmark Administration as Determinations Committee Secretary" (Dec. 16, 2016), available at http://www2.isda.org/news/isda-selects-ice-benchmark-administration-as-determinations-committees-secretary.

4 iHeartCommunications, Inc.'s Current Report on Form 8-K (filed Dec. 13, 2016).

5 Id.

6 Petition for Declaratory Judgment filed in iHeartCommunications Inc., f/k/a Clear Channel Communications, Inc., et al. v. The Bank of New York

n/k/a The Bank of New York Mellon Corporation, No. 2016-CI-21289 (District Court of Bexar County,

TX, Dec. 12, 2016) (hereinafter "Declaratory Judgment Petition").

7 A Failure to Pay could not have occurred any earlier than December 20, 2016 because the Definitions im-posed a Grace Period of Three Business Days where none is provided in the terms of the relevant Obliga-tion.

8 Paul, Weiss, Rifkind, Wharton & Garrison LLP, argued that the non-payment of the CCH-held Notes was a Failure to Pay(See, Paul, Weiss, Rifkind, Wharton & Garrison LLP, Memorandum submitted to ISDA Credit Derivatives Determinations Committee re iHeart Communications, Inc. Failure to Pay Credit Event (Dec. 20, 2016), available at http://dc.isda.org/documents/2016/12/iheart-pai-dec-20.pdf, hereinafter, the "Paul Weiss Memorandum"), while Linklaters LP argued the opposite (See, Linklaters LP, Memorandum submitted to ISDA Credit Derivatives Determinations Committee re iHeart Communications, Inc. Failure to Pay Credit Event (Dec. 15, 2016), available at http://dc.isda.org/documents/2016/12/iheart-pai-dec-16.pdf, hereinafter, the "Linklaters Memorandum").

9 In paragraph 76 of the Declaratory Judgment Petition, iHeart explained: "The trustee and paying agent of the [Notes] maintains records of the notes outstanding and includes the notes held by [CCH] as outstand-ing. iHeart pays interest on the notes held by its subsidiaries in the same manner as it does other outstand-ing notes. The various trustees and agents of iHeart's other debt also treat and have historically treated debt held by iHeart subsidiaries as outstanding. In addition, the [Notes] have been listed as assets on the books and records of iHeart and its subsidiaries, including the financial statements of [CCH]."

10 Indeed, the Linklaters Memorandum would seem to make arguments contrary to its author's own published views: "On the other hand, if the creditors merely agree not to enforce their rights or demand payment . . . the due date for payment will remain the same and a default will occur if payment is not made on that date." Derivatives: Law and Practice, Simon Firth (Sweet & Maxwell 2003), at Section 2.3.

11 We note, though, that if an amendment had been made to the Notes, and if (as is not difficult to imagine) it were not possible to determine whether the relevant amendment had become effective as of the instant at which the relevant payment was first due, an interpretative question as to the proper reading of Section 4.5 of the Definitions might have arisen, as it unclear whether the terms of the Obligation must be construed before or after the relevant Grace Period.

To view the full report please click here.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.