ASC 740 for Private Companies: A 2026 Guide to the Income Tax Provision and ASU 2023-09

If you are a controller at a private company and someone just asked you for "the tax provision," your stomach probably tightens a little. The income tax footnote is one of the smallest sections of the financial statements, and it absorbs a wildly disproportionate share of audit hours, review notes, and last-minute restatements. Starting with fiscal year 2026, that scrutiny is about to get tighter: private companies adopting ASU 2023-09 will face new disaggregated income-tax-paid disclosures and clearer expectations around how their rate reconciliation is explained, even when a numerical reconciliation is not required.

ASC 740 — the FASB codification that governs accounting for income taxes — is where book-basis accounting and tax-basis accounting meet, argue, and produce a number. Here is a working guide to how private company controllers can build a clean current and deferred tax provision, navigate Schedule M-1 reconciliations, evaluate valuation allowances and uncertain tax positions, and prepare for the disclosure changes that arrive with calendar year 2026.

What ASC 740 Actually Requires

ASC 740, "Income Taxes," tells preparers how to recognize, measure, present, and disclose income taxes in U.S. GAAP financial statements. It applies to both public and private entities, although disclosure expectations differ. The core idea is straightforward: book income and taxable income are almost never the same number, and the difference must be accounted for in two pieces.

• Current income tax is the tax owed (or refundable) for the current year, calculated essentially the same way it shows up on Form 1120, 1120-S, or 1065. It is what hits the return.
• Deferred income tax captures the future tax consequences of temporary differences — items that affect book income and taxable income in different periods but eventually reverse.

Add the two together and you get the total tax provision, which appears as a single line — "provision for income taxes" — on the income statement.

The reason controllers find ASC 740 hard is rarely the math. It is the documentation, the judgment calls, and the supporting workpapers that have to survive an auditor's review. Most provision failures in practice are process failures, not calculation errors.

A Repeatable Workflow for the Current Provision

Start with pretax book income from continuing operations. Then walk it to taxable income, the same way the tax return walks Schedule M-1 (or M-3 for larger filers) from book net income to taxable income.

1. Capture book income by entity and jurisdiction. If the legal entity structure includes a partnership, an S corporation, or non-U.S. subsidiaries, each leg of the structure needs its own column.
2. Identify permanent differences. Permanent items — meals not deductible, fines and penalties, tax-exempt interest, certain officer life insurance, GILTI inclusions that never reverse — affect the current year and the effective tax rate but never create a deferred balance.
3. Identify temporary differences. Depreciation methods, accruals not yet deductible, allowance accounts, capitalized R&D under §174, deferred revenue, and stock compensation differences all flow through current tax expense and also build (or release) a deferred balance.
4. Apply tax credits and incentives. R&D credit, FICA tip credit, work opportunity credit, energy credits, foreign tax credit — each one reduces current tax and often comes with documentation requirements an auditor will sample.
5. Compute current tax payable by jurisdiction. Federal, each state, and any foreign country with a filing obligation. State apportionment factors and combined-return rules can shift this number significantly, especially for businesses with multi-state presence.

The result is your current income tax expense. Tie it back to the actual return when the return is filed. The difference becomes a return-to-provision (RTP) true-up in the following year — auditors will absolutely look at the size and pattern of RTP adjustments to gauge the maturity of your process.

The Five-Step Deferred Tax Model

Deferred taxes are where the discipline shows. The classic ASC 740 deferred tax model has five steps.

1. Identify temporary differences. Compare each balance sheet account's book basis with its tax basis. The difference is a temporary difference.
2. Classify each as taxable or deductible. A taxable temporary difference (book basis > tax basis for an asset) creates a future taxable amount and a deferred tax liability. A deductible temporary difference (tax basis > book basis for an asset, or book carrying amount > tax basis for a liability) creates a future deductible amount and a deferred tax asset.
3. Multiply by the enacted tax rate expected to apply in the period the difference reverses. Use the rate enacted as of the balance sheet date — not the rate currently in pending legislation.
4. Recognize NOL and credit carryforwards as deferred tax assets at the same enacted rate.
5. Evaluate realizability of the deferred tax assets, and record a valuation allowance for any portion that is "more likely than not" not to be realized.

Two common pitfalls show up here. First, controllers sometimes track temporary differences cumulatively but lose the year-over-year rollforward — they cannot explain why the deferred tax asset for "deferred revenue" moved from $480,000 to $612,000. The fix is a clean, line-by-line deferred tax rollforward that ties opening balance to current movement to ending balance, with each movement explained. Second, the deferred balances should mathematically tie to the difference between book and tax basis. If you cannot reconstruct that tie-out from your trial balance and your tax depreciation schedule, your auditor will keep asking until you can.

Schedule M-1 (and M-3): Where Book Meets Tax

Schedule M-1 on Form 1120 reconciles book net income to taxable income before NOL and special deductions. Schedule M-3 does the same job in more detail for corporations with $10 million or more in assets, and it is also required of certain S corporations and partnerships above asset and reportable-entity thresholds.

Your ASC 740 working file should mirror Schedule M-1 line items closely. Every permanent and temporary difference identified in the provision should appear, with the same dollar amount, on Schedule M-1 (or M-3) when the return is prepared. When the provision and the return use different categorizations of the same item, controllers end up explaining differences twice — once to the auditor and once to themselves — and the RTP adjustment grows.

A practical tip: maintain a single, versioned book-to-tax difference schedule that powers both your provision and your return. The schedule should include the description of the difference, opening balance, current-year movement, ending balance, classification (permanent or temporary), source documentation, and the M-1 line where it will be reported. This single source of truth eliminates a major class of provision errors.

Valuation Allowances: The Judgment Call That Defines Your Provision

A valuation allowance reduces a deferred tax asset to the amount that is "more likely than not" — greater than 50 percent likely — to be realized. It is one of the most judgment-intensive areas of ASC 740, and one of the most common sources of audit comments at private companies.

You must weigh all available positive and negative evidence. The four sources of future taxable income to consider are:

• Future reversals of existing taxable temporary differences (your deferred tax liabilities).
• Future taxable income exclusive of reversing differences and carryforwards. This is the projection-based argument and it requires support.
• Carryback potential to prior taxable years, if the tax law allows.
• Tax planning strategies — prudent and feasible actions a company would undertake to prevent a carryforward from expiring.

Negative evidence weighs heavily. A cumulative three-year loss is treated in practice as significant negative evidence that is difficult to overcome, and it usually requires a full valuation allowance unless very strong positive evidence is available. Recent startups and venture-backed companies with substantial NOL carryforwards almost always carry a full valuation allowance because they lack the earnings history to support realization. That valuation allowance is then released — sometimes in dramatic fashion — when sustained profitability is achieved.

Document the analysis. The argument matters as much as the conclusion. Auditors want to see how you weighted the evidence, not just the final position.

Uncertain Tax Positions: The Two-Step Test

ASC 740-10 (formerly FIN 48) governs uncertain tax positions. The framework has two steps.

1. Recognition. Determine whether a tax position is more likely than not to be sustained on examination by the relevant taxing authority, based on the technical merits and assuming the authority has full knowledge of all relevant facts. Detection risk — the probability that the taxing authority will catch the issue — cannot be considered.
2. Measurement. For positions that pass step one, measure the benefit as the largest amount of benefit that is greater than 50 percent likely to be realized upon ultimate settlement.

Private companies sometimes assume FIN 48 only applies to large multinationals with complicated transfer pricing. That is not the standard. A privately held distributor that takes an aggressive position on a state nexus question, or a closely held manufacturer that classifies a costly repair as a deduction rather than capitalizing it, may have an uncertain tax position requiring recognition and disclosure. Treating these positions as "immaterial" without going through the formal recognition-and-measurement framework is a recurring audit finding.

What's New for 2026: ASU 2023-09

ASU 2023-09, "Improvements to Income Tax Disclosures," is the most significant change to the income tax footnote in over a decade. For private companies (non-public business entities), it is effective for annual periods beginning after December 15, 2025 — generally calendar year 2026.

Two things change in a material way for private companies.

Rate Reconciliation: Qualitative Relief, but Higher Scrutiny

Private companies are not required to present the numerical, category-by-category rate reconciliation that public business entities must now provide. Instead, private companies must provide qualitative disclosures explaining the nature and effect of differences between the statutory federal rate and the effective tax rate.

That sounds like relief, and it is — but the qualitative explanation has to be specific. "Other state and local taxes, net of federal benefit" is no longer enough. Disclosures should describe the underlying drivers in plain language: which states caused the variance, what specific permanent items drove the difference, whether one-time items like a valuation allowance release affected the rate, and how each contributed to the gap between statutory and effective rates.

Income Taxes Paid: Granular Disaggregation, No Relief

The income-taxes-paid disclosure applies uniformly — public and private companies alike. Annual disclosure must show income taxes paid, net of refunds received, disaggregated by:

• Jurisdiction: federal, state, and foreign.
• Individual jurisdictions equal to or greater than 5 percent of total income taxes paid (net of refunds received).

For a multi-state private company, this is a meaningful operational change. Your cash tax records have to be organized by jurisdiction in a way many private companies have never required before. If your accounting system aggregates state estimated payments into a single "state taxes paid" account, that has to change.

Start preparing now. Set up your general ledger and tax payment tracking with the disaggregation in mind, so that calendar 2026 (and the comparative prior-year data) can be pulled cleanly when the disclosure is required.

How Private Company Controllers Actually Get This Right

Three habits separate clean ASC 740 provisions from painful ones.

Make the workpapers tell the story. A good provision binder reads from front to back: pretax book income, walk to taxable income (organized like Schedule M-1), current tax by jurisdiction, deferred tax rollforward by item, valuation allowance analysis, uncertain tax positions, total provision tie-out, and journal entries. Each section references its supporting documentation. A reviewer should be able to recompute the provision from your workpapers without asking for additional files.

Separate preparation from review. The person who prepares the provision should not also be its only reviewer. Even at small private companies, a partner at the outside firm or an internal manager outside the tax function should sign off on the judgmental areas — valuation allowance, uncertain tax positions, and any non-routine transaction (acquisitions, divestitures, restructurings).

Treat the return-to-provision true-up as a diagnostic. If your RTP adjustment is consistently 5 percent or more of your total provision, something in your provision process is breaking down. Track the size and direction of RTPs over multiple years and identify which line items repeatedly drive them. Fix the upstream cause.

How Bookkeeping Quality Drives Provision Quality

Every weakness in the income tax provision begins as a weakness in the books. If your fixed asset register is incomplete, your deferred tax for depreciation will be wrong. If you do not track stock compensation expense by grant type, your permanent and temporary differences for §83 events will be wrong. If your accruals are recorded only at year-end, the temporary differences for accrued bonuses, vacation, and warranty reserves will be impossible to reconcile.

A clean, well-organized general ledger — with consistent account naming, well-documented accruals, a fixed asset subledger that ties to the trial balance, and supporting documentation for each non-routine entry — makes the ASC 740 provision dramatically easier. The math is much faster when the records are right.

This is also why plain-text, version-controlled accounting fits well with the ASC 740 workflow. When every entry is reproducible and every change has an audit trail, walking from book to tax (and explaining the walk to your auditor) becomes a query against your data rather than a forensic exercise.

Common Mistakes That Become Audit Comments

• Not maintaining a deferred tax rollforward that ties opening to closing balances.
• Treating uncertain tax positions as immaterial without applying the two-step framework.
• Failing to record return-to-provision adjustments in the correct year, or burying them in current tax.
• Using an out-of-date enacted tax rate, especially around state rate changes and federal legislation effective dates.
• Inconsistent classification of items between the provision and Schedule M-1.
• Ignoring jurisdictions other than federal — state and foreign currents and deferreds often get under-attention until an auditor flags them.
• Releasing a valuation allowance prematurely without sufficient positive evidence (or holding one too long after sustained profitability).
• Underestimating the data work required to support the new ASU 2023-09 income-taxes-paid disclosure.

Keep Your Financial Records Provision-Ready

As you build or refine your ASC 740 process, the quality of your underlying books is what determines whether your provision takes two days or two weeks. Beancount.io provides plain-text, version-controlled accounting that gives controllers complete transparency into every entry, every adjustment, and every reclassification — exactly the audit trail an ASC 740 review depends on. Get started for free and see why finance teams that care about clean, reproducible records are switching to plain-text accounting.