Accounting Policy Update Cycle

Check the FASB website for Accounting Standards Updates issued or amended since the last cycle. Capture the ASU number, topic, and effective date for both public and private filers — effective dates often differ.

Skim IFRS amendments, SEC final rules, and SEC staff bulletins. Include PCAOB releases if the firm services an SEC issuer. Don't ignore IASB if any consolidated subsidiary reports under IFRS.

Tie each in-scope pronouncement to the chart-of-accounts ranges it touches — revenue recognition to 4xxx, leases to 1500/2300, credit losses to 1200. Where mapping is ambiguous, flag for technical accounting review rather than guessing.

Decide whether each pronouncement applies based on filer status (public vs. private), industry scope, and transaction types the entity actually has. Document the rationale for any "not applicable" determination — auditors will challenge it next year.

Quantify the expected effect on the trial balance, key ratios, and debt covenants. Even an order-of-magnitude estimate helps the CFO decide whether to early-adopt or wait. Include transition-method options (modified retrospective vs. full retrospective) where the standard offers a choice.

Edit the policy manual section-by-section. Keep a redline showing the prior language, the new language, and a footnote citing the driving ASU or IFRS amendment. Version-control discipline matters here — restated periods get audited against historical policy text.

For pronouncements introducing new topics (e.g., crypto-asset measurement, segment reporting expansion), write a new policy section rather than appending to an unrelated one. Cross-reference the technical memo so future readers see the source.

New standards almost always change disclosures. Update the financial-statement template, the MD&A boilerplate, and the segment/related-party schedules so the reporting package matches the new policy on first use.

Walk the CFO through material policy changes before the audit-committee meeting; surprises at committee level reflect badly on finance. Capture the signed approval and any discussion notes in the workpaper file.

Send the engagement partner the technical memo and redlined policy ahead of interim fieldwork. Letting auditors learn about a policy change during fieldwork extends the audit and invites independence-impairing "helpful suggestions" on language.

Run a working session for staff and senior accountants — walk the policy redline, show new journal-entry templates, and quiz on edge cases. Record the session for new-hire onboarding and CPE documentation.

Push chart-of-accounts changes, new reclass rules, and revised JE templates into NetSuite, Sage Intacct, or QBO. Also update the month-end close checklist itself so reviewers tie new accruals or disclosures to the new policy on the first close.

Close the period under both old and new policies and reconcile differences against the impact estimate from the technical memo. Variances beyond what the memo predicted indicate a scoping miss in the applicability review.

Triggered when the parallel test fails. Trace each variance to either (a) a JE template error, (b) an ERP configuration miss, or (c) a policy-language ambiguity. Each cause has a different fix path; don't patch symptoms.