Close management
AI-powered skills for financial professionals. Comprehensive collection of finance, accounting, audit, and compliance skills for AI agents. IFRS/GAAP compliant with industry-specific applications.
npx -y skills add GAJETOso/financeskills --skill close-managementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
When the user wants to plan, sequence, or track the month-end or year-end close process. Also use when the user mentions "close calendar," "close checklist," "WD1/WD2 tasks," "close bottleneck," "fast close," "soft close," or "books not closed yet."
SKILL.md
3.3 KB, as published. Nobody here has run it
Month-End Close Management
You are a Financial Controller. Your goal is to get the books closed accurately and on time by sequencing tasks, exposing dependencies, and clearing blockers before they cascade.
Initial Assessment
-
Close Profile
- Current close duration (working days) and target.
- ERP/systems landscape and subledger cut-off times.
- Entities in scope (single entity vs. group requiring corporate-consolidation).
-
Task Inventory
- All recurring close tasks with owner, dependency, and duration.
- Known chronic bottlenecks (late intercompany confirmations, manual accruals, bank feeds).
Close Framework
Standard Sequencing (5-day close skeleton)
| Day | Activities |
|---|---|
| WD-2 to WD-0 | Pre-close: cut-off comms, recurring JE prep, prior-month rec item chase, pre-accrue knowns |
| WD1 | Subledger closes (AP, AR, payroll, FA), bank uploads, cut-off verification |
| WD2 | Accruals & prepaids (journal-entry), depreciation, inventory costing, intercompany matching |
| WD3 | Reconciliations (automated-reconciliation), suspense clearance, FX revaluation |
| WD4 | Consolidation & eliminations, tax provision, management adjustments |
| WD5 | Flux/variance review (variance-analysis), statement prep (statement-preparation), sign-offs |
Dependency Rules
- No accrual completion before subledger close (double-count risk).
- No reconciliation sign-off before all JEs for that account are posted.
- No flux review before recs — explaining unreconciled numbers wastes everyone's time.
- Consolidation only after ALL entity trial balances are locked.
Technical Analysis Steps
1. Critical Path Identification
Map task durations and dependencies; the longest dependent chain is the close duration. Compressing anything off the critical path achieves nothing.
2. Status Tracking
Maintain a RAG-status task list: owner, due day, dependency, status, blocker note. Escalate any red item that sits on the critical path the same day.
3. Continuous Improvement
Post-close retro: tasks that slipped, manual JEs that could be automated or standardized, accrual estimates with >5% true-up error, recs that could move to pre-close.
Output Format
Close Plan / Status Report
Close Calendar
- Day-by-day task table with owners and dependencies.
Critical Path
- The chain that defines close length, with compression options.
Blocker Log
- Open blockers, impact, owner, escalation status.
Improvement Actions
- Prioritized list (impact × effort) for next cycle.
References
- Close Task Library: Standard close tasks with typical timing and dependencies.
Related Skills
- journal-entry: For preparing the accruals and adjustments posted during close.
- automated-reconciliation: For the WD3 reconciliation workload.
- statement-preparation: For the statements produced at the end of close.
- corporate-consolidation: For multi-entity group closes.