alirezarezvani/claude-skills / finance/month-end-close/skills/month-end-close
month-end-close
VerifiedUse when running, planning or speeding up a month-end (or quarter-end) close โ building or reviewing the close checklist and calendar, reconciling a bank statement or sub-ledger to the general ledger, writing or reviewing flux (variance) explanations, or finding why the close takes too many days. Orders close tasks by dependency and finds the critical path, proves each reconciliation and ages what is left, and refuses to sign off material fluctuations explained with boilerplate.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.5 KB |
| assets/bank_statement.example.csv | other | 213 B |
| assets/close_plan.example.json | config | 2.0 KB |
| assets/flux_input.example.csv | other | 654 B |
| assets/gl_cash.example.csv | other | 308 B |
| assets/reconciliation_signoff.md | markdown | 1.2 KB |
| references/close_calendar_and_benchmarks.md | markdown | 4.3 KB |
| references/flux_analysis_and_materiality.md | markdown | 4.0 KB |
| references/reconciliation_standards.md | markdown | 4.2 KB |
| scripts/close_calendar_planner.py | script | 11.0 KB |
| scripts/flux_analyzer.py | script | 9.0 KB |
| scripts/reconciliation_matcher.py | script | 16.6 KB |
references/close_calendar_and_benchmarks.md
View on GitHub# Close calendar and benchmarks
How to order a close, why the critical path is the only place to save days,
and what the published days-to-close numbers do and do not say.
Confidence key: ๐ข read in the primary source ยท ๐ก secondary or vendor source ยท ๐ด convention or recommendation.
## 1. The close is a dependency graph
A typical group close, as one ERP vendor describes it: ๐ก [Workday]
1. Entity close: sub-ledger cut-off, journal entries, reconciliations, adjustments
2. Trial balance submitted and validated; local charts mapped to the group chart
3. Intercompany matching and elimination
4. Foreign-currency translation
5. Group top-side adjustments, after subsidiary data is consolidated and reconciled
6. Consolidation and review
7. Reporting and filing
Two orderings are stated outright: intercompany before consolidation, and
mapping before eliminations. No auditing body publishes a canonical task
sequence; the order "sub-ledgers โ accruals โ intercompany โ reconciliations โ
consolidation โ flux โ reporting" is industry convention. ๐ด
Write your checklist as a graph (`depends_on` in the plan JSON), not a list.
`close_calendar_planner.py` refuses a cycle and an unknown dependency, because
both mean the checklist is wrong, not the calendar.
## 2. Critical path
Forward pass: each task starts when its last predecessor finishes. Backward
pass from the last finish: latest start without delaying the close. Slack =
latest start - earliest start. Tasks with zero slack form the critical path.
๐ด standard project-scheduling method (CPM)
Consequences that change behaviour:
- Automating an off-critical task (e.g. depreciation with two days of slack)
does not move the close date at all.
- Splitting a long critical task between two people, or starting it earlier
with a soft cut-off, does.
- A person who owns more than half the critical path is the close date. The
planner warns on that (C6) and on any day one person is booked above one day of work (C4).
## 3. Workday deadlines
Deadlines are written as WD+n: WD1 is the first business day after period
end. The planner skips weekends and listed holidays when it maps workdays to
dates. COSO 2013 Principle 12 lists "performs in a timely manner" and
"establishes responsibility and accountability" among the points of focus for
deploying control activities, which is what a deadline and a named owner per
task make checkable. ๐ข [COSO P12]
## 4. Days-to-close benchmarks, with caveats
- APQC's Open Standards Benchmarking measure is cycle time "from running the
trial balance to completing consolidated financial statements". Figures
widely quoted from it: top performers about 4.8 calendar days, median about
6.4, bottom performers 10 or more. ๐ก โ the APQC article is members-only, and
these numbers come from vendors quoting APQC data from around 2017. [numeric, APQC]
- APQC's own annual-close article: top performers 10 days or less, median 18,
slower performers 35. ๐ข [APQC annual]
Use benchmarks to start a conversation, not to set a target. A five-day close
with plugged reconciliations is worse than an eight-day close that proves. ๐ด
## 5. Auditor's view of the close
PCAOB AS 2201 requires the auditor to evaluate the period-end financial
reporting process, including how totals are entered into the general ledger
and how recurring and non-recurring adjustments are recorded. ๐ข [AS 2201 ยถ.26]
The close calendar, owner list and review evidence are what an auditor walks
through, so the plan JSON doubles as audit documentation. ๐ด
## Sources
1. Workday. *Financial consolidation and close process guide.* https://blog.workday.com/en-gb/financial-consolidation-close-process-guide.html (vendor)
2. APQC. *Cycle Time to Perform the Monthly Close* (members-only). https://www.apqc.org/knowledge-base/documents/cycle-time-perform-monthly-close
3. Numeric. *How long does month-end close take?* (vendor, quoting APQC). https://www.numeric.io/blog/how-long-does-month-end-close-take
4. APQC. *How to streamline the annual closing process.* https://www.apqc.org/resources/blog/how-streamline-annual-closing-process-and-speed-year-end-close
5. COSO (2013). *Internal Control โ Integrated Framework*, Principle 12, via AAA. https://aaahq.org/node/35157
6. PCAOB. *AS 2201: An Audit of Internal Control Over Financial Reporting.* https://pcaobus.org/oversight/standards/auditing-standards/details/AS2201
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page โ title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "ไผ่ฎฎ็บช่ฆ". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |