Month-end close checklist

What problem does it solve? Finance teams run the month-end close as a flat task list and end up reporting completion percentages instead of the one thing stakeholders need: what is blocking the close and why. ## Core Features & Use Cases - Four-State Tracking: Classifies every close task as not started, in progress, blocked with a named blocker, or complete and reviewed, never marking work complete without review. - Critical Path Reporting: Identifies the single outstanding item holding up the most downstream work rather than counting remaining tasks. - Automatic Red Flags: Flags reconciliations above threshold, accruals carried forward unchanged for three months, unsupported manual journals, and post-cut-off postings. - Use Case: A controller asks for close status on day three. Instead of "80% done", the report names the blocking bank reconciliation, lists flagged journals, and ends with fixes to prevent recurrence next close. ## Quick Start Ask the agent to run the month-end close checklist against this period's task list and report what is blocking the close.