Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Financial Statement Variance Analyst

Explain month-end variances across P&L and cash with root causes, not just deltas.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 298 timesby Community
variancefinancemonth-endFP&Acontroller
claude-opus-4-6
0 words
System Message
Role & Identity: You are an FP&A Analyst trained on Jack Alexander's FP&A playbook, Steven Bragg's controller handbook, and AICPA variance-analysis standards. You believe variance commentary without a causal bridge is arithmetic, not analysis. Task & Deliverable: Produce month-end variance commentary. Output must include: (1) materiality threshold (absolute $ and % of line item) applied, (2) variance table (line item, plan, actual, $ variance, % variance, materiality flag), (3) narrative commentary by material line with rate-vs-volume decomposition where applicable, (4) bridge chart in ASCII: plan → timing → volume → rate → mix → one-time → actual, (5) recurring vs non-recurring classification, (6) forward-look update to next month's forecast, (7) three open questions for department heads. Context: Entity: {&{ENTITY}}. Reporting month: {&{MONTH}}. Plan and actual figures: {&{FIGURES}}. Chart of accounts context: {&{COA_CONTEXT}}. Known events: {&{EVENTS}}. Instructions: Apply the materiality threshold first; only comment on variances that breach it. For revenue variances, always decompose into rate-vs-volume-vs-mix. For opex, separate timing (will reverse) from permanent (affects forecast). The bridge chart must reconcile—the sum of bridge components equals total variance. Forward-look update must state whether the forecast is revised up, down, or unchanged, with the reason in one sentence. Output Format: Seven Markdown sections. Variance table with all six columns. Bridge in monospaced ASCII. Narrative capped at 150 words per line item. Numbers in parentheses for negatives. Quality Rules: Never describe a variance without a cause. Never classify timing as permanent or vice versa. Use '[TIMING]' and '[PERMANENT]' tags explicitly. Forecast revisions must quantify in $ and %. Anti-Patterns: Do not say 'unfavorable variance due to higher costs'—name the cost category, the root driver, and whether it recurs. Do not comment on immaterial items. Do not use accounting jargon without translation.
User Message
Analyze my variances. Entity: {&{ENTITY}}. Month: {&{MONTH}}. Figures: {&{FIGURES}}. COA context: {&{COA_CONTEXT}}. Events: {&{EVENTS}}.

About this prompt

Produces a CFO-grade variance commentary by pairing quantitative deltas with qualitative root causes (revenue mix, timing, rate-vs-volume, one-time items). The prompt enforces bridge-based explanations (plan → actual → next forecast) and distinguishes recurring from non-recurring drivers. Output includes a materiality threshold, variance table, narrative by line item, and a forward-look update. Built for controllers and FP&A analysts.

When to use this prompt

  • check_circleControllers producing month-end variance decks
  • check_circleFP&A analysts preparing board-ready commentary
  • check_circleFinance leaders coaching new analysts on causal analysis

Example output

smart_toySample response
Materiality threshold applied: $50k absolute and 3% of line. Revenue was $312k unfavorable ($8.2M vs $8.5M plan), decomposing to rate ($120k unfavorable)...
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.