Monthly management report skill - Control Documentation

Use this sample when a finance team prepares the same monthly update repeatedly. It can produce report copy, a presentation outline, or content for an editable slide deck.

Copy this skill

---
name: monthly-management-report
description: Create a verified monthly management report after Control confirms that accounting data is ready.
---

# Monthly management report

1. Confirm the tenant, group scope, calendar month, audience, output format, reporting currency, layout, comparison basis, and materiality thresholds. This skill supports group reports only; reroute entity-specific requests to an entity-reporting workflow before fetching data.
2. Call `get_monthly_close_readiness` for the confirmed group and period before fetching report data.
3. Continue only when the status is exactly `Ready` and there are no blockers. Otherwise stop and report the blocker codes and messages.
4. Fetch the configured monthly and YTD sections with `get_group_statement_actuals`.
5. When requested, fetch the selected plan with `get_budget_plan_values` and consolidated cash flow with `get_group_cash_flow_monthly`.
6. Reconcile periods, layout rows, entity scope, and currency before calculating comparisons.
7. Rank material movements. Separate transaction-backed operating rows from formulas, eliminations, and currency-translation rows, using `search_statement_layout_tree` when their composition is unclear.
8. Use `get_group_transactions_browse` only for the configured maximum number of transaction-backed variances.
9. Build links back to the matching Control views when link tools are available.
10. Create a concise report or editable presentation brief. Reconcile every displayed number to the tool results.

## Rules

- Never infer that a month is closed from statement values or prose.
- Never answer an entity-specific request with group-level results.
- Separate reported facts, derived calculations, and interpretation.
- Do not invent a cause when transaction evidence does not establish one; write `requires review`.
- Do not use an empty transaction result to explain a formula, elimination, or currency-translation movement.
- Treat missing budget, comparison, entity, or currency coverage as a caveat, not zero.
- Do not add decorative precision: use the customer's reviewed rounding and materiality rules.
- A generated deck is an editable communication artifact, not the source of truth.
- Do not send or publish the report unless the user separately asks for delivery and the destination workflow prevents duplicates.

## Output

Return an executive summary, KPI table, material variances, cash and balance-sheet highlights, risks and follow-ups, data caveats, and Control links. For a presentation, add one clear takeaway per slide and speaker notes containing the supporting evidence.

Try it

Create the June 2026 management report as an editable PowerPoint outline. Compare with May, budget, and June 2025.

Draft a five-slide board update for Q2 2026 and include only movements above €50,000.

Check whether last month is ready. If it is, prepare a concise finance-team report; if it is not, return only the blockers.

A more prescriptive internal skill may also claim and record a report run before Slack or email delivery. Keep provider credentials and destination identifiers outside the shared skill.

⌘I