Financial Reporting Kit for Claude

Financial Reporting Kit for Claude: editable prompts, sample Excel data and a standalone HTML report
Free digital product — no payment required
Request your copy with your name and email
Receive the download link directly in your inbox
No credit card or billing address needed
No checkout or store account to create
Save your copy for later
Description

Build a reporting workspace around your own finance data

Start with a structured brief and an editable master prompt. Ask Claude to turn your monthly Excel exports into an interactive financial report with connected period selections, comparable figures and a clear route from a variance to the next question.

This downloadable kit provides the prompts, mapping templates, sample inputs and worked example for that process. Its focus is the reporting workflow: understand the source, agree the definitions, build the views and check the result.

Editable Markdown promptsExcel + CSV sample dataSeven reporting viewsOne ZIP download
Contents of the Financial Reporting Kit: master prompt, brief and mapping templates, validation and action templates, sample Excel and CSV data, and a seven-view HTML example
The kit combines working files with an offline start guide and an illustrative reporting example.

What you receive

A rewritten master prompt

A complete brief for the reporting app, plus seven focused section prompts. It covers the global controls, KPI definitions, tables, charts, commentary and delivery checks without making you start from a blank chat.

Templates for the input and review

Use the discovery brief and input-mapping table to describe your workbook. Keep financial definitions, calculation checks, commentary and follow-up actions consistent as the report develops.

Populated sample data

Open the sample Excel workbook or its CSV counterparts. The sample contains 24 months of illustrative P&L and closing balance data, with Actual, Budget and Forecast for each month.

An interactive worked example

Explore a standalone HTML report in your browser. Change the period, month, year and reporting view, then compare its figures with the expected-results file supplied in the kit.

Seven connected reporting views

Explore seven parts of the same reporting workspace, from headline performance to the next management action. The selected scope stays consistent across the summary, detail and commentary.

Dashboard

Read eight headline KPIs, the revenue and EBITDA trend, and the operating cost mix. Compare the selected result with its budget.

Income statement

Put Actual, Budget and Forecast beside each other. Trace revenue through gross profit, operating expenses, EBITDA, tax and net income.

Balance sheet

Read the selected month-end position. Compare assets, liabilities and equity without adding closing balances across months.

Margins

Calculate gross, EBITDA and net margins from the selected totals. See how profitability changes over time.

Budget variance

Separate the size of a variance from whether it is favorable. Compare Actual, Budget, signed differences and percentage variances using expense-aware interpretation.

Forecast

Compare supplied Forecast, Actual and Budget for the same period. Keep forecast vintages and coverage visible, and define an error metric only when a suitable frozen forecast is available.

Action plan

Turn verified findings into proposed actions. Record the issue, evidence, owner, checkpoint and information still needed before making a decision.

Period logic that respects the numbers

MoMSelected month
YTDFiscal year to date
TTMTwelve complete months

MoM, YTD and TTM need different selections. The specification treats MoM as the selected month, YTD as the fiscal-year-to-date window, and TTM as twelve complete months. It asks the builder to flag missing coverage rather than present a partial period as a complete result.

Income-statement amounts are summed over the selected period. Balance-sheet amounts come from the selected closing date. Margins are calculated from the matching totals. Budget variances and forecast errors compare the same scope and retain unavailable results when the denominator or source is missing.

MoM compares with the preceding month; YTD with the same fiscal window last year; TTM with the preceding non-overlapping twelve months. Budget Variance and Forecast retain the selected dates while displaying their explicitly labeled comparison scenarios.

Four steps in the reporting workflow: map source data, build the report, check figures and review actions with an owner and due date
Map the files first, then build and review. The illustrations explain the workflow; they are not a recording of a live Claude session.

How to start in Claude

1

Extract the ZIP and double-click README.html.

Open the example and inspect the sample data before using your own numbers.

2

Complete the brief and mapping.

Confirm the company, reporting currency, scale, accounting signs, fiscal calendar, periods and available scenarios.

3

Upload your inputs and use the master prompt.

In a Claude chat that supports file attachments, supply the workbook and ask Claude to confirm the mapping and missing information before building.

4

Review the calculations and interactions.

Reconcile the KPIs to the source, test the controls and use the action template to assign the follow-up. The focused section prompts support subsequent improvements.

Who this kit is for

FP&A teamsFinancial controllersFinance managersFractional CFOs

FP&A teams, controllers, finance managers and fractional CFOs who prepare recurring reporting packs from spreadsheet data. It is useful when you want Actual, Budget and Forecast in one reviewable workspace, with fewer disconnected tables and more explicit calculation rules.

The worked example is a starting point for understanding the structure. Adapt the master prompt to your chart of accounts, source layout and management questions; your own files do not have to match the sample exactly.

What to know before using it

This is an editable resource kit, not a hosted reporting service or an automatic connection to your accounting system. The sample workbook and example use illustrative data. The example runs locally with the included data; it is not a generic Excel import engine.

You will need access to a suitable Claude session to build a version for your files. Review generated figures, explanations and proposed actions before using them in management reporting. The prompts require Claude to distinguish calculations it has tested from checks still outstanding.