Managing Accounting Policy Changes

---
name: managing-accounting-policy-changes
language: en
description: Evaluates new accounting standard impacts with transition planning and disclosure preparation. Use when implementing new standards, assessing ASU impacts, or planning accounting transitions.
tags:
  - management
  - accounting
metadata:
  author: casemark
  practice_areas:
    - Financial Reporting
    - Audit
    - Accounting
  document_types:
    - Management Report
  skill_modes:
    - Management
    - Coordination
---
# Managing Accounting Policy Changes

Evaluates new accounting standard impacts, builds transition timelines, quantifies financial statement effects, and prepares disclosure language for adoption of new or revised standards (ASUs, IFRS amendments, SEC rule changes).

## When To Use

- A new ASU or IFRS amendment has been issued and the entity needs an impact assessment
- The entity is selecting between transition methods (full retrospective, modified retrospective, prospective)
- Management needs a project plan for standard adoption with milestones and responsible parties
- Auditors or the audit committee have requested a readiness memo on upcoming standards
- Disclosure drafting is needed for "standards not yet adopted" footnotes or change-in-estimate narratives

## Inputs To Gather

- **Standard identification**: ASU number, IFRS amendment, or SEC rule reference and effective date [VERIFY]
- **Entity profile**: public vs. private filer status, SRC/EGC elections, fiscal year-end (determines adoption timeline) [VERIFY]
- **Current accounting policies**: existing policy language for affected areas (e.g., revenue, leases, credit losses)
- **Relevant data**: trial balance extracts, contract populations, portfolio compositions, or other quantitative inputs needed for impact sizing
- **Prior period financials**: comparative-period data if retrospective application is required
- **Stakeholder list**: controller, external auditor, audit committee chair, IT/systems owners affected by data or process changes

## Workflow

1. **Scope the standard change**
   - Identify the specific ASC/IFRS paragraphs superseded or amended
   - Determine effective date for the entity's filer category [VERIFY]
   - List all financial statement line items, disclosures, and EPS calculations potentially affected
   - Flag whether early adoption is permitted and whether management has elected it

2. **Quantify financial statement impact**
   - Map affected balances and transaction populations to the new measurement or recognition model
   - Estimate cumulative-effect adjustment to retained earnings (if modified retrospective)
   - Model restated comparative periods (if full retrospective)
   - Calculate tax effects of transition adjustments, including deferred tax asset/liability remeasurement
   - Document materiality conclusions — quantitative thresholds and qualitative factors considered

3. **Select and document transition method**
   - Compare available transition approaches permitted by the standard
   - Evaluate practical expedients and policy elections; document elections chosen and rationale
   - Prepare a transition-method memo suitable for audit committee and external auditor review

4. **Build the adoption project plan**
   - Define phases: gap analysis → system/process changes → parallel run → go-live → post-adoption monitoring
   - Assign owners for accounting policy drafting, IT configuration, data migration, internal controls updates, and training
   - Set milestone dates working back from the effective date, including interim reporting deadlines
   - Identify external resource needs (valuation specialists, actuaries, system vendors)

5. **Update internal controls and processes**
   - Document new or modified controls required by the standard (e.g., new impairment models, variable consideration constraints)
   - Assess SOX/ICFR implications — determine whether new controls need to be tested before effective date [VERIFY]
   - Update accounting policy manuals and close checklists

6. **Draft disclosure language**
   - Prepare "standards not yet adopted" footnote for periods before adoption (quantitative and qualitative impact)
   - Draft "change in accounting policy" footnote for the adoption period, including transition adjustments
   - Include required tabular reconciliations (e.g., opening balance sheet impact, line-by-line effects)
   - Ensure consistency between MD&A discussion and footnote disclosures

7. **Coordinate review and approval**
   - Circulate impact memo and draft disclosures to external auditor for pre-clearance
   - Present adoption summary to audit committee with financial statement impact, timeline, and risk areas
   - Document auditor concurrence on transition method and key judgments

## Output

- **Impact assessment memo**: standard summary, affected accounts, quantified adjustments, materiality analysis, and transition method recommendation
- **Adoption project plan**: phased timeline with owners, milestones, dependencies, and status tracking
- **Disclosure drafts**: "not yet adopted" and "change in policy" footnotes with required tabular data
- **Internal controls update**: new/modified control descriptions and SOX testing implications
- **Audit committee presentation**: executive summary of financial impact, key elections, and residual risks

## Quality Checks

- Effective dates match the entity's specific filer status and fiscal year — do not assume calendar year-end or large accelerated filer status [VERIFY]
- Cumulative-effect adjustments tie to underlying data and are tax-effected
- Practical expedient elections are explicitly documented with rationale, not silently assumed
- Disclosure language satisfies the specific transition disclosure requirements of the standard (cross-reference paragraph numbers)
- All comparative-period restatements, if applicable, are consistently reflected across primary statements, footnotes, and MD&A
- Project plan milestones account for interim reporting periods, not just the annual adoption date
- Mark any jurisdiction-specific tax treatment or regulatory filing requirement with [VERIFY]