Why ASC 820 Valuations Fail Audit, And How to Build a Process That Doesn’t

Introduction

Most ASC 820 valuations do not fail audit because the math is wrong. The numbers usually check out fine. The real trouble starts when an auditor asks a simple question: why? Why this discount rate? Why this peer group? Why did the value move since last quarter? “The model calculated it” is not a real answer.

An ASC 820 valuation measures fair value. That is the price a company or asset would fetch in a fair, open sale today. Many kinds of companies need this rule. Firms that hold private investments. Firms that issue complex securities. Firms that need a financial reporting valuation. The valuations that sail through audit share one trait. Every key input has a clear, written reason behind it. The ones that stall rarely fail from a broken model. They fail because the file cannot answer the auditor’s next question.

Transaction Capital LLC has helped private equity firms, venture funds, and finance teams with thousands of fair value projects. This guide shows how skilled valuation teams think about ASC 820. Not just what the rule says. Where the real audit risk hides. And how to get ahead of it before the auditor opens the file.

Key Takeaways

• Most ASC 820 audit trouble comes from weak records, not bad math.
  
• Fair value is a market price. It is never just an internal opinion of worth.
  
• Level 3 valuations draw the most audit scrutiny because they rely on inputs no one can look up.
  
• Auditors challenge the assumptions behind a model far more than the model’s math.
  
• A written policy, an input log, and a value bridge stop most audit findings before they start.
  
• Tying a model to a real, recent deal gives auditors a clear story instead of loose guesses.
  
• Building the model at deal time, not at year-end, cuts audit time by a wide margin.
  

What Is ASC 820 Fair Value Measurement?

ASC 820 is the U.S. GAAP rule for how companies measure and report fair value. The Financial Accounting Standards Board (FASB) wrote the rule. It first came out as Statement No. 157. The goal: one standard for every industry.

Fair value under ASC 820 is an exit price. It is the price a company would get to sell an asset. Or the price it would pay to hand off a debt. This happens in a fair sale between willing buyers on the measurement date. This is not the same as a 409A valuation. A 409A valuation sets the tax value of one common share for IRS stock option rules. ASC 820 and 409A measure different things for different readers. Mixing them up is a common, costly mistake.

Companies most often need an ASC 820 valuation for:

• Purchase price allocations (ASC 805) after a deal closes
  
• Stock-based pay reports under ASC 718
  
• Fund marks for private equity and venture capital portfolios
  
• Goodwill and intangible asset impairment tests
  
• Complex securities and preferred stock valuations

The Market-Participant Foundation of ASC 820

ASC 820 defines fair value as the price a company would get to sell an asset, or pay to hand off a debt, in a fair trade between market buyers on the measurement date. It is an exit-price rule built on buyer logic, not the owner’s own view of worth.

This point matters more than it seems. ASC 820 never asks what an asset is worth to the company that holds it. It asks what an outside, informed buyer would pay for it today. Every input in the model should hold up from that outside view. This means growth rates, required returns, risk add-ons, and capital mix. An input that only makes sense inside the company is a red flag. If no real buyer would use it, it draws audit questions fast.

ASC 820 vs. 409A Valuation: Why the Difference Matters

Founders often assume ASC 820 and 409A valuations measure the same thing. They do not. A 409A valuation sets the tax value of common stock so a company can price employee stock options under IRS rules. ASC 820 sets the fair value of a company’s investments, securities, or acquired assets for its financial statements.

The two rules can produce different numbers for the same firm on the same day. That is normal. It is not a mistake. An auditor who reviews an ASC 820 file wants proof the team knows this gap. Reusing a 409A number for a financial report, with no fix, is a red flag.

Key Takeaways

• Fair value under ASC 820 is a market-based, exit-price concept, not a management opinion.
  
• Every input should be defensible from the perspective of an outside, informed buyer.
  
• ASC 820 and a 409A valuation measure different things and often produce different numbers for the same company.
  

How Auditors Evaluate Level 3 Valuations

ASC 820 sorts inputs into three levels. Level 1 covers quoted prices for identical assets. Level 2 covers other data the market can confirm. Level 3 covers inputs no one can look up. Level 3 drives most audit friction: private company stakes, venture equity, preferred shares, warrants, and earn-outs.

Auditors rarely push back on Level 1 or Level 2 numbers. Market data does most of the work there. Level 3 is different. The answer leans on management’s own judgment. So auditors care less about neat math. They care more about proof behind each guess. A model can use perfect math and still draw a long list of audit notes. That happens when no one wrote down the reasoning as it happened.

The Fair Value Hierarchy at a Glance

Level	Input Type	Typical Example	Audit Scrutiny
Level 1	Quoted prices, identical assets, active markets	Public stock on the NYSE or NASDAQ	Minimal
Level 2	Other data the market backs up	A rate swap or a locked-up public stock	Moderate
Level 3	Inputs built by management	Private equity, preferred stock, warrants	Heaviest

One hidden input can drop a whole valuation to Level 3, even if every other input is Level 1 or Level 2. Level 3 is not a grade of quality. A well-documented Level 3 file can be just as solid as a Level 1 one. It just needs more proof to show it.

Key Takeaways

• The hierarchy is about the inputs used, not the method itself.
  
• A DCF is not always Level 3. Market data does not always mean Level 2. The weight of the hidden input decides the level.
  
• Level 3 files need notes written in real time, not rebuilt after the fact.
  

Choosing Between the Market, Income, and Cost Approaches

ASC 820 allows three approaches: Market, Income, and Cost. The right pick depends on the asset and the data at hand, not on which one gives the nicest number.

The Market Approach works best with a solid list of peer companies or deals. The Income Approach, usually a discounted cash flow model, fits firms with strong, provable forecasts whose worth ties to future cash. The Cost Approach is less common for securities, but it can fit certain hard assets, or very young companies with a short track record.

Approach	Best For	How It Works
Market Approach	Firms with public peers or recent deals	Applies real multiples or deal prices from similar firms
Income Approach	Later-stage firms with steady cash flow	Discounts future cash to today’s value with a fair rate
Cost Approach	Early-stage or asset-heavy firms, wind-downs	Values the assets, minus wear or a swap cost

One habit shows up often: a team keeps using last year’s method without asking if it still fits. A change in method is not a problem on its own. Auditors know things shift. But a change with no reason on file, or no record of why the first choice was made, invites the kind of question that stalls an audit.

Key Takeaways

• Pick the method based on the asset and the data on hand.
  
• “We used it last year” is not a real reason. Write down the actual logic.
  
• Explain method changes. Do not just make them.
  

Supporting Financial Projections Under ASC 820

For Level 3 files, the forecast is usually the most heavily tested part of the whole package. Auditors want to know who built it, whether it matches the board-approved budget, and what proof, contracts, sales pipeline, renewal rates, price changes, backs up the growth story.

The biggest issue in audit support work is rarely the forecast itself. It is the missing link between the numbers and the real business. A forecast that grows revenue from $20 million to $150 million in five years is not wrong on its face. But if the file does not explain what drives that growth, an auditor has no way to judge it.

Testing old forecasts against real results is one of the easiest ways to build trust in this part of the file. If last year’s forecast missed by a wide margin, say why. Show that the same risks were not simply repeated this year without change.

Key Takeaways

• Tie forecasts to real drivers, not just a top-line growth number.
  
• Match forecasts to the board-approved budget before the audit starts.
  
• Test old forecasts against real results. Write down why they missed.
  

The Biggest Documentation Mistakes Companies Make

Two mistakes come up again and again, and both are easy to fix: how peers get picked, and how a multiple gets picked.

Peer selection often falls back on a broad industry list instead of real similarity. Picking every public company in a sector adds little value if the target firm differs in growth stage, margin, or capital needs. A short, well-reasoned peer list with clear notes on who was in and who was left out holds up far better than a long list built on labels alone.

The second issue is where in the range a multiple lands. If peers trade between 4x and 7x EV/EBITDA, and the team picks a number near 7x, the file needs to say why. Faster growth? Better margins? Less risk from one big customer? A real edge? Picking a number just because it produces the answer someone wants, with no proof behind it, is one of the fastest ways to trigger extra audit questions.

Two Errors Auditors Push Back On Most

Two more mistakes draw pushback across almost every engagement.

The first: pricing every share class at the latest round price. Share classes carry different rights and different places in line if the company is sold. In a real sale, junior shares get less than senior ones. Treating every class as equal misstates the file. Using the round price as one input is fine. Treating all classes as the same, despite unequal rights, is not.

The second: treating past volatility as a stand-in for future volatility without a second look. Volatility in an option model should look forward, not backward. Past data is a starting point. But if that data has odd spikes that will not repeat, the file should explain the fix.

Key Takeaways

• Pick peers for real similarity, not just an industry label.
  
• Write down why each peer was kept or cut.
  
• Any multiple picked away from the middle of the range needs real proof.
  
• Pricing every class the same, and treating old volatility as automatically forward-looking, are two of the most common Level 3 errors.
  

Building a Defensible Discount Rate

Picking a discount rate draws more scrutiny than almost any other choice in a Level 3 file. Auditors rarely fight the math behind the weighted average cost of capital, or WACC. They fight the inputs behind it. Common questions: does the beta match firms with a truly similar business? Does the capital mix reflect a real buyer? Does a company-specific risk add-on double up on risk already baked into cautious forecasts?

That last point is worth a closer look, since it is one of the sneakiest and most common errors: counting the same risk twice. Once in the cash flow forecast. Again in the discount rate. When two different people set these without talking to each other, the result can understate fair value by a wide margin. A reviewer will rarely catch it unless the file spells out where each risk lives.

Key Takeaways

• Auditors usually fight the WACC inputs, not the formula.
  
• Write down the source for beta, capital mix, and any company-specific risk add-on.
  
• Check that no risk gets counted twice, once in cash flow and again in the rate.
  

Terminal Value, Recent Financings, and When to Calibrate

Terminal value often makes up most of total value in a DCF, so it earns close attention. A long-run growth rate should reflect a mature, steady business. It should not just stretch out a company’s current hot streak, since no company can outgrow the broader economy forever.

Teams often treat a recent funding round as an easy stand-in for fair value. That is a mistake. A round from several quarters back may no longer match today’s market. A funding round can be strong proof of value. But check three things first. Was it a fair, open deal? Did real market buyers set the price? Has anything big changed since it closed?

What Calibration and the Backsolve Actually Do

Calibration means tying a model’s inputs to one real, observed deal, usually the company’s latest funding round, then rolling those inputs forward as results and the market shift. It gives auditors a clear story instead of a string of loose, disconnected changes.

The backsolve is one way to calibrate. It works backward through an option pricing model to find the total equity value that would match the actual round price. That solved value then feeds the next step, where a method like the Option Pricing Model splits the total across share classes. Anchoring the model to the deal date, then rolling it forward with clear notes on each change, is one of the most useful tools in private company valuation.

Key Takeaways

• Long-run growth should reflect a mature business, not today’s growth spurt.
  
• A recent funding round needs a second look, not automatic trust, as proof of value.
  
• Calibration tells real value changes apart from random shifts in method.
  
• A backsolve ties a model to a known deal price. A separate step then splits that value across share classes.
  

Valuing Complex Capital Structures and Discounts

Private companies rarely have simple cap tables. Preferred stock, SAFEs, convertible notes, warrants, and options each carry their own rights and place in line. Splitting total value evenly across all shares is almost always wrong. Depending on the facts, the right tool may be the Option Pricing Method (OPM), the Probability-Weighted Expected Return Method (PWERM), the Current Value Method (CVM), a Waterfall model, or a mix of these.

The OPM suits a company with an unclear path to exit. PWERM fits later-stage firms where the exit options are known. Think an IPO, a sale, or a wind-down. Each option gets weighted by its odds. A Waterfall or CVM model fits a holder who controls when the exit happens. None of these tools is required by law. ASC 820 only asks for a fair, market-based value. So the file should say why the chosen tool fits this company’s facts.

The same care applies to discounts for low marketability, low liquidity, or credit risk. An unexplained percentage cut is one of the most common, and most avoidable, audit findings. The file should say why the discount applies, how it was sized, and what backs it up.

Key Takeaways

• Splitting value evenly across share classes rarely fits a complex cap table.
  
• Pick OPM, PWERM, CVM, Waterfall, or a mix based on real exit paths and real rights.
  
• Every discount needs a written reason, method, and proof.
  

Documentation Checklist Before Audit

A strong model is not enough. An audit-ready process needs real structure around it:

• A written policy. It sets the method, the review timing, and the sign-off steps.
  
• An input log. It tracks each key number, its source, and why it changed.
  
• A value bridge. It explains, in plain terms, why fair value moved since last period.
  
• Stress tests. Run them on WACC, growth rates, and exit multiples.
  
• A second review. Someone who did not build the first model should check it.
  
• A match check. The numbers in the financial statements should equal the numbers in the file.
  

ASC 820 Disclosure Requirements to Reconcile Before Audit

The valuation file and the footnotes in the financial statements must tell the same story. ASC 820 sets clear rules for what a company must show. A gap between the two is an easy, avoidable audit note. Key items to show include:

• The fair value of each asset and debt, sorted by level
  
• The method and key inputs used for Level 2 and Level 3 items
  
• A start-to-end summary of Level 3 balances for the period
  
• Any move between levels, and why it happened
  
• Any change in method from last period, and why it happened
  

Most audit notes point to gaps in these records. They rarely point to errors in the final number. The value often stays the same. The file just needs more proof before the audit can close.

Key Takeaways

• Strong records, not a fancy model, decide most audit outcomes.
  
• Build the input log and value bridge as choices happen, not after the fact.
  
• Match the valuation file to the financial statement notes before the audit starts.
  

Common Audit Findings We See Across Engagements

The same issues show up again and again across our fair value work. Forecasts with no real support. Peer lists built on industry labels, not real fit. Multiples with no proof behind the pick. Discount rates with no clear source. Method changes with no notes. Disclosures that do not match the valuation report. Almost every one of these is avoidable. Not through a fancier model, but through notes built while the work happens, not rebuilt under audit pressure.

How to Build an Audit-Ready ASC 820 Valuation Process

Fixing single audit notes helps. The bigger win is a process that stops most of them from happening at all. Six steps make the biggest difference.

1. Write the policy first. Pick the right method for each asset type before the first measurement date. Not while an auditor waits on an answer.
   
2. Build the model at deal time, not year-end. When a round closes, the terms, the cap table, and the peer list are fresh. Capture them right away. Each later update becomes a quick roll-forward, not a full rebuild.
   
3. Write down choices as they happen. An input log kept in real time carries far more weight with an auditor than a story pieced together months later.
   
4. Anchor to the latest deal. Tie the model to one real, observed price. Explain each later change through real results or market shifts.
   
5. Run a second review before the audit. Someone who did not build the first model should test the answer and the notes together.
   
6. Match the disclosures to the file. Confirm the hierarchy level and inputs in the financial statements match the full report.
   

Companies that follow these six steps report shorter audits and fewer follow-up questions. Their records already answer the question before the auditor asks it.

Why Work With Transaction Capital LLC

Bringing in an outside valuation firm does not move blame away from management. The financial statements are still theirs to own. But it does add a fresh, outside view. It also adds habits built to survive an audit, right where Level 3 work gets hard.

Transaction Capital LLC has closed 2,500+ valuation projects for clients across the United States and beyond. Our work covers:

• Level 3 investment and private company valuations
  
• Private equity and venture capital fund valuations
  
• Complex securities and cap table valuations
  
• Purchase Price Allocations (ASC 805)
  
• Stock compensation valuations (ASC 718) and 409A valuations
  
• Intangible asset valuations
  
• Independent opinions built for auditors and financial reports
  

Our reports follow four key standards:

• USPAP
  
• AICPA SSVS No. 1
  
• IVS
  
• NACVA guidance
  

Each report is built to hold up under review. That means an auditor, an investor, or a regulator can trust it. Our team holds four top credentials: ABV, ASA, CVA, and MRICS. Every project starts at a flat fee of $500. Most reports take 3 to 5 business days. Each one comes with a pay-after-draft-review guarantee. You see the work before you commit to it.

Frequently Asked Questions

1. What is ASC 820 Fair Value Measurement?

ASC 820 is the U.S. GAAP rule for measuring fair value when another accounting standard calls for it. It is based on an exit price and a buyer’s view, not the owner’s own opinion. 

2. Why do Level 3 valuations get the most audit attention? 

Because they lean on inputs no one can look up, and on management’s own judgment. Forecasts, discount rates, peer picks, and multiples all need clear, real support. 

3. What’s the most common reason ASC 820 valuations fail audit? 

Weak records, not bad math. The final number often stays the same. Auditors just need to see the reasoning behind each big input. 

4. Does hiring an external valuation firm remove management’s responsibility? 

No. Management still owns the financial statements. The team must understand the method, the inputs, and the answer, even when an outside firm builds the valuation. 

5. How can a company cut down on ASC 820 audit questions? 

Start early. Write down choices as they happen. Test old forecasts against real results. Tie the model to recent deals where it fits. Match the file to the financial statement notes before the audit starts. 

6. Is ASC 820 the same as a 409A valuation? 

No. ASC 820 sets fair value for financial reports. A 409A valuation sets the tax value of common stock for IRS rules. The two use different units and often land on different numbers for the same firm. 

7. How often should a company recheck fair value under ASC 820? 

Most firms recheck fair value at least once a year, often each time they close a reporting period. Some check every quarter, depending on investor terms and how fast the business is changing.

Read More:

• Personal Goodwill vs. Enterprise Goodwill in Divorce: A Complete Guide
• Finnerty vs Chaffe DLOM Models: Which Discount Is Defensible in 2026?
• Top 10 Business Valuation Firms in the USA (2026)
• DLOM vs DLOC: Understanding Valuation Discounts in Business Valuation