Set up
Try a plugin
The Finance plugin ships with /variance-analysis and other finance skills as a starting point. /variance-analysis already knows how to compare periods and structure commentary. If your admin manages plugins and it's not available yet, skip this step. The prompt below works without it.
/variance-analysisDecompose financial variances into drivers with narrative explanations and waterfall analysis./financial-statementsGenerate financial statements (income statement, balance sheet, cash flow) with period-over-period comparison and variance analysis.Connect your tools
Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access(opens in new tab).
Add a connector(opens in new tab) for each tool you want Claude to use.
Set your working folder
Drag the files you'll use (actuals, prior period, budget, chart of accounts) into one folder on your machine, then give Claude access to it(opens in new tab) in the Claude desktop app. Claude reads from the folder and writes the narrative back to it. If you'll run this every close, create a project(opens in new tab) from that folder so instructions, memory, and scheduled runs stay attached to it.
The prompt
Copy this into Claude
Draft this month's variance commentary for the monthly review. Compare actuals to last month and to budget, and for every line that moved more than 10% or $50K explain what moved and why, in plain English for a leadership audience. Write it to the close folder.
Why this works
Set the threshold. "10% or $50K" is your materiality line, so the narrative covers what matters and skips the rest.
Name the audience. "For leadership" tells Claude who's reading, so the same numbers are written with less line-level detail and more interpretation than the audit version would.
Say where the output goes. Name a specific file and Claude edits it; otherwise it creates the draft in your working folder for you to audit.
Get a better draft
Add an example to match. Drop last quarter's commentary in the folder and Claude matches your structure and voice.
Ask it to flag uncertainty. Add "flag any line where the driver isn't clear from the data" so you know exactly where to dig before the review.
Make Claude work for you
Tell Claude your own rules for this task, such as your materiality threshold and your commentary format, then save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.
Make what we've done in this task so far into a skill called /variance-narrative.
Review the skill, and save it if Claude hasn't already.
Make it repeatable
Share it as an artifact
A document is a snapshot. Ask Claude to publish the same view as an artifact that reads the actuals through a connector, and it becomes a link the CFO can open any time to see the latest numbers. Everyone who opens it connects their own account.
Publish that variance analysis as an artifact for leadership. Have it read the actuals through a connector so it shows the latest numbers each time it opens.
Run it on a schedule
Variance commentary is due every close. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and /variance-narrative runs against the latest actuals automatically.
Set up a scheduled task for every Monday at 9am: if a new actuals file is in FY26-Close, run /variance-narrative against it and write the draft to that folder.
Runs /variance-narrative against the latest actuals in FY26-Close and writes the draft commentary to the same folder.
To use a folder on your computer during a scheduled task, keep your computer on and awake with the Claude desktop app open so Claude can access it.
Share with your teammates
Your /variance-narrative skill now carries your team's standards. Share it so everyone on the close runs the same version, same threshold, same format, same voice.