What Are Financial Statement Footnotes?
Financial statement footnotes, formally the notes to the financial statements, are a required component of a complete set of GAAP financial statements. The audit opinion covers the statements and the notes together, so a reader who stops at the four statements has read a fraction of the document.
The notes aren’t an appendix to the statements. They’re part of them.
Three authorities say so directly:
- FASB Concepts Statement No. 8, Chapter 8, issued in August 2018, sets the Board’s framework for deciding what belongs in the notes. Its stated premise is that the primary purpose of notes is to supplement or further explain the information on the face of the statements. The full text sits in FASB’s conceptual framework chapter on notes.
- GAAS defines financial statements to include the notes. AU-C section 700 describes financial statements as a structured representation of historical financial information including related notes.
- Management owns them. AU-C section 210 makes management’s acknowledgment of responsibility for the preparation and fair presentation of the financial statements a precondition of accepting the audit engagement.
That third point is the one that lands on your desk. The audit firm issues the disclosure checklist and reviews the drafts. Management writes the words.
Why a private company’s set looks different from a public company’s is itself documented. The FASB and Private Company Council Private Company Decision-Making Framework identifies five factors that differentiate private company reporting, including the number of primary users, their direct access to management, ownership and capital structure, and the accounting resources available to the preparer. Disclosure is one of the five areas where the framework contemplates different requirements. Those primary users are mostly lenders and equity holders, which is part of why investors expect GAAP statements rather than a management reporting package.
Controllers reach out to indinero at exactly this point. First audit, a checklist in hand, and no prior-year note set to work from.
The Disclosure Set a Private Company Owes
A private company owes a note for every material balance, transaction class, risk, and post balance sheet event the Codification assigns a Section 50 requirement. Your auditor’s financial statement disclosure checklist is the working inventory, usually a commercial GAAP disclosure library organized by frequency of applicability. The AICPA’s own presentation and disclosure checklist for the FRF for SMEs framework is a published example of the format.
Private company disclosure requirements diverge from public ones note by note, not wholesale. Here is the inventory with the exact reference and the relief where one exists.
| Note | Primary ASC reference | Private company relief or variation |
|---|---|---|
| Nature of operations and use of estimates | ASC 275-10-50-1 through 50-4 | None. Required of all entities. |
| Significant accounting policies | ASC 235-10-50-1 through 50-6 | None, but every PCC alternative and practical expedient elected must be disclosed here. |
| Revenue, disaggregation and contract balances | ASC 606-10-50-1 through 50-23 | Five elections. ASC 606-10-50-7, 50-11, 50-16, 50-21, and ASC 340-40-50-4. |
| Leases | ASC 842-20-50-1 through 50-9, maturity table at 842-20-50-6 | Risk free rate election by class of underlying asset, which must itself be disclosed. |
| Debt | ASC 470-10-50-1 | None. Five years of maturities plus sinking fund requirements. |
| Income taxes | ASC 740-10-50, non-PBE rate reconciliation at 740-10-50-13 | Qualitative rate reconciliation only. No numerical tabular reconciliation. |
| Equity and stock compensation | ASC 718-10-50 | Practical expedients at ASC 718-10-30-20C through 30-20F must be disclosed if elected. |
| Fair value | ASC 820-10-50-2, nonpublic provisions at 820-10-50-2F and 50-2G | No Level 3 rollforward, no range or weighted average of unobservable inputs. |
| Commitments | ASC 440-10-50 | None. |
| Contingencies | ASC 450-20-50 for losses, ASC 450-30-50 for gains | None. |
| Risks and concentrations | ASC 275-10-50-16 through 50-22 | No bright line threshold. The ASC 280 10% test does not apply. |
| Related parties | ASC 850-10-50-1 through 50-3 | None. |
| Subsequent events | ASC 855-10-50-1 and 50-2 | Window and required date disclosure both differ from an SEC filer. |
| Going concern | ASC 205-40-50 | None. The evaluation window keys to the available to be issued date. |
| Segments | ASC 280 | Not required. Private companies are outside the scope. |
Two notes a private company does not owe are worth stating out loud, because their absence reads as an omission to anyone trained on public filings. Segment information under ASC 280 and earnings per share under ASC 260 are both public entity requirements.
Leases. The ASC 842 note carries a maturity table at ASC 842-20-50-6 that has to reconcile to the recognized lease liabilities, and the risk free rate election is a disclosure in its own right. The measurement mechanics are their own subject, covered in our guide to ASC 842 lease accounting for private companies.
Related parties. ASC 850-10-50-1 requires the nature of the relationship, a description of the transactions including those to which no amount or a nominal amount was ascribed, the dollar amounts for each period presented, and amounts due to and from related parties. ASC 850-10-50-2 then requires receivables from officers, employees, or affiliated entities to be shown separately rather than buried in a general receivables caption. The identification work is covered in our post on related party transaction disclosure.
Going concern. ASC 205-40 requires management to evaluate whether it is probable the entity will be unable to meet its obligations as they become due within one year after the date the statements are issued or are available to be issued. That evaluation runs on the same clock as subsequent events, and the conclusion drives whether a note is required at all.
The Significant Accounting Policies Note
The significant accounting policies note runs off ASC 235-10-50-1 through 50-6, and ASC 235-10-50-3 lists the policies commonly expected: basis of consolidation, depreciation methods, amortization of intangibles other than goodwill, inventory pricing, recognition of profit on long term construction type contracts, recognition of revenue from contracts with customers, and recognition of revenue from leasing operations. ASU 2014-09 added the revenue from contracts with customers item, which is why the ASC 606 policy paragraph belongs here and not only in the revenue note.
It comes first for a mechanical reason, not a stylistic one. ASC 235-10-50 contemplates the summary either preceding the notes or presented as the initial note, because every number in every later note is unreadable without the measurement basis behind it.
For a private company this note is also the ledger of elections. The PCC alternatives for goodwill amortization (ASU 2014-02), identifiable intangibles in a business combination (ASU 2014-18), and the VIE scope exception for common control arrangements (ASU 2018-17) are policy decisions a reader can’t infer from the face of the statements. The same goes for the practical expedients: the ASC 842 risk free rate, the ASC 718-10-30-20C through 30-20F current price expedient, and the ASC 606-10-50-7 disaggregation relief. ASC 235-10-50-4 cuts the other way as well. The policy note shouldn’t duplicate detail presented elsewhere in the notes.
Commitments, Concentrations, and Contingencies
Three different Topics, routinely collapsed into one heading, with three different triggers. The combined caption is a presentation convention, not a single standard.
- Commitments, ASC 440-10-50. Obligations the company has entered into that aren’t on the balance sheet. The guidance requires a purchaser to disclose unconditional purchase obligations that are noncancelable, or cancelable only on a remote contingency, with the other party’s permission, on signing a replacement agreement, or on payment of a penalty large enough that continuation appears reasonably assured. No expected loss is needed to trigger it.
- Contingencies, ASC 450-20-50 for losses and ASC 450-30-50 for gains. The loss disclosure is triggered when a loss isn’t both probable and reasonably estimable and therefore isn’t accrued. It covers the nature of the contingency and an estimate of the possible loss or range of loss, or a statement that such an estimate can’t be made.
- Concentrations, ASC 275-10-50-16 through 50-22. Triggered when a concentration exists at the balance sheet date, that concentration makes the entity vulnerable to the risk of a near term severe impact, and it is at least reasonably possible the events causing that impact will occur in the near term. The Codification defines reasonably possible as more than remote but less than likely, and near term as not exceeding one year from the date of the financial statements.
Here is the point most first-year sets get wrong. The familiar 10% major customer threshold is ASC 280-10-50-42, which sits inside segment reporting, and ASC 280 applies only to public entities. A private company’s concentration disclosure flows from ASC 275 instead, and ASC 275 carries no numeric threshold at all. That bright line isn’t yours.
Categories in scope under ASC 275:
- Volume of business with particular customers, suppliers, or lenders
- Revenue from particular products, services, or fund raising events
- Available sources of supply of materials, labor, or services
- Market or geographic area
Subsequent Events Through the Issuance Date
For a private company the subsequent events window does not close at the issuance date. Under ASC 855, an entity that isn’t an SEC filer evaluates subsequent events through the date the statements are available to be issued, which the Codification defines as the date they are complete in a form and format that complies with GAAP and all approvals necessary for issuance have been obtained, including approval from management and the board where applicable. An SEC filer evaluates through the date the statements are issued.
ASC 855-10-50-1 then requires disclosure of the date through which subsequent events were evaluated and whether that date is the issued date or the available to be issued date. Note the asymmetry ASU 2010-09 created. SEC filers were relieved of disclosing that date. Everyone else, private companies included, has to disclose it. The date stamp is an obligation, not a convention.
The split that drives treatment:
- Recognized, so adjust the statements. A customer files for bankruptcy protection in February. The receivable was already uncollectible in substance at the December 31 balance sheet date, and the filing is evidence about a condition that existed then, so the allowance is adjusted in the December statements. Same logic for litigation that settles after year end on a claim that existed at year end, and for inventory whose obsolescence is confirmed after the fact.
- Nonrecognized, so disclose only. A Series B closes in March on a December 31 balance sheet. That’s a new condition arising after the balance sheet date, so nothing is recognized, and ASC 855-10-50-2 requires disclosure of the nature of the event and an estimate of its financial effect, or a statement that such an estimate can’t be made. Same treatment for a post year end acquisition, a post year end debt issuance, and a post year end facility lease signing.
SaaS-Specific Application
For a growth stage SaaS company, four notes do most of the work: revenue under ASC 606, concentration, commitments, and equity.
Revenue. ASC 606 gives a nonpublic entity five discrete disclosure elections, not a general waiver.
- ASC 606-10-50-7. Elect out of the quantitative disaggregation guidance in ASC 606-10-50-5 through 50-6. The floor if you elect is revenue disaggregated by timing of transfer, point in time versus over time, plus qualitative information about how economic factors such as customer type, geography, and contract type affect revenue.
- ASC 606-10-50-11. Elect out of the contract balance detail in ASC 606-10-50-8(b) through (d) and 50-10. The floor is the opening and closing balances of receivables, contract assets, and contract liabilities under 606-10-50-8(a). For a SaaS company that means the deferred revenue opening and closing balances are not optional. What’s optional is the rollforward narrative and the revenue recognized from the beginning contract liability balance.
- ASC 606-10-50-16. Elect out of the remaining performance obligation disclosures in ASC 606-10-50-13 through 50-15. This is the relief that removes the public style RPO or backlog table.
- ASC 606-10-50-21. Elect out of specified significant judgment disclosures.
- ASC 340-40-50-4. Elect out of the disclosures on assets recognized from costs to obtain or fulfill a contract, which is where capitalized sales commissions live.
Even with every election taken, the set still owes disaggregation by timing of transfer, the deferred revenue balances, and a revenue policy paragraph in the ASC 235 note. Our primer on ASC 606 revenue recognition covers the measurement work behind those numbers.
Concentration. A single logo at a double digit share of ARR is the most commonly skipped disclosure in growth stage SaaS, usually because the controller went looking for the ASC 280 trigger that doesn’t apply. The ASC 275-10-50-16 test is qualitative, and it’s met whenever losing that customer would cause a severe impact in the near term. Receivables concentration is a separate assessment from revenue concentration, and often the sharper one.
Commitments. Two items recur. Committed cloud spend, whether an AWS enterprise discount program or an Azure or GCP committed use discount, is a noncancelable minimum purchase obligation inside ASC 440-10-50. The office lease is an ASC 842 liability with its maturity table at ASC 842-20-50-6, and a short term lease election is a policy disclosure. A company that signed a three year compute commitment and disclosed nothing has an omission the auditor will find in the contracts folder.
Equity. SAFEs and convertible notes are the hard part, and they aren’t an ASC 718 question. No dedicated US GAAP standard addresses a SAFE, and practice diverges on whether the instrument falls under ASC 480 or is evaluated as a contract in the entity’s own equity under ASC 815-40. Many SAFEs with a valuation cap land in liabilities at fair value with changes running through earnings, which is a disclosure consequence as much as a measurement one. Our breakdown of SAFE note GAAP classification walks the decision. Separately, ASU 2021-07 added a practical expedient at ASC 718-10-30-20C through 30-20F for determining the current price of an underlying share, and a nonpublic entity that elects it has to disclose the election.
Common Pitfalls
Six failure modes account for most of the disclosure findings on a first private company audit, and every one of them is avoidable before fieldwork starts.
- Copying a public company’s note set. It over discloses, imports the ASC 280 and ASC 260 notes you don’t owe, and worst of all asserts elections you never made. A borrowed policy note that says revenue is disaggregated by geography commits you to a disclosure you may not be able to support.
- A stale policy note after adopting a standard. The policy note is the first thing an auditor reads and the last thing anyone updates.
- Closing the subsequent events window at the balance sheet date. The window runs to the available to be issued date, and that date has to appear in the note.
- Numbers in the notes that don’t tie to the face of the statements. The ASC 842-20-50-6 maturity table has to reconcile to recognized lease liabilities. The ASC 470-10-50-1 five year schedule has to foot to long term debt. Tie out before the auditor does, which is far easier when the supporting schedules fall out of a disciplined month end close.
- No commitments note at all. The committed cloud spend and the purchase obligations sit in the contracts folder whether or not they appear in the notes.
- Skipping the concentration note because it looks like a weakness. The ASC 275-10-50-16 trigger isn’t discretionary, and a lender who finds the concentration in diligence instead of in the notes draws a worse conclusion.
Most of these get caught in review rather than in drafting, which is the argument for a second set of CPA eyes before the drafts go back to the auditor. Indinero handles the GAAP discipline upfront, so audit prep is months of clean books instead of weeks of scramble.
The Audit-Ready Standard
An omitted material disclosure is a GAAP departure, and under AU-C section 705 a GAAP departure is a material misstatement. What changes is what your engagement level does about it.
Audit. AU-C section 705 establishes three modified opinions: qualified, adverse, and a disclaimer. A material misstatement can arise from inappropriate or inadequate disclosure, or from the omission of a required disclosure. Where the statements are materially misstated, the auditor issues a qualified opinion if the effect is material but not pervasive and an adverse opinion if it is pervasive. Inadequate disclosure is named explicitly as a GAAP departure in the AICPA’s currently effective Statements on Auditing Standards.
Review. Full disclosure is required. Omitting substantially all disclosures is not an available election under AR-C section 90.
Compilation. The only level where the notes can go. AR-C section 80 permits compiled statements that omit substantially all disclosures required by the applicable framework, but only when the omission is not, to the accountant’s knowledge, undertaken with the intention of misleading users. The accountant also has to include a separate paragraph in the compilation report stating that management elected the omission, that the omitted disclosures might influence the user’s conclusions about financial position, results of operations, and cash flows, and that the statements aren’t designed for those who are not informed about such matters.
So the hierarchy is clean. Compilation can omit, by election, on the record. Review cannot. Audit cannot. If the service level itself is still open, our comparison of audit, review, and compilation sets out the rest of the tradeoff, and the audit prep checklist covers the readiness work the note set sits inside.
Who Drafts the Note Set
Not your auditor, though the rule is more precise than the shorthand suggests. For an SEC registrant it’s absolute. Regulation S-X Rule 2-01(c)(4)(i) treats preparing the audit client’s financial statements that are filed with the Commission as a prohibited bookkeeping service.
For a private company audit under the AICPA Code, preparing the financial statements is a nonattest service that creates a self review threat, because the firm would be auditing a document it authored. It is permitted only where that threat is reduced to an acceptable level and the general requirements of ET 1.295.040 are met. The client agrees to assume all management responsibilities, oversees the service by designating an individual with suitable skill, knowledge, and experience, evaluates the adequacy and results of the service, and accepts responsibility for the results. Here is the nuance that matters in practice. The designated individual satisfies the oversight requirement but does not cure the self review threat, so a safeguard such as review by a partner not otherwise involved in the engagement is still required. The AICPA’s Nonattest Services Toolkit sets out that analysis.
Which is why, in practice, the audit firm hands over a checklist and reviews drafts instead of authoring the set.
How Indinero Approaches Financial Statement Disclosure
Financial statement preparation, the note set included, sits inside indinero’s accounting services engagement. That placement isn’t a marketing choice. It’s the slot the independence rules leave open.
It works because the inputs and the disclosures come from the same team. The elections recorded in the ASC 235 note, the ASC 606 contract conclusions behind the revenue note, the lease and debt schedules behind the maturity tables, and the tax provision behind the ASC 740 note are all produced inside one monthly engagement, rather than passed between a bookkeeper, a tax preparer, and a consultant three weeks before fieldwork. Books are accrual basis and ASC 606 compliant by default, which is the difference between drafting a note set and reconstructing one.
Indinero has maintained continuous operations since 2009, with 500+ regular customers and 100+ years combined team experience behind the work. We’re SOC 2 compliant (2026). Pricing starts at $750/mo, with month-to-month engagements available.
Your auditor will tell you what the disclosure checklist requires. Nobody at the audit firm is going to write it for you. If that checklist landed on your desk this quarter and there’s no prior-year set to work from, reach out for a free consultation. We’d love to learn about your business and find where we can help.
Frequently asked questions
The questions controllers ask most often once the disclosure checklist arrives, answered below.
Do reviewed or compiled statements need footnotes too?
Reviewed statements require full disclosures, and only compiled statements can omit substantially all of them when management elects that omission on the record. AR-C section 90 gives no omission election for a review, so a review owes the same note set an audit does. AR-C section 80 permits a compilation to omit substantially all disclosures, but only when the omission isn’t intended to mislead users and a separate paragraph in the compilation report says management elected it.
Can the auditor draft our footnotes for us?
In practice no, your audit firm supplies the disclosure checklist and reviews drafts while management writes the footnotes. For an SEC registrant, Regulation S-X Rule 2-01(c)(4)(i) prohibits it as a bookkeeping service. For a private company audit it’s a nonattest service creating a self review threat, permitted only where the client assumes management responsibility and designates an individual with suitable skill, knowledge, and experience. The designated individual satisfies oversight but doesn’t cure the self review threat, so an uninvolved partner review is still required.
How long does a first-year disclosure set take to write?
A first-year disclosure set has no published benchmark, and the timeline depends on how many notes apply and how complete your supporting records are. The real drivers are the number of applicable notes, whether your policy elections are already documented, how clean the trial balance is, whether prior-year comparatives exist, and how fast management can answer questions on commitments and concentrations. Indinero scopes that work in a free consultation rather than quoting a generic timeline.
What happens if we leave out a disclosure the auditor considers material?
An omitted material disclosure is a GAAP departure, and under AU-C section 705 it can turn a clean opinion into a modified one. The auditor issues a qualified opinion when the effect is material but not pervasive and an adverse opinion when it is pervasive. The consequence that lands hardest sits outside the report. A lender or investor holding a GAAP compliance covenant can treat a modified opinion as a breach.
Do investors read the footnotes or just the statements?
Investors read the footnotes, and a diligence team usually reads them before the statements themselves. Concentrations, commitments, related party transactions, subsequent events, and the equity structure all live in the notes, which is exactly what a diligence team tests. A thin note set reads as weak controls, and a lender who finds a customer concentration in diligence instead of in the notes draws a worse conclusion than the disclosure would have.