For your team · The Closing Cycle
Accounting & Monthly Close
Own the books through month-end, then survive the audit. Every shortcut leaves something on the books the auditor finds later.
The Closing Cycle puts each team on the close desk at Sentinel Corp (public), Beacon Industries (PE-backed private) or Crestmoor Foundation (nonprofit). Every active day the inbox brings 1-5 close items: a late vendor invoice, a bank reconciliation out by $87K, a warranty accrual running 22% light, a PCAOB inspection letter, an ERP outage 48 hours before publish. About two in three are choices; the rest ask for a 100-150 word memo that a senior controller / audit partner LLM grades 0-10, with the team's current books and its earlier calls and memos on the topic in front of it. Under the inbox the team keeps books. Every 5 active days is one month-end close with 4.5 staff hours for each item: thorough treatments cost hours, shortcuts save hours and can leave a dollar error on the team's uncorrected-error list. At the end of each close the whole list is tested against the company's materiality ($1.5M at Sentinel, 5% of pre-tax income): over the line is a material error and the close is restated, and errors passed on at the close review stay on the books and are tested again next close (SAB 108). Running over the hours makes the close slip past the company's days-to-close target. Control lapses (unapproved entries, variances parked in suspense, compressed review) are graded deficiency, significant deficiency or material weakness, and the year ends with the team's audit report: the opinion, the proposed adjustments, the control findings and a management letter written from the team's own calls and memos.
One Close Score on every screen: the plain average of the four pillars, each 60% graded calls and 40% measured from the team's books. Calls are graded against the options the team had (the best available option scores 100, the weakest 0; a memo its 0-10 grade × 10; a missed item 0), averaged by severity (urgent 1.5×, info 0.5×) from two neutral 50s. The measured parts: days to close (80 on target, 50 at 20% over), errors cleaned up by the next close, control findings (100 less 6 per deficiency, 15 per significant deficiency, 30 per material weakness), and errors left against materiality at each close test (0 for a restated close). A student's suggested grade is 70% Close Score + 30% their own work (25 points memo quality: their average memo grade, counted at n/(n+5) for n graded and the team's memo average for the rest; 5 points answering their share of the team's items on time); once any team in the class claims a role, that is 80% of the grade and role credit the other 20% (half owned work in each close: items the student's role owns, and for the Controller memos signed off; half a reflection of 40+ words on each close). With roles on, a memo no second teammate signed off is a light approval gap (0.1 of lapse weight in journal entries and approvals, 1.0 at most together): never reviewing costs a strong team 6 points of measured Audit Readiness, 0.6 on the Close Score. A team of one is never marked down for it.
60% grades on review, sign-off and close-process calls; 40% days to close against the company's target.
60% grades on reconciliations, variances and suspense items; 40% how much of the uncorrected-error list the team cleaned up in time.
60% grades on the calls that have to survive the auditor; 40% the control findings (deficiencies, significant deficiencies, material weaknesses).
60% grades on accruals, adjustments, revenue and disclosures; 40% the errors left on the books at each close test against materiality.
Shortcuts leave dollar errors on an uncorrected-error list, tested against materiality at every month-end close. Small errors add up; errors passed on carry into the next close; over the line, the close is restated.
Every treatment costs staff hours against a fixed budget per close. Thorough work slips the close past the company's days-to-close target; shortcuts close fast and pile up errors. Always picking the most thorough option stops being safe.
The Final Report is the team's audit report: the opinion, proposed adjustments, control findings graded deficiency to material weakness, the auditor's sample, and a management letter written from the team's own calls and memos.
The senior controller / audit partner grader sees the team's current books and its earlier calls and memos on the topic, so a memo that contradicts the team's own earlier position gets noticed.
Sentinel Corp (SEC reporting, SOX, PCAOB; 5-day close target), Beacon Industries (PE-backed, covenant reporting; 8 days) and Crestmoor Foundation (net assets, donor restrictions, Form 990, Single Audit; 12 days), each with its own materiality and items.
Four roles: Controller (the reviewer: review and process items, the close review, signing off memos), Senior Accountant (reconciliations and accruals), Technical Accounting & SEC Reporting (adjustments and reporting) and Audit Liaison (audit items). Every memo is prepared by one teammate and signed off by another; the inbox shows who did each, and the audit report counts the memos reviewed.
One sim day per active day, and a month-end close every 5 days: 25 days (five closes) on the 5-week format, 40 (eight) on 8-week, 70 on a semester, then the audit. Mon-Fri at 3 items a day by default.
Designed for ~15-30 students in teams of 4-5. Each team runs one persistent close team and splits four light roles (one student can hold two on a small team).
Graduate or upper-undergraduate accounting courses, controllership and audit electives, accounting capstones.
The only sim where the close has a calendar, the books keep score and the year ends with an audit. Case studies teach standards; this teaches what closing books under time pressure and auditor scrutiny actually costs.
One of many pre-authored prompts from the sim’s Week 1 debrieflibrary. Grounded in the team’s actual decisions and used as a scheduled teaching moment.
Week 1 debriefThe late invoice — accrue or hold?
A vendor invoice arrived after close cutoff this week. Show us your team's memo. Did you accrue, hold in next period, or push back on the vendor? What is your team's materiality threshold, and did the memo reference it?
A single in-tray event drawn from the sim’s live event catalog — the kind of decision a student team sees in their inbox on any given active day.
A $42K legal invoice for services rendered in close period arrived 3 days after we closed the period. Our post-close adjustment threshold is $25K. Adjust the prior period? Book in current? Both have implications.
Canvas, Blackboard, Brightspace, Moodle via LTI 1.3. Students launch from your LMS with single sign-on; one-click grade publish posts scores back with the rubric breakdown as the comment.
Per semester. No platform fee, no per-section charge, no seat minimums. Institutional invoicing available.