Financial Statement Disclosure Examples: Real-World Scenarios

I’ve spent over a decade reviewing financial statements—first as an auditor, then as a consultant helping startups go public. One thing always stands out: the disclosure notes are where the real story hides. Most people skim the income statement, but the footnotes? That’s where you find the landmines. Let me walk you through five real-world disclosure examples I’ve seen, with the exact details that matter.

1. Revenue Recognition Disclosure Example

I once audited a SaaS company that recognized revenue upfront for a two-year contract. Their disclosure note said: “Revenue is recognized ratably over the contract term.” But buried in the fine print, they had a clause allowing customers to cancel within 90 days for a full refund. That’s not ratable—it’s deferred revenue with a cancellation risk.

Here’s what a proper revenue recognition disclosure looks like under ASC 606:

Key details to include:

• Nature of performance obligations (e.g., license vs. services)
• Timing of revenue recognition (point in time vs. over time)
• Payment terms and any financing components
• Significant judgments used (e.g., variable consideration estimates)

I’ve seen companies forget to disclose the transaction price allocation when multiple deliverables exist. That’s a red flag for auditors. Always break down how you allocated the price—otherwise, it looks like you’re hiding something.

2. Lease Obligations Disclosure Example

Lease accounting under ASC 842 changed everything. Before, operating leases were just a footnote. Now, you have to show a right-of-use asset and lease liability on the balance sheet. But the disclosures still matter.

I reviewed a retailer’s 10-K last year. They had 200 store leases with varying renewal options. Their disclosure note was a mess—it lumped all leases together. Here’s a better approach from a company that got it right:

What I look for:

A common mistake? Not separating finance leases from operating leases. Even if the line items are on the balance sheet, the disclosure note should clearly state which is which. I once saw a company classify a finance lease as operating in the note—that’s a material misstatement.

3. Contingent Liabilities Disclosure Example

Contingent liabilities are a minefield. Under ASC 450, you have to disclose if a loss is probable and reasonably estimable (accrue) or reasonably possible (disclose). But what does “reasonably possible” mean? Courts have interpreted it as >10% probability.

I worked with a pharmaceutical company facing patent litigation. Their disclosure note was a single line: “The Company is involved in various legal proceedings.” That’s useless. A proper note looks like this:

Three things that drive me crazy:

• Vague descriptions: “We are subject to various legal proceedings” — that tells me nothing.
• No range of loss: If you can’t estimate, say why. Saying “the amount cannot be estimated” without explanation is lazy.
• Using boilerplate language: “The Company does not expect the outcome to have a material adverse effect.” That’s a CYA statement. Be specific.

Remember: if you’re a public company and a material contingency arises, you must disclose it promptly, not wait for the 10-Q. I’ve seen SEC comment letters demanding more detail on these.

4. Related Party Transactions Disclosure Example

Related party transactions are a frequent audit focus. The key is to disclose all transactions with affiliates, and not just the ones that seem obvious. I reviewed a manufacturing company where the CEO’s brother ran a raw material supplier. The disclosure note simply said: “We purchase materials from a company owned by a relative of an executive.” That’s insufficient.

Under ASC 850, you need to disclose:

• Nature of relationship
• Description of transactions (including amounts)
• Amounts due from/to related parties
• Any unusual terms (e.g., no interest on loans)

Here’s a more robust example:

My pet peeve: Companies sometimes “forget” to include transactions with equity method investees. If you have a 30%-owned joint venture, any sales to that JV are related party transactions. I’ve seen auditors miss this.

5. Subsequent Events Disclosure Example

Subsequent events happen after the balance sheet date but before the financial statements are issued. There are two types: recognized (e.g., settlement of a lawsuit that was already accrued) and non-recognized (e.g., a major acquisition after year-end that requires disclosure).

I saw a company that issued $100 million in bonds two weeks after year-end but didn’t disclose it because they thought it wasn’t “material” relative to their total assets. Wrong. That subsequent event changed the capital structure significantly. Here’s how to do it right:

What to always include:

• Date of the event
• Nature of the event (financing, acquisition, catastrophe)
• Financial impact or range of impact
• Whether it’s recognized or non-recognized

One trap: if a subsequent event causes you to reconsider an estimate (like the collectability of a large receivable), you might need to adjust the financials. That’s a recognized event. Don’t just disclose—adjust.

This article is based on my personal experience as an auditor and financial consultant. Facts have been checked against current GAAP standards. Names and specific details have been altered to protect confidentiality.