If your private company files GAAP financial statements and you have an audit, an investor reporting package, or a credit agreement that requires US GAAP, then the income tax footnote isn't just a tax problem—it's a financial reporting problem. ASC 740 is the standard that controls how that footnote gets built, and starting with fiscal years that begin after December 15, 2025, the rules around what you have to disclose are changing in ways that catch a lot of finance teams off guard.
Here's the part most controllers underestimate: the number on your tax return is not the number you book. The provision under ASC 740 starts from book income, not taxable income, and the gap between the two has to be reconciled, classified into permanent and temporary differences, measured at the right enacted rate, and—if you have any deferred tax assets—stress-tested for whether you'll ever realize them. Get any one of those steps wrong and the audit cycle stretches by weeks while the deferred tax rollforward refuses to tie out.
This guide walks through how the income tax provision is actually built for a private company, where the most common errors hide, and what changes when ASU 2023-09 kicks in for non-public business entities in 2026.
Why ASC 740 Exists at All
Tax accounting under the Internal Revenue Code answers one question: how much tax do you owe to the government this year? GAAP financial reporting answers a different question: how much tax expense matches the income you reported on your books?
Those two numbers diverge for two reasons. First, the rules for what counts as income or expense are not the same for tax purposes as for book purposes. Some items are different forever (permanent differences, like fines or 50% of meals). Others are different only for now and will reverse in some future year (temporary differences, like depreciation, accruals, and bad debt reserves).
ASC 740 forces companies to recognize today the future tax consequences of those temporary differences. If your books deduct an accrued bonus that the IRS won't let you deduct until it's paid next year, then you have a deductible temporary difference today that will produce a tax benefit later. ASC 740 says: book a deferred tax asset for that future benefit now, in the same period the bonus expense hits your books. The tax expense in your income statement should match the income, not lag it by years.
The output of that process is your total income tax provision, and it has two components:
Total tax expense = Current tax expense + Deferred tax expenseCurrent expense roughly tracks what's on your tax return. Deferred expense captures the change in your net deferred tax position from the beginning to the end of the year. Together they should reconcile back to your effective tax rate.
Step 1: Build the Current Tax Provision
The current provision starts with pretax book income and walks down to taxable income. The line items on that walk are:
- Pretax GAAP income (loss).
- Plus or minus permanent differences (items that never reverse).
- Plus or minus temporary differences (items that will reverse in future periods).
- Less usable net operating loss carryforwards.
- Equals taxable income.
- Multiplied by the applicable enacted statutory rate.
- Less applicable tax credits.
- Equals current federal tax expense.
You then repeat the analysis for state and foreign jurisdictions, layering in their own permanent and temporary differences, apportionment, and credits. State current tax in particular can be a meaningful share of the total provision for any company with multistate nexus, and if you skip the state walk you'll likely understate your effective rate.
The current provision is the easier of the two halves because it tracks your actual return. The harder half is what comes next.
Step 2: Build the Deferred Tax Provision
ASC 740 uses a balance-sheet approach for deferred taxes. You're not measuring the tax effect of this year's income statement directly. You're measuring the change in your deferred tax assets and liabilities from the beginning of the year to the end, and the change becomes the deferred portion of your provision.
The standard five-step deferred tax model goes like this:
Step 1: Identify temporary differences. Compare the GAAP carrying value of every asset and liability to its tax basis. Anywhere those two numbers differ for a reason that will eventually reverse, you have a temporary difference. Common examples: accumulated depreciation (tax often takes bonus depreciation while books take straight-line), accrued vacation, deferred revenue, allowance for doubtful accounts, stock-based compensation, and lease ROU assets and liabilities under ASC 842.
Step 2: Categorize each difference. A temporary difference is either a future taxable amount (it will increase taxable income when it reverses, producing a deferred tax liability) or a future deductible amount (it will decrease taxable income when it reverses, producing a deferred tax asset). NOL carryforwards and credit carryforwards are also deferred tax assets even though they aren't temporary differences in the classic sense.
Step 3: Determine the applicable tax rate. Deferred taxes are measured at the enacted tax rate expected to apply when the difference reverses. Not proposed, not announced, not "likely to pass"—enacted. If a state has a graduated rate or a sunset provision, you have to model out reversal years and use the rate that will apply in each year. Document this clearly; reviewers will ask.
Step 4: Multiply. Temporary differences times applicable enacted rate equals deferred tax assets and liabilities.
Step 5: Evaluate for valuation allowance. This is where most private companies stumble.
The Valuation Allowance Question
A deferred tax asset is only worth booking if the company can actually realize it. Realization happens when there's future taxable income against which the deferred deduction or credit can be applied. ASC 740 requires that you record a valuation allowance against any portion of a deferred tax asset that is more likely than not (MLTN, meaning greater than 50% likely) to not be realized.
The MLTN evaluation is a "totality of evidence" test, weighting positive evidence (such as a strong history of profitability, existing taxable temporary differences that will reverse and provide income, and tax planning strategies) against negative evidence (cumulative losses in recent years, expiring carryforward periods, and going concern issues).
A practical rule of thumb: if your company has cumulative pretax losses in the most recent three years, that's considered objectively significant negative evidence that's hard to overcome. Many early-stage and growth companies maintain a full valuation allowance on their net deferred tax assets for exactly this reason. As the company turns profitable and the cumulative loss position reverses, releasing the allowance becomes a multi-year judgment call.
When you do release a valuation allowance, the release flows through deferred tax expense in the period the judgment changes. That can produce a large one-time tax benefit that distorts the effective rate—be ready to explain it.
Step 3: Account for Uncertain Tax Positions
ASC 740 also incorporates what was originally FIN 48: a two-step model for uncertain tax positions (UTPs). If your company has taken a tax position on a return that might not survive examination, you can't recognize the full benefit on the financial statements.
Recognition (Step 1): A position is recognized only if it is more likely than not to be sustained on examination based solely on its technical merits. The "based solely on technical merits" phrase is important—you ignore detection risk. The question is not "what are the odds the IRS will catch this," it's "if the IRS does examine the position, what are the odds we'd win on the law and the facts?"
Measurement (Step 2): If the position passes recognition, you measure the benefit at the largest amount that is more than 50% likely to be realized upon settlement with the taxing authority. That often produces an unrecognized tax benefit (UTB) that lives on the balance sheet as a long-term liability.
For a private company, common UTPs include aggressive transfer pricing positions, R&D credit calculations, state nexus determinations where you've decided not to file, and characterizations of items as deductible vs. capital. The UTB liability has to be rolled forward each year, with interest and penalty accruals tracked separately.
Schedule M-1, M-3, and the Reconciliation You'll Be Asked For
Once the current and deferred provisions are calculated, your audit and tax workpapers should produce a clean reconciliation between book income and taxable income. The IRS uses Schedule M-1 (or M-3 for larger entities) on the corporate return to capture this same walk, and a well-organized provision binder should map line by line to those schedules.
The reconciliation is a forensic tool. If your effective tax rate doesn't tie out to the statutory rate after walking through permanent items, there's an error somewhere in your provision—usually a misclassified temporary difference or a missed permanent item.
What Changes for Private Companies in 2026: ASU 2023-09
ASU 2023-09, Improvements to Income Tax Disclosures, changes the income tax footnote for everyone, but the rules and timing differ between public business entities (PBEs) and non-PBEs.
For non-PBEs—which is most private companies—the standard is effective for annual periods beginning after December 15, 2025. For a calendar-year private company, that means fiscal year 2026 financial statements will be the first to incorporate the new disclosures. Early adoption is permitted, and the standard is applied prospectively (with an option for retrospective application).
The two big buckets of change:
Rate reconciliation disaggregation. Public companies have to provide a numerical tabular reconciliation broken into eight specified categories (federal, state, foreign, enactment of new tax law, effect of cross-border tax laws, tax credits, valuation allowances, and nontaxable/nondeductible items), with further disaggregation by jurisdiction for amounts equal to or exceeding 5% of the domestic statutory tax expense. Private companies (non-PBEs) are not required to provide the numerical tabular reconciliation. Instead, non-PBEs must qualitatively describe the nature and effect of those same significant categories of reconciling items and the jurisdictions causing significant differences between the statutory and effective rates.
Income taxes paid disaggregation. Both PBEs and non-PBEs must disclose income taxes paid (net of refunds) disaggregated by federal, state, and foreign jurisdictions, with further disaggregation by individual jurisdictions whose taxes paid equal or exceed 5% of total income taxes paid. This is a new requirement that will surface state-level data many private companies haven't tracked at this level of granularity before.
The practical implication for non-PBEs is that the rate reconciliation footnote becomes longer and more narrative, and your jurisdiction-by-jurisdiction tax payment tracking has to be tighter. If you've been booking state income taxes paid in a single account without the ability to break out which states received what, you'll want to fix that ledger structure before the close.
Where Private Company Provisions Most Often Go Wrong
After watching hundreds of audit cycles, the same handful of failure modes show up year after year:
- Deferred tax rollforwards that don't tie. The opening balance on January 1 has to match the closing balance from the prior year's audited provision. If they don't tie within a small immaterial difference, every reviewer will dig in and the close cycle slows.
- Misclassified book-tax differences. Treating a permanent item as temporary (or vice versa) doesn't change the current year's expense materially, but it pollutes deferred balances and can take years to unwind.
- Stale enacted rates. Federal rate changes are easy to catch. State rate phase-ins, foreign rate changes, and the OBBBA-era extensions of expiring provisions are the items that get missed.
- Valuation allowance assertions that don't match the cumulative loss test. Claiming a deferred tax asset is realizable while the company has cumulative pretax losses requires substantial positive evidence and detailed documentation. Hand-waving doesn't survive an audit.
- State provisions calculated as a flat rate on federal taxable income. State apportionment, addbacks, and modifications can create state effective rates that look nothing like the headline statutory rate. For multistate businesses, the state component can easily be 20% or more of total tax expense.
- Missing UTB liability for known aggressive positions. If your tax preparer is comfortable with a position but the technical merits are 60/40, you may still need a UTB for the gap between the return position and the measurement amount.
- Forgetting interim period considerations. If you have to issue an interim provision (quarterly statements for lenders, for instance), ASC 740-270 requires an annual effective tax rate approach that's different from the year-end calculation.
A Practical Close Calendar for the Provision
A clean provision close looks roughly like this:
- Day 1–3 of close: Reconcile the trial balance and lock book income. The provision can't start until book income is final.
- Day 4–7: Identify and quantify permanent and temporary differences. Compare to prior year as a sanity check.
- Day 8–10: Calculate current federal, state, and foreign provisions. Tie out the effective rate at a high level.
- Day 11–14: Roll forward deferred tax assets and liabilities. Reconcile movements to current year activity.
- Day 15–17: Evaluate valuation allowance and uncertain tax positions. Document the conclusions.
- Day 18–20: Build the income tax footnote, including the new ASU 2023-09 disclosures. Tie every number in the footnote back to a workpaper.
- Day 21+: Audit review and revisions.
The single highest-leverage activity is keeping a clean deferred tax rollforward that ties to the prior year and shows every movement in the current year as a separately identifiable item: current-year activity, return-to-provision adjustments, rate changes, acquisitions, and other items.
Keep Your Books Audit-Ready from Day One
ASC 740 calculations are only as good as the underlying general ledger. If your trial balance is messy, your accruals are buried in catch-all accounts, or you can't quickly produce a fixed asset roll forward by jurisdiction, your provision close will be painful no matter how skilled your tax provider is. Plain-text accounting gives controllers a transparent, version-controlled source of truth: every journal entry is a readable text record, every account balance ties back to specific transactions, and your auditors can trace numbers without waiting for a report to be regenerated. Beancount.io brings that workflow to a hosted, AI-ready platform—get started for free and see why developers and finance teams choose plain-text accounting for the kind of clean data that makes provision season manageable.