For Financial Analyst (Corporate)s ·
What you'll accomplish
By the end of this guide, you'll have Claude set up with your company's financial reporting structure so it can draft your entire monthly variance commentary in under 10 minutes — instead of the 3–5 hours it currently takes. You'll set this up once and use it every month.
What you'll need
What you should see: A clean chat window with a text box at the bottom. Troubleshooting: If you see a "Claude is at capacity" message, try again in a few minutes or sign up for Claude Pro which has priority access.
The free Claude account has message limits that can be restrictive during close week when you're running many reports. Claude Pro ($20/month) removes most limits and unlocks the Projects feature.
What you should see: Your account badge changes to "Pro."
Projects let you give Claude persistent instructions so you don't have to re-explain your company's structure every month.
What you should see: A new project page with a section for "Project instructions."
This is the key step. You're going to tell Claude everything it needs to know about your reporting structure. Click in the "Project instructions" text area and write the following, customized for your company:
You are my financial reporting assistant. You help me draft monthly variance commentary for our management P&L report.
COMPANY CONTEXT:
Company: [Your Company Name]
Reporting period: Monthly, closes on the [Xth] business day after month-end
Report audience: CFO and senior leadership team
Reporting currency: USD
BUSINESS UNITS / COST CENTERS:
[List your business units or cost centers by name, e.g.:]
- North America Commercial
- EMEA Operations
- Corporate G&A
- Technology & Infrastructure
- Research & Development
VARIANCE COMMENTARY FORMAT:
For each line item, write commentary following this exact structure:
"[Line Item] was $[amount]M, $[variance]M [favorable/unfavorable] to budget [and $[prior period variance]M [favorable/unfavorable] to prior year]. The variance was primarily driven by [key driver]. [Any context or outlook sentence if relevant.]"
Keep each comment under 50 words. Use millions with one decimal (e.g., $1.2M, not $1,200K).
For positive variances in expense lines, use "favorable." For negative variances in expense lines, use "unfavorable."
For revenue lines, favorable means above budget.
WRITING STYLE:
- Direct and factual
- No jargon or accounting language
- Do not editorialize (no "impressively" or "unfortunately")
- One sentence per driver, maximum
Click "Save" when done.
What you should see: Claude confirms the instructions are saved. From now on, every conversation in this project starts with Claude already knowing your context.
Before close week, test the setup with data you already know the answers to.
What you should see: A draft commentary for each line that roughly matches the format you specified. The drivers Claude infers may not be exactly right (it can only see what's in the numbers), but the structure should be spot-on.
Based on your test, add any corrections to the Project instructions.
Common refinements:
On your next close cycle:
Total time per month after setup: 10–15 minutes.
Standard month-end run:
Here is the [Month] P&L variance table. Draft commentary for each line per your instructions.
[Paste table]
With one-time item context:
Here is the [Month] variance table. Note: the Marketing Events variance is favorable because the annual conference was postponed from March to May (one-time timing). Draft commentary accordingly.
[Paste table]
Executive summary after commentary:
Based on the variance table we just worked through, write a 1-paragraph CFO executive summary (under 150 words) covering: overall P&L performance vs. budget, the 2-3 biggest drivers, and any forward-looking context.
Commentary review:
Review the commentary I've drafted below and suggest improvements for clarity, conciseness, or accuracy. Flag anything that sounds like accounting jargon a non-finance executive might not understand.
[Paste your draft]