The Closing Cycle teaches the lived rhythm of accounting work through a continuous in-tray, not batched period closes. Every active day (professor picks Mon-Fri or any weekday pattern), each team gets 1-5 events from senior accountants, the controller, audit managers, legal, HR, and IT: a late vendor invoice three days post-close, a bank reconciliation out by $87K, a warranty accrual that needs reassessment, a PCAOB inspection letter, an ASC 606 revenue-cutoff question, an ERP outage 48 hours before publish. Some events are multiple-choice with explicit deltas across the four pillars; others require a written response (accrual methodology memo, investigation plan, audit response) that a senior controller / audit partner LLM grades on technical accuracy, process discipline, and audit readiness. Four equally-weighted pillars compound: Close Discipline, Issue Resolution, Audit Readiness, Reporting Accuracy. Persistent state also tracks closes completed and material errors across the whole sim.
Share this with your team— printable one-pager for a chair or procurement./for-your-team/closing-cycleFirst close events land: accrual questions, small reconciliation breaks, process asks. Learn the cadence and workpaper rhythm.
Materiality calls, methodology reassessments, intercompany mismatches. The reviewer voice starts getting louder.
Suspense balances, revenue cutoff under ASC 606, out-of-period items. Reviewer questions land in writing; defend the framework.
Audit-manager and PCAOB-style letters. Workpaper discipline gets stress-tested against real inspection scrutiny.
Reporting-package accuracy, external audit signoff, post-close debrief. What worked, what leaks into next cycle.
Log in to start playing with your team. Make strategic decisions and compete on the leaderboard.