FAR Area III.B Mastery Notes: Contingencies and Commitments (Recognition, Measurement, Disclosure)
Contingencies vs. commitments: what you’re accounting for (and why it’s tricky)
A contingency is an existing situation involving uncertainty about a possible gain or loss that will be resolved by a future event (or events). The key idea is that the underlying condition already exists today—you just don’t yet know the outcome. Classic examples include lawsuits, threatened regulatory actions, product warranties, and environmental remediation.
A commitment is different: it’s typically an executory contract—a binding agreement where both sides still have significant performance remaining (for example, a firm purchase commitment to buy inventory next year at a fixed price, or a commitment to extend credit). Commitments often don’t meet the definition of a liability today because, absent loss conditions, neither party has performed and there isn’t a present obligation to transfer assets yet. Even so, commitments can create significant risk, so GAAP often requires disclosure, and sometimes loss recognition if the commitment becomes unfavorable.
Why FAR tests this heavily: these topics sit right on the boundary between (1) what must be recognized on the balance sheet and (2) what is “off-balance-sheet” but still important. The exam frequently asks you to apply probability thresholds, decide between accrual vs disclosure, and measure the amount to record.
The organizing framework you should internalize
Under U.S. GAAP (especially ASC 450 for many contingencies), you generally make two decisions:
- Recognition (accrue or not?)
- Do you record a liability (and expense or loss) now?
- Disclosure (footnote or not?)
- Even if you don’t record it, do users need to be told?
Those decisions depend on the likelihood of an outflow (for losses) and whether you can reasonably estimate the amount.
Exam Focus
- Typical question patterns
- You’re given a lawsuit/warranty scenario and must choose accrue vs disclose vs do nothing.
- You’re given a range of potential losses and must determine the amount to record.
- You’re asked what to do with gain contingencies (often a trap).
- Common mistakes
- Treating a commitment like a liability even when no loss is indicated.
- Confusing “reasonably possible” with “probable” and recording too early.
- Recording the maximum of a loss range when GAAP usually requires a different approach.
Loss contingencies (ASC 450): recognition thresholds and the probability ladder
A loss contingency is a contingency that could result in a loss (or an impairment) in the future—meaning a future outflow of resources or a reduction in asset value.
The probability categories (remote, reasonably possible, probable)
U.S. GAAP uses three probability descriptors:
- Probable: the future event is likely to occur.
- Reasonably possible: more than remote but less than likely.
- Remote: slight chance.
These words are intentionally judgmental. On the CPA exam, the fact pattern will usually signal the category using wording like “legal counsel believes it is likely” (probable) or “could occur” (reasonably possible).
When you accrue a loss
You accrue (record) a loss contingency when both conditions are met:
- It is probable that a liability has been incurred as of the financial statement date, and
- The amount of loss can be reasonably estimated.
If either condition is not met, you generally do not record a liability—though you may still need disclosure.
Why this rule exists: financial statements should reflect obligations that are effectively already “real” at the reporting date. But GAAP also tries to prevent companies from recording speculative amounts that are more guesswork than measurement.
When you disclose (but don’t accrue)
You generally disclose a loss contingency when:
- There is at least a reasonable possibility of loss (even if not probable), or
- The loss is probable but not reasonably estimable.
Disclosure typically includes the nature of the contingency and an estimate or range of possible loss, or a statement that such an estimate cannot be made.
When you do nothing
If the chance of loss is remote, you usually do not accrue and do not disclose.
A practical way to remember the hierarchy:
- Probable + estimable: record it.
- Reasonably possible: disclose it.
- Remote: ignore it (usually).
Measuring the amount to accrue (single best estimate vs. range)
Once you decide to accrue, you must determine how much.
- If one amount within a range is a better estimate than any other amount, accrue that best estimate.
- If no amount in the range is a better estimate than any other (all are equally likely), accrue the minimum amount in the range, and disclose the range.
This is a common FAR testing point because many people instinctively want to “be conservative” and record the high end. Under GAAP, that’s not the default unless it’s the best estimate.
Example 1: lawsuit—probable and estimable (accrue)
Assume a company is sued. Legal counsel believes an unfavorable outcome is probable and estimates the loss will be between and , with as the best estimate.
How it works: because the loss is probable and a best estimate exists, you record the best estimate.
Record:
- Loss expense
- Litigation liability
Footnote disclosure would still typically describe the nature of the contingency (and may mention the range, depending on facts), but the key point is the accrual.
Example 2: warranty claims—probable and estimable using expected experience
Warranties are a classic loss contingency because the sale has already occurred, creating a present obligation to repair/replace if claims arise. You often estimate warranty expense based on historical claim rates.
Assume sales for the year are and expected warranty costs are of sales.
Compute estimated warranty cost:
Record:
- Warranty expense
- Warranty liability
What goes wrong: students sometimes wait until actual claims are paid. That would violate accrual accounting because the obligation is incurred when the product is sold (matching principle).
Example 3: loss range with no best estimate (accrue minimum + disclose range)
Assume a company faces a probable environmental penalty estimated to fall in the range to , and no amount is a better estimate than any other.
Accrue the minimum:
Disclose the range to in the footnotes.
Exam Focus
- Typical question patterns
- Given probability wording and an amount or range, decide accrue/disclose/neither.
- Given a range, decide whether to accrue the best estimate or the minimum.
- Warranty scenarios that test whether you understand the obligation arises at sale.
- Common mistakes
- Accruing when the outcome is only reasonably possible.
- Accruing the maximum of a range when no best estimate exists.
- Ignoring the “estimable” criterion (probable but not estimable usually means disclose, not accrue).
Gain contingencies: why GAAP is stricter (and what you can still disclose)
A gain contingency is a contingency that could result in a gain—for example, winning a lawsuit, receiving an insurance recovery in excess of recorded losses, or collecting a disputed claim.
The core rule: don’t recognize gains until realized or realizable
Under U.S. GAAP, you generally do not record a gain contingency before it is realized (or realizable). Even if the gain seems “probable,” GAAP is conservative about recognizing income that could reverse.
Why it matters: recognizing gains too early can inflate earnings and mislead users. A company might look profitable based on a lawsuit “win” that later evaporates on appeal.
What you can do: disclose when the gain is probable
If realization of a gain is probable, you may disclose it—being careful not to imply a certainty that doesn’t exist. Disclosure tends to be more qualitative and less precise than for losses.
Example: lawsuit where the company is the plaintiff
A company sues a supplier. Counsel believes the company will likely win .
- No journal entry for the gain before resolution.
- Possible disclosure if the gain is probable, typically describing the nature and status.
What goes wrong: a common FAR trap is to treat probable gain contingencies like probable loss contingencies and record a receivable/income. That is not the GAAP model.
Exam Focus
- Typical question patterns
- “Should the company record a receivable for a probable settlement?” (Usually no.)
- Questions contrasting loss vs gain treatment using identical probability terms.
- Common mistakes
- Recording gain contingencies based on “probable.”
- Netting a gain contingency against a loss contingency (generally not allowed—recognition rules differ).
Special contingency applications commonly tested: litigation, unasserted claims, insurance recoveries, and guarantees
ASC 450 provides the backbone, but FAR commonly tests how that backbone applies in specific real-world situations.
Litigation and claims (including unasserted claims)
Litigation is the most common setting for ASC 450.
- If a lawsuit is probable and estimable, accrue.
- If reasonably possible, disclose.
- If remote, usually do nothing.
Unasserted claims add a twist: these are potential claims where no one has filed suit (yet). You consider accrual/disclosure only if:
- It is probable that a claim will be asserted, and
- The outcome would be unfavorable, and the loss is probable/estimable under normal rules.
In practice, unasserted claims require judgment because you’re predicting whether someone will even bring the claim.
Insurance recoveries related to losses
Companies often have insurance that may reimburse part of a loss (for example, damages from a lawsuit or casualty). The key is to separate:
- The loss contingency (what you owe or what you lost), and
- The potential recovery (what the insurer might pay).
If the underlying loss is probable and estimable, you record the loss. You record an insurance recovery only when it is probable the recovery will be received (and it is estimable). Importantly, you generally do not net the recovery against the loss in a way that hides gross exposures—presentation and disclosure depend on facts, but the exam often focuses on recognition timing.
What goes wrong: students delay recording the loss because “insurance will cover it.” GAAP focuses on the loss obligation/exposure first.
Guarantees (often associated with ASC 460)
A guarantee is an obligation to make payments if a specified event occurs—such as guaranteeing a third party’s debt, guaranteeing the residual value of leased assets, or providing a standby letter of credit.
From a financial reporting perspective, guarantees are tricky because the guarantor may have:
- A noncontingent obligation at inception (a stand-ready obligation), and/or
- A contingent obligation depending on whether the triggering event occurs.
FAR questions often test that guarantees can require recognition and disclosure even if the chance of payment seems low, because the guarantor has taken on risk by issuing the guarantee. In many cases, the guarantor recognizes a liability at fair value when the guarantee is issued (with subsequent accounting depending on the arrangement).
If a guarantee later becomes a probable loss under ASC 450-type thinking, additional accruals may be required.
Example: separating a recorded loss from a probable insurance recovery
Assume a company faces a probable litigation loss of . The insurer has confirmed coverage and counsel believes it is probable the insurer will reimburse .
Record the loss:
- Litigation loss
- Litigation liability
Record the recovery (because it is probable and estimable):
- Insurance receivable
- Gain from insurance recovery (or reduction of loss, depending on presentation guidance and the nature of the item)
On the exam, the main learning is that the loss recognition is not “blocked” by the recovery.
Exam Focus
- Typical question patterns
- “A claim has not been asserted—what needs to be accrued/disclosed?”
- “There is insurance—do we still accrue the loss?”
- Guarantee scenarios that ask whether a liability exists even before default.
- Common mistakes
- Recording a gain contingency for insurance proceeds when receipt is not probable.
- Ignoring unasserted claims entirely even when assertion is probable.
- Treating guarantees as purely remote contingencies with no accounting impact.
Commitments: disclosure-driven—until a loss makes it an accounting problem
A commitment is typically a binding agreement that will be performed in the future. Examples include:
- Purchase commitments (to buy inventory, commodities, equipment)
- Take-or-pay contracts (commit to buy a minimum quantity or pay a penalty)
- Commitments to extend credit (loan commitments)
- Capital commitments (commitments to build facilities or buy significant assets)
Why commitments are usually not recorded
In many commitments, both parties have not yet performed. Until performance occurs, there is often no present obligation that meets the definition of a liability. So GAAP frequently requires footnote disclosure rather than recognition.
But commitments matter because they create future cash flow obligations and risk. Users want to know about them—especially if market conditions shift and the company is stuck in an unfavorable contract.
Purchase commitments and the “onerous contract” idea (loss recognition when unfavorable)
A purchase commitment is an agreement to purchase goods at a fixed price in the future.
- If the fixed price is roughly equal to expected market price, there’s usually no accounting entry—just possible disclosure if material.
- If market price falls below the committed price, the commitment becomes unfavorable.
Under U.S. GAAP, when a firm purchase commitment becomes unfavorable and a loss is probable and estimable, you generally recognize a loss for the difference between the commitment price and the market price (subject to specific facts and guidance). The logic is that the company has effectively locked itself into paying more than the economic value it will receive.
Example: firm purchase commitment becomes unfavorable
Assume a company commits to buy units of raw material at per unit. Before year-end, market price falls to and the contract is noncancelable.
Compute the expected loss:
If the loss is probable and the company cannot avoid it, record:
- Loss on purchase commitment
- Liability for purchase commitment
When the inventory is later purchased, the accounting typically results in inventory recorded at market (or the lower amount) with the previously recognized loss not double-counted—on the CPA exam, you’re often tested mainly on recognizing the loss when the decline happens.
What goes wrong: students wait until the inventory is delivered. But if the contract is firm and unavoidable, the loss is associated with the unfavorable commitment at the reporting date.
Commitments to extend credit
A loan commitment is a promise to lend funds under specified terms. Usually, the commitment itself is disclosed (if material) rather than recorded as a liability. However, the commitment can create exposure—especially if terms are below-market or if fees are involved (specialized guidance can apply).
For FAR purposes, the highest-yield skill is distinguishing:
- Normal executory commitments (often disclosure) vs.
- Situations where the commitment has become a probable, estimable loss (which pushes you back into an ASC 450-style analysis).
Take-or-pay arrangements (conceptual)
In a take-or-pay contract, you must either:
- “Take” a minimum quantity of product/service, or
- “Pay” a penalty for not taking it.
Economically, this can resemble a fixed commitment. If circumstances indicate an unavoidable loss (for example, demand collapses and penalties are unavoidable), you analyze whether a loss is probable and estimable and whether recognition is required.
Exam Focus
- Typical question patterns
- “Is a firm purchase commitment recorded?” (Usually no, unless it’s unfavorable.)
- Compute and record the loss when market price drops below commitment price.
- Disclosure-only questions: “Which commitments must be disclosed?”
- Common mistakes
- Recording a liability for every commitment automatically (overrecognition).
- Failing to recognize a loss on an unfavorable, unavoidable purchase commitment.
- Mixing up market decline accounting for inventory (LCM concepts) with purchase commitment loss recognition.
Disclosure, presentation, and timing: putting contingencies/commitments into financial statements
Even when you’ve decided whether to accrue, FAR often tests how these items are communicated.
What contingency disclosures generally try to convey
For contingencies that are not accrued (or are accrued but still significant), disclosures typically address:
- Nature of the contingency (what happened?)
- Timing and uncertainty (what’s unresolved?)
- Estimated loss or range, or a statement that an estimate cannot be made
The guiding purpose is to help users understand risk exposures that may affect future cash flows.
Accrued contingencies: why disclosure can still be necessary
Recording a liability answers “how much is currently recognized,” but users may still need context:
- The accrued amount might be a minimum in a wide range.
- Outcomes might include nonfinancial impacts (injunctions, operational restrictions).
- The matter might be material and unusual.
So don’t assume “I accrued it, so I’m done.” Material matters often require both accrual and footnote discussion.
Remote-but-disclosed exceptions (conceptual note)
While the general rule is “remote = no disclosure,” in practice there are limited circumstances in GAAP where even remote exposures can warrant disclosure (for example, certain guarantee-related or severe risk exposures). On the CPA exam, you’ll usually be guided by the specific fact pattern and the general ASC 450 ladder unless a question explicitly signals a special-case standard (like guarantees).
Timing and the link to subsequent events
Contingencies are especially sensitive to the balance sheet date and what becomes known afterward. A helpful mental model:
- The contingency assessment is about conditions existing as of year-end.
- Information learned after year-end may provide additional evidence about what the condition was at year-end.
So if you learn after year-end (but before issuance) that you lost a lawsuit related to a pre-year-end event, that outcome can strongly affect whether a loss was probable/estimable at year-end and may require accrual.
Conversely, if the underlying event occurs after year-end (a brand-new lawsuit from a post-year-end incident), it usually doesn’t lead to accrual at year-end—though disclosure might be required depending on significance.
Mini-scenario: adjusting vs. nonadjusting logic applied to contingencies
- A customer injury occurred in December (pre-year-end), and in January you receive strong evidence of the likely settlement amount. That January info helps you measure a pre-existing condition—often leading to accrual at year-end.
- A factory accident occurs in January (post-year-end). Even if the expected loss is huge, it generally doesn’t create a year-end liability because the condition didn’t exist yet—though disclosure as a subsequent event may be needed.
Exam Focus
- Typical question patterns
- Distinguish whether new information after year-end changes the year-end accrual decision.
- Identify what a proper footnote disclosure should include (nature + estimate/range or inability to estimate).
- Common mistakes
- Treating all post-year-end developments as nonadjusting (some provide evidence about year-end conditions).
- Omitting disclosure when loss is reasonably possible.
- Assuming disclosure is unnecessary once an amount is accrued.