close-management-pre-close-last-2-3-business-days-of-the-month
Sub-skill of close-management: Pre-Close (Last 2-3 Business Days of the Month) (+5).
Best use case
close-management-pre-close-last-2-3-business-days-of-the-month is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of close-management: Pre-Close (Last 2-3 Business Days of the Month) (+5).
Teams using close-management-pre-close-last-2-3-business-days-of-the-month should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/pre-close-last-2-3-business-days-of-the-month/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How close-management-pre-close-last-2-3-business-days-of-the-month Compares
| Feature / Agent | close-management-pre-close-last-2-3-business-days-of-the-month | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of close-management: Pre-Close (Last 2-3 Business Days of the Month) (+5).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Pre-Close (Last 2-3 Business Days of the Month) (+5) ## 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
Related Skills
flywheel-closeout
Use this at the end of substantial repo or agent waves to convert evidence-backed lessons into proposed durable assets: skills, scripts, rules/checks, prompt templates, docs, or issues. Always use it when the user mentions flywheel, wave closeout, repo ecosystem learning, durable asset promotion, or learning-to-tools.
overnight-verify-close-and-blocker-conversion
Use overnight Codex lanes to clear stale-open GitHub issues by verification-first closure, and convert blocked PR-repair attempts into dedicated blocker issues instead of speculative edits.
orcawave-orcaflex-semantic-proof-wave-closeout
Close out an OrcaWave/OrcaFlex semantic-proof wave after a PR merges, split unrelated CI blockers, and seed the next semantic-proof issue wave without duplicating existing issues.
overnight-verify-close-batch
Build overnight parallel batches that close stale-open GitHub issues by proving landed work already satisfies the issue, instead of wasting implementation lanes on redoing completed work.
cron-job-management
Patterns for creating, testing, debugging, and maintaining cron-driven automation in workspace-hub, including log strategy, failure analysis, and safe git-aware job design.
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
github-issue-closeout-race-safe
Close GitHub issues without losing the evidence comment when multiple agents or races may close the issue concurrently.
doc-audit-and-close-workflow
A repeatable workflow for executing a batch of documentation, audit, or planning tasks. For each task, it audits the current state, creates a plan/report, commits the result, and closes the corresponding GitHub issue. The process is designed to be idempotent.
data-management
Comprehensive DataFrame loading, filtering, transformation, and data pipeline management from Excel, CSV, and multiple sources with YAML-driven configuration.
closed-issue-plan-refile-loop
Reopen and re-drive a previously closed GitHub plan issue after review/governance blockers are fixed, without prematurely restoring approval state.
taxact-business-c-corp-filing-packet
Assemble and execute a packet-first TaxAct Business filing workflow for C-Corp Form 1120 returns using existing repo artifacts, with strict pre-submit gates and human approval.
task-management
Simple task management using a shared TASKS.md file for tracking commitments and action items.