accrual-schedule

name	accrual-schedule
description	Use when financial-services work requires 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..
version	0.1.0
author	Changhochien
license	MIT
platforms	["linux","macos","windows"]
metadata	{"hermes":{"tags":["financial-services","fund-admin","operations"],"related_skills":[]}}

Accrual schedule

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.

For each accrual on the policy list

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

Draft JE

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.

Output

One table (the schedule) plus a JE draft block. Do not post — this is staged for controller sign-off.

Hermes Profile Notes

This skill was packaged from pi-financial-services source path plugins/vertical-plugins/fund-admin/skills/accrual-schedule for the Hermes financial-services profile. Use institutional data connectors first when available, cite sources, and stage outputs for qualified human review.

Common Pitfalls

1. Do not present drafts as investment, legal, tax, or accounting advice.
2. Do not use web search as the primary source when an institutional MCP/data connector is available.
3. Do not execute transactions, contact clients, post to a ledger, or approve onboarding. Stage outputs for review.

Verification Checklist

• Inputs, assumptions, dates, and currencies are explicit.
• Numbers tie across tables, models, decks, and memos.
• Sources are cited and institutional data is preferred where available.
• Output is labeled draft / for human review where appropriate.