Chapter 2 — Loss Contingencies and Commitments
Chapter 2 — Loss Contingencies and Commitments
2.1 Overview
ASC 450 defines a loss contingency as “[a]n existing condition, situation, or set of
circumstances involving uncertainty as to possible loss to an entity that will
ultimately be resolved when one or more future events occur or fail to occur.”
Resolution of uncertainty in the context of a loss contingency may confirm the loss,
the impairment of an asset, or the incurrence of a liability. This chapter provides
an overview of the scoping, recognition, measurement, and disclosure requirements
for loss contingencies, along with certain interpretive guidance on accounting for
them.
Contingent liabilities are liabilities for which the possible loss
outcome is unknown or uncertain, such as pending or threatened litigation, actual or
possible claims, or product defects. Uncertainty is inherent in all loss
contingencies. The terms “probable,” “reasonably possible,” and “remote” in ASC
450-20 are used to determine the likelihood of the future event that will confirm a
loss, an impairment of an asset, or the incurrence of a liability. No quantitative
characteristics are provided in the codified definitions; accordingly, entities need
to exercise judgment when applying the terms.
Accrual of a loss contingency is required when (1) it is probable that a loss has
been incurred and (2) the amount can be reasonably estimated. An entity must
determine the probability of the uncertain event and demonstrate its ability to
reasonably estimate the loss from it to accrue a loss contingency. Loss
contingencies that do not meet both of these criteria for recognition may need to be
disclosed in the financial statements.
Typically, under the accounting literature, an entity uses either a
probability-based model or a fair value model when dealing with uncertainty related
to losses. The probability-based recognition guidance in ASC 450-20 differs from
that in other Codification topics under which an entity measures liabilities in
accordance with a fair value objective. To measure a liability at fair value, an
entity must consider events whose occurrence is less than probable. Therefore, a
fair value measurement will result in the recognition of a liability for a
conditional obligation for which the likelihood of future settlement, although more
than zero, is less than probable; a liability would not be recognized in this
situation under the guidance in ASC 450-20 that applies to loss contingencies.
2.1.1 Relationship Between Recognized Loss Contingencies and Reserves
As indicated in ASC 450-20-05-8 and 05-9, when accruing a loss contingency, an
entity does not create or set aside funds to lessen the possible financial
impact of a loss. ASC 450-20-05-8 states, in part:
Confusion
exists between accounting accruals (sometimes referred to as accounting
reserves) and the reserving or setting aside of specific assets to be used
for a particular purpose or contingency. Accounting accruals are simply a
method of allocating costs among accounting periods and have no effect on an
entity’s cash flow. Those accruals in no way protect the assets available to
replace or repair uninsured property that may be lost or damaged, or to
satisfy claims that are not covered by insurance, or, in the case of
insurance entities, to satisfy the claims of insured parties. Accrual, in
and of itself, provides no financial protection that is not available in the
absence of accrual.
In addition, ASC 450-20-05-9 states:
An
entity may choose to maintain or have access to sufficient liquid assets to
replace or repair lost or damaged property or to pay claims in case a loss
occurs. Alternatively, it may transfer the risk to others by purchasing
insurance. The accounting standards set forth in this Subtopic do not affect
the fundamental business economics of that decision. That is a financial
decision, and if an entity’s management decides to do neither, the presence
or absence of an accrued credit balance on the balance sheet will have no
effect on the consequences of that decision. Insurance or reinsurance
reduces or eliminates risks and the inherent earnings fluctuations that
accompany risks. Unlike insurance and reinsurance, the use of accounting
reserves does not reduce or eliminate risk. The use of accounting reserves
is not an alternative to insurance and reinsurance in protecting against
risk. Earnings fluctuations are inherent in risk retention, and they are
reported as they occur.
Further, in a manner consistent with ASC 450-20-50-1, which
requires entities to disclose the nature of recognized accruals, entities should
refrain from using the term “reserves” when referring to the accrual of a loss
contingency.
2.2 Scope
ASC 450-20
15-2 The
following transactions are excluded from the scope of this
Subtopic because they are addressed elsewhere in the
Codification:
- Stock issued to employees, which is discussed in Topic 718.
- Employment-related costs, including deferred compensation contracts, which are discussed in Topics 710, 712, and 715. However, certain postemployment benefits are included in the scope of this Subtopic through application of paragraphs 712-10-25-4 through 25-5.
- Uncertainty in income taxes, which is discussed in Section 740-10-25.
- Accounting and reporting by insurance entities, which is discussed in Topic 944.
- Measurement of credit losses for instruments within the scope of Topic 326 on measurement of credit losses.
All loss contingencies should be evaluated under ASC 450-20 unless
they are within the scope of other authoritative literature. The table below
contains a nonexhaustive list of examples of contingencies or uncertainties that are
within the scope of other authoritative literature.
The sections below address certain scope-related topics.
2.2.1 Firmly Committed Executory Contracts
Although the ASC master glossary does not define “executory contract,” an entity
may find the following considerations useful in assessing the meaning of this
term:
- Although never finalized and ultimately removed from the EITF’s agenda, EITF Issue 03-17 refers to an executory contract as “a contract that remains wholly unperformed or for which there remains something to be done by either or both parties of the contract.”
- IAS 37 refers to an executory contract as a contract “under which neither party has performed any of its obligations or both parties have partially performed their obligations to an equal extent.”
The ASC master glossary defines a firm purchase commitment as “an agreement with
an unrelated party, binding on both parties and usually legally enforceable,”
that is both (1) specific in “all significant terms, including the price and
timing of the transaction,” and (2) “includes a disincentive for nonperformance
that is sufficiently large to make performance probable.” Disincentives for
nonperformance may be, for example, in the form of (1) a fixed payment
requirement for each period under the agreement regardless of whether the
purchaser takes delivery or (2) the inability of a purchaser to change the
contractual delivery and payment terms with a supplier without a penalty payment
for nonperformance.
At the inception of a firmly committed executory contract, both parties to the
contract expect to receive benefits from the contract that are equal to or
greater than the costs to be incurred under the contract. However, during the
term of the contract, the fair value of the remaining contractual rights may
unexpectedly decline below the remaining costs to be incurred, resulting in a
firmly committed executory “loss contract.”
When determining whether to recognize a contingent liability for
such a loss contract, entities should first consider the applicability of any
industry- and transaction-specific guidance. Firmly committed executory
contracts addressed under U.S. GAAP include the following:
- A firm purchase commitment for goods or inventory under ASC 330.
- Construction or production-type contracts within the scope of ASC 605-35 (see Deloitte’s Roadmap Revenue Recognition for a discussion of onerous performance obligations).
- Certain executory contracts subject to ASC 420 related to exit or disposal activities.
- An insurance contract with a premium deficiency subject to ASC 944-60.
- Certain derivative contracts within the scope of ASC 815.
The EITF discussed loss recognition for all other firmly
committed executory contracts (i.e., contracts not otherwise within the scope of
authoritative literature that provides recognition and measurement guidance on
losses in accordance with firmly committed executory arrangements) from the
perspective of the (1) buyer and (2) seller. However, the EITF was unable to
reach a consensus on these issues because of their broad scope and recommended
that the FASB add a project on executory contracts to its agenda. Currently,
there is no authoritative accounting guidance, other than that referred to
above, that would support the recognition of a contingent liability when the
fair value of remaining contractual rights under a firmly committed executory
contract declines below the remaining costs to be incurred.
While the EITF did not provide authoritative guidance on the
recognition of a liability for a loss contract, on the basis of comments by the
SEC staff, it is generally inappropriate to accrue for a loss related to a
firmly committed executory contract unless there is specific authoritative
literature to the contrary. However, regardless of whether an entity has
recognized a liability related to a firmly committed executory contract, the
entity should consider the need for disclosure of the arrangement in the
financial statements to prevent the financial statements from being misleading.
In addition, SEC registrants should consider whether commitments related to
executory contracts should be included in their SEC Regulation S-K disclosures
(e.g., within MD&A). See Section 2.8.4 for a discussion of the disclosure requirements
for firmly committed executory contracts.
2.2.2 Application of ASC 450 to Employee Benefit Arrangements
Compensation to executives and employees in addition to base salary
or wages can take many forms, including (1) share-based payment arrangements; (2)
deferred compensation or bonus plans; and (3) postemployment benefit, postretirement
benefit, and special termination or early retirement plans. The specific accounting
requirements vary depending on the nature of the compensation arrangement. ASC 450
should be applied to certain compensation or benefit plans that are not specifically
addressed by other authoritative accounting literature (e.g., certain cash bonus
arrangements).
In addition, certain compensation arrangements are accounted for in
accordance with ASC 710 and not ASC 450 when specific conditions are met. For
instance, certain postemployment benefits within the scope of ASC 7121 that meet the following conditions as defined in ASC 710-10-25-1 are accounted
for in accordance with ASC 710-10:
- The employer’s obligation to provide an employee with postemployment compensation is attributed to the employee’s services already rendered.
- “The obligation relates to rights that vest or accumulate.”
- “Payment of the compensation is probable.”
- “The amount can be reasonably estimated.”
However, ASC 712-10-25-5 requires that certain postemployment benefits that do not
meet the above conditions be accounted for in accordance with ASC 450-20-25-2 when
the loss is probable and can be reasonably estimated.
Example 2-1
Postemployment
Benefits
Two weeks of workers’ compensation benefits
may be available to employees in the event of a disability.
Additional years of service do not result in an increased
workers’ compensation benefit. This type of nonvesting and
nonaccumulating postemployment benefit plan is accounted for
in accordance with ASC 450-20-25-2. Upon the occurrence of
the event that gives rise to the liability (i.e., the injury
that entitles the employee to disability benefits), the
associated estimated stream of future cash flows is accrued.
In contrast, ASC 712-10-25-4 requires that postemployment
benefits that vest or accumulate be accrued as service is
performed.
See Section 2.3.2.7 for a discussion of the recognition of
liabilities related to annual bonus plans.
2.2.3 Collectibility of Receivables
Entities must apply the current expected credit loss (CECL) model to
receivables and other financial instruments that are within the scope of ASC 326-20.
Under the CECL model, receivables that are expected to be uncollectible but do not
yet meet the “probable” threshold will result in recognition of losses. Accordingly,
credit losses resulting from receivables and other financial instruments within the
scope of ASC 326-20 are outside the scope of ASC 450-20. However, the incurred loss
model in ASC 450-20 continues to apply to certain financial instruments that are not
within the scope of ASC 326-20. For more information about the scope, recognition,
and measurement guidance in ASC 326-20, see Deloitte’s Roadmap Current Expected Credit
Losses.
2.2.4 Differentiating Between Contingent Liabilities and Contractual or Legal Liabilities
Contingent liabilities involve uncertainty about whether a loss has
been incurred and differ from contractual liabilities. Therefore, an entity must
distinguish between a contingent liability, which is within the scope of ASC 450-20,
and a contractual or legal liability, which is not. Contingent liabilities comprise
only liabilities in which an entity’s obligation to pay another entity is uncertain.
Contractual or legal liabilities are debts or obligations between two or more
parties that are typically settled by the transfer of cash, assets, or services; for
these liabilities, there is generally little to no uncertainty about the likelihood
of occurrence of the future settlement. A liability is not an unasserted claim or
assessment under ASC 450-20 if the settlement of the liability is required by law or
by contract.
Liabilities established by law or by contract are recorded at the
stated amounts due unless otherwise indicated in U.S. GAAP. The probability of
payment is not relevant to the accounting for such liabilities.2 If an entity is required by law, regulation, or contract to make a future
payment associated with an event that has already occurred, that event imposes a
present duty upon the entity. An entity’s uncertainty about whether an obligee will
require performance does not allow the entity to choose to avoid the future
sacrifice, nor does the uncertainty relieve the entity of the obligation. That is,
when the obligating event has occurred, the entity has incurred a liability;
accordingly, there is no contingency. For example, an entity must recognize accounts
payable on the basis of the amount that it is contractually required to pay. The
entity may not recognize accounts payable on the basis of the amount that it would
expect to ultimately pay if the creditor filed suit to collect the liability. This
conclusion is supported by analogy to ASC 410-20-25-15, which states that an
“unambiguous requirement that gives rise to an asset retirement obligation coupled
with a low likelihood of required performance still requires recognition of a
liability.” Once recognized, a contractual or legal liability that is not deferred
revenue (i.e., a contract liability under ASC 606) should be derecognized only when
the conditions for liability derecognition in ASC 405-20-40-1 have been met.
ASC 405-20
40-1 Unless addressed by other
guidance (for example, paragraphs 405-20-40-3 through 40-4
or paragraphs 606-10-55-46 through 55-49), a debtor shall
derecognize a liability if and only if it has been
extinguished. A liability has been extinguished if either of
the following conditions is met:
- The debtor pays the creditor and is
relieved of its obligation for the liability. Paying
the creditor includes the following:
- Delivery of cash
- Delivery of other financial assets
- Delivery of goods or services
- Reacquisition by the debtor of its outstanding debt securities whether the securities are cancelled or held as so-called treasury bonds.
- The debtor is legally released from being the primary obligor under the liability, either judicially or by the creditor. For purposes of applying this Subtopic, a sale and related assumption effectively accomplish a legal release if nonrecourse debt (such as certain mortgage loans) is assumed by a third party in conjunction with the sale of an asset that serves as sole collateral for that debt.
A contractual or legal liability is subject to the above liability
derecognition guidance regardless of whether an entity believes that, on the basis
of a probability assessment, such a liability can be settled for less than the
stated legal obligation.
The examples below illustrate the accounting for a liability for
which payment is required by law or contract but detection and settlement are
uncertain.
Example 2-2
Probability Assessment
Related to Sales Tax Liability for Which Payment Is
Required by Law but Detection and Settlement Are
Uncertain
Entity Z has sold goods in Jurisdiction Y
for 15 years and continues to sell them. By law, those sales
would be subject to sales tax in Y if Z had nexus there. To
assess whether Z has sales tax nexus in Y and should record
a sales tax liability, Z diligently reviews prior-period
sales records and interviews sales managers. Through this
analysis, Z determines and documents that sales tax nexus in
Y has existed for the past 15 years. Therefore, Z’s products
have always been taxable and subject to sales tax
collection; however, Z has never collected sales tax or
filed sales tax returns in Y. Entity Z has never been
audited or contacted regarding a sales tax audit by tax
authorities in Y. Entity Z believes that the risk of
detection by the tax authorities in Y is low. However, if
the tax authorities in Y were presented with all the facts
about Z’s activities, Z believes that it is probable that Y
would assert that Z is liable for uncollected sales taxes
and demand payment. Entity Z believes that Y would settle
for an amount less than the full liability.
Entity Z should record a sales tax liability
on the basis of its sales activities for the full amount
that it is legally obligated to remit to the tax authorities
in Y. The sale of goods triggers the obligation to make the
related sales tax payments. In measuring its sales tax
liability, Z may not consider that the risk of detection by
the tax authorities in Y is low. Further, Z must assume that
the tax authorities in Y have all the relevant facts about
Z’s operations in Y. Interest and penalties should also be
included in the estimate of the liability if the imposition
of interest and penalties is required by law.
Note that some state tax authorities may
have a widely understood administrative practice and
precedent in which, in the event of an examination and in
the absence of a voluntary disclosure agreement, the tax
authority would look back no more than a certain number of
years to determine the amount of sales tax deficiency due.
Alternatively, a statute of limitations may exist. Thus, Z
should evaluate whether the tax authorities in Y will assess
Z back to the first year of taxable sales (i.e., the full 15
years) or whether the liability will be limited by a statute
of limitations or Y’s administrative policies. In performing
this evaluation, Z must use judgment to determine what
constitutes “widely understood.” If Z asserts that an
administrative practice and precedent is widely understood,
Z should document the basis of that assertion as well as any
evidence to support it. Such evidence may include reliable
knowledge of the tax authority’s past dealings with Z on the
same tax matter when the facts and circumstances were
similar. An assessment of what Z believes it could negotiate
as a settlement with the tax authority would generally not
represent a “widely understood” administrative practice and
precedent.
Similarly, Z should also adjust its
liability to the extent that its customers have paid use tax
on any portion of Z’s sales during any part of the look-back
period. However, because the obligating event is the sale of
goods, Z should not record a sales tax liability for future
sales until those sales actually occur.
Entity Z should regularly assess its sales
tax obligations in the jurisdictions in which it conducts
business. If Z has any uncertainty about those obligations,
Z might need to obtain legal opinions. Sales tax liabilities
should be adjusted upward as sales are made and should be
adjusted downward only when the liability is paid or
otherwise extinguished. (Note that sales taxes are not
within the scope of ASC 740.)
Example 2-3
Royalty Liability for
Which Payment Is Required by Contract but Detection and
Settlement Are Uncertain
Company Y manufactures technical equipment
and has a contractual obligation to pay, on the basis of
sales volume, royalties to various patent holders. The
amount of royalties paid each period is calculated by Y. In
accordance with this obligation, patent holders have the
right to audit Y’s sales volume, but they have rarely
exercised this right.
Company Y should record a royalty liability
for the full amount that it is contractually obligated to
pay according to the royalty agreements. The contracts
require Y to make royalty payments on the basis of sales
volume. Therefore, Y is under an obligation to the patent
holders as the equipment is sold (i.e., Y has a present duty
to the patent holders). The liability should be adjusted
upward as sales are made and should be adjusted downward
only when the liability is paid or otherwise extinguished in
accordance with ASC 405-20-40-1.
In a scenario in which a patent holder
cannot be located, Y should consider whether liability
derecognition has occurred once the escheat laws of the
relevant jurisdiction are complied with and the obligation
no longer exists. Company Y’s uncertainty about whether a
patent holder will audit the sales volume does not allow it
to avoid future payment. Finally, Y should not record a
royalty liability for future sales until those sales
actually occur.
Connecting the Dots
There may be uncertainty about whether an entity is subject to or within the
scope of a current law, regulation, or contract owing to ambiguity about the
interpretation of the current law, regulation, or contract. Examples include
uncertainties related to a tax based on gross receipts, revenue, or capital.
In these circumstances, an entity should evaluate the uncertainty in
accordance with the flowchart below.
The example below illustrates the analysis an entity would perform
in determining whether (1) it has a liability that is subject to contract, law, or
regulation or (2) the uncertainty should instead be accounted for in accordance with
ASC 450-20.
Example 2-4
Determining Whether an
Entity Is Subject to a Disputed Contractual Executory
Agreement
Company B manufactures and sells glass
containers for beverages and food. On January 6, B enters
into a contractual agreement with Vendor T to develop an
inventory management system, customized to B’s specific
needs. It is estimated that the project will take 18 months
and will cost $1.5 million, payable in equal quarterly
installments or $250,000 for services provided to date. The
agreement can be terminated only for cause and includes no
termination penalty; however, B will be liable for $1.5
million unless T breaches the contract.
Six months into the system development,
despite assurance provided by T, B realizes that the system
T is developing will not be able to perform certain
functions B deems essential to a new glass bottle
manufacturing and distribution inventory management system.
On September 1, before the third quarterly installment is
due to T for services performed to date, B’s legal counsel
sends a breach of contract notice to T. The notice indicates
that B is not receiving the inventory management system it
had contracted for. Upon receipt of the notice, T ceases
performing all services on September 1. Because B has
terminated the executory contract with T by providing a
breach of contract notice, and T has ceased performing
services, as of the third quarter ended September 30, B
determines that it is not contractually obligated for any
remaining unpaid amounts in accordance with the contract for
unperformed services. Accordingly, B compensates T for
third-quarter services received through September 1. Company
B will separately assess, in accordance with ASC 450-20,
whether a contingent liability exists for amounts that would
have otherwise been due (through either September 30 or the
end of the 18-month contract term) if the contract had not
been terminated. If B determines that T is disputing the
termination of the executory contract, B should determine
whether the contingent liability recognition criteria have
been met in accordance with ASC 450-20-25 and should provide
adequate disclosures related to the contract and
dispute.
2.2.5 Elements of a Litigation Settlement
There may be litigation settlements in which the settlement
agreement includes past obligations and disputes and modifies the ongoing
contractual terms of the business relationship. When accounting for a litigation
settlement that also includes a separate element (such as a revenue element) and
bifurcating the elements, an entity should consider a speech made by Eric West, associate chief accountant in the
SEC’s Office of the Chief Accountant, at the 2007 AICPA Conference on Current SEC
and PCAOB Developments. We consider the interpretive guidance shared by Mr. West to
be relevant and useful to private companies in addition to SEC registrants. Mr. West
summarized a settlement arrangement as follows:
[A] company pays
cash and conveys licenses to a plaintiff in order to settle a patent
infringement and misappropriation of trade secrets claim. In exchange for the
payment and licenses given, the company receives a promise to drop the patent
infringement lawsuit, a covenant not to sue with respect to the misappropriation
of trade secrets claim, and a license to use the patents subject to the
litigation.
Mr. West noted that the different elements of the arrangement should
be identified and that an entity will need to understand the nature of each item to
make this identification. In addition to the litigation settlement component, there
could be recognizable intangible assets related to the covenant not to sue and for
patent licenses received. Regarding the license to patents given to the plaintiff,
Mr. West noted:
If the licenses are expected to be used by the
plaintiff in their operations, it may be appropriate for the company to
recognize revenue or income with a corresponding increase in litigation
settlement expense. However, if the licenses are given as part of a litigation
defense strategy and don’t have value to the plaintiff, it seems unlikely that
any revenue should be recognized.
With respect to the amount of consideration to allocate to each element of the
transaction, Mr. West noted the following:
While EITF 00-21 was written for
multiple element revenue arrangements, we believe that its allocation guidance
is also useful to determine how to allocate consideration paid in a multiple
element legal settlement. In this regard, we believe that it would be acceptable
to value each element of the arrangement and allocate the consideration paid to
each element using relative fair values. [Footnote omitted]
Even though Mr. West was speaking about the separation guidance in EITF Issue 00-21, which was codified in ASC 605-25 and has been superseded by ASC
606, it is still appropriate for an entity to consider the principles of separation
of performance obligations within the context of the revenue guidance in ASC 606.
Specifically, as shown below, ASC 606 includes guidance on how to allocate
consideration to different elements of a contract with a customer that are partially
within the scope of ASC 606 and partially within the scope of another topic.
ASC 606-10
15-4 A contract with a customer
may be partially within the scope of this Topic and
partially within the scope of other Topics listed in
paragraph 606-10-15-2.
- If the other Topics specify how to separate and/or initially measure one or more parts of the contract, then an entity shall first apply the separation and/or measurement guidance in those Topics. An entity shall exclude from the transaction price the amount of the part (or parts) of the contract that are initially measured in accordance with other Topics and shall apply paragraphs 606-10-32-28 through 32-41 to allocate the amount of the transaction price that remains (if any) to each performance obligation within the scope of this Topic and to any other parts of the contract identified by paragraph 606-10-15-4(b).
- If the other Topics do not specify how to separate and/or initially measure one or more parts of the contract, then the entity shall apply the guidance in this Topic to separate and/or initially measure the part (or parts) of the contract.
Connecting the Dots
In an agreement that contains a settlement of a litigation
component and a revenue contract with a customer, an entity should bifurcate
the revenue element and the nonrevenue element (i.e., litigation) and
allocate the consideration to both elements in a manner consistent with Mr.
West’s remarks and ASC 606. There may be situations in which the entity has
clear, compelling evidence that there is little to no value related to the
litigation settlement; in those situations, the entire arrangement should be
accounted for as a single element under ASC 606. When the entity determines
that the entire arrangement should be accounted for as a single element
under ASC 606, it may be appropriate to allocate consideration for the
entire arrangement to the revenue element; however, the entity should not
apply the residual method and allocate all of the proceeds to the revenue
element by default..
The discussion above applies to both gain and loss
contingencies that are settled by entering into a revenue contract with a
customer. See Chapter
3 of Deloitte’s Roadmap Revenue Recognition for further
discussion of contracts that include both revenue and nonrevenue elements.
Chapter 7
of Deloitte’s Roadmap Revenue Recognition addresses estimating
stand-alone selling prices, including application of the residual
method.
Further, the same allocation principle applies when the
settlement does not contain a revenue element and is therefore entirely
outside the scope of ASC 606 (i.e., the settlement is not with a customer,
and none of the components constitute an output of the entity’s ordinary
activities). In those circumstances, an entity should still consider the
allocation principle described in Mr. West’s remarks and ASC 606 by
analogy.
2.2.6 Incurrence of a Future Cost of Doing Business
The incurrence of an obligation may represent the settlement of a past liability or a
future cost of doing business. The settlement of a lawsuit by agreeing to make a
cash payment in the absence of other elements of the settlement clearly represents
the settlement of a past liability that should be accrued immediately. Signing an
employment contract that guarantees an executive a fixed salary clearly represents a
future cost of doing business that should be accrued as the executive performs
service. However, it is not always clear how to distinguish between settlement of a
past liability and the incurrence of a future cost of doing business. Companies
sometimes settle litigation by altering the terms of future business arrangements,
which calls into question whether a present liability has been incurred.
Accordingly, an entity must consider all facts and circumstances to determine whether
an obligation represents the settlement of past liabilities or a cost of doing
business in the future. Sometimes it can be argued that the facts and circumstances
support both views, as demonstrated in the example below.
Example 2-5
Differentiating Between Settlement of a Past Liability and
a Future Cost of Doing Business
The Coal Industry Retiree Health Benefit Act of 1992 (the
“Act”) imposed a requirement on certain entities in the coal
industry to make payments to fund medical and death benefits
for retirees. ASC 930-715-25-1 states that “[e]ntities that
currently have operations in the coal industry shall account
for their obligation under the Act . . . either as
participation in a multiemployer plan,” which would be
expensed as payments are made, “or [as] a liability imposed
by the Act,” which would be accrued immediately. The
decision to allow such an accounting choice reflects the
difficulty of differentiating between the settlement of a
past liability and the incurrence of a future cost of doing
business.
The incurrence of a future cost of doing business is often indicated
by a payment stream that is contingent on the future sale of products or services in
the ordinary course of business (e.g., royalties due to a licensor for the license
and use of intellectual property). The future sale would be considered the event
giving rise to the liability. Additional evidence that a payment is, in substance, a
future cost of doing business is the inability to currently estimate the amount. It
may not be possible to reasonably estimate a payment that is contingent on a measure
such as future sales volume. Thus, a future cost of doing business would often fail
to qualify for recognition under ASC 450-20-25-2 because the obligating event has
not yet occurred, the amount is not reasonably estimable, or both.
Example 2-6
Liability Settled by
Incurring a Future Cost of Doing Business
A group of entities in the tobacco industry
settles litigation with a governmental body by agreeing to
higher future taxation. Under the terms of the agreement,
each company in the industry will pay a portion of the
settlement in proportion to its respective market share in
the preceding year. If a company exits the tobacco industry,
no additional payments are due.
The terms of the agreement specifically
preclude payment of the settlement out of existing assets;
rather, payments must be funded through future increases in
product prices. Because the settlement costs will be passed
through to the end consumer, the event giving rise to the
liability is the sale of products during future periods. No
present obligation has been incurred given that the tobacco
company could exit the tobacco industry immediately and
avoid the settlement payment. As a result, a liability
should be recorded when sales occur in the following year on
the basis of a pro rata portion of the following year’s
annual payment to the governmental body.
An entity may sometimes agree to settle a claim by agreeing to offer
the claimant(s) a price concession on future purchases of the entity’s goods or
services by the claimant(s). In such a scenario, the claimant(s) will be required to
make an independent future purchasing decision to realize the benefit of the
settlement. An entity that is obligated to provide such price concessions in
connection with a settlement will need to assess whether the settlement (1)
represents a liability that should be currently recognized for the estimated
settlement amount or (2) should be accounted for as a sales incentive in accordance
with ASC 606, which generally results in the entity’s accounting for the sales
incentive at the time the claimant or claimants use the price concession in
connection with the purchase of the entity’s goods or services.
While an entity may need to use significant judgment to determine
the appropriate accounting, a settlement with an existing customer (or group of
customers) that entitles such customer(s) to future price concessions for goods or
services, when the entity believes on the basis of compelling evidence that such
customer(s) would have purchased the goods or services in the absence of the
concession, could lead the entity to conclude that liability recognition is
appropriate provided that a reasonable estimate can be made. Alternatively, a
settlement with a claimant or claimants for future price concessions of the entity’s
goods or services, when there was no preexisting customer/vendor relationship, may
represent a situation in which such a settlement is in substance more akin to a
future price concession that should be accounted for in accordance with ASC 606
rather than a settlement of a prior liability. If the former view was taken for such
a fact pattern (i.e., the settlement is accounted for as a liability), the entity
may nonetheless conclude that it is unable to reasonably estimate the future price
concession (e.g., in a circumstance in which there is an insufficient sales history
with the claimant(s) or the concession is stated as a percentage of future sales of
an unknown quantity), meaning that not all of the recognition criteria in ASC
450-20-25-2 are met. Irrespective of when the future price concession is accounted
for, any settlement with a customer or a vendor would need to be evaluated in
accordance with ASC 606 or ASC 705-20, respectively, regarding the income statement
presentation of the settlement. See below for further discussion of the income
statement presentation for settlements with customers and vendors.
2.2.6.1 Income Statement Classification for Settlements With Customers and Vendors
When determining the appropriate income statement classification
of a litigation settlement with a counterparty that is a customer, the entity
should first look to the guidance on consideration payable to a customer in ASC
606-10-32-25 through 32-27 to determine whether the consideration is for a
distinct good or service for which the entity can reasonably estimate fair value
and, if so, classify such settlement payments in accordance with applicable U.S.
GAAP. Similarly, when a litigation settlement involves a counterparty that is a
vendor, the entity must consider ASC 705-20 to determine the appropriate income
statement presentation of the settlement.
When the settlement counterparty is a customer or a vendor and
the entity is able to determine the distinct litigation settlement benefit and
can reasonably estimate the fair value of the litigation settlement benefit, the
entity may recognize some or all of the settlement amount as an expense. To
determine the appropriate amount to recognize as an expense, entities should
consider the factors discussed in a speech made by Eric West, associate chief
accountant in the SEC’s Office of the Chief Accountant, at the 2007 AICPA
Conference on Current SEC and PCAOB Developments. Mr. West summarized the
classification of a settlement arrangement as follows:
Classification of the
Settlement
In the fact pattern that I’ve talked about so far it
would be appropriate to record the consideration allocated to the
litigation within operating expenses since the company did not have a
prior relationship with the plaintiff. However, we believe that a
different answer may result if the plaintiff is also a customer of the
defendant. Assume a company settles a claim for over
billing its customers for an amount that is in excess of the amounts
they over billed. The company believed that the excess payment was
necessary to preserve the customer relationship and had induced the
customer to settle the claim. In this case we do not believe that
classification of the entire payment as a settlement expense would
be consistent with existing GAAP. Since the settlement payment was
made to the company’s customers, we believe that the payment is
within the scope of EITF 01-9. [Footnote omitted] As you may know, this EITF addresses the accounting
for consideration given by a vendor to a customer. The scope is
broadly written and includes all consideration given by a vendor to
a customer. It also requires that cash consideration paid be
classified as a reduction of revenues unless the vendor receives an
identifiable benefit and the fair value of that benefit can be
reliably measured. In this fact pattern, we believe that the excess amount paid to the customer represents both a payment to retain the customer and settle the litigation. However, if the company is unable to determine the fair value of each of these components, we believe that EITF 01-9 requires the entire payment to be classified as a
reduction of revenues. Had the company been able to
directly value the litigation, classification of that portion of the
settlement payment as an expense may have been appropriate.
[Emphasis added]
Even though Mr. West was speaking about the guidance in EITF Issue 01-9 on consideration payable to a customer, which was codified in ASC
605-25 and has been superseded by ASC 606, it is still appropriate for an entity
to consider the principles outlined in the speech since the principle underlying
the guidance in ASC 605-25 remains relatively consistent under ASC 606. Mr. West
acknowledged that classification of a litigation component as an expense is
appropriate in certain circumstances, specifically when (1) a prior
customer/vendor relationship with the plaintiff does not exist or (2) a prior
customer/vendor relationship does exist and the vendor receives an identifiable
benefit for which the fair value of that benefit can be reliably measured.
Further, in evaluating the income statement classification of a litigation
settlement in situations in which the counterparty is a vendor or customer, the
entity should consider whether the settlement amount was based on an agreed-upon
formula (e.g., whether it was based on total product sales to a customer or
supplies purchased from a vendor) in such a way that there is a direct and
observable correlation between the settlement amount and the previous revenue or
purchase transaction. Such a correlation may be an indication that the
settlement amount should be recognized as an adjustment to the transaction price
received from a customer or to the cost of goods or services purchased from a
vendor.
If settlement consideration payable to a customer is in exchange
for a distinct good or service but the fair value cannot be reasonably
estimated, the settlement consideration should be recognized entirely as a
reduction in transaction price. For example, in a litigation settlement with a
customer, an entity may determine that an element of the consideration pertains
to settling the litigation and therefore is representative of a distinct
benefit. The entity may have historical experience in settling similar cases and
therefore may be able to readily determine the distinct litigation settlement
benefit; however, unless the entity can reasonably estimate the fair value of
the litigation settlement element, the entire settlement amount should be
accounted for as a reduction in transaction price. For more information about
consideration payable to a customer, see Chapter 6 of Deloitte’s Roadmap Revenue
Recognition.
Similarly, regarding classification of the settlement when
payments are received from a vendor, entities should consider ASC 705-20, as
discussed in Chapter
6 of Deloitte’s Roadmap Revenue Recognition, as well as the
gain contingency recognition guidance addressed in Chapter 3 of this Roadmap.
Footnotes
1
See ASC 712-10-15-3 and 15-4 for a discussion of
transactions that could be subject to the scope of ASC 710.
2
For example, the issue of how an entity should account for
uncertain tax positions and breakage when a customer is not expected to
exercise all of its contractual rights to goods or services in a revenue
contract is specifically addressed in U.S. GAAP. Chapter 4 of Deloitte’s Roadmap
Income Taxes
addresses uncertain tax positions. Section 8.8 of
Deloitte’s Roadmap Revenue Recognition addresses breakage associated
with certain revenue contracts.
2.3 Recognition
ASC 450-20
25-1 When a loss contingency
exists, the likelihood that the future event or events will
confirm the loss or impairment of an asset or the incurrence
of a liability can range from probable to remote. As
indicated in the definition of contingency, the term
loss is used for convenience to include many
charges against income that are commonly referred to as
expenses and others that are commonly referred to as losses.
The Contingencies Topic uses the terms probable,
reasonably possible, and remote to
identify three areas within that range.
25-2 An estimated loss from a
loss contingency shall be accrued by a charge to income if
both of the following conditions are met:
- Information available before the financial statements are issued or are available to be issued (as discussed in Section 855-10-25) indicates that it is probable that an asset had been impaired or a liability had been incurred at the date of the financial statements. Date of the financial statements means the end of the most recent accounting period for which financial statements are being presented. It is implicit in this condition that it must be probable that one or more future events will occur confirming the fact of the loss.
- The amount of loss can be reasonably estimated.
The purpose of those conditions is to
require accrual of losses when they are reasonably estimable
and relate to the current or a prior period. Paragraphs
450-20-55-1 through 55-17 and Examples 1–2 (see paragraphs
450-20-55-18 through 55-35) illustrate the application of
the conditions. As discussed in paragraph 450-20-50-5,
disclosure is preferable to accrual when a reasonable
estimate of loss cannot be made. Further, even losses that
are reasonably estimable shall not be accrued if it is not
probable that an asset has been impaired or a liability has
been incurred at the date of an entity’s financial
statements because those losses relate to a future period
rather than the current or a prior period. Attribution of a
loss to events or activities of the current or prior periods
is an element of asset impairment or liability
incurrence.
When an entity obtains information before the financial statements
are issued or available to be issued, indicating that it is probable that a future
event will confirm a financial statement loss that occurred on or before the date of
the financial statements, the entity should accrue such a loss contingency provided
that the loss can be reasonably estimated.
The flowchart below outlines the criteria for recognition of a
contingent liability, taking into consideration all information about the loss that
becomes available before the financial statements are issued (or are available to be
issued).
A contingent liability is not recognized when either (1) it is not
probable that a future event will confirm that a loss had been incurred on or before
the date of the financial statements or (2) the amount of the loss is not reasonably
estimable. The entity should carefully evaluate whether appropriate disclosure is
necessary to keep the financial statements from being misleading. See additional
disclosure requirements in Section 2.8.
2.3.1 Assessing the Probability of Whether a Loss Has Been Incurred
2.3.1.1 “Probable,” “Reasonably Possible,” and “Remote”
For an entity to recognize a loss contingency under ASC 450-20,
it must be probable that one or more future events will occur or fail to occur,
thereby confirming a loss. In the ASC 450-20 glossary, loss contingencies are
categorized on the basis of the likelihood of occurrence as follows:
ASC 450-20 — Glossary
Probable
The future event or events are likely to
occur.
Reasonably
Possible
The chance of the future event or events
occurring is more than remote but less than likely.
Remote
The chance of the future event or events
occurring is slight.
Although ASC 450-20 defines each of these terms, it provides no
quantitative thresholds. The word “probable” is not intended to mean that
virtual certainty is required before a loss is accrued. However, “likely to
occur” is a higher threshold than “more likely than not,” which is generally
considered as indicating a chance of occurrence of more than 50 percent.
While no codified guidance defines the quantitative thresholds,
an entity that is evaluating these thresholds may find it useful to consider
interpretive guidance from paragraph 160 of AICPA Statement of Position 96-1,
which states, in part:
If the FASB Statement No. 5 criteria
of remote, reasonably possible, and probable were mapped onto a range of
likelihood of the existence of a loss spanning from zero to 100 percent, the
reasonably possible portion would span a significant breadth of the range
starting from remote and ending with probable.
“Probable” is discussed in paragraph 49 of the Background Information and Basis for Conclusions of FASB Statement 114, which states, in
part:
“ ‘[P]robable’ . . . has, in the case of banks,
come to mean ‘virtually certain,’ rather than ‘more likely than not,’ ” and
“the ‘probable’ requirement as it is sometimes applied has unduly delayed
loss recognition . . . of problem assets.” The Board did not intend
“probable” to mean “virtually certain to occur.” The Statement 5 definition
of probable states that “the future event or events are likely to
occur” (emphasis added). The Board recognizes that application of
the term probable in practice requires judgment, and to clarify its intent
the Board has reiterated the guidance in paragraph 84 of Statement 5 in
paragraph 10 of this Statement. The term probable is used in this Statement
consistent with its use in Statement 5. This Statement does not specify how
a creditor should determine that it is probable that it will be unable to
collect all amounts due according to a loan’s contractual terms.
In addition, the SEC’s November 16, 2011, staff paper comparing
U.S. GAAP with IFRS® Accounting Standards states the following
regarding the quantitative threshold used to recognize environmental
obligations:
Both IFRS and U.S. GAAP contain a
“probable” threshold for the recognition of an environmental liability.
Probable within IFRS is defined as more likely than not (i.e., more than
50%), whereas probable is not as clearly defined under U.S. GAAP (but is
interpreted in this context to be a percentage somewhat greater than
50%).
ASU
2014-15 discusses “probable” in the context of determining
what constitutes substantial doubt about an entity’s ability to continue as a
going concern. In ASU 2014-15, the FASB observes that “probable” in the ASC
master glossary’s definition of “substantial doubt about an entity’s ability to
continue as a going concern” carries the same meaning that it does in ASC 450’s
definition of the word. The ASU’s general discussion of a Board member’s
dissenting view indicates, in part:
As mentioned in
paragraph BC17, a commonly cited academic paper (Boritz, 1991) noted that
the threshold for the substantial doubt likelihood of an entity being unable
to meet its obligations is between 50 and 70 percent. The guidance in this
Update increases that threshold to probable, which many assert as being in
the 70–75 percent range.
While there is diversity in practice related to the likelihood
percentage that “probable” represents, in a manner consistent with the
discussion in ASU 2014-15, the threshold for “probable” would need to be at
least 70 percent. Further, although the term “remote” is not discussed
quantitatively in any guidance issued by the FASB, it is used in practice to
indicate a likelihood of 10 percent or less.
A loss contingency is recognized only when the likelihood of a
future event’s occurrence indicates that it is probable that a loss has occurred
(provided that the loss contingency is also reasonably estimable). If the
likelihood of a future event’s occurrence is only reasonably possible, entities
should provide appropriate disclosures in accordance with ASC 450-20-50,
although loss accrual is not appropriate. For events for which the likelihood
that a loss has been incurred is remote, recognition is not appropriate and
disclosure is not required under ASC 450-20; however, entities should use
judgment in determining whether omitting disclosures would cause the financial
statements to be misleading. See Section 2.8 for disclosure
considerations.
Entities may need to consider various factors and use
significant judgment in determining the likelihood of a future event’s
occurrence or nonoccurrence that will confirm whether a loss has been incurred
on the date of the financial statements. Specifically, in the case of class
action lawsuits or litigation, an entity may need to consider (among other
things) the opinion of in-house or external legal counsel, the entity’s history
and experience with similar cases, prior case law, how the entity intends to
respond, and the nature of the settlement mechanism.
Certain contingencies are not considered probable until the
underlying future events occur because of various external factors associated
with the determination of the probability threshold. Examples of such underlying
future events include casualty events, the enactment of proposed legislation,
the successful completion of an initial public offering (IPO), and the
occurrence of a business combination, all of which are discussed below.
2.3.1.2 Occurrence of a Business Combination or Successful Completion of an IPO
Certain liabilities are contingent on the occurrence of a
business combination or the completion of an IPO. For example, an amount may be
payable upon completion of an IPO, or a restructuring plan may be adopted upon
consummation of a business combination.
There are many external factors and uncertainties that can
affect the successful completion of an IPO or the consummation of a business
combination. These external factors and uncertainties make it difficult to
determine whether the probability threshold has been met before the effective
date of an IPO or a business combination. Therefore, the incurrence of a
liability contingent on an IPO or a business combination cannot be considered
probable until the transaction is completed. This position does not affect or
apply to freestanding derivative contracts or embedded derivative features that
are within the scope of ASC 815 (e.g., a put option contingent on an IPO).
A business combination is an event for which discrete accounting
is required when the combination is consummated. Accordingly, when the
occurrence of a liability is contingent on the completion of a business
combination, one of the events that obligates the entity and therefore gives
rise to the liability has not occurred until the combination has occurred.
Because of the uncertainties involved in, and the discrete nature of, business
combinations, a liability should not be accrued until the business combination
is consummated.3
However, in certain situations, a liability may exist even if a
proposed business combination is not consummated. The fact that an entity has
agreed to settle a preexisting litigation matter as a condition to completing
such a business combination does not necessarily mean that the contingent
liability should be recognized only on completion of the business combination.
See further discussion in Example 2-7.
Example 2-7
Settlement of
Litigation in Conjunction With a Business
Combination
Company A has entered into a proposed merger with Company
B for which the approval of the U.S. Department of
Justice (DOJ) is required. Before the proposed merger,
the DOJ asserted that A is liable for false claims made
against a department of the U.S. government. While A is
contesting the lawsuit on the basis that it is not
guilty of the DOJ’s allegations, if A loses the lawsuit,
it could be subject to civil penalties and damages of up
to $200 million.
The DOJ has informed A that it will not approve the
merger until the lawsuit with A is resolved. Further,
the DOJ has offered to settle the lawsuit with A for $50
million; such settlement will occur coterminously with
the closing of the merger. If, however, the merger does
not close, A is not obligated to settle the lawsuit for
$50 million and would continue to defend itself against
the lawsuit. In such cases, the outcome would be
uncertain.
For financial reporting periods ending before completion
of the business combination with B, it would not be
acceptable for A to avoid recognizing a liability for
the lawsuit solely on the basis that it is contingent on
the merger with B. This is because the lawsuit is
unrelated to the proposed merger. Rather, A should
consider all facts and circumstances related to the
case, including the settlement offer, in determining the
amount (if any) to recognize as a contingent liability
for the lawsuit.
2.3.1.3 Proposed Legislation
The enactment of legislation by a governmental authority may
give rise to a liability. In some circumstances, a company may expect that
pending legislation will give rise to a liability upon enactment. However, a
liability should not be accrued in advance of enactment even if the entity
believes such enactment to be probable. Future laws or changes in laws should
not be anticipated when an entity is accruing a liability in accordance with ASC
450-20-25-2. Before enactment of a law, the specific content of the final law is
uncertain. Substantive changes to the law may materially affect the nature,
timing, and extent of resources a company will be required to expend. The
accounting for liabilities should reflect the provisions of enacted laws on a
jurisdiction-by-jurisdiction basis. This treatment is consistent with the
guidance on changes in income tax laws in ASC 740.
Connecting the Dots
The enactment date is the date on which all steps in the
process for legislation to become law have been completed (e.g., in the
United States, this could be the case when the president signs the
legislation and it becomes law). For rules and regulations issued by
federal regulatory agencies to implement enacted U.S. laws, the
enactment date is generally the date on which final rules or regulations
promulgated by the federal regulatory agency are published in the
Federal Register, which may differ from the effective date of
such rules or regulations. Entities may need to exercise considerable
judgment and obtain the assistance of legal counsel in determining (1)
the enactment date of laws and regulations implemented in jurisdictions
(i.e., local, state, federal, or foreign) or (2) when regulations issued
by governmental agencies to implement and interpret these laws are
enacted. For an illustrative example of an enacted rule published in the
Federal Register, see Section 5.5.1 of Deloitte’s
Roadmap Environmental Obligations and Asset Retirement
Obligations.
Example 2-8
Legal Liabilities as
a Result of the Enactment of Legislation
The European Parliament and the Council
of the European Union (the “Council”) issue two types of
legislation: (1) regulations and (2) directives.
Regulations become law upon passage by the European
Parliament and the Council. Directives are fundamental
objectives to be achieved by laws, regulations, and
administrative provisions enacted by the individual
member states of the European Union. Although directives
must be passed by the European Parliament and the
Council, they do not become law until implemented by
laws, regulations, and administrative provisions of the
respective member states. To comply with a directive,
member states must enact such a measure within 18 months
of the directive’s passage by the European Parliament
and the Council.
The passage of a directive by the
European Parliament and the Council does not satisfy the
criteria for recognition of a liability under ASC
450-20-25-2 because a legal obligation has not been
established. The obligating event is the enactment of
laws, regulations, and administrative provisions to
comply with a directive. Although it may be probable
that passage of a directive by the European Parliament
and the Council will result in the enactment of measures
needed to comply with the directive, future laws or
changes in laws should not be anticipated. Rather,
liabilities should be recognized in a manner that
reflects the provisions of enacted laws on a
jurisdiction-by-jurisdiction basis.
2.3.1.4 Assessing Whether a Loss Is Reasonably Estimable
When accruing a loss, an entity must determine, in accordance
with the recognition criteria in ASC 450-20-25-2, whether the loss is probable
and reasonably estimable. Recognition of a loss that cannot be reasonably
estimated, even if it is probable that the loss has been incurred, would impair
the integrity of the financial statements. Alternatively, the entity should not
delay accrual of a loss because of the inability to estimate a single amount.
The ability to estimate a loss within a range would indicate that some amount of
a loss has occurred and that the entity should therefore accrue a liability in
accordance with ASC 450-20-25-2(b). The entity may use past experience or other
information to demonstrate its ability to reasonably estimate the loss.
If both recognition criteria under ASC 450-20-25-2 are met, the
estimated loss will be charged to income. ASC 450-20-25-7 indicates that if a
loss cannot be accrued in the period in which it is determined that it is
probable that a loss has been incurred “because the amount of loss cannot be
reasonably estimated, the loss shall be charged to the income of the period in
which the loss can be reasonably estimated and shall not be charged
retroactively to an earlier period. All estimated losses for loss contingencies
shall be charged to income rather than charging some to income and others to
retained earnings as prior period adjustments.”
2.3.1.5 General Reserves and Risk of Loss From Future Events
ASC 450-20-25-8 specifically indicates that “[g]eneral or
unspecified business risks” should not be accrued in the financial statements
since they do not meet the “probable” and “reasonably estimable” requirements of
ASC 450-20-25-2. Therefore, it is not acceptable to record an accrual for
general contingencies in an attempt to address uncertainties in the financial
statements that may not be probable or reasonably estimable.
In addition, mere exposure because of uninsured or underinsured
risk of loss or damage of an entity’s property by fire, explosion, or other
hazards does not mean that an asset has been impaired or a liability has been
incurred; therefore, such risk of loss should not be accrued as a liability
under ASC 450-20. To recognize such a liability related to exposure because of
uninsured or underinsured risk would be to recognize a liability under ASC
450-20 when it is not probable that the uncertain future events will confirm
that a loss occurred on or before the date of the financial statements. As noted
in ASC 450-20-55-7 by way of example, “an entity with a fleet of vehicles should
not accrue for injury to others or damage to the property of others that might
be caused by those vehicles in the future even if the amount of those losses may
be reasonably estimable.” However, ASC 450-20-55-8 indicates that an uninsured
loss resulting from injury to others or damage to property of others is accrued
as a loss contingency if that event took place before the date of the financial
statements and the entity is able to reasonably estimate the amount of such a
loss through prior experience or available information.
A risk of loss from future events that interrupt the normal
course of business is not considered “probable” until those events occur.
Further, the costs of insurance coverage and the availability of coverage for
certain types of risk (e.g., professional malpractice, product liability, director’s and officer’s liability, and pollution liability) have a significant effect on many companies. To minimize premium costs or to satisfy insurers, some companies have modified the terms of their coverage (e.g., by increasing the amounts of deductibles, reducing coverage, or both); others are forming captive insurance companies by using a self-insurance method. It is not appropriate to accrue for uninsured or underinsured expected losses in a systematic fashion before such losses occur. Before the issuance of FASB Statement 5, many entities
that did not carry insurance against certain risks, such as property damage from
fire or explosion, charged earnings in a systematic fashion (e.g., as if an
insurance premium were being expensed) to establish an insurance reserve against
which actual losses could then be charged. However, charges in lieu of insurance
are not permitted under ASC 450.
2.3.2 Other Recognition Considerations
2.3.2.1 Unasserted Claims
Unasserted claims are possible claims or assessments of which an entity has not
yet been notified by the injured party or potential claimant. Entities often are
exposed to financial loss before the commencement of a formal claim. Litigation
may be expected as a result of a past action. Alternatively, an entity may
expect a current government investigation to result in a formal claim upon the
investigation’s completion.
To determine under which circumstances an unasserted claim
should be accrued, an entity must first determine whether a past event has
triggered a loss contingency. If such a past event has occurred, the entity must
then determine the probability that (1) a lawsuit will be filed or a claim will
be asserted against it and (2) such a lawsuit or claim will result in an
unfavorable outcome for the entity. If it is probable that an unasserted claim
will result in an unfavorable outcome for the entity, and if the amount of the
loss can be reasonably estimated, the entity should accrue a loss contingency in
accordance with ASC 450-20-25-2. Additional disclosure may be required if it is
reasonably possible that there is exposure to loss in excess of the amount
accrued.
If an unfavorable outcome is only reasonably possible, or if the
amount of the loss cannot be reasonably estimated, an amount should not be
accrued but disclosure would be required under ASC 450-20-50. See Section 2.8 for
disclosure considerations.
Entities may incur losses as a result of incidents that occur
before the date of the financial statements but are not reported by a claimant
until a later date. ASC 720-20-25-14 requires the accrual for incurred but not
reported (IBNR) claims if both criteria in ASC 450-20-25-2 are met. Examples 2-9 and
2-10 illustrate
the application of the recognition criteria under ASC 450-20 to unasserted
claims.
SEC Considerations
For certain IBNR claims, such as asbestos liability
claims, entities may establish a liability for a rolling fixed number of
years (i.e., the entity is able to reliably estimate its expected
liability for IBNR for the next 20 years of claims, but it is unable to
reliably estimate a liability for the period beyond 20 years).
Typically, these liabilities have years, and sometimes decades, of
settlement claims history. The SEC staff has frequently commented on
these rolling fixed-term liabilities and has asked companies to provide
more detail about the process undertaken, including the related ICFR, by
management to conclude that it could not estimate for the period beyond
a specific time horizon.
Example 2-9
Assessing Accrual
Related to an Outcome of an Incomplete
Investigation
Company R is being investigated by a
government agency for potential breach of contract and
allegations of illegal pricing for prior sales
transactions. As of year-end, the government has not
filed any charges or specified a monetary penalty
against R for these matters. To determine whether
accrual or disclosure of the contingency is appropriate
in R’s year-end financial statements, R’s management
must first determine the probability that a lawsuit will
be filed or a claim will be asserted against R. If the
filing of a lawsuit or the assertion of a claim is
probable in management’s judgment, management must
determine the probability that such a lawsuit or claim
will result in an unfavorable outcome for R. If an
unfavorable outcome is probable and the amount of the
loss can be reasonably estimated, accrual of the loss is
required. If the amount of the loss cannot be reasonably
estimated, no accrual is required; however, R should
disclose the contingency. Further, if an unfavorable
outcome is only reasonably possible but not probable, R
should disclose the contingency.
Example 2-10
Accrual of Probable
Settlement Costs
Company T has decided to abandon certain
distributor agreements that it had in place. Company T
believes that it will be involved in legal actions
brought by the distributors and that it is probable that
the company will incur costs to settle these actions. To
the extent that it is probable that these claims will be
asserted and will result in an unfavorable outcome for
T, it should accrue a loss under ASC 450-20 if the
settlement amount can be reasonably estimated.
2.3.2.2 Loss Recognition Before the Occurrence of a Casualty Event for an Insurance Company
One of the most controversial issues addressed in ASC 450-20 is
related to whether a property and casualty insurance company should recognize a
liability for future losses resulting from catastrophes. When an insurance
company issues a policy, it assumes the risk that a catastrophe (e.g., a
hurricane) might occur within the policy coverage period. Insurance companies
have asserted that they are able to predict the occurrence rate of catastrophes
and related losses by using actuarial methods based on past occurrences.
Insurance companies use such methods for rate-setting purposes; therefore, many
believe that the losses are reasonably estimable and should be accrued.
However, ASC 944-40-55-3 indicates that catastrophe reserves
fail to satisfy the conditions of ASC 450-20 for accrual because losses from
potential future catastrophes over the relatively short periods covered by
policies in force cannot be reasonably estimated. In addition, unless a
catastrophe occurs within the policy period, no asset is impaired and no
liability is incurred as of the date of the financial statements; therefore, no
accrual for a catastrophe loss should be made. On the other hand, a property and
casualty insurer is required to accrue losses from catastrophes that occurred
before the date of the financial statements even though claims have not been
submitted by policyholders if (1) it is probable that those claims will be made
and (2) a reasonable estimate of the loss can be made. Accrual of a premium
deficiency is also required by ASC 450-20 and ASC 944-60.
2.3.2.3 Litigation, Claims, and Assessments
A common uncertainty many entities will encounter is the risk of litigation.
Class actions, product liabilities, lawsuits, and actions brought by government
agencies are not uncommon, and an entity may need to accrue or disclose
contingencies related to the risk of such litigation (e.g., the potential future
obligation to pay an uncertain amount as a result of past activities) in the
financial statements.
Adverse consequences of litigation could include the obligation to pay damages,
the imposition of fines and penalties, the need to repay consideration from a
revenue contract that was previously received, and even discontinuation of
certain operations. Further, the entire nature of the entity may change as a
result of the litigation (e.g., the entity may seek protection from the
litigation through bankruptcy).
Types of litigation that an entity may face include the following:
-
Antitrust.
-
Restraint of trade.
-
Breach of contract.
-
Patent infringement.
-
Product liability.
-
Violation of federal securities laws.
-
Government actions.
-
Discrimination.
-
Environmental protection matters.
-
Violation of wage and price guidelines or controls.
-
Renegotiation of government contracts.
-
Income tax disputes.
-
Violation of other laws and regulations (e.g., the Foreign Corrupt Practices Act).
In determining whether an accrual is required in connection with litigation,
claims, and assessments, an entity should consider various factors that include,
but are not limited to, the following:
- The nature of the settlement mechanism — The parties involved may have agreed to use a settlement mechanism other than the court system that is binding on the parties. Accordingly, it is necessary to evaluate, on the basis of the specific facts and circumstances, the ability of the party that is subject to an adverse legal judgment to appeal the matter.
- The progress of the case — If a planned appeal is not the entity’s first appeal of an adverse judgment (i.e., the entity has been unsuccessful in prior appeals of the judgment), the entity should consider the results or findings of the earlier rulings when assessing its evidence for and against liability recognition.
- The opinions or views of legal counsel and other advisers:
- A legal analysis usually will include counsel’s opinion regarding the likelihood that the entity will prevail on appeal. For example, a legal opinion may state counsel’s belief that the entity’s chance for a successful appeal is probable, more likely than not, or reasonably possible. The terms “probable” and “reasonably possible” do not signify precise quantitative thresholds and may be interpreted and applied differently by different parties, as described in Section 2.3.1.1. The meaning of such terms should be understood in the context of the legal opinion related to the entity’s specific facts and circumstances so that management’s assertions about the likelihood of success on appeal can be compared with those of counsel. An indication from legal counsel that an entity plans to vigorously defend itself against a claim does not relieve the entity from evaluating the probability of a future loss.
- Management should review the basis for counsel’s conclusions and assess whether the reasons cited by counsel to support its assessment are consistent with the evidence used by the entity to support its decision about whether to record a loss contingency.
- Management should fully consider any qualifications or conditions that counsel identified as affecting its assessment. In interpreting language used by counsel to explain its conclusion, management may find it helpful to consider the guidance in AU-C Sections 620 and 501 of the AICPA’s auditing standards, which apply to financial statement audits.
- Counsel’s opinion is a critical piece of evidence that needs to be analyzed carefully. Counsel’s expression of an opinion that an entity will be successful on appeal does not, in itself, support a conclusion that an accrual of a loss is not warranted. In addition, ASC 450-20-55-12(c) notes that “the fact that legal counsel is unable to express an opinion that the outcome will be favorable to the entity should not necessarily be interpreted to mean that the condition in paragraph 450-20-25-2(a) is met.” However, when the entity has received an adverse legal judgment, counsel’s inability to express an opinion may leave the entity with insufficient positive evidence to overcome the judgment.
- The experience of the entity or other entities in similar cases — The prior experiences of the entity or other entities with similar litigation may serve as additional evidence of the entity’s likelihood of success. For example, management could consider possible outcomes specific to (1) certain jurisdictions, (2) certain courts, (3) the use of certain defense strategies, or (4) other related aspects of the litigation.
- Prior case law for similar cases — Gaining an understanding of prior case law may enable the entity to identify certain precedents that could affect the likelihood of its success.
- Management’s decision regarding how the entity intends to
respond:
-
Although certain adverse legal judgments may be appealed, the entity’s decision to appeal will depend on a variety of factors. The entity should consider its specific facts and circumstances when assessing the likelihood that it will seek an appeal.
-
Because an adverse legal judgment may involve multiple components, the entity should analyze each component thoroughly to determine whether a litigation accrual should be recorded. For example, the entity should determine whether it will appeal all components of the judgment or only selected components.
-
-
The entity’s intended basis for an appeal — As discussed above, an understanding of the legal basis for the entity’s appeal, combined with a review of prior case law or the experiences of the entity or other entities in similar cases, may serve as evidence that helps the entity gauge the likelihood that it will prevail on appeal.
-
The audit committee’s assessment of the entity’s opportunity for appeal — The audit committee’s assessment of the entity’s opportunity for appeal, considered along with the assessments of internal or outside counsel and the entity’s management, may constitute additional information about the entity’s defense strategy and its chances for success on appeal.
Example 1 in ASC 450-20-55-18, Cases A through D of Example 2 in
ASC 450-20-55-22, and Example
2-11 illustrate the accounting for various litigation
scenarios.
ASC 450-20
Example 1:
Litigation Open to Considerable
Interpretation
55-18 An entity may be
litigating a dispute with another party. In preparation
for the trial, it may determine that, based on recent
developments involving one aspect of the litigation, it
is probable that it will have to pay $2 million to
settle the litigation. Another aspect of the litigation
may, however, be open to considerable interpretation,
and depending on the interpretation by the court the
entity may have to pay an additional $8 million over and
above the $2 million.
55-19 In that case, paragraph
450-20-25-2 requires accrual of the $2 million if that
is considered a reasonable estimate of the loss.
55-20 Paragraphs 450-20-50-1
through 50-2 require disclosure of the nature of the
accrual, and depending on the circumstances, may require
disclosure of the $2 million that was accrued.
55-21 Paragraphs 450-20-50-3
through 50-8 require disclosure of the additional
exposure to loss if there is a reasonable possibility
that the additional amounts will be paid.
Example 2:
Multiple Case Litigation Example
55-22 The following Cases
illustrate application of the accrual and disclosure
requirements in the following stages of litigation:
- The trial is complete but the damages are undetermined (Case A).
- The trial is incomplete but an unfavorable outcome is probable (Case B).
- The trial is incomplete and unfavorable outcome is reasonably possible (Case C).
- There is a range of loss and one amount is a better estimate than any other (Case D).
Case A: Trial Is Complete but Damages
Are Undetermined
55-23 An entity is involved
in litigation at the close of its fiscal year and
information available indicates that an unfavorable
outcome is probable. Subsequently, after a trial on the
issues, a verdict unfavorable to the entity is handed
down, but the amount of damages remains unresolved at
the time the financial statements are issued or are
available to be issued (as discussed in Section
855-10-25). Although the entity is unable to estimate
the exact amount of loss, its reasonable estimate at the
time is that the judgment will be for not less than $3
million or more than $9 million. No amount in that range
appears at the time to be a better estimate than any
other amount.
55-24 In this Case, paragraph
450-20-30-1 requires accrual of the $3 million (the
minimum of the range) at the close of the fiscal
year.
55-25 Paragraphs 450-20-50-1
through 50-2 require disclosure of the nature of the
contingency and, depending on the circumstances, may
require disclosure of the amount of the accrual.
55-26 Paragraphs 450-20-50-3
through 50-8 require disclosure of the exposure to an
additional amount of loss of up to $6 million.
Case B: Trial Is Incomplete but
Unfavorable Outcome Is Probable
55-27 Assume the same facts
as in Case A, except it is probable that a verdict will
be unfavorable and the trial has not been completed
before the financial statements are issued or are
available to be issued (as discussed in Section
855-10-25). In that situation, the condition in
paragraph 450-20-25-2(a) would be met because
information available to the entity indicates that an
unfavorable verdict is probable. An assessment that the
range of loss is between $3 million and $9 million would
meet the condition in paragraph 450-20-25-2(b).
55-28 In this Case, if no
single amount in that range is a better estimate than
any other amount, paragraph 450-20-30-1 requires accrual
of $3 million (the minimum of the range) at the close of
the fiscal year.
55-29 Paragraphs 450-20-50-1
through 50-2 require disclosure of the nature of the
contingency and, depending on the circumstances, may
require disclosure of the amount of the accrual.
55-30 Paragraphs 450-20-50-3
through 50-8 require disclosure of the exposure to an
additional amount of loss of up to $6 million.
Case C: Trial Is Incomplete and
Unfavorable Outcome Is Reasonably Possible
55-31 Assume the same facts
as in Case B, except the entity had assessed the verdict
differently (for example, that an unfavorable verdict
was not probable but was only reasonably possible). The
condition in paragraph 450-20-25-2(a) would not have
been met and no amount of loss would be accrued.
Paragraphs 450-20-50-3 through 50-8 require disclosure
of the nature of the contingency and any amount of loss
that is reasonably possible.
Case D: Range of Loss and One Amount Is
a Better Estimate Than Any Other
55-32 Assume that in Case A
and Case B the condition in paragraph 450-20-25-2(a) has
been met and a reasonable estimate of loss is a range
between $3 million and $9 million but a loss of $4
million is a better estimate than any other amount in
that range.
55-33 In this Case, paragraph
450-20-30-1 requires accrual of $4 million.
55-34
Paragraphs 450-20-50-1 through 50-2 require
disclosure of the nature of the contingency and,
depending on the circumstances, may require disclosure
of the amount of the accrual.
55-35 Paragraphs 450-20-50-3
through 50-8 require disclosure of the exposure to an
additional amount of loss of up to $5 million.
Example 2-11
Broker-Dealer
Dispute With Investors
Company A, a broker-dealer, markets and
sells investments in certain financial products. The
investments do not contain an option for investors to
put the investments back to A. Company A later faces
criticism and potential litigation for misleading
investors about the economic characteristics of the
investments. As a result, A enters into a settlement
agreement that gives each investor the right to demand
that A repurchase the investment for cash equal to its
par value on a specified future date (or range of dates)
upon physical delivery of the investment to A.
The accounting considerations depend on
whether A has entered into a legally enforceable
settlement agreement that meets the definition of a firm
commitment (i.e., an “enforceable settlement
agreement”).
Accounting Before
Settlement Agreement
Before an enforceable settlement
agreement or the resolution of any associated
litigation, the potential that a broker-dealer has
incurred a loss in connection with its past selling or
marketing of investments is a loss contingency within
the scope of ASC 450-20 and should be evaluated as a
contingent liability for recognition and disclosure
purposes.
Under ASC 450-20-25-2, the broker-dealer
should accrue a liability for the contingency and
recognize a related charge in current-period income if
information that is available before the financial
statements are issued (or before they are available to
be issued) indicates that (1) it is probable that a
liability has been incurred as of the date of the
financial statements in connection with the
broker-dealer’s past selling or marketing of investments
and (2) the amount of the loss can be reasonably
estimated. ASC 450-20-50-3 and 50-4 specify that if it
is reasonably possible that a loss or an additional loss
in excess of the amount of the loss accrued may have
been incurred or the loss amount cannot be reasonably
estimated, the broker-dealer should disclose the “nature
of the contingency” and an “estimate of the possible
loss or range of loss or a statement that such an
estimate cannot be made.”
Accounting Once a
Settlement Agreement Becomes Legally
Enforceable
On the date A enters into an enforceable
settlement agreement, the uncertainty regarding whether
a loss has been incurred is resolved, and A must
recognize an obligation for issuing the written put
option.
If A determines that the written put
option does not meet the definition of a derivative
instrument under ASC 815-10, it would account for the
option as a guarantee contract under ASC 460-10.
Accordingly, at initial recognition of the obligation
undertaken in issuing the guarantee, A should apply ASC
460-10-30-3, which states, in part, that the amount
initially recognized in connection with the written put
option should be the greater of:
- The amount that satisfies the fair value objective as discussed in the preceding paragraph
- The contingent liability amount required to be recognized at inception of the guarantee by Section 450-20-30.
ASC 460-10-35 does not address
subsequent measurement in detail; however, A would be
expected to subsequently measure the put option in a
manner consistent with the SEC staff’s long-standing
position that written options should be marked to fair
value through current-period earnings.
2.3.2.4 Evaluating the Impact of an Adverse Legal Judgment on the Recognition and Measurement of a Loss Contingency
In some cases, an entity may receive an adverse legal judgment
for payment of a specific amount related to an event that occurred on or before
the date of the financial statements. This judgment may be determined before the
date of the financial statements, or after the date of the financial statements
but before the financial statement issuance or the date on which the financial
statements are available to be issued. The entity may not have previously
recognized a contingent liability for this matter because it did not believe
that the criteria in ASC 450-20-25-2 had been met.
The rendering of an adverse legal judgment against an entity
does not automatically trigger recognition of a liability for a loss contingency
since the entity may be successful in overturning all or part of the original
judgment on appeal. As mentioned above, ASC 450-20-25-2 requires entities to
accrue, by a charge to income, an estimated loss from a loss contingency if (1)
it is probable that a “liability had been incurred” and (2) the “amount of loss
can be reasonably estimated.” In determining the probability and the estimate of
the loss, the entity must analyze all available information.
An adverse legal judgment constitutes significant objective evidence of the
probability that an entity has incurred a liability as of the date of the
financial statements. Consequently, for an entity that intends to appeal the
judgment to conclude that no liability has been incurred as of the date of the
financial statements, evidence supporting nonrecognition must be sufficient to
counterbalance the external legal determination (i.e., the adverse legal
judgment) and any other similar evidence. That is, to support nonrecognition,
the evidence as a whole must reduce the likelihood that a liability has been
incurred as of the date of the financial statements to a level below the
probable threshold under ASC 450-20; otherwise, a liability should be recognized
as long as the amount of the liability is reasonably estimable.
After analyzing all of the available information, the entity
that received the adverse legal judgment may conclude that no loss contingency
accrual is necessary because one or both of the conditions in ASC 450-20-25-2
have not been met. However, the entity would still be required to disclose the
contingency (in accordance with ASC 450-20-50-3) if it is at least reasonably
possible that a loss has been incurred as of the date of the financial
statements. It is unlikely that an entity that has received an adverse legal
judgment will have sufficient information to conclude that the likelihood of a
loss is remote. Also, it is likely that the disclosure would need to contain
sufficient information to enable financial statement users to understand the
status of the litigation, the fact that an adverse judgment had been determined,
and the factors the entity considered to determine that the loss should not be
recognized.
If the entity is unable to or does not intend to appeal the
adverse judgment, or otherwise concludes in accordance with ASC 450-20-25-2(a)
that it is probable that a liability has been incurred, the entity should
determine whether the liability can be reasonably estimated in accordance with
ASC 450-20-25-2(b). If a reasonable estimate of the liability is a range, the
entity should apply the guidance in ASC 450-20-25-5 and ASC 450-20-30-1. That
is, when one amount within a range appears to be a better estimate than any
other amount within the range, that amount should be accrued; when no amount
within the range is a better estimate than any other amount, the minimum amount
in the range should be recorded.
2.3.2.5 Accrual of Future Legal Costs
In determining the amount to accrue for a loss contingency
involving litigation, entities must consider whether expected legal fees related
to the litigation should be accrued when the loss contingency is initially
recognized or when the legal services are actually provided at a future date.
Practice related to this issue has varied owing to the absence of definitive
guidance. As a result, the SEC staff suggested that the EITF Agenda Committee
consider the need to add an item to the EITF’s agenda to address this issue.
The EITF Agenda Committee discussed this potential issue before
the January 1997 meeting but did not reach a recommendation for the Task Force.
The Agenda Committee considered whether the Task Force should recommend that the
FASB undertake the project so that it receives adequate due process, but the
Agenda Committee did not reach a conclusion. The Agenda Committee also discussed
the existing practice related to the accrual of legal fees associated with a
loss contingency and determined that it might be helpful to ask the Task Force
for input on whether such practice is diverse. The SEC observer indicated that
the SEC staff will need to consider whether to provide interim guidance while
the EITF or the FASB decides whether to address this issue.
In addition, the minutes of the January 23, 1997, EITF meeting contain the
following discussion of this issue, which is also summarized in an SEC staff
announcement codified in ASC 450-20-S99-2:
The Task Force Chairman reported
on the meeting of the EITF Agenda Committee. The Task Force discussed a
potential new issue relating to the accounting for legal costs expected to
be incurred in connection with a FASB Statement No. 5, Accounting for
Contingencies [codified as ASC 450-20], loss contingency. Some Task Force
members observed that they believe practice typically has expensed such
costs as incurred; however, other Task Force members suggested that practice
may not be consistent in this area. The Task Force also discussed whether it
should recommend that the FASB address this potential new issue but decided
not to take any action. The Task Force declined to add this potential new
issue to its agenda. The SEC Observer indicated that the SEC staff will
attempt to better understand what practice is in this area and monitor the
issue. The SEC Observer also noted that he would expect a registrant’s
accounting policy to be applied consistently and APB Opinion No. 22,
Disclosure of Accounting Policies [codified as ASC 235], requires disclosure
of material accounting policies and the methods of applying those
policies.
In the absence of further guidance from the FASB or the SEC
staff, entities should apply the guidance above, which indicates that the
decision to accrue legal costs on the basis of an estimate of future legal costs
or expense when incurred is a matter of accounting policy that should be
consistently applied and disclosed, when material. Factors an entity needs to
consider when determining the accounting policy for legal fees include whether
the policy provides for meaningful presentation of the balance sheet and income
statement, whether the policy improves comparability among entities that may
have ongoing litigation exposure, and whether the accrual of legal fees is
representative of the way in which the entity manages its litigation exposure
(when resolution and legal defense costs are so directly interrelated that they
are inseparable from the overall liability determination). Whether expensed as
incurred or accrued in advance, litigation expense should generally be
classified as an operating expense in the statement of operations.
2.3.2.6 Measurement Date for Stock Issued in Settlement of Litigation
A company may settle a legal action by issuing shares of its
stock or other equity-classified instruments to the counterparty. ASC 450 does
not provide specific guidance on measuring equity instruments for settlement of
a contingent liability. The scope of ASC 718, as indicated in ASC 718-10-15-3,
is “all share-based payment transactions in which a grantor
acquires goods or services to be used or consumed in the grantor’s own
operations or provides consideration payable to a customer by issuing
(or offering to issue) its shares, share options, or other equity instruments or
by incurring liabilities to an employee or a nonemployee that meet either of the
following conditions” (emphasis added). The settlement of a legal action does
not represent the acquisition of goods or services to be used or consumed in the
grantor’s operations. Although such a transaction is not within the scope of ASC
718, depending on the facts and circumstances specific to the legal matter, it
may be appropriate to apply certain principles from ASC 718 by analogy.
Parties to litigation may reach a preliminary agreement, subject to court
approval, on the number of shares to be issued. Under an agreement that is
subject to court approval, the court approval date is the appropriate
measurement date for stock issued in settlement of litigation. The court’s
approval of a settlement is a substantive event rather than an administrative
matter or a formality. The approval of a legal settlement by a court that serves
as the ultimate judge of fairness (i.e., approval is not perfunctory) represents
the final “future event” that gave rise to the original characterization of the
loss as a contingency under ASC 450-20. This view is consistent with the
definition of the grant date in ASC 718-20, which indicates that for plans that
are subject to shareholder approval, a measurement date for a stock award is the
date when shareholder approval is obtained. Therefore, the total expense
recognized in connection with the final settlement of a lawsuit should be
measured on the court approval date.
When determining the share price to be used in measuring a
liability that is recognized as of a balance sheet date before final settlement
in situations in which a party offers to issue equity instruments to settle a
claim, it may be appropriate for an entity to analogize to the guidance in ASC
718 regarding the measurement of liability-classified share-based payment award
transactions and to use the period-end share price. In other arrangements,
information that becomes available after the balance sheet date but before the
financial statements are issued (or available to be issued) may be relevant to
the measurement as of the balance sheet date (e.g., a settlement offer).
Alternatively, when shares are used as “currency” to settle the liability, an
entity may measure the contingent liability on the basis of its best estimate of
the amount of loss that has been incurred. An entity should carefully evaluate
such transactions in determining the appropriate share price to use in measuring
the liability at period-end. The accounting may ultimately depend on whether the
dispute involves the issuance of shares or whether an entity is merely using its
shares as “currency” to resolve a matter.
Example 2-12
Litigation
Settlement in Shares Subject to Court
Approval
Entities A and Z are parties to ongoing
litigation that is subject to a court-mandated mediation
process. Once the mediator, A, and Z agree on a
settlement amount, final court approval is needed for
the settlement to be finalized. On March 3, 20X9, as a
result of the mediation process, A agrees to issue
200,000 shares to Z to settle the litigation, subject to
the court’s final approval.
Before March 3, 20X9, A had previously
recognized a contingent liability related to the
litigation for $1.75 million because A had concluded
that it was probable that a loss had been incurred and
$1.75 million was its estimate for the loss. On the
agreement date, March 3, 20X9, the fair value of A’s
shares was $10 per share and A adjusted its recognized
liability to $2 million ($10 per share × 200,000 shares)
by debiting expense and crediting a contingent liability
for $250,000. This adjustment is considered a change in
accounting estimate.
On March 30, 20X9, the court approves
the settlement agreement of 200,000 shares to be issued
by A to Z. On the court approval date, the fair value of
A’s shares was $11 per share. Entity A must recognize
the incremental $200,000 [($11 per share − $10 per
share) × 200,000 shares] loss in income at this time
since the court approval was a substantive part of the
litigation settlement. The measurement date for the
ultimate liability is the court approval date of March
30, 20X9. Upon issuance of its shares, A should debit
the total contingent liability recognized of $2.2
million, with a corresponding credit to equity. This
adjustment is considered a change in accounting
estimate.
2.3.2.7 Recognition of Annual Bonus Plan Liabilities
Many companies use cash bonus plans to compensate employees. Annual bonus plans
may be based on specific formulas and performance targets or may be at the
discretion of management and the compensation committee of the company’s board
of directors. In some plans, annual bonus amounts are determined after the end
of a fiscal year and may not be determined until after the financial statements
are issued. Bonuses also may be forfeited if an employee is terminated or
resigns.
The recognition criteria of ASC 450-20 should be used to
estimate the amount of a bonus whose payment is probable when the cash bonus
plan is not subject to other applicable U.S. GAAP (such as ASC 718). If the
amount of a bonus that will be achieved or granted is uncertain, a range should
be computed under ASC 450-20-30-1. If “no amount within the range is
[considered] a better estimate than any other amount,” the low end of the range
should be selected. Entities must carefully evaluate bonuses that are based on
achievement of a target to determine whether such achievement is probable.
Once an entity has determined the amount of the probable bonus,
it should recognize the amount over the service period. Recognizing compensation
expense in this manner is analogous to recognizing expense in connection with
stock-based compensation arrangements over the related service period, as
required by ASC 718. Under this model, the obligating event giving rise to the
liability is considered the employee’s performance of service. Recognition of a
bonus liability should not be delayed just because the bonus would not be paid
if an employee were to terminate employment before the end of the service
period. Rather, if a reliable estimate of employee turnover is possible, the
entity may factor this estimate into the range of estimates when determining the
probable liability. Any difference between the actual bonus paid and the amount
accrued is considered a change in accounting estimate.
Example 2-13
Employee Benefit
Arrangements
Company P is preparing its financial
statements for the fiscal year ending December 31, 20X4.
On January 2, 20X4, P initiates an incentive
compensation plan for its senior executives. Under the
plan, each executive is allocated a portion of a pool of
500 units. The value of each unit will be determined as
of the plan measurement date (December 31, 20X5) in
accordance with a plan formula that uses as its basis
the difference between P’s net income in 20X5 and P’s
net income in 20X4. On December 31, 20X6, each executive
who has remained with P in uninterrupted service during
the period from January 1, 20X4, through December 31,
20X6, will receive a cash bonus based on this
calculation of unit value.
Although P annually prepares a
projection of its net income for the year, there is
uncertainty about whether the amount will ultimately be
attained since the company has failed to achieve its
targets in recent years. Management has calculated that
if P meets its forecasted level of net income in fiscal
year 20X5, the bonus (payable at the end of 20X6 under
the plan) could be as high as $8 million.
Company P should use all available
information to reasonably estimate its liability for the
cash bonus plan and accrue in fiscal year 20X4 the
percentage of the liability that is related to the 20X4
service period. When considering its forecast of net
income for fiscal year 20X5, P should take into account
any recent trends or developments and the accuracy of
its prior projections.
The probable percentage of the liability
that is related to the expired service period, which is
estimated by management to be 33.3 percent (calculated
on the basis of one of three fiscal years for which the
executive is required to have been employed), should be
accrued as of December 31, 20X4. The remaining 66.7
percent should be accrued over the following two years.
The amount of the probable bonus should be reconsidered
in each subsequent reporting period.
In accordance with ASC 450-20-30-1, if P
determines that the range of the bonus amount could be
from $1 million to $8 million and no amount within the
range is considered a better estimate than any other
amount, it would be appropriate for P to accrue a
liability on the basis of the $1 million low end of the
range.
However, since it is reasonably possible
that a liability greater than $1 million has been
incurred, ASC 450-20-50-4 requires P to disclose in its
fiscal year 20X4 financial statements a complete
description of the plan and an estimate of the possible
bonus amount or range of bonus amount or a statement
that such an estimate cannot be made.
2.3.2.7.1 Interim Considerations
When allocating annual bonuses to interim periods, entities should consider
the guidance in ASC 270-10-45-8 through 45-10. Costs and expenses should be
allocated to interim periods so that each interim period bears a reasonable
portion of the annual expense. Each quarter, entities should determine the
amount of bonus for which achievement is probable in accordance with ASC
450-20-25-2 and recognize this amount so that each interim period bears a
reasonable portion of the annual expense. Entities must exercise judgment in
determining the appropriate allocation method, and they should apply the
selected method consistently in each reporting period.
For example, an entity may have a discretionary bonus plan
that provides for the payment of annual bonuses to certain employees on the
basis of the entity’s overall achievement of specific key financial metrics.
In accordance with ASC 450-20, in each reporting period, the entity would
estimate the amount of bonus for which payment is probable and recognize an
amount that bears a reasonable portion of the annual expense. The entity may
conclude that, as a result of recognizing the bonus on a straight-line basis
over the performance period, each interim period bears a reasonable portion
of the annual bonus expense. Alternatively, the entity may conclude that
each interim period bears a reasonable portion of the annual bonus as a
result of recognizing the annual bonus on the basis of the entity’s
proportionate achievement of specific key financial metrics. The entity
would apply the method used consistently in each reporting period.
2.3.2.8 Injury or Damage Caused by Products Sold
ASC 450-20
55-2 If it is
probable that a claim resulting from injury or damage
caused by a product defect will arise with respect to
products or services that have been sold, accrual for
losses may be appropriate. The condition in paragraph
450-20-25-2(a) would be met, for instance, with respect
to a drug product or toys that have been sold if a
health or safety hazard related to those products is
discovered and as a result it is considered probable
that liabilities have been incurred. The condition in
paragraph 450-20-25-2(b) would be met if experience or
other information enables the entity to make a
reasonable estimate of the loss with respect to the drug
product or the toys.
Entities may be subject to recalls on their products (e.g.,
pharmaceutical drugs, car engines, food products). While some product recalls
are voluntary (e.g., the manufacturer has chosen to remove the product from the
shelves or has notified consumers to cease using the product), other recalls may
be required by law or a regulator (e.g., the FDA).
If an entity is not otherwise required by law or a regulator to
initiate a product recall, the obligating event triggering liability recognition
for the costs (i.e., repurchasing inventory) associated with a voluntary product
recall would generally be the announcement of the recall. Except as provided for
in a warranty arrangement, an entity has no legal obligation or duty associated
with product design or manufacturing defects after the product is sold. Because
there is no legal obligation, there is no event that gives rise to a probable
loss until a recall is announced voluntarily. If, however, a warranty
arrangement exists, the obligating event is the identification of a problem with
the product or the need for product recall, not the voluntary recall
announcement.
Alternatively, an entity may conclude, on the basis of current
laws or regulations, that it is probable that such a law or regulation will
require the entity to initiate a product recall as a result of adverse events or
conditions associated with the product in the distribution channel (i.e.,
inventory that has been sold but has not yet been consumed). In such a
situation, the obligating event triggering liability recognition for the costs
of the recall is the existence of the current law or regulation, and liability
recognition for the estimated costs of the recall would generally be required
once the entity has concluded that it is probable that such a law or regulation
will require a recall and the associated costs can be reasonably estimated.
Further, such a conclusion could be reached before formal notification by a
regulator that a recall will be mandated.
The above discussion regarding the obligation associated with a
product recall does not take into account situations in which a product may have
caused harm or damage that could result in potential loss against a company. In
such a situation, a loss contingency would be recorded once the loss is deemed
probable and reasonably estimable in accordance with ASC 450-20-25-2.
Unless other authoritative literature requires entities to
classify costs of fulfilling product recalls in a particular manner (i.e., in
accordance with the guidance in ASC 606 on consideration for a product returned
from a customer), such costs should be classified as operating costs in the
financial statements because they result from an inherent business risk.
Example 2-14
Voluntary Recall
Initiated by an Entity
Big Pharma develops and manufactures
health care products, including medicines and vaccines
to advance wellness, prevention, treatments, and cures.
In May and June, Big Pharma distributes 25,000 bottles
of a pediatric drug to various distributors. The drug is
commonly used to reduce fever and relieve symptoms from
conditions such as the flu and a common head cold.
In August, Big Pharma discovers that
8,500 of the bottles, specifically the 3 oz. cherry
flavor, were distributed with the incorrect dosage cups.
The dosage instruction provides dosing in teaspoons,
while the dosage cups included in the packaging were
labeled in tablespoons. Since 1 tablespoon contains 3
teaspoons, Big Pharma is concerned that the usage of the
tablespoon dosage cups could result in dangerous
overdoses if the cups’ labeling was overlooked.
There is no law or regulation in place
requiring Big Pharma to recall the drugs for including
the incorrect dosage cups. In addition, no consumer
lawsuits have been brought against Big Pharma regarding
this matter. However, Big Pharma weighs the potential
overdose risks of consumers’ overlooking the measurement
metric on the dosage cup and decides to voluntarily
recall the product. On August 11, 20X9, Big Pharma
announces the recall for the 8,500 affected bottles.
Upon announcing the recall, Big Pharma recognizes a
liability for the estimated costs of removing the
bottles from distributors and retail stores, replacing
them, and notifying consumers. Because Big Pharma was
not otherwise required by law to initiate the product
recall, the obligating event triggering the liability
recognition is the announcement of the recall on August
11, 20X9. Any liability related to potential consumer
lawsuits would be accounted for in accordance with ASC
450-20. Such accounting would be separate from that for
the costs Big Pharma expects to incur in connection with
the recall.
Example 2-15
Recall Required by a Regulator
Mattress Store designs mattresses and
sells them through various online retail Web sites.
Mattress Store recently developed a new sleeper sofa
that is available in various sizes, including twin,
queen, and king, in a color choice of gray, blue, and
black. Mattress Store begins selling the sleeper sofa in
January. In March, Mattress Store discovers that the
blue sleeper sofa is not in compliance with the
mandatory federal flammability standard for mattresses
and therefore poses a fire hazard. Although there have
been no incidences reported or litigation brought
against Mattress Store, the sleeper sofa is in violation
of a federal law, and if it were reported to the U.S.
Consumer Product Safety Commission, the commission would
mandate a product recall and bar Mattress Store from
selling the sleeper sofa. Therefore, Mattress Store
announces a product recall in April to refund consumers
who bought the sleeper sofa and reacquire all sold
inventory.
Although the recall is announced in
April and the regulator has not yet provided formal
notification of a mandated recall for the sleeper sofa,
Mattress Store had determined in March that it was
probable that the U.S. Consumer Product Safety
Commission would require the company to recall the
sleeper sofa upon discovery of the violation of
flammability standards. Further, Mattress Store
concluded that sufficient information was available in
March to make a reasonable estimate for the cost of the
recall. Accordingly, Mattress Store records a liability
for the product recall in March, before the April recall
announcement or a regulator-mandated recall. Any
liability related to potential consumer lawsuits would
be accounted for in accordance with ASC 450-20. Such
accounting would be separate from that for costs
Mattress Store expects to incur in connection with the
recall.
2.3.3 Threat of Expropriation
ASC 450-20-55-9 states that “[t]he threat of expropriation of assets
is a contingency (as defined) because of the uncertainty about its outcome and
effect.” The guidance requires recognition of a loss from threat of expropriation of
assets only if (1) expropriation is imminent and (2) consideration received for the
expropriated assets will be less than the carrying amount, resulting in a loss. With
respect to (1), “[i]mminence may be indicated, for example, by public or private
declarations of intent by a government to expropriate assets of the entity or actual
expropriation of assets of other entities.” With respect to (2), an entity would
recognize a loss only when the consideration received is less than the carrying
value of the expropriated asset. The condition in ASC 450-20-25-2(b) requires that
accrual be made only if the amount of loss can be reasonably estimated. In
accordance with ASC 450-20-55-9, “[i]f the conditions for accrual are not met,” the
entity should provide appropriate disclosures “if there is at least a reasonable
possibility that an asset has been impaired” (see Section 2.8 for a discussion of disclosure
requirements).
Footnotes
3
This position is consistent with the guidance in ASC 420
and ASC 805-20-55-50 and 55-51, which indicate that the liability for
termination benefits and curtailment losses that will be triggered by
the consummation of a business combination should be recognized only
upon completion of the business combination.
2.4 Measurement
ASC 450-20
30-1 If some amount
within a range of loss appears at the time to be a better
estimate than any other amount within the range, that amount
shall be accrued. When no amount within the range is a better
estimate than any other amount, however, the minimum amount in
the range shall be accrued. Even though the minimum amount in
the range is not necessarily the amount of loss that will be
ultimately determined, it is not likely that the ultimate loss
will be less than the minimum amount. Examples 1–2 (see
paragraphs 450-20-55-18 through 55-35) illustrate the
application of these initial measurement standards.
Once the recognition criteria under ASC 450-20-25-2 are met, entities
should accrue the estimated loss with a charge to income. If the amount of the loss is a
range, the amount that appears to be a better estimate within that range should be
accrued. If no amount within the range is a better estimate, the minimum amount within
the range should be accrued, even though the minimum amount may not represent the
ultimate settlement amount. See Section 2.3.2.3 for examples illustrating the application of ASC
450-20-30-1.
A contingent liability should be estimated independently from any
possible claim for recovery (see Chapter 4 for the accounting for loss recoveries). For example, entities
may enter into certain insurance contracts to protect themselves from a litigation loss,
but the presence of insurance does not relieve the entity from being the primary
obligor, since an entity generally would be unable to transfer to an insurance company
its primary obligation to a potential claimant without the claimant’s consent. Because a
potential claimant typically is not asked to consent to an insurance contract between
the entity and an insurance company, the entity may be unclear about the circumstances
in which its primary obligation to a potential claimant could shift to the insurance
company under an insurance contract.
Some have asserted that since workers’ compensation arrangements and other similar
insurance arrangements arise from and are governed by state law, it is possible for the
insurance company, rather than the insured entity, to be the primary obligor to the
claimant/employee by operation of law. In a typical workers’ compensation arrangement,
an entity purchases a policy from a third-party insurance company and the insurance
company pays the full cost of all claims directly to the employees, subject only to the
deductible. Actual claim experience will not further affect the entity’s potential
economic upside or downside aside from any insurance provisions that allow rates to be
adjusted retrospectively.
While such arrangements may exist, it is expected to be rare that a
legal analysis of the insurance contract and the applicable workers’ compensation laws
and regulations would support an assertion that the insurance company is the primary
obligor. An entity that asserts that it no longer is a primary obligor in those or
similar circumstances would need sufficient analysis and documentation to support its
conclusion.
2.4.1 Offer to Settle Litigation
Entities will often make offers to settle litigation. An offer by management to
settle litigation creates a presumption that it is probable that a liability has
been incurred. The settlement offer establishes a low end of the range under ASC
450-20-30-1, resulting in accrual of a liability. Withdrawal of a settlement
offer before acceptance and before issuance of the financial statements
generally would not change this conclusion since the existence of the offer
provides evidence that the company may be willing to settle the litigation for
at least that amount.
The presumption that a settlement offer triggers accrual of a
liability and the establishment of a low end of the range is generally
considered to be a high hurdle to overcome, and its rebuttal should be based on
persuasive evidence. The evidence should substantiate that it is not probable
that the offer will be accepted. In addition, the evidence should substantiate
that it is not probable that further negotiations will lead to an out-of-court
settlement for which the entity will owe payment to the counterparty. In certain
circumstances, an out-of-court settlement may be the only realistic litigation
strategy because a trial is deemed too risky. In such circumstances, the
extension of an offer to settle out of court is a strong indicator that the
entity will ultimately settle with the counterparty for an equal or greater
amount. Accordingly, when an offer has been extended to settle out of court, it
must be at least reasonably possible that the litigation will ultimately be
settled via court proceedings or arbitration and that the entity will not be
obligated to make a payment. An entity that believes that the presumption has
been overcome should consider consulting with its accounting advisers.
It may not always be appropriate to accrue a contingent liability at the amount
of a settlement offer. For example, if the counterparty to the settlement offer
has rejected the offer and proposed a higher settlement amount, the amount an
entity should accrue for the loss may exceed the settlement offer made by the
entity. In such situations, an entity should use judgment and consider the
relevant facts and circumstances.
Connecting the Dots
An entity should carefully consider all facts and
circumstances when assessing whether an “offer” has been extended to
settle litigation. Questions may arise about distinguishing when a
formal offer has been made from when parties have explored potential
settlement amounts. In determining whether there is a formal offer to
settle, an entity should consider whether approval from additional
members of management or the board of directors is required. Further,
the evidence available to substantiate that an offer does not constitute
the low end of the range is often subjective, and the entity should be
careful when evaluating whether the presumption can be overcome.
Example 2-16
Offer to Settle Litigation
Company X is in the medical device
business and has been named as the defendant in a
lawsuit alleging personal injury resulting from use of
one of its surgical devices. After year-end but before
issuance of the financial statements, X offers to settle
the litigation for $10 million. The plaintiff has not
responded to the offer, and X believes that if the
matter ultimately goes to trial, the outcome is
uncertain. Company X’s management believes that the
parties are still far from deciding on a settlement
value and therefore that the plaintiff is not likely to
accept the offer. However, given the significant
exposure X faces in a trial, it is probable that the
matter will eventually be settled.
The offer to settle is significant objective evidence
that it is probable that a liability has been incurred
as of the date of the financial statements and that the
amount of the offer constitutes the minimum amount in
the range and should be accrued in the financial
statements in accordance with ASC 450-20-30-1. Company X
must also disclose any additional reasonably possible
exposure to loss in its financial statements if the
disclosure requirements in ASC 450-20-50-3 are met.
2.4.2 Comparison of the “Probability-Based” and “Expected Value Cash Flow” Accounting Models
The liability measurement guidance in FASB Concepts Statement 7 should not be applied to the measurement of contingent liabilities recognized in accordance with ASC 450-20 because the expected value cash flow model in Concepts Statement 7 differs from the probability-based accounting model in ASC 450-20-25-2. Although the expected value cash flow model in Concepts Statement 7 is
probability-weighted, it addresses the measurement of expected cash flows that may incorporate events into its measurement that are not considered probable from a loss contingency perspective under ASC 450-20. Alternatively, the probability-based accounting model in ASC 450-20-25-2 addresses the recognition of an uncertain event. Differences of this nature are further discussed in paragraph B35 of the Basis for Conclusions of FASB Statement 143 (superseded), which states, in part:
Statement 5 and Concepts Statement 7 deal with uncertainty in
different ways. Statement 5 deals with uncertainty about whether a loss has been
incurred by setting forth criteria to determine when to recognize a loss
contingency. Concepts Statement 7, on the other hand, addresses measurement of
liabilities and provides a measurement technique to deal with uncertainty
about the amount and timing of the future cash flows necessary to settle the
liability. Because of the Board’s decision to incorporate probability into the
measurement of an asset retirement obligation, the guidance in Statement 5 and
FASB Interpretation No. 14, Reasonable Estimation of the Amount of a
Loss, is not applicable.
Therefore, it is not appropriate to use the measurement guidance in Concepts Statement 7 when measuring a contingent liability in accordance with ASC 450-20. Further, the use of the fair value measurement guidance in ASC 820 is also inappropriate in such situations because a fair value measurement is similar to the expected cash flow approach in Concepts Statement 7 and such an approach does not
satisfy the measurement objective in ASC 450-20 for the reasons described above.
2.4.3 Application of Present-Value Techniques to the Measurement of a Contingent Liability
The objective of recognizing and measuring a loss contingency is to
accrue a liability that will equal or approximate the ultimate settlement amount
when the uncertainty related to the loss contingency is finally resolved. In limited
instances, it may be appropriate to use present-value techniques to discount a
contingent liability recognized in accordance with ASC 450-20-25-2. However, it is
not appropriate to discount contingent liabilities unless both the timing and
amounts of future cash flows are fixed or reliably determinable on the basis of
objective and verifiable information. In most situations, as of the date the timing
and amount of future cash flows become fixed or determinable, the obligation will no
longer represent a contingency (i.e., it will be a contractual obligation). Thus, an
entity is generally not permitted to discount contingent liabilities.
The application of discounting to liabilities recognized in
accordance with ASC 450-20-25-2 differs from the present-value-based measurements
required by other accounting standards. The sections below provide additional
guidance on applying present-value techniques.
2.4.3.1 Guidance That Applies to Discounting Contingent Liabilities
ASC 450-20 does not provide guidance on whether it is
appropriate to discount a contingent liability that is within its scope.
Although ASC 410-30 specifically addresses environmental remediation
liabilities, an entity may find this guidance useful in evaluating whether
discounting is appropriate for similar loss contingencies. ASC 410-30-35-12
states that the “measurement of the liability, or of a component of the
liability, may be discounted to reflect the time value of money if the aggregate
amount of the liability or component and the amount and timing of cash payments
for the liability or component are fixed or reliably determinable.”
The SEC has provided guidance on discounting claims liabilities
related to short-duration insurance contracts. The SEC staff’s interpretive
response to Question 1 of SAB Topic 5.N
(codified in ASC 944-20-S99-1) states, in part:
The staff
is aware of efforts by the accounting profession to assess the circumstances
under which discounting may be appropriate in financial statements. Pending
authoritative guidance resulting from those efforts however, the staff will
raise no objection if a registrant follows a policy for GAAP reporting
purposes of: . . .
- Discounting liabilities with respect to settled
claims under the following circumstances:(1) The payment pattern and ultimate cost are fixed and determinable on an individual claim basis, and(2) The discount rate used is reasonable on the facts and circumstances applicable to the registrant at the time the claims are settled.
By analogy to the above guidance, discounting of a contingent liability is
permitted, but not required, if both the timing and amounts of future cash flows
are fixed or reliably determinable. However, because the timing and amounts of
future cash flows of many contingent liabilities are inherently subjective, it
is often difficult for an entity to meet the criteria for discounting a
contingent liability (e.g., in the early phases of litigation and environmental
remediation efforts).
The SEC staff has indicated that it continues to scrutinize
compliance with this requirement and that the notion of “reliably determinable”
is inconsistent with a disclosure that additional losses beyond amounts accrued
are reasonably possible. Similarly, if the low end of a range of possible losses
were accrued in accordance with ASC 450-20-30-1, discounting would not be
appropriate because the aggregate obligation is not fixed or reliably
determinable.
SEC Considerations
The SEC staff’s interpretive response to Question 1 of
SAB Topic 5.Y (codified in ASC
450-20-S99-1) states that if a contingent liability is recognized on a
discounted basis, the “notes to the financial statements should, at a
minimum, include disclosures of the discount rate used, the expected
aggregate undiscounted amount, expected payments for each of the five
succeeding years and the aggregate amount thereafter, and a
reconciliation of the expected aggregate undiscounted amount to amounts
recognized in the statements of financial position.”
By analogy to ASC 410-30-35-10 and 35-11, if a contingent liability is
discounted, any related asset recognized as a result of a third-party recovery
also should be discounted.
In addition, ASC 835-30 provides guidance on discounting
payables. ASC 835-30-15-2 applies to “payables that represent . . . contractual
obligations to pay money on fixed or determinable dates, whether or not there is
any stated provision for interest.” However, ASC 835-30-15-3(a) specifically
exempts from present-value techniques those “[p]ayables arising from
transactions with suppliers in the normal course of business that are due in
customary trade terms not exceeding approximately one year.”
Example 2-17
Discounted Environmental Obligation
Company C is subject to environmental obligations in
connection with groundwater contamination at several of
its domestic plants. Company C has substantially
satisfied all initial remediation costs but expects to
incur charges for monitoring costs on an ongoing basis
at several plant sites. The exact term of the monitoring
activities is not specified in the remediation agreement
approved by the Environmental Protection Agency, but C
expects that, on the basis of past experience and
internal estimates, the likely term for such monitoring
activities is 30 years. Company C has estimated the
costs for these monitoring activities each year by
adjusting current annual maintenance costs at each plant
for inflation and productivity improvements. It has
proposed to use an appropriate rate to discount this
future obligation.
The absence of a definitive required post-remediation
monitoring term does not preclude discounting this
element of an environmental remediation liability.
Similarly, the need to estimate inflation, productivity
improvements, or both does not, in and of itself, lead
to the conclusion that the cash flows are not reliably
determinable. A rate appropriately blending such factors
with the discount rate would be reasonable in this
circumstance.
Although discounting of a contingent liability may be considered
inappropriate, ASC 450-20 does not preclude an entity from measuring a
contingent liability on the basis of its best estimate of the current amount it
would be required to pay to another party to settle a dispute. To the extent
that the plaintiff would accept a lump sum payment that inherently reflects the
time value of money, the entity would not be precluded from recognizing that
amount as the contingent liability. Such an approach is not considered to
involve an inappropriate form of discounting.
2.4.3.2 Selection of an Appropriate Discount Rate
If an entity has determined that a contingent liability
qualifies for discounting, the entity should consider the appropriate discount
rate. ASC 835-30 provides guidance on the selection of a discount rate; however,
that guidance does not apply to contingent liabilities.
The SEC staff’s interpretive response to Question 1 of SAB Topic
5.Y states that the discount “rate used to discount the cash payments should be
the rate that will produce an amount at which the . . . liability could be
settled in an arm’s-length transaction with a third party. . . . [T]he discount
rate used to discount the cash payments should not exceed the interest rate on
monetary assets that are essentially risk free and have maturities comparable to
that of the . . . liability” (footnote omitted). Discount rates based on the
registrant’s incremental cost of capital, incremental borrowing rate, or
investment portfolio yields are not appropriate. In most cases, it will be
difficult for an SEC registrant to justify a discount rate higher than the
risk-free rate because market transactions are rarely available. SEC registrants
should apply this guidance in selecting an appropriate discount rate for all
contingent liabilities. An entity that proposes using a credit-adjusted discount
rate should consider consultation with the SEC staff on a preclearance
basis.
Non-SEC registrants may also consider the preceding guidance in
SAB Topic 5.Y. However, there is diversity in practice among non-SEC
registrants, and selection of a discount rate for contingent liabilities on the
basis of a measure other than the risk-free rate (e.g., high-quality
fixed-income debt securities) may also be acceptable.
2.4.3.3 Accounting for Subsequent Changes in the Discount Rate
Entities that elect to discount contingent liabilities must consider the impact
of changing discount rates when adjusting the amount of the liability as of each
balance sheet date. Entities should select their discounting approach as part of
their accounting policies to be applied consistently to all contingencies.
Two methods are used in practice to account for the change in a liability
attributable to fluctuations in the discount rate. One alternative, the
immediate recognition approach, is to remeasure the liability at the current
discount rate and recognize any increase or decrease in the liability through
earnings.
Alternatively, a “lock-in” approach may be used. Under the
lock-in approach, an entity would effectively create a separate layer of
liability each time the obligation is remeasured. The lock-in principle is
discussed in an AICPA issues paper, The Use of Discounting in Financial
Reporting for Monetary Items With Uncertain Terms Other Than Those Covered
by Existing Authoritative Literature. Issue 4B of this paper concludes
that “changes in the discount rate should not be recognized in the financial
statements and the original discount rate should be used in all subsequent
periods (that is, locked in).” The conclusion also indicates that “[i]If the
lock-in concept is adopted, . . . there are situations where a discount rate
other than the rate used in the initial recording of the item may be used.” For
example, if changes in circumstances subsequently resulted in an upward
adjustment to the liability, the incremental liability would be recorded at a
current discount rate rather than the discount rate used to measure the original
liability.
Connecting the Dots
The above guidance does not apply to contractual liabilities subject to
ASC 835-30. An entity does not adjust the discount rate used at
inception to initially recognize a contractual obligation unless (1) the
fair value option is applied to the liability or (2) the liability
represents a floating-rate obligation.
2.4.3.4 Change in Accounting Policy Related to Discounting of Contingent Liabilities
For those contingent liabilities that qualify for discounting,
the election to discount is a matter of accounting policy that should be
consistently applied and disclosed. An entity contemplating discounting a
contingent liability accounted for under ASC 450 should consider the guidance in
ASC 250-10-45-12 to determine whether discounting would be considered a
voluntary change in accounting principle that is preferable. If the entity
concludes that discounting a contingent liability is an allowable but not
preferred method, a change in accounting principle is not allowed. A voluntary
change in accounting principle would be accounted for in accordance with ASC
250-10.
On the other hand, if a change in the entity-specific facts and
circumstances regarding the predictability in the timing and amount of the
liability payments causes the contingent liability to no longer qualify for
discounting, a change to measuring the liability on an undiscounted basis would
not constitute a voluntary change in accounting principle; rather, it would be
accounted for as a change in accounting estimate in accordance with ASC
250-10.
2.5 Consideration of Inflation
A topic closely related to the discounting of liabilities is the
consideration of inflation when liabilities are measured. Contingent
liabilities may ultimately be settled many years after the current reporting
period. It is appropriate for an entity to consider the impact of inflation
when measuring a contingent liability, irrespective of whether the liability
qualifies to be discounted and ultimately is discounted, unless it is
impracticable for the entity to do so. Although ASC 450-20 does not provide
guidance on whether an entity should consider the impact of inflation when
measuring a contingent liability, an entity should consider the guidance in
ASC 410-20 and ASC 410-30 on asset retirement obligations and environmental
obligations, respectively, which may be useful for evaluating whether the
impact of inflation should be considered when other types of contingent
liabilities are measured. Specifically, ASC 410-20-55-13(b) and ASC
410-30-30-17 require an adjustment for inflation unless it is impracticable.
See also Section
3.4 of Deloitte’s Roadmap Environmental Obligations and Asset
Retirement Obligations.
2.6 Remeasurement and Derecognition of a Contingent Liability
2.6.1 Remeasurement
Unlike a contractual or legal liability (discussed in Section 2.2.4), whose measurement is
established on the basis of the contract or law, the initial and subsequent
measurement of a contingent liability in accordance with ASC 450-20-30 may
involve a number of judgments, including those discussed in Section 2.4. These
uncertainties may necessitate the continual evaluation and remeasurement of the
contingent liability as new information becomes available. Such remeasurement in
accordance with ASC 450-20-30 could produce an estimated amount that is lower or
higher when compared with the amount previously recognized, thereby resulting in
a reduction or increase, respectively, of the contingent liability. If the new
information indicates a reduction of the previously recognized liability, such a
reduction should not be viewed as tantamount to derecognition of the contingent
liability. That is, the remeasurement of a previously recognized contingent
liability on the basis of new information that supports a lower estimated
probable loss should not be viewed as a partial derecognition of a loss whose
occurrence was and continues to be considered probable; rather, it should be
viewed and accounted for as a change in estimate in accordance with ASC 250.
There may also be circumstances in which sufficient and reliable
data no longer are available to support an estimate that was previously made for
a contingent liability whose occurrence remains probable. For example, an entity
may recognize a contingent liability on the basis of an actuarial analysis of
historical loss data, but the availability of settlement data during recent
periods may have declined significantly because of external factors. The
decrease in the availability of recent loss data may have diminished the
entity’s ability to reasonably estimate the amount of the previously recognized
contingent liability. However, the entity may believe that it is still probable
that one or more future events will confirm that a liability has been incurred.
Therefore, while the entity concludes that a loss associated with the contingent
liability remains probable, it will nonetheless need to assess whether the
previously accrued amount continues to represent an appropriate estimate or
whether another estimate should be made on the basis of the recent circumstances
associated with the availability of recent data, which could result in a
reduction, or even a complete reversal, of the previously recognized loss. When
the entity is evaluating whether it is appropriate to remeasure a contingent
liability in such a circumstance, it should carefully support remeasurement with
compelling and sufficiently reliable evidence that provides a reasonable basis
for concluding that there has been a change in its previous judgment regarding
the amount of the estimated loss to accrue. Further, clear disclosure of the
change in facts and circumstances should be considered.
2.6.2 Derecognition When Settlement Is No Longer Considered Probable
As noted in Section 2.3, a contingency that fails to meet one or both of the two
criteria in ASC 450-20-25-2 does not reach the threshold for recognition in the
financial statements. However, questions may arise about when it is appropriate for
an entity to derecognize a previously recognized contingent liability when
settlement is no longer considered probable.
For example, an entity may recognize a contingent liability related
to the probable incurrence of a loss because of pending litigation. Subsequently and
on the basis of the facts and circumstances related to the litigation, the entity
may conclude that such a loss is no longer considered probable, even though the
matter is not subject to legal release or the statute of limitations given the
noncontractual nature of the contingency. In such a scenario, derecognition of the
contingent liability would be reasonable given the conclusion that a loss is no
longer considered probable. However, the assessment of whether a contingency is
likely to occur often involves considerable subjectivity. In those cases, it may be
prudent to reduce or reverse an existing accrual only when there is reasonably clear
or compelling evidence that a loss is no longer considered probable. When
determining the sufficiency of evidence to support derecognition, an entity should
consider the potential that derecognition in certain circumstances could be
misleading to financial statement users because it could inappropriately communicate
that the liability has been extinguished when the contingency still exists. The
entity should clearly disclose the change in the accrual and the underlying facts
and circumstances.
The example below illustrates a scenario in which derecognition of a
contingent liability may be appropriate when settlement is no longer considered
probable.
Example 2-18
Derecognition of a Contingent Liability
Company S is a defendant in a lawsuit filed in 20X2 by a
competitor, Company Z. In 20X4, a jury finds in favor of Z
and awards damages of $10 million. Company S’s management
determines that it is probable that a liability has been
incurred despite its intent to appeal the verdict, and S
recognizes a loss in the 20X4 financial statements. In
December 20X8, the appeals court sets aside the previous
jury verdict and remands the case back to the lower court
for another trial. Company S has obtained an opinion from
its legal counsel that says S has meritorious defenses and
that the outcome of the new trial is uncertain after taking
into account the reasons for the findings of the appeals
court. Company S therefore derecognizes the previously
recognized contingent liability given that it has determined
that the evidence supported a conclusion that it was no
longer probable that it would incur a loss in accordance
with the litigation.
Company S should ensure that it has properly disclosed the
change in facts and circumstances in the financial
statements. In addition, although this illustrative example
is provided to present the analysis an entity may undertake
to determine when to derecognize a contingent liability, as
a practical matter, entities may often find it challenging
to obtain sufficiently compelling evidence to support a
conclusion to reverse some or all of an existing contingent
liability before complete elimination of the uncertainty.
Company S will need to consider the totality of evidence
available, including counsel’s views.
2.7 Balance Sheet Classification
The balance sheet
classification of an accrued contingent liability
should be based on the period in which the entity
expects the contingency to be settled. A liability
should be classified as short-term if it is
expected to be settled within one year or less of
the balance sheet date (or longer if the entity’s
operating cycle is greater than one year).
Otherwise, the liability should be classified as
long-term.
2.8 Disclosures
2.8.1 Disclosure Considerations Under ASC 450-20 and ASC 275
Disclosures of loss contingencies required under ASC 450-20 are intended to
provide users of financial statements with an understanding of risks and how
they could potentially affect the financial statements.
When performing accrual accounting, an entity must make
estimates in current-period financial statements to reflect current events and
transactions, the effects of which may not be precisely determinable until some
future period. The final results may not match original expectations.
Uncertainty about the outcome of future events is inherent in economics, and an
entity should understand that fact when reading reports on economic activities,
such as published financial statements. A business, to a great extent, is a
function of the environment in which it operates. Thus, it can be affected by
changing social, political, and economic factors. In addition, every entity is
subject to uncertain future events that may affect the entity or the industry in
which it operates. These uncertainties may or may not be considered
contingencies as defined by ASC 450-10-20. As a result, the disclosures required
by ASC 275-10-50 supplement and, in many cases, overlap the disclosures required
by ASC 450-20-50.
Not all uncertainties inherent in the accounting process give
rise to contingencies as that word is used in ASC 450. Estimates are required in
financial statements for many of an entity’s ongoing and recurring activities.
The fact that an estimate is involved does not by itself constitute the type of
uncertainty referred to in the definition of a contingency in ASC 450-10-20. For
example, the fact that estimates are used to allocate the known cost of a
depreciable asset over the period of use by an entity does not make depreciation
a contingency; the eventual expiration of the use of the asset is not uncertain.
Thus, depreciation of assets is not a contingency as discussed in ASC
450-10-55-2. In addition, matters related to depreciation (e.g., recurring
repairs, maintenance, and overhauls) are similarly outside the scope of ASC 450.
Amounts owed for services received, such as advertising and utilities, are not
contingencies even though the accrued amounts may have been estimated; there is
nothing uncertain about the fact that those obligations have been incurred.
Some degree of estimation is required for nearly all financial
statement amounts. However, many lawsuits that may create a material liability
are not recorded because one or both conditions for recognizing a contingent
liability are not met; they are nonetheless disclosed to the extent that a loss
is reasonably possible.
Neither ASC 450-20 nor any other authoritative literature
contains definitive guidelines on measuring the difference between estimates
that are affected by uncertainty that can be estimated reasonably and those that
cannot be estimated reasonably. Although estimates generally include some level
of uncertainty, they are not necessarily loss contingencies. Thus, estimates
regarding events in the normal course of business have frequently been included
in the financial statements without specific disclosure since ASC 450-20-50
requires disclosure of only contingencies. ASC 275-10-50 extends disclosure
requirements to numerous risks and uncertainties, many of which are not
considered contingencies.
ASC 450-20
Accruals for Loss Contingencies
50-1 Disclosure of the nature
of an accrual made pursuant to the provisions of
paragraph 450-20-25-2, and in some circumstances the
amount accrued, may be necessary for the financial
statements not to be misleading. Terminology used shall
be descriptive of the nature of the accrual, such as
estimated liability or liability of an estimated amount.
The term reserve shall not be used for an accrual
made pursuant to paragraph 450-20-25-2; that term is
limited to an amount of unidentified or unsegregated
assets held or retained for a specific purpose. Examples
1 (see paragraph 450-20-55-18) and 2, Cases A, B, and D
(see paragraphs 450-20-55-23, 450-20-55-27, and
450-20-55-32) illustrate the application of these
disclosure standards.
50-2 If the
criteria in paragraph 275-10-50-8 are met, paragraph
275-10-50-9 requires disclosure of an indication that it
is at least reasonably possible that a change in an
entity’s estimate of its probable liability could occur
in the near term. Example 3 (see paragraph 450-20-55-36)
illustrates this disclosure for an entity involved in
litigation.
50-2A The disclosures required
by paragraphs 450-20-50-3 through 50-6 do not apply to
credit losses on instruments within the scope of Topic
326 on measurement of credit losses. (See paragraph
310-10-50-21.)
50-3
Disclosure of the contingency shall be made if there is
at least a reasonable possibility that a loss or an
additional loss may have been incurred and either of the
following conditions exists:
- An accrual is not made for a loss contingency because any of the conditions in paragraph 450-20-25-2 are not met.
- An exposure to loss exists in excess of the amount accrued pursuant to the provisions of paragraph 450-20-30-1.
Examples 1–3 (see paragraphs 450-20-55-18 through 55-37)
illustrate the application of these disclosure
standards.
50-4 The
disclosure in the preceding paragraph shall include both
of the following:
- The nature of the contingency
- An estimate of the possible loss or range of loss or a statement that such an estimate cannot be made.
50-5 Disclosure is preferable
to accrual when a reasonable estimate of loss cannot be
made. For example, disclosure shall be made of any loss
contingency that meets the condition in paragraph
450-20-25-2(a) but that is not accrued because the
amount of loss cannot be reasonably estimated (the
condition in paragraph 450-20-25-2(b)). Disclosure also
shall be made of some loss contingencies that do not
meet the condition in paragraph 450-20-25-2(a) — namely,
those contingencies for which there is a reasonable
possibility that a loss may have been incurred even
though information may not indicate that it is probable
that an asset had been impaired or a liability had been
incurred at the date of the financial statements.
50-6
Disclosure is not required of a loss contingency
involving an unasserted claim or assessment if there has
been no manifestation by a potential claimant of an
awareness of a possible claim or assessment unless both
of the following conditions are met:
- It is considered probable that a claim will be asserted.
- There is a reasonable possibility that the outcome will be unfavorable.
50-7
Disclosure of noninsured or underinsured risks is not
required by this Subtopic. However, disclosure in
appropriate circumstances is not discouraged.
ASC 275-10
50-7 Various
Topics require disclosures about uncertainties addressed
by those Topics. In particular, Subtopic 450-20
specifies disclosures to be made about contingencies
that exist at the date of the financial statements. In
addition to disclosures required by Topic 450 and other
accounting Topics, this Subtopic requires disclosures
regarding estimates used in the determination of the
carrying amounts of assets or liabilities or in
disclosure of gain or loss contingencies, as described
below.
50-8
Disclosure regarding an estimate shall be made when
known information available before the financial
statements are issued or are available to be issued (as
discussed in Section 855-10-25) indicates that both of
the following criteria are met:
- It is at least reasonably possible that the estimate of the effect on the financial statements of a condition, situation, or set of circumstances that existed at the date of the financial statements will change in the near term due to one or more future confirming events.
- The effect of the change would be material to the financial statements.
50-9 The
disclosure shall indicate the nature of the uncertainty
and include an indication that it is at least reasonably
possible that a change in the estimate will occur in the
near term. If the estimate involves a loss contingency
covered by Subtopic 450-20, the disclosure also shall
include an estimate of the possible loss or range of
loss, or state that such an estimate cannot be made.
Disclosure of the factors that cause the estimate to be
sensitive to change is encouraged but not required. The
words reasonably possible need not be used in the
disclosures required by this Subtopic.
50-11 This
Subtopic’s disclosure requirements are separate from and
do not change in any way the disclosure requirements or
criteria of Topic 450; rather, the disclosures required
under this Subtopic supplement the disclosures required
under that Topic as follows:
- If an estimate (including estimates that involve contingencies covered by Topic 450) meets the criteria for disclosure under paragraph 275-10-50-8, this Subtopic requires disclosure of an indication that it is at least reasonably possible that a change in the estimate will occur in the near term; Topic 450 does not distinguish between near-term and long-term contingencies.
- An estimate that does not involve a contingency covered by Topic 450, such as estimates associated with long-term operating assets and amounts reported under profitable long-term contracts, may meet the criteria in paragraph 275-10-50-8. This Subtopic requires disclosure of the nature of the estimate and an indication that it is at least reasonably possible that a change in the estimate will occur in the near term.
50-12 If a
loss contingency meets the criteria for disclosure under
both Topic 450 and paragraph 275-10-50-8, this Subtopic
requires disclosure that it is at least reasonably
possible that future events confirming the fact of the
loss or the change in the estimated amount of the loss
will occur in the near term.
In addition to being required to provide the primary disclosures
under ASC 450-20, an entity must provide certain additional disclosures under
ASC 275 when it is reasonably possible that a change in estimate will occur in
the near term. The disclosure requirements under ASC 450-20 and ASC 275 are
summarized in the table below.
Possibility That a Loss Has Been Incurred
|
Ability to Estimate a Loss
|
Disclosure Requirements of ASC 450-20 and ASC 275
|
---|---|---|
Reasonably possible
|
May or may not be reasonably estimable
|
Disclose all of the following:
|
Probable
|
Not reasonably estimable
|
Disclose both of the following:
|
Probable
|
Reasonably estimable
|
Disclose all of the following:
|
Remote
|
Not reasonably estimable
|
No specific disclosure requirements related to remote
contingencies; however, disclosures may be provided if
their omission could cause the financial statements to
be misleading.
|
Example 3 of ASC 450-20-55-36 illustrates the determination and disclosure of a
range of estimates.
ASC 450-20
Example 3: Illustrative Disclosure
55-36 Entity
A is the defendant in litigation involving a major
competitor claiming patent infringement (Entity B). The
suit claims damages of $200 million. Discovery has been
completed, and Entity A is engaged in settlement
discussions with the plaintiff. Entity A has made an
offer of $5 million to settle the case, which offer was
rejected by the plaintiff; the plaintiff has made an
offer of $35 million to settle the case, which offer was
rejected by Entity A. Based on the expressed willingness
of the plaintiff to settle the case along with
information revealed during discovery and the likely
cost and risk to both sides of litigating, Entity A
believes that it is probable the case will not come to
trial. Accordingly, Entity A has determined that it is
probable that it has some liability. Entity A’s
reasonable estimate of this liability is a range between
$10 million and $35 million, with no amount within that
range a better estimate than any other amount;
accordingly, $10 million was accrued.
55-37 Entity
A provides the following disclosure in accordance with
Section 450-20-50.
On March 15, 19X1,
Entity B filed a suit against the company claiming
patent infringement. While the company believes it has
meritorious defenses against the suit, the ultimate
resolution of the matter, which is expected to occur
within one year, could result in a loss of up to $25
million in excess of the amount accrued.
SEC Considerations
ASC 450-20-50-4 requires disclosures about the nature of any material
contingency, including the amounts that might be paid, if a loss is at
least reasonably possible. In addition, SEC Regulation S-K, Item 303,
requires discussion of items that might affect a company’s liquidity or
financial position in the future, including contingent liabilities.
The SEC staff has consistently commented on and
challenged registrants’ compliance with the disclosure requirements in
ASC 450-20. For example, Scott Taub, deputy chief accountant in the
SEC’s Office of the Chief Accountant, noted the following in a
speech at the 2004 AICPA Conference on Current SEC
and PCAOB Developments:
Given [the requirement to
record an accrual if payment is both probable and estimable and the
requirement to disclose the nature of any material contingency,
including the amounts that might be paid, if a loss is at least
reasonably possible], the recording of a material accrual for a
contingent liability related to an event that occurred several years
before should not be the first disclosure regarding that
contingency. Rather, disclosures regarding the nature of the
contingency and the amounts at stake should, in most cases, have
already been provided. Disclosures should discuss the nature of the
contingency and the possible range of losses for any item where the
maximum reasonably possible loss is material. Vague or overly broad
disclosures that speak merely to litigation, tax, or other risks in
general, without providing any information about the specific kinds
of loss contingencies being evaluated are not sufficient.
Furthermore, I should point out that Statement 5
and Interpretation 14 [codified as ASC 450-20] require accrual for
probable losses of the most likely amount of the loss. While the low
end of a range of possible losses is the right number if no amount
within the range is more likely than any other, I find it somewhat
surprising how often “zero” is the recorded loss right up until a
large settlement is announced. [Footnote omitted]
The SEC staff made similar remarks at subsequent
conferences, including the 2010 AICPA Conference on Current SEC and
PCAOB Developments. To ensure compliance with the requirements in ASC
450-20, registrants should continually review their disclosures and
update them as additional information becomes available.
Non-SEC registrants may also consider the preceding SEC
staff remarks given that the disclosure objectives outlined by the staff
would generally be expected to apply to these entities’ financial
statements as well.
2.8.2 Disclosure of Unasserted Claims
ASC 450-20-50-6 indicates that a disclosure of a loss contingency
involving an unasserted claim is not required unless both of the following
conditions are met:
- It is considered probable that a claim will be asserted.
- There is a reasonable possibility that the outcome will be unfavorable.
This exception is specific to unasserted claims and should not be
applied by analogy to claims other than unasserted claims. An entity must evaluate
all the facts and circumstances in determining whether to disclose such a loss
contingency.
2.8.3 Disclosure of Loss Contingencies Occurring After Year-End
ASC 855-10-50-2 requires an entity to disclose a nonrecognized
subsequent event if it is “of such a nature that [it] must be disclosed to keep the
financial statements from being misleading.” Although whether to provide such a
disclosure is a matter of judgment, it would seem prudent for an entity to disclose
any matter that could materially affect its financial position, results of
operations, or trend of operations. In addition, an entity should consider
disclosing any accruals made in the subsequent reporting period as a nonrecognized
subsequent event within the current-period financial statements if the accruals (1)
are unusual or material to earnings of the current reporting period or (2)
materially affect the trend of earnings.
Disclosures about a loss or loss contingency occurring after year-end should include
(1) the nature of the loss or loss contingency and (2) an estimate of the amount or
range of loss or possible loss or a statement that such an estimate cannot be made.
If the effect on the entity’s financial position is material, it may be useful for
the entity to provide supplemental pro forma financial data reflecting the loss as
if it had occurred as of the date of the financial statements.
2.8.4 Disclosure of Firmly Committed Executory Contracts
ASC 440-10
50-2 An
unconditional purchase obligation that has all of the
following characteristics shall be disclosed in accordance
with paragraph 440-10-50-4 (if not recorded on the
purchaser’s balance sheet) or in accordance with paragraph
440-10-50-6 (if recorded on the purchaser’s balance
sheet):
- It is noncancelable, or cancelable
only in any of the following circumstances:
- Upon the occurrence of some remote contingency
- With the permission of the other party
- If a replacement agreement is signed between the same parties
- Upon payment of a penalty in an amount such that continuation of the agreement appears reasonably assured.
- It was negotiated as part of arranging financing for the facilities that will provide the contracted goods or services or for costs related to those goods or services (for example, carrying costs for contracted goods). A purchaser is not required to investigate whether a supplier used an unconditional purchase obligation to help secure financing, if the purchaser would otherwise be unaware of that fact.
- It has a remaining term in excess of one year.
Unrecognized Commitments
50-4 A
purchaser shall disclose unconditional purchase obligations
that meet the criteria of paragraph 440-10-50-2 and that
have not been recognized on its balance sheet. Disclosures
of similar or related unconditional purchase obligations may
be combined. The disclosures shall include all of the
following:
- The nature and term of the obligation(s)
- The amount of the fixed and determinable portion of the obligation(s) as of the date of the latest balance sheet presented, in the aggregate and, if determinable, for each of the five succeeding fiscal years
- The nature of any variable components of the obligation(s)
- The amounts purchased under the obligation(s) (for example, the take-or-pay or throughput contract) for each period for which an income statement is presented.
The preceding disclosures may be omitted only if the
aggregate commitment for all such obligations not disclosed
is immaterial.
50-5 Disclosure
of the amount of imputed interest necessary to reduce the
unconditional purchase obligation(s) to present value is
encouraged but not required. The discount rate shall be the
effective initial interest rate of the borrowings that
financed the facility (or facilities) that will provide the
contracted goods or services, if known by the purchaser. If
not, the discount rate shall be the purchaser’s incremental
borrowing rate at the date the obligation is entered
into.
Recognized Commitments
50-6 A
purchaser shall disclose for each of the five years
following the date of the latest balance sheet presented the
aggregate amount of payments for unconditional purchase
obligations that meet the criteria of paragraph 440-10-50-2
and that have been recognized on the purchaser’s balance
sheet.
An entity should provide the incremental disclosures required by ASC
440-10-50-2 that pertain to unconditional purchase obligations or firmly committed
executory contracts. Specifically, when an executory contract is material and has
not been recognized in the financial statements, the entity should comply with the
disclosure requirements of ASC 440-10-50-4(a)–(d). When the entity has recognized an
executory contract on the balance sheet, it should disclose total payments for each
of the five years after the date of the latest balance sheet.
SEC Considerations
In addition to providing the footnote disclosures required
by ASC 440-10-50, an entity must provide incremental disclosures within
MD&A under SEC Regulation S-K, Item 303. Because the disclosures
required by SEC Regulation S-K may be broader than those required by ASC
440-10-50-2, SEC registrants may reflect different amounts related to
purchase obligations in the notes to the financial statements than they do
in MD&A.
2.9 Subsequent-Event Considerations
Entities should have processes in place to capture and evaluate events
that occur after the balance sheet date, but before the financial statements are issued
or are available to be issued, to determine whether the events should be recognized in
current-period or subsequent-period financial statements.
The recognition, measurement, and disclosure principles related to loss
contingencies described in this chapter apply to the period after the balance sheet date
but before the financial statements are issued or are available to be issued.
ASC 450-20 includes guidance on accounting for subsequent events.
ASC 450-20
25-2 An estimated
loss from a loss contingency shall be accrued by a charge to
income if both of the following conditions are met:
- Information available before the financial statements are issued or are available to be issued (as discussed in Section 855-10-25) indicates that it is probable that an asset had been impaired or a liability had been incurred at the date of the financial statements. Date of the financial statements means the end of the most recent accounting period for which financial statements are being presented. It is implicit in this condition that it must be probable that one or more future events will occur confirming the fact of the loss.
- The amount of loss can be reasonably estimated.
The purpose of those conditions is to require
accrual of losses when they are reasonably estimable and relate
to the current or a prior period. Paragraphs 450-20-55-1 through
55-17 and Examples 1–2 (see paragraphs 450-20-55-18 through
55-35) illustrate the application of the conditions. As
discussed in paragraph 450-20-50-5, disclosure is preferable to
accrual when a reasonable estimate of loss cannot be made.
Further, even losses that are reasonably estimable shall not be
accrued if it is not probable that an asset has been impaired or
a liability has been incurred at the date of an entity’s
financial statements because those losses relate to a future
period rather than the current or a prior period. Attribution of
a loss to events or activities of the current or prior periods
is an element of asset impairment or liability incurrence.
25-6 After the date
of an entity’s financial statements but before those financial
statements are issued or are available to be issued (as
discussed in Section 855-10-25), information may become
available indicating that an asset was impaired or a liability
was incurred after the date of the financial statements or that
there is at least a reasonable possibility that an asset was
impaired or a liability was incurred after that date. The
information may relate to a loss contingency that existed at the
date of the financial statements, for example, an asset that was
not insured at the date of the financial statements. On the
other hand, the information may relate to a loss contingency
that did not exist at the date of the financial statements, for
example, threat of expropriation of assets after the date of the
financial statements or the filing for bankruptcy by an entity
whose debt was guaranteed after the date of the financial
statements. In none of the cases cited in this paragraph was an
asset impaired or a liability incurred at the date of the
financial statements, and the condition for accrual in paragraph
450-20-25-2(a) is, therefore, not met.
The guidance in ASC 450 indicates that entities should consider
information available before the financial statements are issued or are available to be
issued when determining whether it is probable that an asset has been impaired or a loss
event has occurred as of the balance sheet date. ASC 450 does not specifically address
events occurring after the balance sheet date that provide additional information
related to the measurement of a loss contingency; however, entities should consider the
subsequent-event guidance that is codified in ASC 855-10.
ASC 855-10
Recognized Subsequent
Events
Evidence About Conditions
That Existed at the Date of the Balance
Sheet
25-1 An entity shall
recognize in the financial statements the effects of all
subsequent events that provide additional evidence about
conditions that existed at the date of the balance sheet,
including the estimates inherent in the process of preparing
financial statements. See paragraph 855-10-55-1 for examples of
recognized subsequent events.
55-1 The following are examples of
recognized subsequent events addressed in paragraph
855-10-25-1:
- If the events that gave rise to litigation had taken place before the balance sheet date and that litigation is settled after the balance sheet date but before the financial statements are issued or are available to be issued, for an amount different from the liability recorded in the accounts, then the settlement amount should be considered in estimating the amount of liability recognized in the financial statements at the balance sheet date.
- Subsequent events affecting the realization of assets, such as inventories, or the settlement of estimated liabilities, should be recognized in the financial statements when those events represent the culmination of conditions that existed over a relatively long period of time.
Nonrecognized Subsequent
Events
Evidence About Conditions
That Did Not Exist at the Date of the Balance
Sheet
25-3 An entity
shall not recognize subsequent events that provide evidence
about conditions that did not exist at the date of the balance
sheet but arose after the balance sheet date but before
financial statements are issued or are available to be issued.
See paragraph 855-10-55-2 for examples of nonrecognized
subsequent events.
55-2 The following are examples of
nonrecognized subsequent events addressed in paragraph
855-10-25-3:
- Sale of a bond or capital stock issued after the balance sheet date but before financial statements are issued or are available to be issued
- A business combination that occurs after the balance sheet date but before financial statements are issued or are available to be issued (Topic 805 requires specific disclosures in such cases.)
- Settlement of litigation when the event giving rise to the claim took place after the balance sheet date but before financial statements are issued or are available to be issued
- Loss of plant or inventories as a result of fire or natural disaster that occurred after the balance sheet date but before financial statements are issued or are available to be issued
- Changes in estimated credit losses on receivables arising after the balance sheet date but before financial statements are issued or are available to be issued
- Changes in the fair value of assets or liabilities (financial or nonfinancial) or foreign exchange rates after the balance sheet date but before financial statements are issued or are available to be issued
- Entering into significant commitments or contingent liabilities, for example, by issuing significant guarantees after the balance sheet date but before financial statements are issued or are available to be issued.
50-2 Some
nonrecognized subsequent events may be of such a nature that
they must be disclosed to keep the financial statements from
being misleading. For such events, an entity shall disclose the
following:
- The nature of the event
- An estimate of its financial effect, or a statement that such an estimate cannot be made.
Connecting the Dots
ASC 450 and ASC 855 provide guidance on how to evaluate events
occurring after the balance sheet date. The period through which subsequent
events must be evaluated differs for (1) SEC filers and “conduit bond obligor[s]
for conduit debt securities that are traded in a public market (a domestic or
foreign stock exchange or an over-the-counter market, including local or
regional markets)” and (2) entities that are neither SEC filers nor conduit bond
obligors. SEC filers and conduit bond obligors should evaluate events that occur
through the date on which the financial statements are issued, whereas entities
that are neither SEC filers nor conduit bond obligors should evaluate events
that occur through the date on which the financial statements are available to
be issued. To determine whether an entity is a conduit bond obligor, entities
should refer to the definitions of “SEC filer” and “conduit debt securities” in
the ASC master glossary.
If an event takes place after the balance sheet date but before the
financial statements are issued or are available to be issued, and the event indicates
that it is probable that an asset has been impaired or a liability has been incurred as
of the balance sheet date, the event is considered a recognized subsequent event. The
event provides additional evidence of the loss incurred before the balance sheet date
and should be reflected in the financial statements.
Examples of events that provide additional information about conditions
that existed as of the balance sheet date and therefore should be accounted for as
recognized subsequent events include the following:
- An unfavorable court ruling in a lawsuit. The company had previously determined that the likelihood of an unfavorable outcome would be remote or reasonably possible but now considers it probable.
- A litigation settlement that indicates a loss amount different from that previously recognized in the financial statements.
- The identification of asset misappropriation that occurred on or before the balance sheet date and for which no loss had previously been recognized.
If events constitute additional information that an asset had been
impaired or a liability had been incurred as of the balance sheet date, but the amount
of the loss cannot be reasonably estimated before the financial statements are issued or
are available to be issued, the entity should consider whether disclosures are provided
in accordance with Section
2.8.1.
A loss should be recognized only when events confirm that an asset had
been impaired or a liability existed as of the balance sheet date. If a loss contingency
that did not exist as of the balance sheet date occurs after the balance sheet date but
before the financial statements are issued or are available to be issued, the entity
would not recognize the loss as of the balance sheet date but may need to disclose it as
a subsequent event to keep the financial statements from being misleading.
The enactment of a law that gives rise to a liability after the balance
sheet date but before the financial statements are issued or are available to be issued
is a nonrecognized subsequent event. The newly enacted law does not provide evidence of
conditions that existed as of the balance sheet date. However, the entity should
consider whether it is required to disclose the event to keep the financial statements
from being misleading. For additional information on the enactment of a law or
legislation, see Section
2.3.1.3.
Example 2-19
Legislation Enacted After
the Balance Sheet Date
Company A, a public entity with a December 31,
20X1, year-end, operates in the banking industry and is subject
to proposed legislation that will impose a fee on deposits that
existed as of June 30, 20X1. The legislation is expected to be
enacted after year-end but before the issuance of the financial
statements. Company A believes that because enactment of the
legislation is probable and is related to balances as of a date
before the balance sheet date, an accrual should be made.
However, the obligating event in this case is the enactment of
the legislation, before which A did not incur a liability even
though a fee was assessed on preexisting balances; thus, no
accrual should be made as of December 31, 20X1. Instead, the
impact of the new legislation is a nonrecognized subsequent
event, and A should consider whether it is required to disclose
the event in its December 31, 20X1, financial statements to keep
them from being misleading.
If a recognized contingent liability is settled after the balance sheet
date but before the financial statements are issued or are available to be issued, a
contingent liability should be reversed as of the balance sheet date to the extent that
the recognized liability exceeds the settlement amount. The settlement constitutes
additional evidence of conditions that existed as of the balance sheet date and would be
considered a recognized subsequent event.