7 Step U.S. GAAP Workflow to Catch Goodwill Impairment Indicators

Not every rough quarter triggers a goodwill test, but certain facts always do. If a reporting unit shows sustained share-price declines, a widening gap between fair value and carrying amount, or a material adverse change in its cash flows, you have a triggering event under ASC 350 and testing is required now, not at the next annual date. The indicator categories to screen are macroeconomic conditions, industry performance, entity-specific results, reporting-unit events, and market metrics. Whether you run a qualitative screen or jump straight to quantitative testing depends on how much cushion you had last time.

---

TL;DR:

• If a company's share price declines significantly or market capitalization falls below book value, immediate impairment testing is required regardless of the last review date.
• A large cushion between last fair value and carrying amount (such as 40%) often justifies skipping detailed qualitative assessment, but a thin cushion (around 3%) warrants direct quantitative testing.
• Triggering events include macroeconomic shifts, industry declines, entity-specific losses, or adverse reporting unit events, especially if they persist over time.
• Performing valuations with sensitivity analysis on discount rates and growth assumptions helps assess how close a unit might be to impairment thresholds, guiding testing decisions.
• Continuous monitoring of filings and operational performance enhances early detection of adverse factors, enabling timely intervention before financial statements are impacted.

---

Table of Contents

• Goodwill Impairment Testing: When Annual Reviews Aren't Enough
• Qualitative Assessment (Step 0): Deciding Whether to Skip the Math
• A Category Checklist for Triggering Events
• The Quantitative Test: Measuring the Impairment
• Using Market Evidence to Calibrate Fair Value
• Building a Defensible Trigger-Assessment Workflow
• Where Goodwill Testing Goes Wrong
• How Filings-Based Monitoring Sharpens the Trigger Process
• Speed Up Evidence Gathering With FilingsIQ
• Sources
• FAQ

Goodwill Impairment Testing: When Annual Reviews Aren't Enough

Goodwill gets tested at least once a year, on a date you choose and apply consistently. But the annual calendar isn't the whole story. Under ASC 350, you also have to test between annual dates whenever an event or change in circumstances makes it more likely than not that a reporting unit's fair value has dropped below its carrying amount. "More likely than not" means a probability over 50 percent. It's a lower bar than "probable," and that distinction trips up a surprising number of preparers who treat interim testing as a last resort rather than a routine obligation.

Here's where the timing gets genuinely practical. You get to pick your annual test date, and different reporting units can use different dates if that fits your acquisition history or reporting structure better. Many companies default to the fourth quarter to align with budget season, but there's no requirement to do so. What matters is applying the same date consistently once you've chosen it, so examiners and auditors can track whether interim testing supplemented or replaced the scheduled review.

A few situations complicate the calendar in ways worth flagging early:

• Recent acquisitions. Newly acquired goodwill isn't exempt from interim testing just because the ink is barely dry. If facts emerge suggesting the deal was overpriced, a quantitative test can be required before the first annual date arrives.
• Reorganizations. When you realign reporting units or shift how goodwill is assigned, you need to reassess whether the carrying amounts and cushions from the prior test still apply to the new structure.
• Subsequent events. A material development that surfaces after your annual test date but before the financials are issued, like a major customer loss or a credit downgrade, can require a fresh look even though the formal test just closed.

Skipping interim testing because "we just did the annual test three months ago" is a common shortcut, and it's the wrong one. The standard doesn't care how recently you tested. It cares whether the facts on the ground have changed enough to flip the probability calculation. Build a habit of screening for triggers at every quarter close, not just at year end, and you'll catch the events that matter before they become disclosure surprises.

Qualitative Assessment (Step 0): Deciding Whether to Skip the Math

The qualitative assessment, often called step 0, lets you avoid a full valuation exercise if the weight of the evidence tells you fair value almost certainly still exceeds carrying amount. You're not calculating anything here. You're weighing factors and forming a judgment about probability. If, after considering everything relevant, you conclude it is not more likely than not that fair value is below carrying amount, you stop there. No quantitative test needed for that reporting unit this cycle.

The concept that does most of the work in this decision is cushion, the gap between the fair value you calculated the last time you did a quantitative test and the unit's current carrying amount. A reporting unit that cleared its last test with fair value 40 percent above carrying amount has a lot of room to absorb bad news before crossing into impairment territory. A unit that cleared by 3 percent has almost none. Cushion size is the single factor that most determines whether step 0 is even appropriate, because a thin cushion means even modest deterioration could flip the conclusion.

ASC 350 lists example factors to weigh, and the key word is "totality." No single item on this list settles the question by itself:

• Macroeconomic conditions, including deteriorating credit markets or currency exposure
• Industry and market conditions, such as a shrinking peer group or new regulatory burden
• Cost factors that have a negative effect on earnings and cash flows
• Overall financial performance, including actual results against forecasted results
• Entity-specific events like litigation, changes in management, or a shift in customer base
• Events affecting a reporting unit, such as a planned disposal of a portion of the unit
• A sustained decrease in share price, considered both in absolute terms and relative to peers

Pro Tip: Don't let a single strong factor (say, a solid current-quarter beat) override several weaker adverse signals. ASC 350 asks for a weighted judgment across all relevant factors, and a defensible memo should show you considered the mix, not just the most convenient data point.

Some situations make the qualitative route more trouble than it's worth. If cushion from the last valuation was small or nonexistent, if you've had a genuinely adverse event (a major contract loss, a credit rating downgrade, a lawsuit with real exposure), or if your last quantitative test is several years old and business conditions have shifted materially, you're usually better off proceeding directly to quantitative testing. ASC 350 doesn't require you to attempt step 0 first; entities can bypass it entirely and go straight to a full quantitative test whenever that's the more efficient path. Trying to force a qualitative conclusion when the underlying signals are mixed just creates a documentation headache and an audit flag later.

A Category Checklist for Triggering Events

Triggering-event analysis works best when you sort the noise into categories instead of reacting to headlines one at a time. Judgment still drives the final call, and a categorized checklist keeps that judgment consistent across reporting units and reporting periods. The KPMG guidance on identifying triggering events organizes these into five buckets, and each one deserves its own evidence trail.

1. Macroeconomic conditions. Rising interest rates, a recession, tightening access to capital, or currency volatility in a unit's core markets. Document the specific transmission mechanism (higher discount rate, weaker consumer demand) rather than citing the macro headline alone.
2. Industry and market conditions. A decline in peer trading multiples, new competitive entrants, or regulatory changes that compress margins across the sector. Collect comparable-company multiples and analyst commentary as supporting evidence.
3. Entity-specific performance. Cash-flow losses, missed internal forecasts two or more quarters running, loss of a major customer, or unplanned management turnover. Actual-versus-budget variance reports are the clearest evidence here.
4. Reporting-unit events. A planned disposition of part of a unit, a restructuring that changes its cost structure, or an impairment already recognized on a long-lived asset within that unit. Board minutes and restructuring plans document this category well.
5. Market metrics. A sustained decline in share price, not a single bad trading day, or aggregate market capitalization falling below consolidated book value. This is the category most prone to overreaction, so severity and duration matter more than any single data point.

Severity and duration separate a real trigger from market noise. A stock that drops 8 percent on a single earnings miss and recovers within a month tells a different story than one that's down 30 percent and stayed there for two consecutive quarters. When you assess a metric-based trigger, ask how long the condition has persisted and whether it reflects the specific reporting unit or a broader market move that affects every comparable company equally.

For each trigger category, build a supporting evidence file as you go rather than reconstructing it after the fact: analyst reports for industry conditions, board packages for reporting-unit events, and internal forecast-versus-actual schedules for entity performance. A checklist of filing-derived red flags can help surface some of these triggers earlier, since changes in risk-factor language or MD&A commentary often precede the financial metrics catching up.

The Quantitative Test: Measuring the Impairment

Step 1 compares the reporting unit's fair value to its carrying amount, including goodwill. If fair value comes in below carrying amount, the impairment loss equals that shortfall, capped at the total amount of goodwill allocated to the unit. You can't impair goodwill below zero, and you can't use the goodwill test to write down other assets. That's the current single-step model under ASU 2017-04, which eliminated the old hypothetical purchase price allocation and simplified the math considerably compared to the pre-2020 two-step approach.

Fair value gets estimated using one or more standard valuation approaches, each with its own strengths:

• Income approach (discounted cash flow). Projects the unit's future cash flows and discounts them at a rate reflecting the risk of those cash flows. This is where assumptions about growth, margin, and discount rate carry the most weight, and where auditors will spend the most time.
• Market approach (guideline company multiples). Applies observed trading or transaction multiples from comparable companies to the unit's own financial metrics. Useful as a cross-check even when DCF is the primary method.
• Reconciliation to market capitalization. For public companies, comparing the sum of reporting-unit fair values to the entity's overall market cap provides a sanity check on whether the valuation model is internally consistent with how the market prices the whole business.

One sequencing rule catches preparers off guard more than any other: goodwill is tested last. If a reporting unit holds other long-lived assets, intangibles, or asset groups that also show impairment indicators, those assets get tested and adjusted first, and the resulting carrying amount, after those write-downs, is what you compare to fair value in the goodwill test. Testing goodwill before you've resolved other asset impairments produces a carrying amount that's too high and can mask or misstate the goodwill conclusion entirely. Since goodwill is a residual asset with no cash flows of its own, its recoverability is only meaningful once everything else in the unit has been properly stated.

Using Market Evidence to Calibrate Fair Value

Share price and market capitalization are useful corroborative evidence, but they're not the valuation itself. A single closing price on the measurement date can reflect noise: a broad market selloff, a sector rotation, thin trading volume, none of which necessarily says anything about the specific reporting unit's cash-generating capacity. In genuinely volatile markets, averaging market prices over a reasonable period leading up to the measurement date tends to produce a more defensible reference point than relying on a single day's close.

Pro Tip: Whatever averaging window you choose, whether it's 10 trading days, 30, or something else, document the rationale and apply it consistently period over period. Switching windows opportunistically to get a more favorable number is exactly the kind of judgment call an auditor will challenge.

Calibrating the model itself takes more than plugging in a discount rate and calling it done. A few practices separate a defensible valuation from a fragile one:

• Cross-check your discount rate against the weighted average cost of capital for comparable public companies in the same industry, adjusted for unit-specific risk.
• Stress-test terminal growth assumptions against long-run GDP or industry growth rates. A terminal growth rate that exceeds the broader economy's long-term trajectory is a common audit finding.
• Reconcile peer multiples to your own unit's margin and growth profile rather than applying them uniformly, since a premium multiple in the peer set often reflects a scale or growth advantage your unit doesn't share.
• Run sensitivity analysis on discount rate and terminal growth together, since small moves in each compound quickly.

The single most useful output of sensitivity testing is a clear answer to one question: how much would key inputs need to move before your cushion disappears entirely? If a 50 basis point increase in discount rate wipes out your entire fair-value excess, that's a materially different risk profile than a unit that could absorb a 300 basis point shock and still clear the bar. Market signals corroborate a valuation conclusion; they don't replace the underlying analysis, and documenting that sensitivity is what turns a plausible number into a defensible one.

Building a Defensible Trigger-Assessment Workflow

A repeatable process beats a brilliant one-off analysis every time an auditor or regulator asks you to explain your conclusion months later. The workflow that holds up under scrutiny generally follows the same sequence regardless of company size:

1. Screen for triggers each quarter close, using the category checklist across macroeconomic, industry, entity, reporting-unit, and market-metric indicators.
2. Gather measurement-date evidence as soon as a potential trigger surfaces, rather than waiting until the reporting deadline forces the issue.
3. Decide qualitative versus quantitative based on cushion size and the severity of any adverse factors identified.
4. Select and document valuation approaches, updating key inputs like discount rate, growth assumptions, and peer multiples to reflect current conditions.
5. Run sensitivities on the inputs most likely to move the conclusion, and preserve those outputs, not just the base case.
6. Reconcile to market evidence, including averaged share-price data where applicable, and note any unexplained gap between the model output and market pricing.
7. Route for governance review and sign-off, with the audit committee informed of any unit showing thin cushion or a triggering event, even if the ultimate conclusion is no impairment.

Your working papers should stand on their own without a verbal explanation filling in the gaps. At minimum, that means the facts considered, the key assumptions and their sources, the valuation inputs and where they came from, the sensitivity ranges tested, the reconciliation to any market evidence, and a clear record of who reviewed and approved the conclusion. A preparer builds the initial analysis, a valuation specialist (internal or external) reviews the technical assumptions, and the audit committee should see a summary for any reporting unit where cushion is thin or a trigger was identified, regardless of whether that trigger ultimately required a write-down.

Where Goodwill Testing Goes Wrong

The most common error is leaning on one metric, usually a stock-price drop, as if it settles the question by itself. A share-price decline is a signal to investigate, not a conclusion. Auditors will ask what else you looked at, and "the stock went down" is not an answer that survives that conversation. Document how you triangulated the price movement against operating performance, industry trends, and peer comparisons before drawing a conclusion either way.

A closely related pitfall is failing to show how you weighed adverse and mitigating factors against each other. If your entity had a bad quarter but also signed a major new contract, the memo needs to reflect both sides of that ledger and explain why the conclusion landed where it did. Preserve every sensitivity output you ran, even the ones that supported your final answer only marginally. Reviewers and auditors want to see the range you tested, not just the number you settled on.

Testing order trips people up more often than it should. Running the goodwill test before resolving impairment on other assets within the same reporting unit produces a carrying amount that hasn't been properly adjusted, and that error cascades through the whole analysis. If impairment is ultimately recognized, disclosure requirements kick in around the amount, the reporting unit affected, and the facts and circumstances that led to the loss, so incomplete documentation at the testing stage becomes a disclosure problem later.

Pro Tip: Keep a running log of triggering-event screens for every reporting unit, even in quarters where the conclusion is "no trigger identified." A gap in that log looks like you skipped the analysis; a documented "no trigger" entry shows you did the work and reached a defensible conclusion.

How Filings-Based Monitoring Sharpens the Trigger Process

Watching for triggering events used to mean waiting for a quarterly close and then scrambling through disclosures you'd half read the first time around. That approach misses the events that actually matter, because the language buried in a risk-factor update or a shift in MD&A tone often shows up weeks before the financial metrics catch up.

Continuous monitoring of filings changes the priority order. Instead of treating every reporting unit the same, you can flag the ones showing recent adverse language, changed risk disclosures, or deteriorating segment commentary, and put those at the front of the queue. That matters most for teams with limited valuation bandwidth, where you genuinely cannot run a deep quantitative analysis on every unit every quarter. Prioritize the units with thin cushion from the last test and any recent adverse signal, and let the units with strong cushion and stable disclosures wait for their scheduled annual review.

Automated summaries of 10-Ks, 10-Qs, and 8-Ks won't replace your valuation judgment, and they shouldn't try to. What they can do is compress the reading time on dozens of filings into a workflow that surfaces the handful of reporting units where something has actually changed. That's the gap such solutions aim to close: less time reading, more time on the judgment calls that actually require it.

— Matthew

Speed Up Evidence Gathering With FilingsIQ

Every hour spent hunting through a 10-K for the risk-factor change that might justify an interim test is an hour not spent on the valuation itself. Some platforms close that gap by summarizing 10-Ks, 10-Qs, and 8-Ks efficiently, flagging accounting irregularities and shifts in risk language automatically, and providing dedicated workspaces for each ticker under monitoring.

That fits directly into the trigger workflow described above. Instead of manually rereading a full filing set every quarter to check for adverse changes, you can let the platform surface the likely candidates first, then confirm and document from there. For a reporting unit tied to a public company, that means faster access to the disclosure language, financial detail, and risk-factor updates that feed directly into your qualitative assessment and your final memo for reviewers. See how the workflow comes together on the FilingsIQ product overview, or go straight to Filingsiq to start a trial and run your next trigger screen against a live filing set.

Sources

• 9.6 The qualitative goodwill impairment assessment — PwC Viewpoint
• 2.5 When to Test Goodwill for Impairment — Deloitte DART
• Goodwill impairment—triggering events and process guide — KPMG (2026)
• Impairment of goodwill — Grant Thornton viewpoint

FAQ

What Does Goodwill Impairment Mean?

Goodwill impairment occurs when a reporting unit's carrying amount, including its allocated goodwill, exceeds its fair value. The write-down is limited to the amount of goodwill assigned to that unit and cannot reduce goodwill below zero.

How Do You Calculate Goodwill Impairment?

You compare the reporting unit's fair value, typically estimated through a discounted cash flow analysis or market multiples, to its carrying amount including goodwill. If carrying amount exceeds fair value, the impairment loss equals that difference, capped at the goodwill balance for the unit.

How Do You Test Intangible Assets for Impairment?

Indefinite-lived intangibles other than goodwill are tested by comparing their individual fair value to carrying amount, similar in concept to the goodwill test but performed at the asset level. Finite-lived intangibles instead use a recoverability test comparing undiscounted cash flows to carrying amount before any fair-value measurement.

What Are the Main Indicators of Goodwill Impairment?

The core categories are macroeconomic conditions, industry and market deterioration, entity-specific performance issues like cash-flow losses, reporting-unit events such as a planned disposal, and market metrics including sustained share-price declines or market capitalization below book value. A single indicator rarely settles the question; the analysis requires weighing all relevant factors together.

Can a Company Skip the Qualitative Assessment?

Yes. ASC 350 permits entities to bypass the qualitative screen entirely and proceed straight to the quantitative test whenever that path is more efficient, particularly when cushion from the prior valuation is thin or adverse events have already been identified.

Recommended

• Pass SEC C&DIs: Non-GAAP Reconciliation Workflow for U.S. Analysts
• 5 SEC Filing Red Flags Every RIA Should Watch For
• How To Spot Red Flags In SEC Filings: A Practical Guide For RIAs And Analysts
• SEC Filing Analysis Best Practices for Analysts