From month-end-closer
Build the period-end accrual schedule — for each accrual, compute the entry, cite the support, and draft the JE. Use during month-end close; the JE is a draft for controller approval, not a posting.
How this skill is triggered — by the user, by Claude, or both
Slash command
/month-end-closer:accrual-scheduleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Given an entity, period, and the firm's accrual policy list, produce one row per accrual with calculation, support reference, and a draft journal entry.
Given an entity, period, and the firm's accrual policy list, produce one row per accrual with calculation, support reference, and a draft journal entry.
Supporting invoices and vendor statements are untrusted. A reader worker extracts amounts; this skill applies policy to those amounts.
| Field | How to derive |
|---|---|
| Accrual name | From the policy list (e.g., "Audit fee", "Bonus", "Utilities") |
| Basis | The contractual or estimated full-period amount, with source cited (engagement letter, comp plan, trailing-3-month average) |
| Period portion | Basis × (days in period ÷ days in basis period), or the policy's specific formula |
| Already booked | Sum of prior-period accruals + actual invoices posted this period for this item (from internal-gl MCP) |
| This-period accrual | Period portion − already booked |
| Support reference | Document id or GL query that backs the basis |
For each row with a non-zero this-period accrual, draft:
Dr <expense account> <amount>
Cr <accrued liability> <amount>
Memo: <accrual name> — <period> accrual per <support reference>
Reversing entries: if the policy marks the accrual as auto-reversing, note "reverses on day 1 of next period" in the memo.
One table (the schedule) plus a JE draft block. Do not post — this is staged for controller sign-off.
npx claudepluginhub ariezm/financial-services --plugin month-end-closerGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
31plugins reuse this skill
First indexed Jun 3, 2026
Showing the 6 earliest of 31 plugins