// Table of Contents
Effective prompting is the difference between Claude producing generic financial text and Claude producing production-quality outputs that your team can use with minimal editing. After 200+ finance deployments, we've refined a set of prompt templates that consistently deliver high-quality results across the most common finance workflows.
These templates follow a consistent structure: a system prompt that establishes context and style, a task specification with clear formatting requirements, and structured data input using XML tags. This pattern reliably produces outputs that match your company's voice, satisfy compliance requirements, and integrate into downstream workflows without substantial rework.
How to Use These Templates
Each template below uses placeholder text in [BRACKETS] that you should replace with your company-specific information. The most effective implementation approach is to create a Claude Project with a master system prompt for your finance function, then use the task-specific prompts below as conversation starters within that project.
Your finance system prompt should include: company name and industry, fiscal year structure, reporting currency and primary markets, key terminology and internal naming conventions, preferred writing style (formal board report vs. conversational management update), and any standing disclosure or compliance language. This context, set once in the system prompt, flows into every prompt your team runs.
Want a custom prompt library for your finance team?
Our prompt engineering service builds a complete, production-ready finance prompt library tuned to your company's specific reporting workflows and style.
Learn About Prompt Engineering →Variance Commentary Templates
Variance commentary is one of the highest-volume writing tasks in any finance function. These templates cover the most common scenarios.
Template 1: Monthly P&L Variance Commentary
<context> You are a senior finance analyst at [COMPANY NAME], a [INDUSTRY] company. Write in [formal board report / executive management pack / internal management] style. Currency: [USD/GBP/EUR]. Fiscal year ends [MONTH]. </context> <task> Write monthly P&L variance commentary for [PERIOD]. Cover: 1. Revenue — headline vs. budget and prior year, key drivers 2. Gross margin — rate and volume variances 3. Opex — material line items with explanations 4. EBITDA — net impact and outlook Length: 300-400 words. Use specific numbers. Avoid vague language. Flag 1-2 items requiring management attention. </task> <data> Revenue: Actual [X], Budget [Y], Prior Year [Z] Gross Margin %: Actual [X%], Budget [Y%], Prior Year [Z%] Opex: Actual [X], Budget [Y] EBITDA: Actual [X], Budget [Y] Key drivers (bullet points from finance team): - [Driver 1] - [Driver 2] - [Driver 3] </data>
Template 2: Departmental Budget Variance Explanation
<context> You are a finance business partner drafting a variance explanation for the [DEPARTMENT] budget owner. Tone: collaborative, constructive. Audience: [VP/Director/Head of Department] who is not a finance specialist. </context> <task> Draft a budget variance explanation for [DEPARTMENT] in [PERIOD]. Include: what drove the variance, whether it's timing vs. structural, impact on full-year forecast, and recommended actions. Length: 150-200 words. Plain English. No jargon. </task> <data> Department: [NAME] Budget: [X] Actual: [Y] Variance: [+/-Z] ([%]) Nature: [overspend/underspend] Reasons (from finance notes): - [Reason 1] - [Reason 2] Full-year impact: [Your assessment] </data>
Claude for Finance: Automating Analysis & Reporting
Includes 40+ prompt templates for finance teams, system prompt blueprints, and a complete implementation guide with ROI framework.
Download Free →Financial Analysis Prompts
These templates accelerate the analytical layer of finance work—interpreting financial statements, benchmarking against peers, and synthesising insights from multiple data sources.
Template 3: Financial Statement Analysis
<context> You are a senior financial analyst. Conduct rigorous analysis. Flag risks clearly. Do not soften negative findings. </context> <task> Analyse the financial statements below. Provide: 1. Profitability assessment (margins, trend, vs. industry benchmark) 2. Liquidity and solvency (current ratio, debt/equity, interest cover) 3. Cash conversion and working capital efficiency 4. 3 key strengths and 3 key concerns 5. Overall credit/investment assessment: [Strong/Adequate/Weak/Distressed] Use JetBrains Mono formatting for key ratios. </task> <financials> [PASTE: Income statement, balance sheet, cash flow statement] Industry benchmarks: [Gross margin X%, EBITDA Y%, D/E Z%] </financials>
Template 4: Acquisition Target Financial Review
<context> You are a corporate development analyst at [COMPANY]. We are evaluating [TARGET COMPANY] as a potential acquisition. Our strategic rationale: [BRIEF DESCRIPTION]. Our typical acquisition multiple range: [X-Yx EBITDA]. </context> <task> Draft a financial review memo for our IC (Investment Committee). Include: 1. Revenue quality and growth trajectory 2. Margin profile and expansion/compression drivers 3. Key value drivers and risks 4. Preliminary valuation range (EV/EBITDA and EV/Revenue) 5. Top 5 diligence questions for management Format as a structured memo, not bullet points. 400-500 words. </task> <data> [PASTE: Target financials, available market data, news/context] </data>
Budget Narratives and Forecasting
Budget season generates enormous document volume—departmental submissions, consolidated narratives, CFO commentary, and board budget packs. These templates handle the narrative components across the budget cycle.
Template 5: Annual Budget Narrative
<context> You are the CFO of [COMPANY] writing the FY[YEAR] budget narrative for the board of directors. Strategic context: [2-3 sentences on company strategy and key priorities for the year]. Tone: confident, data-driven, forward-looking. </context> <task> Write the executive summary section of the FY[YEAR] board budget pack. Cover: headline financial targets, key assumptions, major investments, risk scenarios (upside/downside), and capital allocation priorities. Length: 500-600 words. Board-ready language. </task> <budget_summary> Revenue: [Budget] vs [Prior Year] ([+/-%]) EBITDA: [Budget] vs [Prior Year] Capex: [Budget] Key growth drivers: [List] Key risks: [List] Macro assumptions: [GDP growth, FX, inflation] </budget_summary>
Investor Reporting Templates
These templates cover the investor-facing communications that require the most careful writing—MD&A sections, earnings commentary, and shareholder letters. Always apply CFO and legal review before any external distribution.
Template 6: Quarterly MD&A Revenue Section
<context> You are an experienced financial writer producing MD&A for [COMPANY], a [EXCHANGE: NYSE/NASDAQ/LSE]-listed [INDUSTRY] company. Follow SEC Regulation S-K plain language requirements. Match the style of the prior-period excerpt below. </context> <prior_style_example> [PASTE 1-2 paragraphs from prior MD&A revenue section] </prior_style_example> <task> Write the Revenue section of Q[N] FY[YEAR] MD&A. Include: headline revenue, YoY and sequential comparison, segment breakdown, geographic mix, key drivers, and forward outlook. Length: 250-350 words. Do not include forward-looking language beyond what management has already guided publicly. </task> <revenue_data> Total Revenue: [Q] [X] vs [Q-1] [Y] vs [Prior Year Q] [Z] Segment A: [figures and drivers] Segment B: [figures and drivers] Geographic: [breakdown] Public guidance: [Management's stated guidance range] </revenue_data>
Audit and Compliance Documentation
Finance teams supporting internal and external audit spend significant time preparing documentation, control narratives, and audit committee updates. These templates address the highest-volume documentation workflows.
Template 7: Internal Control Narrative
<context> You are a finance controller documenting internal controls for SOX/audit purposes. Write in clear, precise language that satisfies external auditor review. Process owner: [NAME/TITLE]. Control owner: [NAME/TITLE]. </context> <task> Write a control narrative for the [PROCESS NAME] process. Structure: Process Overview → Control Objectives → Key Controls (preventive and detective) → Control Testing Approach → Exception Handling. Include specific system names, approval thresholds, and frequency. Length: 300-400 words. Auditor-ready. </task> <process_notes> Process: [DESCRIPTION] Systems involved: [ERP, approval system, etc.] Key risks: [List] Existing controls: [Bullet list] Approval limits: [Thresholds] </process_notes>
For a complete library of 40+ finance prompts, download our Claude for Finance white paper. For prompt engineering training tailored to your finance function, see our prompt engineering service. Related articles: Prompt Engineering for Finance and Financial Reporting Automation with Claude.
Frequently Asked Questions
How do I customise these templates for my company?
Replace placeholder text in [BRACKETS] with your company-specific information. For best results, create a system prompt that includes your company name, industry, reporting style, fiscal year structure, and key terminology. Save this as a Claude Project so every finance team member inherits the same context without repeating it in every prompt.
Should finance teams use Claude.ai or the API?
For most finance teams, Claude Enterprise (accessible via claude.ai) is the right starting point. It offers SOC 2 compliance, data isolation, and team collaboration features without requiring API integration. The API is better suited for automated workflows that run programmatically—such as nightly variance commentary generation or automated report summarisation.
How do I ensure consistent output quality across prompts?
Consistency comes from a well-crafted system prompt and a standardised prompt structure. Use XML tags to separate sections of your prompt (context, data, task, format). This structure helps Claude parse complex financial inputs reliably and produce consistently formatted outputs.
Can I use these prompts with sensitive financial data?
Use Claude Enterprise for any prompts containing real financial data—it provides zero data retention and enterprise-grade security. For highly sensitive data, consider masking specific figures with percentage changes or indexed values, having Claude generate the narrative structure, then inserting actual numbers manually before distribution.
