Role, Finance

Claude for
finance work

The parts of the month that eat hours, translated into things Claude can do in minutes. Commentary, reformatting, board narrative, and a few habits that keep it safe around real numbers.

Finance work is one of the best fits for Claude I've seen. A huge share of the week is writing words around numbers you already trust, which is exactly what it's good at. The trick is knowing where to let it help and where to keep it out. This page is both halves of that.

Three places to start

Three workflows where the return on a well-written prompt is highest. None of them replace your judgement on the numbers. All of them save meaningful time on the writing around them.

1. Variance commentary

The monthly ritual of writing the story above the variance table is maybe the single highest-leverage use of Claude in finance. Give it the table, give it last month's commentary as a voice reference, tell it which drivers are real, and let it draft. You spend the saved time actually thinking about what the numbers mean, which is the bit that matters anyway.

Variance commentary prompt, annotated

The four elements of a good prompt, applied to the monthly ritual.

YouI need to write variance commentary for this month's management accounts, UK trading entity. 1 Here is the variance table, pasted below. Here is last month's commentary as a voice reference, pasted below. 2 Write this month's commentary in the same voice. Lead with the two or three variances that most need explaining. Keep it under 250 words. 3 Only reference drivers I have already told you about. If a line's driver is unclear to you, flag it rather than guessing at a plausible one. 4
1
Context. Which period, which entity, which document. Without this Claude writes generic corporate prose.
2
Example. Last month's commentary is the voice reference. Saves you writing a tone guide from scratch.
3
The ask. Lead order and a length cap, so the output is usable rather than thorough-but-unreadable.
4
Escape hatch. The anti-hallucination line. Without it you get confident-sounding invented drivers.

Where this falls over

It will try to invent drivers for variances you haven't explained. The fix is to be explicit in your prompt that it should only reference drivers you've given it, and to flag any line where it had to guess.

2. Reformatting exports between systems

Every finance team has at least one job that involves taking an export from system A and putting it into the format system B needs. It's boring, error-prone, and the perfect before-and-after task for Claude. Paste the raw, paste the target format, ask it to do the first three rows so you can check, then let it do the rest.

Two versions of the same reformatting ask

Click between the tabs. Notice how the strong version earns a sanity-check step.

Youreformat this export for the target system
What Claude sends back

A best-guess reformat that drops one column you needed, invents a date format you do not use, and converts every currency to USD without asking. You rewrite the whole thing by hand anyway.

YouHere is a raw export from [SOURCE SYSTEM], pasted below. Here is the format [TARGET SYSTEM] expects, pasted below. Six columns: entity, account, period, amount_gbp, dr_cr, memo. Convert the first into the second. Show me the first three rows so I can sanity-check before you do the rest. If any row is missing a field or has an ambiguous value, flag it rather than inventing a default.
What Claude sends back

Here are the first three rows. Confirm these look right and I will do the remaining 247.

entity account period amount_gbp dr_cr memo UK01 4100 2026-03 12500.00 DR March consulting fees UK01 6210 2026-03 3200.00 CR Q1 adjustment UK02 4100 2026-03 ? DR March, amount missing
One thing to flag: row 3 has no amount in the source. I've left it as "?" rather than guessing. Tell me what to do and I'll apply the same rule to any other rows with missing amounts.

Where this falls over

If the source data has missing or ambiguous fields, Claude will sometimes fill them in with plausible defaults. Add "flag missing fields rather than inventing values" to your prompt and that problem goes away.

3. Drafting the narrative pages of a board pack

The numerical pages are yours. The narrative pages around them (exec summary, key highlights, outlook, risks) are where Claude can take a real first pass. Give it the finished numbers and your last three board packs as voice references, and it will produce something you can edit down rather than write from scratch.

BT
Ben T. #finance Yesterday, 18:12

Stole this from the Intermediate handbook. Fed Claude the finished numeric pages of next week's board pack plus our last three packs as voice reference. Asked it to draft the exec summary, key highlights, and outlook sections.

Not the final version, but about 80% of the way there. Spending the saved hour writing the actual commentary on the two numbers the board will care about, which is the bit I should have been spending the time on all along.

8 party 4 heart

Where this falls over

The output will be too long and slightly too polished on the first pass. Budget ten minutes for a ruthless trim, and always check any specific claim it makes against the numbers.

Worked examples

Before and after, on tasks from finance work.

Prompts to steal

Copy any of these, fill in the square brackets, run.

Try this week

Pick one. All of these are under an hour.

The one rule I'd push on finance specifically: never paste anything into Claude you wouldn't paste into an email to a non-finance colleague. Client identifiers, specific numbers tied to named entities, anything sensitive, use judgement. Everything else is fair game.

If you want to go broader, the Beginner guide covers the habits that apply everywhere. The prompt library has the full set of role-tagged prompts in one place.