Close Management

Close Management is an official skill from Anthropic’s Finance plugin in the public knowledge-work-plugins repository. It configures Claude to coordinate a month-end close by organizing work by close phase and business day, making dependencies visible, documenting ownership, and treating delays as blockers. This entry covers the individual close-management directory rather than the entire Finance plugin. According to the provider, the plugin is primarily designed for Claude Cowork and also works in Claude Code. The skill itself is a text-based operating guide, not accounting software, an ERP, or an automatic guarantee that a close is correct.

Purpose and workflow

The skill starts before the close with a preparation window covering the last two or three business days of the month. During that period, the source recommends distributing the close calendar and reminders, confirming cutoff procedures with accounts payable, accounts receivable, payroll, and treasury, checking that source systems are processing normally, preparing a preliminary bank reconciliation, reviewing open purchase orders for possible accruals, aligning the payroll schedule, and collecting information about unusual transactions. After month-end, the template typically sequences work across five business days. Day one includes accruals for received but uninvoiced goods and services, payroll postings, cash activity, intercompany postings, final bank reconciliation, depreciation, and prepaid amortization.

Daily calendar and dependencies

Day two covers revenue recognition, remaining accrual journal entries, accounts receivable and accounts payable subledger reconciliations, inventory adjustments, and foreign-currency revaluation. Day three focuses on balance-sheet reconciliations, adjusting entries, intercompany reconciliation, a preliminary trial balance, and an initial income-statement flux analysis. Day four adds tax provision entries, the equity roll-forward, a soft close, draft financial statements, detailed variance explanations, and management review. Day five includes final adjustments, the hard close, locking the period in the ERP, distributing the reporting package, updating forecasts, and conducting a retrospective. This order is a starting framework. Each organization must adapt it to its accounting policies, controls, systems, deadlines, and jurisdictional requirements.

Status, blockers, and critical path

For each work item, the source recommends a consistent status view containing the task, owner, deadline, status, blocker, and notes. States range from not started to in progress and complete, with blocked and at-risk states for dependency or deadline problems. A brief daily close meeting is intended to surface late work, missing data, reassignment needs, escalation paths, and timeline impact. The typical critical path runs from cash, accounts payable, and accounts receivable entries through subledger reconciliations, balance-sheet reconciliations, tax provision, draft financials, management review, and the hard close. This helps with sequencing and communication, but it does not replace an organization’s approval matrix, segregation of duties, evidence standards, or control sign-offs.

Use, data, and boundaries

The skill can work with supplied spreadsheets, files, and notes. When suitable MCP connections exist for an ERP, data warehouse, spreadsheets, business intelligence, documents, email, or team communication, those sources can be incorporated into an agent workflow. Quality depends on complete data, correct periodization, account mapping, eliminations, documented adjustments, and the permissions granted to connected systems. According to the provider, the Finance plugin does not provide financial, tax, or audit advice. Qualified finance professionals must review outputs before management reporting, regulatory filings, audit documentation, or period locks. A connected language model may transmit inputs and outputs to its model provider; a local skill file does not automatically mean local model processing. The repository is licensed under Apache-2.0. This entry stores no credentials, tokens, or secret sample data.

Catalog fit

Close Management fits Data Analysis because it structures close data, deadlines, variances, and process metrics. It also fits Office because it supports close calendars, status reports, management materials, and retrospectives. The Claude Code, Codex, and Cursor compatibility assignments describe documented use as instruction context; actual data access depends on each client and its connectors. Monorepo popularity is a point-in-time repository signal, not evidence of quality, security, or suitability for this individual skill.