Period-End Accrual Scheduler
Calculate period-end accruals and prepare controller-ready journal entry drafts.
The skill treats invoices and vendor statements as untrusted, requires support references, and explicitly limits output to draft journal entries with no posting, reducing external-effect risk. Deductions apply because least-privilege access, data flow, sensitive-data handling, user confirmation, rollback, and failure behavior for the internal-gl MCP are unspecified.
The workflow, formulas, JE format, and auto-reversal note are internally coherent. Deductions apply because missing or conflicting policies, date boundaries, negative amounts, duplicate invoices, MCP outages, and abnormal inputs lack handling or diagnosable feedback; static evidence cannot support a score above 10.
The audience and scenario are reasonably clear: period-end close using an entity, period, and accrual-policy list to produce a schedule and draft JEs, with posting explicitly out of scope. Deductions apply because trigger precision, non-fit boundaries, account mapping, policy schema, Chinese-language support, and MCP reachability are not sufficiently documented.
The skill has a concise structure with defined fields, formulas, output format, and repository-level Apache-2.0 licensing; the repository also documents validation and maintenance workflows. Deductions apply because the skill lacks its own version, changelog, named maintainer, installation/dependency notes, examples, FAQ, and known-limitations section.
The source directly specifies a schedule with calculations, support citations, and controller-review JE drafts, giving the core output direct practical value. Deductions apply because it depends on an internal GL query and reader worker, with no evidence of complete account mapping or correct handling of complex policies, period boundaries, and exceptions; substantial human review remains necessary.
Inputs, calculation relationships, support references, and JE formatting are auditable from the source, and the repository includes general plugin-validation and secret-scanning workflows. Deductions apply because there is no skill-specific test suite, sample output, or third-party execution evidence, so key paths cannot be independently reproduced; static evidence caps this at 5.
- Draft-only output does not establish accounting correctness; a controller must verify policy, period-day counts, booked amounts, accounts, and support.
- The skill does not define the internal-gl MCP or reader-worker permissions, data residency, or failure behavior.
- Manually confirm missing policies, duplicate or conflicting invoices, negative accruals, cross-period items, and non-standard formulas.
What it does & when to use it
This skill supports month-end close workflows for fund administration and finance operations. Given an entity, period, and firm accrual policy list, it calculates the required accrual for each policy item and records the basis and supporting reference. It also drafts journal entries for non-zero amounts. The entries remain staged for controller approval and are not posted.
Reads the entity, accounting period, and accrual policy list; determines each accrual basis from a contractual or estimated full-period amount and its source; calculates the period portion using a day-count ratio or the policy's formula; uses the internal-gl MCP to sum prior-period accruals and actual invoices posted in the current period; calculates the current-period accrual; produces a schedule with the accrual name, basis, period portion, amount already booked, current-period accrual, and support reference; and drafts debit-expense/credit-accrued-liability entries for non-zero items, including a next-period reversal note when required by policy.
- A fund administration accountant prepares the month-end schedule for audit fees, bonuses, utilities, and other policy-listed accruals.
- A controller reviews the calculation basis, support references, and proposed entries before sign-off.
- A general ledger team combines prior accruals with current-period invoices to determine the amount to accrue or release.
- A finance operations team needs a single period-end worksheet linking each accrual calculation to its supporting evidence.
Pros & cons
- Defines a consistent row structure for calculations, support, and draft entries.
- Includes prior accruals and current-period invoices in the current-period calculation.
- Explicitly keeps journal entries in draft status for controller sign-off.
- Supports policy-driven first-day-of-next-period reversals.
- Requires a firm accrual policy list and complete entity and period inputs.
- Depends on internal-gl MCP, whose setup, permissions, and coverage are not documented.
- The source provides no test suite, platform validation results, or detailed exception handling.
- Invoices and vendor statements are treated as untrusted, so extracted amounts require internal policy and ledger controls.
How to install
The skill is located at plugins/vertical-plugins/fund-admin/skills/accrual-schedule/SKILL.md. The README says to install the collection in Claude Cowork via Settings → Plugins → Add plugin, paste https://github.com/anthropics/financial-services, and select the desired vertical from the marketplace list. The source does not document a standalone installation command for this individual skill.
How to use
Provide an entity, accounting period, and the firm's accrual policy list, then request the schedule and draft entries. Example: Prepare the June 2026 period-end accrual schedule for Entity X using the firm's accrual policy list, with calculations, support references, and journal entry drafts for controller approval. The internal-gl MCP must be available for prior accruals and current-period posted invoices.