Financial Reporting / Tax Provision
Income tax disclosure readiness starts with jurisdiction-grade ERP data.
ASU 2023-09 gives finance teams a useful forcing function: make tax disclosure data traceable, jurisdiction-aware, and reusable. The teams that use 2026 to strengthen cash-tax events, rate-reconciliation drivers, and close evidence can turn a disclosure requirement into a better tax provision operating model.
Thesis: tax disclosure readiness is a data-contract opportunity.
FASB issued ASU 2023-09 to improve income tax disclosures under ASC 740. The accounting change is specific, but the operating lesson is broader: tax facts need to be captured with enough structure that finance can explain where tax expense, cash payments, refunds, and rate drivers came from without rebuilding the story at year-end.
The immediate timing matters. Public business entities adopted the guidance for annual periods beginning after December 15, 2024. Other entities adopt for annual periods beginning after December 15, 2025. For many private-company finance teams, that makes 2026 the implementation year and a practical planning window.
The opportunity is practical. A company that can generate jurisdiction-grade tax facts from ERP, treasury, AP, tax provision, and close systems will be better at disclosure, audit support, acquisition integration, lender reporting, and future finance automation. The same data contract pays off more than once.
The facts finance teams should design around.
Requirement
Effective date
Sourced fact
FASB says ASU 2023-09 is effective for public business entities for annual periods beginning after December 15, 2024, and for other entities for annual periods beginning after December 15, 2025.
ERP implication
Calendar-year public companies are already past first annual adoption, while many private companies are in their 2026 implementation year.
Requirement
Transition
Sourced fact
The ASU should be applied prospectively, with retrospective application permitted, and early adoption is permitted for annual financial statements not yet issued or made available for issuance.
ERP implication
Controllers should decide whether comparative data will be rebuilt and preserve that decision with the close and disclosure evidence.
Requirement
Income taxes paid
Sourced fact
EY summarizes the ASC 740 pending content as requiring annual disclosure of income taxes paid, net of refunds, by federal, state, and foreign categories.
ERP implication
Treasury, AP, tax, and GL data need a shared cash-tax event model instead of separate spreadsheets for tax provision support.
Requirement
Jurisdiction threshold
Sourced fact
The guidance requires separate annual disclosure for individual jurisdictions where income taxes paid, net of refunds, are at least 5 percent of total income taxes paid, net of refunds.
ERP implication
ERP and tax provision systems need jurisdiction codes, refund treatment, payment dates, source accounts, and tie-outs that survive close review.
Requirement
Domestic and foreign split
Sourced fact
EY notes additional annual disclosures for income or loss from continuing operations before tax, disaggregated between domestic and foreign, and income tax expense or benefit by federal, state, and foreign components.
ERP implication
Legal entity, tax residency, management reporting, elimination, and statutory ledger mappings need explicit ownership and version control.
Requirement
Private-company impact
Sourced fact
Cohen & Co states that private companies issuing 2026 fiscal-year financial statements will need to comply with ASU 2023-09.
ERP implication
Private-company teams can use 2026 to turn provision workpapers into controlled data flows before year-end pressure arrives.
The control model: turn tax facts into reusable ERP objects.
Most companies already have the raw ingredients: ledgers, tax authority payments, refunds, provision calculations, state and foreign workpapers, bank records, and close tasks. The gap is usually shape. ASU 2023-09 readiness improves when those ingredients become governed objects that finance can query, reconcile, and review.
Object
Tax jurisdiction master
Design pattern
Create a controlled list of federal, state, local, and foreign jurisdictions with codes, country or territory hierarchy, currency, tax authority, and materiality status.
Evidence to retain
Jurisdiction code, parent jurisdiction, effective date, owner, source authority, and approval history.
Object
Legal entity tax profile
Design pattern
Map each entity to domicile, filing jurisdictions, permanent establishment markers, statutory ledgers, tax consolidation group, and intercompany treatment.
Evidence to retain
Entity ID, tax residency, filing obligations, policy election, reviewer, and change request.
Object
Cash tax event
Design pattern
Record payments and refunds as tax events that retain bank reference, vendor or authority record, account, jurisdiction, tax year, payment type, and GL posting.
Evidence to retain
Payment instruction, bank statement line, jurisdiction allocation, refund offset, journal entry, and proof of payment.
Object
Rate-reconciliation driver
Design pattern
Tag provision adjustments by category, jurisdiction, nature, tax effect, source calculation, and disclosure threshold status.
Evidence to retain
Adjustment ID, source workpaper, category, amount, percentage, reviewer, and threshold evaluation.
Object
Domestic and foreign reporting view
Design pattern
Make domestic, foreign, state, and federal components a governed reporting view instead of a manual copy from the tax workbook.
Evidence to retain
Mapping version, legal entity scope, elimination policy, trial-balance source, and reviewer sign-off.
Object
Disclosure package
Design pattern
Generate the disclosure support package from reconciled facts, not from a late-stage document assembly exercise.
Evidence to retain
Disclosure table, source queries, tie-out workbook, variance explanation, preparer, reviewer, and approval timestamp.
A provision workflow that compounds over time.
The fastest path is a close workflow that captures tax facts once, tests them each period, and reuses them in the disclosure package. The controller should be able to see which jurisdictions cross disclosure thresholds, which cash-tax events support the calculation, and which review decisions explain the final table.
This is also a cost control. If finance can reuse source facts, field mappings, threshold tests, and reviewer sign-offs, the external-audit and advisor cycle becomes more targeted. Reviewers spend less time hunting for support and more time evaluating judgments.
Tax disclosure evidence packet
{
"tax_disclosure_packet_id": "asc740_2026_q4_us_gaap_0018",
"standard": "ASU 2023-09",
"reporting_period": "2026",
"presentation": "prospective",
"cash_tax_events": [
{
"event_id": "taxpay_2026_ca_0042",
"jurisdiction": "US-CA",
"category": "state",
"tax_year": "2026",
"amount": "1845000.00",
"currency": "USD",
"type": "payment",
"bank_reference": "wire_982771",
"gl_entry_id": "je_771904",
"source_document": "ca_estimated_payment_notice_q4.pdf"
}
],
"thresholds": {
"total_income_taxes_paid_net_of_refunds": "31240000.00",
"jurisdiction_disclosure_threshold": "5_percent",
"separately_disclosed_jurisdictions": ["US-FED", "US-CA", "IE", "UK"]
},
"review": {
"prepared_by": "tax_accounting_manager",
"reviewed_by": "controller",
"audit_evidence_complete": true,
"approved_at": "2027-01-18T16:42:00Z"
}
}Constructive failure modes to design around.
Tax payments exist only as bank transactions
Add jurisdiction, tax year, payment type, tax authority, source account, refund treatment, and evidence links at the event level.
The provision workbook owns the definitions
Move stable definitions into governed metadata so the workbook becomes a calculation view, not the system of record.
Jurisdiction names drift across systems
Use one jurisdiction master across ERP, tax provision, AP, treasury, and reporting exports.
Private-company teams wait for year-end
Run a midyear dry close with 2026 data so missing fields and ambiguous jurisdictions surface while there is still operating time.
Thresholds are tested late
Evaluate 5 percent jurisdiction thresholds and rate-reconciliation thresholds each close cycle, then store the result with source facts.
Evidence sits outside the close system
Retain payment proofs, reconciliations, policy memos, review notes, and disclosure tie-outs with the close task and journal lineage.
Questions for ERP and finance-system buyers.
Can the ERP retain tax payments and refunds by jurisdiction, tax year, tax authority, bank reference, GL account, and source document?
Can the system distinguish federal, state, local, and foreign tax facts without relying on account names or free-text memo fields?
Can provision adjustments be tagged by category, jurisdiction, nature, source calculation, preparer, reviewer, and threshold result?
Can domestic and foreign income before tax be generated from a versioned legal-entity and tax-residency mapping?
Can close tasks pull the tax evidence package directly from ERP, treasury, AP, and tax provision sources?
Can auditors trace a disclosed jurisdiction amount back to payments, refunds, bank evidence, GL postings, and approved calculations?
Can comparative periods be rebuilt if the company chooses retrospective presentation?
Can ERP exports preserve the jurisdiction data contract for auditors, tax advisors, and future system migrations?
The practical path forward.
Start with a dry run that gives the policy memo real operating evidence. Pick the most material jurisdictions, pull cash-tax payments and refunds from bank and ERP records, classify them by federal, state, local, and foreign categories, and tie the result to GL postings and provision workpapers. Then run the same test for domestic and foreign income before tax, tax expense components, and rate-reconciliation drivers.
Done well, ASU 2023-09 readiness gives finance teams a cleaner tax data layer. CFOs get better disclosure confidence. Controllers get stronger close evidence. Tax leaders get a repeatable provision workflow. ERP buyers get a concrete standard for evaluating whether finance systems preserve the jurisdiction facts that reporting now needs.
Sources
- FASB: Improvements to Income Tax Disclosures project page
- FASB ASU 2023-09: Income Taxes (Topic 740), Improvements to Income Tax Disclosures
- Deloitte DART: Income Tax Disclosure Considerations Related to the Adoption of ASU 2023-09
- EY Technical Line: FASB requires entities to provide additional income tax disclosures
- Cohen & Co: ASU 2023-09 Impact on Private Company 2026 Income Tax Disclosures
- Plante Moran: ASU 2023-09 aims to enhance transparency in income tax provision disclosures