close-management

작성자: anthropic

월말 마감 프로세스를 작업 순서, 종속 관계 및 상태 추적과 함께 관리합니다. 마감 일정을 계획하거나 마감 진행 상황을 추적할 때 사용하세요.

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill close-management

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:

TaskOwnerDeadlineStatusBlockerNotes
[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:

  1. Review status board: Walk through open tasks, flag any that are behind
  2. Identify blockers: Surface any issues preventing task completion
  3. Reassign or escalate: Adjust ownership or escalate blockers to resolve quickly
  4. Update timeline: If any tasks are at risk, assess impact on overall close timeline

Close Metrics to Track Over Time

MetricDefinitionTarget
Close durationBusiness days from period end to hard closeReduce over time
# of adjusting entries after soft closeEntries posted during management reviewMinimize
# of late tasksTasks completed after their deadlineZero
# of reconciliation exceptionsReconciling items requiring investigationReduce over time
# of restatements / correctionsErrors found after closeZero

Common Close Activities by Day

Typical 5-Day Close Calendar

DayKey ActivitiesResponsible
T+1Cash entries, payroll, AP accruals, depreciation, prepaid amortization, intercompany postingStaff accountants, payroll
T+2Revenue recognition, remaining accruals, subledger reconciliations (AR, AP, FA), FX revaluationRevenue accountant, AP/AR, treasury
T+3Balance sheet reconciliations, intercompany reconciliation, eliminations, preliminary trial balance, preliminary fluxAccounting team, consolidation
T+4Tax provision, equity roll-forward, draft financial statements, detailed flux analysis, management reviewTax, controller, FP&A
T+5Final adjustments, hard close, period lock, reporting package distribution, forecast update, retrospectiveController, FP&A, finance leadership

Accelerated Close (3-Day Target)

For organizations targeting a faster close:

DayKey Activities
T+1All JEs posted (automated + manual), all subledger reconciliations, bank reconciliation, intercompany reconciliation, preliminary trial balance
T+2All balance sheet reconciliations, tax provision, consolidation, draft financial statements, flux analysis, management review
T+3Final 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

BottleneckRoot CauseSolution
Late AP accrualsWaiting for department spend confirmationImplement continuous accrual estimation; set cut-off deadlines
Manual journal entriesRecurring entries prepared manually each monthAutomate standard recurring entries in the ERP
Slow reconciliationsStarting from scratch each monthImplement continuous/rolling reconciliation
Intercompany delaysWaiting for counterparty confirmationAutomate intercompany matching; set stricter deadlines
Management review changesLarge adjustments found during reviewImprove preliminary review process; empower team to catch issues earlier
Missing supporting documentsScrambling for documentation at closeMaintain documentation throughout the month

Close Retrospective Questions

After each close, ask:

  1. What went well this close that we should continue?
  2. What took longer than expected and why?
  3. What blockers did we encounter and how can we prevent them?
  4. Were there any surprises in the financial results we should have caught earlier?
  5. What can we automate or streamline for next month?

anthropic의 다른 스킬

analyzing-financial-statements
anthropic
이 스킬은 재무제표 데이터로부터 투자 분석을 위한 주요 재무 비율과 지표를 계산합니다.
applying-brand-guidelines
anthropic
이 스킬은 생성된 모든 문서에 일관된 기업 브랜딩과 스타일(색상, 글꼴, 레이아웃, 메시징 포함)을 적용합니다.
creating-financial-models
anthropic
이 스킬은 DCF 분석, 민감도 테스트, 몬테카를로 시뮬레이션, 시나리오 플래닝을 포함한 고급 재무 모델링 제품군을 투자…에 제공합니다.
board-minutes
anthropic
이사회 또는 위원회 회의록을 사내 형식으로 작성합니다. 캘린더에서 예정된 이사회 및 위원회 회의를 자동으로 감지하고, 안건을 요청한 후…
crm-cleanup
anthropic
HubSpot에서 오래된 거래, 중복 연락처, 누락된 필드를 스캔한 후 소유자가 승인한 항목을 수정합니다. 선택적 범위 인수를 받아 거래, 연락처 등을 지정할 수 있습니다.
redshift-api
anthropic
Amazon Redshift에 대해 SQL 실행 — 명령문 제출, 상태 폴링, 결과 페이지 탐색, 데이터베이스/스키마/테이블 탐색. 사용자가 원할 때마다 이 기능을 사용하세요…
ticket-deflector
anthropic
고객이 전달한 이메일이나 티켓을 읽고, PayPal에서 주문/환불 상태를 가져오며, HubSpot에서 계정 내역을 조회한 후, 소유자의 어조에 맞춰 답변을 작성합니다.
reg-feed-watcher
anthropic
규제 피드를 지금 확인하고, 마지막 확인 이후 새로 추가된 내용을 사용자의 중요도 기준에 따라 필터링하여 보고합니다. 사용자가 "피드 확인해 줘"라고 말할 때 사용하세요.