agentleFS
GAJETOsoGAJETOso/financeskills/skills/close-management/SKILL.md

close-management

Skill47 starsChanged 7 months agoMITView on GitHub

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.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All recurring close tasks with owner, dependency, and duration.

    line 20
  2. Distinctive:

    No accrual completion before subledger close (double-count risk).

    line 38
  3. Distinctive:

    No reconciliation sign-off before all JEs for that account are posted.

    line 39
  4. Distinctive:

    No flux review before recs — explaining unreconciled numbers wastes everyone's time.

    line 40

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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).
  2. 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)

DayActivities
WD-2 to WD-0Pre-close: cut-off comms, recurring JE prep, prior-month rec item chase, pre-accrue knowns
WD1Subledger closes (AP, AR, payroll, FA), bank uploads, cut-off verification
WD2Accruals & prepaids (journal-entry), depreciation, inventory costing, intercompany matching
WD3Reconciliations (automated-reconciliation), suspense clearance, FX revaluation
WD4Consolidation & eliminations, tax provision, management adjustments
WD5Flux/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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.