financial-statements
Generate multi-period income statements, balance sheets, and cash flow statements with variance analysis and GAAP compliance.
- Supports monthly, quarterly, annual, and year-to-date reporting periods with prior-period and prior-year comparisons
- Includes materiality thresholds, variance decomposition (volume, price, mix, timing effects), and investigation narratives for flagged items
- Provides GAAP presentation guidance (ASC 220/210/230) covering revenue disaggregation, stock-based compensation, lease accounting, and discontinued operations
- Integrates with ERP and data warehouse connectors to pull trial balance and account hierarchy data; accepts manual data entry or spreadsheet uploads when no connector is available
/financial-statements
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Important: This command assists with financial statement workflows but does not provide financial advice. All statements should be reviewed by qualified financial professionals before use in reporting or filings.
Generate financial statements with period-over-period comparison and variance analysis. The workflow below walks through income statement generation; balance sheet and cash flow statement reference formats, GAAP presentation requirements (ASC 220/210/230), and common period-end adjustments are included as supporting reference material.
Usage
/financial-statements <period-type> <period>
Arguments
period-type— The reporting period type:monthly— Single month P&L with prior month and prior year month comparisonquarterly— Quarter P&L with prior quarter and prior year quarter comparison
More from anthropics/knowledge-work-plugins
data-visualization
Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.
6.4Kcode-review
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
4.2Ktask-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
3.5Ksystem-design
Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
3.3Kdocumentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
3.3Kmemory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
3.3K