ASU 2023-09 IPO Guide: Dates, EGCs and Tax Readiness

For tax directors preparing an S-1, the ASU 2023-09 IPO question starts with the annual statements being registered. Decide the adoption period first, then build a tax footnote that reporting, audit and counsel can review against the same evidence.

An IPO timetable isn't an accounting effective date. The useful starting point is a short applicability memo connecting the statement entity, reporting framework, emerging growth company election and actual adoption decision.

Key takeaway: Keep permission to delay, actual adoption and disclosure content in separate fields. One EGC checkbox can't answer all three.

What decides ASU 2023-09 IPO applicability?

Map the annual period to the entity's applicable adoption branch. The dates are annual-period start dates, so a 2026 filing can contain 2025 statements that already require adoption. The analysis should cover each statement entity, including predecessor or acquired-business financial statements, rather than assuming every statement follows the registrant's conclusion.

The final FASB update sets these dates and permits early adoption:

Public business entity, or PBE, is broader than a company whose shares have started trading. The PBE definition includes SEC financial-statement filers and certain regulatory filings preparing for unrestricted securities issuance; it also addresses financial information included in another issuer's filing.

Use this worksheet before circulating the first tax-note draft. These are recommended preparation steps, not extra filing requirements.

For an IFRS reporting basis, start with the relevant framework analysis rather than importing the ASC 740 timetable. Finrep's ASU 2023-09 and IAS 12 comparison provides a separate starting point.

Why doesn't the EGC election settle the tax-footnote format?

An extended transition election changes permitted timing; it doesn't turn an SEC registrant into a non-PBE. Read the cover page alongside the adoption note. A company can retain its broader EGC election while adopting this particular standard earlier, so “we're an EGC” isn't a complete instruction to the tax team.

SEC JOBS Act FAQs 13 and 14 address communicating the choice in the initial confidential submission, irrevocable opt-out and disclosure of the ordinary required date alongside the EGC's intended adoption date. Reassess the conclusion if EGC eligibility changes.

Two filings show why the evidence needs to be read together:

• Deep Fission, February 17, 2026 S-1: its EGC discussion retains extended transition, and the current-company pronouncements section describes ASU 2023-09 effectiveness for annual periods beginning after December 15, 2025. This is a resale registration following a reverse merger, not a conventional underwritten IPO. Deep Fission S-1.
• Figma, 2025 Form 10-K signed February 18, 2026: following its July 2025 IPO, Figma retains extended transition but reports prospective ASU 2023-09 adoption for 2025. Note 16 uses the updated reconciliation for 2025 and the earlier format for 2024 and 2023; its cash disclosure separately identifies Israel. Figma Form 10-K.

Deep Fission's filing contains multiple financial-statement contexts, including older pronouncement text with a different date. Label every extracted passage with its entity, period and note heading before putting it in an applicability memo.

Figma's example comes from its post-IPO annual report. It supports an actual adoption and comparative-presentation observation, not a claim about what its S-1 contained.

What should the tax team change in its disclosure workpapers?

Build a disclosure layer beside the provision workpapers. The provision explains expense; the disclosure layer needs to preserve categories, jurisdiction ownership and supporting descriptions. Start with a mapping sheet that records each adjustment's origin before it becomes an aggregated footnote line.

PBEs reconcile in amounts and percentages; non-PBEs disclose qualitatively. All in-scope entities disaggregate annual cash taxes. FASB amendment text.

For a practical mapping sheet, use columns for the adjustment, imposing jurisdiction, category, nature, amount, rate effect, source document and review conclusion. Link every judgment to a workpaper reference that another person can follow without asking the preparer to reconstruct the reasoning.

Classify Pillar Two by mechanism and imposing jurisdiction: cross-border means incremental domicile-imposed tax on foreign income, not every minimum-tax mechanism. Amended ASC 740-10-50-12A(c).

Keep domestic/foreign pretax and national/state/foreign expense mappings, plus the PBE majority-state explanation. For the broader category discussion, use the Finrep ASU 2023-09 explainer, then check the actual paragraph governing the item.

How do the two 5% tests differ?

The denominators differ: continuing-operations pretax income/loss times the domicile's national statutory rate for rate reconciliation; total net payments for cash taxes. Rate-disaggregation rules vary by category. FASB amendment text.

Consider an illustrative, profitable US company with $80 million of continuing-operations pretax income and an assumed 21% statutory rate. Expected statutory tax is $16.8 million, making the 5% amount $840,000.

The foreign pair nets to a $350,000 benefit, or 0.4375 percentage points. Foreign nature items can qualify despite country totals below threshold; netting has specific exceptions. Amended ASC 740-10-50-12A.

For review, retain the gross inputs and a separate explanation of any permitted netting. A below-threshold result isn't permission to delete the amount from the underlying category or ignore information needed to explain the footnote.

Now assume $10 million of total net cash income taxes. A jurisdiction with $500,000 of net payments is exactly 5% and reaches that test, even though $500,000 is below the example's $840,000 rate-reconciliation threshold.

Keep the two calculations on separate tabs. Give each denominator a visible label, a source reference and a period; an unlabeled “5%” cell is an invitation to copy the wrong number.

How do we build evidence for jurisdictional cash taxes?

Start with payment and refund records, then reconcile the completed register. Current tax expense isn't a substitute for cash movement. The register should make it possible to trace a jurisdiction subtotal through the legal entities that paid it to the underlying payment evidence.

A useful transaction-level register contains:

• Legal entity, imposing jurisdiction, payment date and tax type.
• Gross payment, refund, transaction currency and reporting-currency amount.
• Conversion support, bank or treasury reference and preparer.
• Disclosure bucket, jurisdiction subtotal, threshold outcome and reviewer.

Screen sales taxes and employer payroll taxes out of the income-tax register. Keep exclusion reasons rather than silently deleting transactions, particularly where treasury descriptions use a generic “tax” label.

Ask local teams to confirm jurisdiction ownership, including payments made by one entity on another's behalf. Then investigate differences between the register and the cash-flow disclosure instead of adding a balancing entry that has no jurisdiction.

Negative or near-zero total net payments deserve an explicit technical-review flag. Don't force an ordinary positive-denominator spreadsheet formula onto an unusual refund pattern and assume it produces the right disclosure.

Must we rebuild every comparative year?

Prospective application is the default; retrospective application is permitted. The amendments address annual disclosures. Decide the method before requesting historical data; interim statements don't themselves create new quarterly tables. FASB transition provisions.

This illustrative layout assumes adoption in 2025 and presentation of three annual years. It compares the preparation burden, not an issuer's actual footnote.

If you choose retrospective presentation, check whether older payment records preserve refunds, jurisdiction and currency detail. An old consolidated cash-tax total may be accurate yet insufficient for rebuilding the new detail.

What should tax and SEC reporting resolve before filing?

Agree on a single decision record and an evidence pack. Give the tax lead responsibility for the mapping and cash register, the controller responsibility for statement tie-outs, and SEC reporting responsibility for consistent adoption language. Coordinate unresolved accounting and filing questions with auditors and securities counsel.

Assess the separate SEC overlay, including applicable scaled reporting provisions. Regulation S-X Rule 4-08(h) already addresses tax components and reconciliation, with its own threshold wording and exception; it isn't a replacement for amended GAAP disclosure requirements.

If adoption remains ahead, SAB Topic 11.M supplies staff guidance on describing the standard, required and planned adoption, transition method and reasonably estimable impact. A conclusion about earnings alone doesn't explain the work needed to change disclosures.

Maintain a short open-judgment register: EGC exit, predecessor scope, netting, unusual refunds, Pillar Two mechanism and comparative method. Each issue needs an owner, evidence and a recorded disposition.

Finrep's ASU Applicability workflow describes a cited memo and disclosure checklist. Supply the entity facts, election and periods, then review the output against current licensed ASC and the filing facts; provision calculations and payment validation remain separate work.

Frequently asked questions

Does a 2026 IPO automatically require adoption in its 2025 statements?

No. Use the adoption branches above and document the statement entity, EGC election and actual adoption. The year printed on the S-1 isn't the effective-date test.

Can an EGC use non-PBE disclosure content after adopting?

An EGC timing election doesn't change the PBE assessment. Keep the disclosure-content conclusion separate from permission to adopt later.

Does earlier adoption mean the whole EGC election was abandoned?

Don't infer that from one standard's adoption. Read the election and adoption disclosures together, as the Figma example illustrates.

Are the new 5% calculations a materiality safe harbor?

No. They serve specific disaggregation tests. Preserve the category totals and review whether the resulting explanation lets readers understand the tax effects.

What should we request from local tax teams first?

Request payment and refund evidence by imposing jurisdiction, with tax-type and currency detail. Name the missing field before the close calendar makes it everyone's emergency.