Circulos AI

Finance AI Skill

Closing Checklist Automation

Automate the month-end, quarter-end, and year-end close checklist with task orchestration, deadline tracking, dependency management, and bottleneck alerts. Use when setting up the close calendar, assigning close tasks, tracking close progress in real-time, identifying close bottlenecks, reducing close timeline, or generating close completion reports. Triggers on phrases like "close checklist", "month-end close", "close calendar", "close tasks", "close tracking", "reduce close time", "close automation", "financial close workflow", "close status".

Closing Checklist Automation

Orchestrate the financial close process end-to-end — from task assignment through final sign-off — with automated tracking, alerts, and continuous improvement.

Workflow

  1. Build the master close checklist: Document every task required for a complete close — journal entries, reconciliations, accruals, sub-ledger closes, consolidations, reporting — with owners, deadlines, and dependencies.
  2. Map task dependencies: Define the close sequence — which tasks must complete before others can start (e.g., sub-ledger close before GL close, all reconciliations before financial statements).
  3. Set the close calendar: Establish target close dates for month-end (e.g., T+5 business days), quarter-end (T+10), and year-end (T+15) with milestone checkpoints.
  4. Auto-assign tasks at close kickoff: On the close date, trigger the checklist with all tasks assigned to current owners (account for vacations, acting assignments).
  5. Track real-time progress: Dashboard showing task status (not started, in progress, complete, blocked), completion %, and estimated close date.
  6. Send automated alerts: Escalate delayed tasks — first to task owner, then to manager, then to controller — based on configurable escalation rules.
  7. Document and attach evidence: Require supporting documentation (reconciliation workpapers, approval emails, system screenshots) for each completed task.
  8. Collect electronic sign-offs: Route completed work packages to reviewers for approval with audit trail.
  9. Generate close metrics: Track close duration, task completion rates, rework frequency, and bottleneck patterns for continuous improvement.
  10. Post-close review: Analyze what went well and what didn't; update checklist, deadlines, and owners for next period.

Master Close Checklist Template

MONTH-END CLOSE CHECKLIST
─────────────────────────
Target: Complete by T+5 business days

PHASE 1: SUB-LEDGER CLOSE (Deadline: T+2)
  ────────────────────────────────────────
  [ ] Sales sub-ledger close — Owner: RevOps — Dependency: None
      • Revenue recognition run completed
      • Unbilled revenue calculated
      • Sales commissions accrued
  
  [ ] AR sub-ledger close — Owner: AR Manager — Dependency: Sales sub-ledger
      • All invoices posted
      • Collections posted
      • Write-offs processed and approved
      • AR aging report generated
  
  [ ] AP sub-ledger close — Owner: AP Manager — Dependency: None
      • All invoices posted
      • Payments processed
      • Accruals for goods/services received but not invoiced
      • AP aging report generated
  
  [ ] Fixed Asset sub-ledger close — Owner: FA Analyst — Dependency: None
      • New additions recorded
      • Disposals recorded with gain/loss
      • Depreciation run completed
      • FA roll-forward prepared
  
  [ ] Inventory sub-ledger close — Owner: Inventory Controller — Dependency: AP close
      • Physical count adjustments posted (if applicable)
      • Inventory valuation updated
      • COGS calculation completed
      • Inventory reconciliation to GL

PHASE 2: GENERAL LEDGER (Deadline: T+3)
  ────────────────────────────────────────
  [ ] Standard journal entries — Owner: GL Accountant — Dependency: Sub-ledger close
      • Recurring journal entries (depreciation, amortization, rent)
      • Payroll accruals and benefit accruals
      • Tax provisions
  
  [ ] Manual journal entries — Owner: Various Controllers — Dependency: Sub-ledger
      • Department-specific adjustments
      • Project-related accruals and deferrals
      • Intercompany eliminations (if periodic)
  
  [ ] Journal entry review & approval — Owner: Controller — Dependency: All JE posted
      • Review unusual entries (> threshold or non-standard accounts)
      • Approve all manual entries
      • Post approved entries to GL
  
  [ ] Trial balance review — Owner: Controller — Dependency: All JE posted and approved
      • Review TB for reasonableness vs. prior month
      • Investigate and explain significant movements
      • Flag unusual balances for management review

PHASE 3: RECONCILIATIONS (Deadline: T+4)
  ────────────────────────────────────────
  [ ] Balance sheet reconciliations — Owner: Reconciliation Team
      • Bank accounts reconciled
      • AR, AP, inventory, FA reconciled to sub-ledgers
      • All material BS accounts reconciled per SOX schedule
      • Outstanding items investigated and resolved
  
  [ ] Intercompany reconciliation — Owner: IC Controller
      • Intercompany transactions matched
      • Discrepancies resolved
      • Elimination entries prepared (if applicable)

PHASE 4: CONSOLIDATION & REPORTING (Deadline: T+5)
  ───────────────────────────────────────────────────
  [ ] Financial statements generated — Owner: Senior Accountant — Dependency: All above
      • Income statement, balance sheet, cash flow statement
      • Comparative period included
      • Variance analysis completed
  
  [ ] Management reports — Owner: FP&A — Dependency: Financial statements
      • KPI dashboard updated
      • Budget vs. actual analysis
      • Variance commentary drafted
  
  [ ] Close sign-off — Owner: Controller → CFO
      • Controller certifies completeness and accuracy
      • CFO reviews and signs off
      • Close officially complete

Dependency Map

CLOSE DEPENDENCY CHAIN:

  Day 1 (Month end + 1):
    ├── Sub-ledger close begins
    │     ├── Sales sub-ledger (2 days)
    │     ├── AP sub-ledger (1 day)
    │     ├── Fixed Assets (1 day)
    │     └── Inventory (2 days, depends on AP)
    │
    └── Data gathering for manual entries

  Day 2:
    ├── Sub-ledger close completes
    ├── Standard journal entries
    └── Begin manual journal entries

  Day 3:
    ├── Manual journal entries complete
    ├── Journal entry review & approval
    ├── Trial balance review
    └── Begin reconciliations

  Day 4:
    ├── Reconciliations complete
    ├── Intercompany reconciliation
    └── Begin financial statement generation

  Day 5:
    ├── Financial statements complete
    ├── Management reports
    ├── Variance analysis
    └── Close sign-off → CLOSE COMPLETE

Automated Alert Rules

ESCALATION RULES:

  TASK STATUS: "OVERDUE"
  ──────────────────────
  Trigger: Task deadline passed, status still "Not Started" or "In Progress"
  
  Escalation Chain:
    T+0 (deadline passes): Email notification to task owner
    T+4 hours: Slack/Teams message to task owner + manager
    T+8 hours: Email to task owner + manager + Controller
    T+24 hours: Email to Controller + CFO + task owner's VP
    T+48 hours: Executive alert — close at risk
  
  TASK STATUS: "BLOCKED"
  ──────────────────────
  Trigger: Owner marks task as blocked (waiting on dependency, missing data, system issue)
  
  Escalation Chain:
    T+0: Auto-notify dependency owner
    T+4 hours: Notify both owners' managers
    T+12 hours: Notify Controller for resolution
  
  TASK STATUS: "REWORK"
  ─────────────────────
  Trigger: Reviewer rejects completed task, sends back for correction
  
  Escalation Chain:
    T+0: Notify original owner with reviewer comments
    T+8 hours: If not restarted, notify manager
    T+24 hours: If still open, notify Controller
  
  CLOSE-LEVEL ALERT:
  ──────────────────
  Trigger: > 20% of Phase 1 tasks incomplete by T+2 deadline
  
  Action: Auto-generate "Close at Risk" report for Controller and CFO
  Include: Incomplete tasks, reasons, estimated impact on close date

Close Metrics Dashboard

CLOSE METRICS — January 2025 Close
====================================

CLOSE PERFORMANCE:
  Actual close duration:    4.2 business days  (Target: 5.0) ✓
  Prior month close:        5.1 business days
  12-month average:         4.6 business days
  Best close (YTD):         3.8 business days (November)

TASK COMPLETION:
  Total tasks: 42
  Completed on time: 38 (90.5%)
  Completed late:    3 (7.1%)
  Blocked:           1 (2.4%)
  
  Average completion time per task: 1.8 days
  Rework rate: 2 tasks (4.8%) — below 10% target ✓

BOTTLENECK ANALYSIS:
  Most delayed task: AR reconciliation (2.3 days behind schedule)
    Reason: High volume of year-end adjustments carried into January
    Recommendation: Shift AR cutoff to 25th of month to reduce volume
  
  Most reworked task: Manual journal entries (returned for incomplete support)
    Reason: New accountant on team
    Recommendation: Add JE template with mandatory fields

TREND ANALYSIS (Last 6 Months):
  Month     Close Days  On-Time %  Rework %  Bottleneck
  ──────────────────────────────────────────────────────
  Aug 2024  5.1         85.7%     9.5%      Intercompany rec
  Sep 2024  4.8         88.1%     7.1%      AR reconciliation
  Oct 2024  4.5         90.5%     4.8%      Manual JE
  Nov 2024  3.8         95.2%     2.4%      None (on track)
  Dec 2024  5.3         83.3%    11.9%      Year-end adjustments
  Jan 2025  4.2         90.5%     4.8%      AR reconciliation

IMPROVEMENT INITIATIVES (Q1):
  [ ] Auto-generate standard journal entries (target: save 0.5 days)
  [ ] Implement continuous close for AR/AP (target: save 1.0 day)
  [ ] Add AI-assisted reconciliation (target: save 0.5 days)
  Expected new close target: 3.0 business days by Q2

Continuous Close Approach

TRANSITION FROM MONTH-END TO CONTINUOUS CLOSE:

  Traditional close: All tasks done in T+1 to T+5 crunch
  Continuous close: Tasks spread throughout the month, close is "always current"
  
  CONTINUOUS CLOSE SCHEDULE:
  
  Days 1–5 of month:
    • Prior month's sub-ledger close completes
    • Standard journal entries posted (automated)
  
  Days 6–15 of month:
    • Reconciliations completed (spread across 10 days)
    • Manual entries gathered and reviewed
    • Intercompany reconciliations ongoing
  
  Days 16–20 of month:
    • All reconciliations complete
    • Trial balance reviewed
    • Financial statements "soft close"
    • Management can request reports at any time
  
  Days 21–25 of month:
    • Final review and sign-off
    • Official close
    • Variance analysis and commentary
  
  BENEFITS:
    ✓ No month-end crunch — even workload distribution
    ✓ Financial data available 20+ days into the month
    ✓ Earlier decision-making with current data
    ✓ Less stress on accounting team
    ✓ Fewer errors (no rush)
  
  PREREQUISITES:
    • Automated sub-ledger feeds (no manual data entry at close)
    • Standard journal entry automation
    • Reconciliation tools with auto-matching
    • Team discipline to complete tasks on schedule throughout month
    • Management acceptance of "soft close" before final sign-off

Edge Cases

Output

Close Status Dashboard (Live)

CLOSE STATUS — January 2025 — Day 3 of 5
==========================================

OVERALL PROGRESS: ██████████░░ 72% (30/42 tasks complete)
ESTIMATED CLOSE: Day 4.2 (0.8 days ahead of schedule)

PHASE STATUS:
  Phase 1 — Sub-Ledger Close:   ████████████ 100% (5/5 complete) ✓
  Phase 2 — General Ledger:      ██████████░░  80% (4/5 complete)
    ⚠ Manual JE review — In Progress (due Day 3, on track)
  Phase 3 — Reconciliations:     ██████░░░░░░  50% (4/8 complete)
    ⚠ AR reconciliation — In Progress (started Day 3, was Day 2 target)
    ⚠ Bank reconciliation — Not Started (blocked — waiting on bank feed)
  Phase 4 — Reporting:           ░░░░░░░░░░░░   0% (0/5 complete)

ALERTS:
  🟡 Bank reconciliation blocked — IT investigating bank API feed failure
  🟡 AR reconciliation 1 day behind — high volume, extending deadline to Day 4
  🟢 All other tasks on schedule

Integration Points

Disclaimer: All rights reserved by Circulos AI. These skills are specifically designed for Claude Code, Claude Cowork, Codex, and OpenClaw. When using or referencing any skill, please provide proper attribution to Circulos AI.