
close-management
Manage the month-end close process with task sequencing, dependencies, and status tracking. Use when planning the close calendar, tracking close progress, identifying blockers, or sequencing close activities by day.
- Installs
- 3K
- Last 24h
- +9
- Trending rank
- #9199
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill close-management- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads close-management automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Close Management
Important: This skill assists with close management workflows but does not provide financial advice. All close activities should be reviewed by qualified financial professionals.
Month-end close checklist, task sequencing and dependencies, status tracking, and common close activities organized by day.
Month-End Close Checklist
Pre-Close (Last 2-3 Business Days of the Month)
- Send close calendar and deadline reminders to all contributors
- Confirm cut-off procedures with AP, AR, payroll, and treasury
- Verify all sub-systems are processing normally (ERP, payroll, banking)
- Complete preliminary bank reconciliation (all but last-day activity)
- Review open purchase orders for potential accrual needs
- Confirm payroll processing schedule aligns with close timeline
- Collect information for any known unusual transactions
Close Day 1 (T+1: First Business Day After Month-End)
- Confirm all sub-ledger modules have completed period-end processing
- Run AP accruals for goods/services received but not invoiced
- Post payroll entries and payroll accrual (if pay period straddles month-end)
- Record cash receipts and disbursements through month-end
- Post intercompany transactions and confirm with counterparties
- Complete bank reconciliation with final bank statement
- Run fixed asset depreciation
- Post prepaid expense amortization
Close Day 2 (T+2)
- Complete revenue recognition entries and deferred revenue adjustments
- Post all remaining accrual journal entries
- Complete AR subledger reconciliation
- Complete AP subledger reconciliation
- Record inventory adjustments (if applicable)
- Post FX revaluation entries for foreign currency balances
- Begin balance sheet account reconciliations
Close Day 3 (T+3)
- Complete all balance sheet reconciliations
- Post any adjusting journal entries identified during reconciliation
- Complete intercompany reconciliation and elimination entries
- Run preliminary trial balance and income statement
- Perform preliminary flux analysis on income statement
- Investigate and resolve material variances
Close Day 4 (T+4)
- Post tax provision entries (income tax, sales tax, property tax)
- Complete equity roll-forward (stock compensation, treasury stock)
- Finalize all journal entries — soft close
- Generate draft financial statements (P&L, BS, CF)
- Perform detailed flux analysis and prepare variance explanations
- Management review of financial statements and key metrics
Close Day 5 (T+5)
- Post any final adjustments from management review
- Finalize financial statements — hard close
- Lock the period in the ERP/GL system
- Distribute financial reporting package to stakeholders
- Update forecasts/projections based on actual results
- Conduct close retrospective — identify process improvements
Task Sequencing and Dependencies
Dependency Map
Tasks are organized by what must complete before the next task can begin:
LEVEL 1 (No dependencies — can start immediately at T+1):
├── Cash receipts/disbursements recording
├── Bank statement retrieval
├── Payroll processing/accrual
├── Fixed asset depreciation run
├── Prepaid amortization
├── AP accrual preparation
└── Intercompany transaction posting
LEVEL 2 (Depends on Level 1 completion):
├── Bank reconciliation (needs: cash entries + bank statement)
├── Revenue recognition (needs: billing/delivery data finalized)
├── AR subledger reconciliation (needs: all revenue/cash entries)
├── AP subledger reconciliation (needs: all AP entries/accruals)
├── FX revaluation (needs: all foreign currency entries posted)
└── Remaining accrual JEs (needs: review of all source data)
LEVEL 3 (Depends on Level 2 completion):
├── All balance sheet reconciliations (needs: all JEs posted)
├── Intercompany reconciliation (needs: both sides posted)
├── Adjusting entries from reconciliations
└── Preliminary trial balance
LEVEL 4 (Depends on Level 3 completion):
├── Tax provision (needs: pre-tax income finalized)
├── Equity roll-forward
├── Consolidation and eliminations
├── Draft financial statements
└── Preliminary flux analysis
LEVEL 5 (Depends on Level 4 completion):
├── Management review
├── Final adjustments
├── Hard close / period lock
├── Financial reporting package
└── Forecast updates
Critical Path
The critical path determines the minimum close duration. Typical critical path:
Cash/AP/AR entries → Subledger reconciliations → Balance sheet recs →
Tax provision → Draft financials → Management review → Hard close
To shorten the close:
- Automate Level 1 entries (depreciation, prepaid amortization, standard accruals)
- Pre-reconcile accounts during the month (continuous reconciliation)
- Parallel-process independent reconciliations
- Set clear deadlines with consequences for late submissions
- Use standardized templates to reduce reconciliation prep time
Status Tracking and Reporting
Close Status Dashboard
Track each close task with the following attributes:
| Task | Owner | Deadline | Status | Blocker | Notes |
|---|---|---|---|---|---|
| [Task name] | [Person/role] | [Day T+N] | Not Started / In Progress / Complete / Blocked | [If blocked, what's blocking] | [Any notes] |
Status Definitions
- Not Started: Task has not yet begun (may be waiting on dependencies)
- In Progress: Task is actively being worked on
- Complete: Task is finished and has been reviewed/approved
- Blocked: Task cannot proceed due to a dependency, missing data, or issue
- At Risk: Task is in progress but may not meet its deadline
Daily Close Status Meeting (Recommended)
During the close period, hold a brief (15-minute) daily standup:
- Review status board: Walk through open tasks, flag any that are behind
- Identify blockers: Surface any issues preventing task completion
- Reassign or escalate: Adjust ownership or escalate blockers to resolve quickly
- Update timeline: If any tasks are at risk, assess impact on overall close timeline
Close Metrics to Track Over Time
| Metric | Definition | Target |
|---|---|---|
| Close duration | Business days from period end to hard close | Reduce over time |
| # of adjusting entries after soft close | Entries posted during management review | Minimize |
| # of late tasks | Tasks completed after their deadline | Zero |
| # of reconciliation exceptions | Reconciling items requiring investigation | Reduce over time |
| # of restatements / corrections | Errors found after close | Zero |
Common Close Activities by Day
Typical 5-Day Close Calendar
| Day | Key Activities | Responsible |
|---|---|---|
| T+1 | Cash entries, payroll, AP accruals, depreciation, prepaid amortization, intercompany posting | Staff accountants, payroll |
| T+2 | Revenue recognition, remaining accruals, subledger reconciliations (AR, AP, FA), FX revaluation | Revenue accountant, AP/AR, treasury |
| T+3 | Balance sheet reconciliations, intercompany reconciliation, eliminations, preliminary trial balance, preliminary flux | Accounting team, consolidation |
| T+4 | Tax provision, equity roll-forward, draft financial statements, detailed flux analysis, management review | Tax, controller, FP&A |
| T+5 | Final adjustments, hard close, period lock, reporting package distribution, forecast update, retrospective | Controller, FP&A, finance leadership |
Accelerated Close (3-Day Target)
For organizations targeting a faster close:
| Day | Key Activities |
|---|---|
| T+1 | All JEs posted (automated + manual), all subledger reconciliations, bank reconciliation, intercompany reconciliation, preliminary trial balance |
| T+2 | All balance sheet reconciliations, tax provision, consolidation, draft financial statements, flux analysis, management review |
| T+3 | Final adjustments, hard close, reporting package, forecast update |
Prerequisites for a 3-day close:
- Automated recurring journal entries (depreciation, amortization, standard accruals)
- Continuous reconciliation during the month (not all at month-end)
- Automated intercompany elimination
- Pre-close activities completed before month-end (cut-off, accrual estimates)
- Empowered team with clear ownership and minimal handoffs
- Real-time or near-real-time sub-system integration
Close Process Improvement
Common Bottlenecks and Solutions
| Bottleneck | Root Cause | Solution |
|---|---|---|
| Late AP accruals | Waiting for department spend confirmation | Implement continuous accrual estimation; set cut-off deadlines |
| Manual journal entries | Recurring entries prepared manually each month | Automate standard recurring entries in the ERP |
| Slow reconciliations | Starting from scratch each month | Implement continuous/rolling reconciliation |
| Intercompany delays | Waiting for counterparty confirmation | Automate intercompany matching; set stricter deadlines |
| Management review changes | Large adjustments found during review | Improve preliminary review process; empower team to catch issues earlier |
| Missing supporting documents | Scrambling for documentation at close | Maintain documentation throughout the month |
Close Retrospective Questions
After each close, ask:
- What went well this close that we should continue?
- What took longer than expected and why?
- What blockers did we encounter and how can we prevent them?
- Were there any surprises in the financial results we should have caught earlier?
- What can we automate or streamline for next month?
FAQ
What does the close-management skill do?
Manage the month-end close process with task sequencing, dependencies, and status tracking. Use when planning the close calendar, tracking close progress, identifying blockers, or sequencing close activities by day.
How do I install close-management?
Run npx skills add https://github.com/anthropics/knowledge-work-plugins --skill close-management in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/close-management/ (personal) or .claude/skills/close-management/ (project).
Which AI agents can use close-management?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is close-management safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains close-management?
It is published by anthropics in anthropics/knowledge-work-plugins, and it is an official skill from the maker of the technology it covers. It has 3,038 recorded installs.
More from anthropics/knowledge-work-plugins
data-visualization
anthropics/knowledge-work-plugins
Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.
documentation
anthropics/knowledge-work-plugins
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
code-review
anthropics/knowledge-work-plugins
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
build-dashboard
anthropics/knowledge-work-plugins
Build an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
system-design
anthropics/knowledge-work-plugins
Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
memory-management
anthropics/knowledge-work-plugins
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。