XML 87 R19.htm IDEA: XBRL DOCUMENT
v3.19.3.a.u2

CONTINGENCIES | 6 Months Ended
--- | ---
Dec. 25, 2019
Commitments and Contingencies Disclosure [Abstract] |
Contingencies | Lease Commitments We have, in certain cases, divested brands or sold restaurants to franchisees and have not been released from lease guarantees for the related restaurants. As of December 25, 2019 and June 26, 2019, we have outstanding lease guarantees or are secondarily liable for $40.9 million and $55.3 million, respectively. These amounts represent the maximum potential liability of future payments under the leases. These leases have been assigned to the buyers and expire at the end of the respective lease terms, which range from fiscal 2020 through fiscal 2028. In the event of default under a lease by a franchisee or owner of a divested brand, the indemnity and default clauses in our agreements with such third parties and applicable laws govern our ability to pursue and recover amounts we may pay on behalf of such parties. Our secondary liability position was reduced approximately $9.3 million in the twenty-six week period ended December 25, 2019 due to certain leases associated with the acquisition of 116 restaurants from a franchisee, refer to Note 2 - Chili’s Restaurant Acquisition for details. Letters of Credit We provide letters of credit to various insurers to collateralize obligations for outstanding claims. As of December 25, 2019, we had $27.2 million in undrawn standby letters of credit outstanding. All standby letters of credit are renewable within the next 4 to 10 months. Cyber Security Incident On May 12, 2018, we issued a public statement that malware had been discovered at certain Chili’s restaurants that resulted in unauthorized access or acquisition of customer payment card data. We engaged third-party forensic firms and cooperated with law enforcement to investigate the matter. Based on the investigation of our third-party forensic experts, we believe most Company-owned Chili’s restaurants were impacted by the malware during time frames that vary by restaurant, but we believe in each case began no earlier than March 21, 2018 and ended no later than April 22, 2018. We expect to incur legal and professional services expenses associated with the cyber security incident in future periods, which could be material. We will recognize these expenses as services are received. Related to this incident, payment card companies and associations may request us to reimburse them for unauthorized card charges and costs to replace cards and may also impose fines or penalties in connection with the cyber security incident, and regulatory authorities may also impose fines or other remedies against us. While we do not acknowledge responsibility to pay any such amounts imposed by any third parties, we may become obligated to pay such amounts or incur significant related settlement costs. We have settled claims from two payment card companies, and the settlement amounts are included in the costs described in the following paragraph. We will record an estimate for any additional losses at the time when it is both probable that a loss has been incurred and the amount of the loss is reasonably estimable. To limit our exposure to cyber security events, we maintain cyber liability insurance coverage. This coverage and certain other insurance coverage may reduce our exposure for this incident. Our cyber liability insurance policy contains a $2.0 million retention that was fully accrued during fiscal 2018. Since the incident, through December 25, 2019, we have incurred total costs of $4.3 million related to the cyber security incident. This includes the $2.0 million retention recorded in fiscal 2018, an additional $0.4 million during fiscal 2019 for expenses not believed to be covered by our insurance coverage recorded to Other (gains) and charges in the Consolidated Statements of Comprehensive Income (Unaudited), $1.0 million in costs that have been reimbursed by our insurance carriers, and $0.9 million of receivable for costs incurred that we believe are reimbursable and probable of recovery under our insurance coverage. The Company was named as a defendant in a putative class action lawsuit in the United States District Court for the Middle District of Florida styled In re: Brinker Data Incident Litigation, Case No. 18-cv-00686-TJC-MCR (the “Litigation”) relating to the cyber security incident described above. In the Litigation, plaintiffs assert various claims stemming from the cyber security incident at the Company’s Chili’s restaurants involving customer payment card information and seek monetary damages in excess of $5.0 million, injunctive and declaratory relief and attorney’s fees and costs. On January 4, 2019, we filed a Motion to Dismiss all of plaintiffs’ claims asserting that plaintiffs do not have standing to bring the lawsuit and that plaintiffs have failed to state a claim on which relief can be granted. Following completion of briefing by the parties, the court conducted a hearing on our motion on June 24, 2019. On August 1, 2019, the court granted our Motion to Dismiss for lack of standing as to two plaintiffs and denied the motion as to the remaining plaintiffs. The court deferred its ruling on our argument that plaintiffs failed to state a claim on which relief could be granted pending further briefing. On August 16, 2019, the parties filed their Joint Notice of Choice of Law Briefing Preference. The Company represented that we are ready to move forward with briefing, but plaintiffs claimed that they require a significant amount of additional discovery before briefing can commence. On November 11, 2019, the Company filed a Motion for Protection seeking to limit the scope of some of plaintiffs’ discovery requests. On November 12, 2019, the court issued an order indicating that it would move forward with its ruling on our Motion to Dismiss without further briefing. It also stayed all pending discovery and depositions. Plaintiffs filed their response to our Motion for Protection on December 6, 2019 and we now await the Court’s order. We believe we have defenses and intend to continue defending the Litigation. As such, as of December 25, 2019, we have concluded that a loss from this matter is not determinable, therefore, we have not recorded a liability related to the Litigation. We will continue to evaluate this matter based on new information as it becomes available. Legal Proceedings Evaluating contingencies related to litigation is a complex process involving subjective judgment on the potential outcome of future events, and the ultimate resolution of litigated claims may differ from our current analysis. Accordingly, we review the adequacy of accruals and disclosures pertaining to litigated matters each quarter in consultation with legal counsel and we assess the probability and range of possible losses associated with contingencies for potential accrual in the Consolidated Financial Statements. We are engaged in various legal proceedings and have certain unresolved claims pending. Liabilities have been established based on our best estimates of our potential liability in certain of these matters. Based upon consultation with legal counsel, management is of the opinion that there are no matters pending or threatened which are expected to have a material adverse effect, individually or in the aggregate, on the consolidated financial condition or results of operations.

X
- References No definition available. + Details
Name: | us-gaap_CommitmentsAndContingenciesDisclosureAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure for commitments and contingencies. + References Reference 1: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 450 -URI http://asc.fasb.org/topic&trid=2127136 Reference 2: http://fasb.org/us-gaap/role/ref/legacyRef -Publisher FASB -Name Accounting Standards Codification -Topic 440 -URI http://asc.fasb.org/topic&trid=2144648 + Details
Name: | us-gaap_CommitmentsAndContingenciesDisclosureTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration