financial-statements

Financial Reporting

Important: This skill guides financial-reporting workflows but does not provide financial advice. All statements, memos, and disclosures should be reviewed by qualified financial professionals before use in reporting or filings.

This is the general guideline for financial reporting — financial statements, reporting packages, footnotes and disclosures, technical accounting memos and position papers, management commentary, and financial-review / board / investment-committee decks. Match the guidance to the deliverable you must produce:

• Statements & reporting packages — the workflow below (income statement, trial-balance workbook, monthly summary, balance sheet, cash flow, GAAP presentation ASC 220/210/230, period-end adjustments) with period-over-period comparison and variance.
• Technical accounting memos / position papers / reference guides (impairment, capitalization, revenue recognition, lease/debt) — write the actual technical analysis, scaffolded: (1) entity/business background — nature of operations, offerings, customers, primary expense categories; (2) the governing ASC cited at subsection level, with every criterion, scope exception, and definitional component of the cited subsections enumerated and individually assessed — a correct gist that omits a listed exception or half of a two-part definition is incomplete; (3) the comparison the standard's chosen path requires — and only that path: a qualitative (step-0) assessment provides a substantive section for each qualitative factor — relevant macroeconomic conditions, industry and market considerations, cost factors, financial performance, entity-specific events — writing the actual conditions that apply (with figures and named developments) and tying each to management's specific facts, then concludes there; related-standard context that frames the analysis (e.g., ASC 730 R&D classification for pre-feasibility costs, feasibility elements under ASC 985) is part of the required substance, not padding, without proceeding to an unrequested quantitative test and without importing public-market indicators for a private reporting unit unless their relevance is explained; when the quantitative path applies, show it (e.g., fair value vs. carrying amount for impairment) with actual and forecast data; (4) for segment/CODM analyses, the CODM's title and review/allocation frequency. These are graded on substance, not brevity — a terse "no adverse change" conclusion fails.
• Slide decks (financial-review, board, investment-committee) — build the reporting content here, then use financial-presentations for deck structure, slide principles, and chart selection.

Clarify like the professional in the room: resolve a genuinely fatal ambiguity (two entities share the requested name; the reporting period is unstated) explicitly before building — but ask only what the requester's role can answer, never re-ask facts the conversation already gave, and list each recurring action once under its correct cadence (an item is monthly or annual, never duplicated as both).

Read Financial Reporting Standards before you build — the build contract these deliverables are graded on, applied as checks on your own work rather than a template: enumerate every named artifact as a grid before building, link derived figures with live formulas, apply only the reporting conventions that fit the requested shape, and work through its verification checklist before returning any workbook.

Whatever the deliverable: before handing over, re-open the delivered file and confirm every explicitly requested file, tab, section, and figure exists under its requested name and is internally consistent.