finance-close-checklist
Skill4 starsChanged 7 months agoMITView on GitHub
Use when running or preparing a month-end close checklist, tracking owners, blockers, reconciliations, accruals, revenue, AR, AP, payroll, and reporting readiness.
In this repository8 other files it gives its agents.
- ar-collectionsSkill
- cfo-briefingSkill
- contract-to-invoiceSkill
- dunning-emailsSkill
- invoice-health-checkSkill
- payment-reconciliationSkill
- revenue-recognition-qaSkill
- usage-billing-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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
- Distinctive: line 8
Use this skill to turn a close calendar and supporting data into a practical close status report.
- Distinctive: line 36
Do not mark an area complete without evidence.
- Distinctive: line 37
Do not hide immaterial cleanup if it affects reporting deadlines or audit trail.
- Distinctive: line 39
Keep close updates factual and action-oriented.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Finance Close Checklist
Use this skill to turn a close calendar and supporting data into a practical close status report.
Inputs
- Close checklist with tasks, owners, due dates, dependencies, and status.
- Trial balance, subledger reports, bank reconciliations, AR/AP aging, payroll, revenue schedules, accruals, and variance analysis.
- Materiality threshold and reporting deadline.
Workflow
- Group tasks by close area: cash, AR, revenue, AP, expenses, payroll, accruals, fixed assets, tax, intercompany, reporting, and review.
- Identify blocked, late, missing-evidence, and high-risk tasks.
- Tie blockers to owners, dependencies, and decisions needed.
- Highlight financial statement risk separately from operational cleanup.
- Build a concise next-action plan for the remaining close window.
Output
Return:
- Close status: on track, at risk, blocked, or ready for review.
- Area-by-area checklist with owner, due date, status, blocker, and next action.
- Material unresolved items.
- Questions and approvals needed.
- Draft controller/CFO update when requested.
Guardrails
- Do not mark an area complete without evidence.
- Do not hide immaterial cleanup if it affects reporting deadlines or audit trail.
- Separate "needs review" from "done."
- Keep close updates factual and action-oriented.
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
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.