// 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.
| name | accrual-schedule |
| description | 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. |
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.
Scan the portfolio for the highest-leverage AI opportunities and rank where to deploy operating-partner time. Ingests quarterly updates and financials across multiple portfolio companies, identifies quick wins at each, and stacks them into a single ranked action list. Use during quarterly portfolio reviews, annual planning, or when deciding which companies get AI investment first. Triggers on "AI readiness", "AI opportunity scan", "where should we deploy AI", "AI across the portfolio", "AI quick wins", or "which portcos are ready for AI".
Produce a .xlsx file on disk (headless) instead of driving a live Excel workbook — for managed-agent sessions with no open Office app.
Root-cause a reconciliation break to its source transaction or posting — follow the audit trail from the break row back to the originating entry on each side and state what differs and why. Use after gl-recon has classified a break.
Reconcile general ledger to subledger for a trade date or period — match at the position or transaction level, surface breaks, and classify each break by likely cause. Use for daily or month-end recon runs across asset classes.
Parse an investor or client onboarding packet into structured KYC fields — identity, ownership, control, source of funds, and document inventory. Use as the first step of KYC screening; output feeds the rules engine.
Apply the firm's KYC/AML rules grid to a parsed onboarding record — assign a risk rating, list every rule outcome with the rule cited, and flag what's missing or escalation-worthy. Use after kyc-doc-parse; this skill decides nothing, it scores and routes.