The AI For Series

Claude for Excel vs Claude Code: Which to Use for Finance Work

By Chandan Gupta, CA, CIA · 2026-11-14

Anthropic offers two ways for a finance team to use Claude on spreadsheets. Claude for Excel is an add-in that opens as a panel inside Excel and works on the workbook in front of you. Claude Code is Anthropic's AI tool that works on files in a folder on your own computer, usually by writing and running scripts; it needs a paid Claude plan.

Many teams will have both. They are good at different jobs, and they handle your data differently, so it helps to have a simple rule for which one to reach for. This guide gives that rule.

Everything here about the add-in comes from Anthropic's own documentation as it stood when the book was written. Add-ins change faster than books, so check Anthropic's current page before you rely on a detail.

What the add-in is

According to Anthropic's documentation:

What each one sends

This is the part to settle with IT before anyone starts.

Per Anthropic's documentation, when you sign in with a Claude account the add-in sends your conversation to Anthropic, including the content Claude reads from your workbook and any files you attach. Chat history is also stored in your browser on your machine, and clearing it there does not delete what Anthropic has received. The documentation also notes that the add-in does not inherit custom data-retention settings an organization may have set, and that its activity is not included in Enterprise audit logs (it is covered by Anthropic's Compliance API for Enterprise organizations that use it).

Claude Code works differently when you use it with the local-script pattern. You ask it to look at the headers and a few rows, write a script, and run that script on your laptop. The model mostly sees headers, sample rows and the script's results, while the full data is processed locally. That reduces what is sent; it does not make it zero, because sample rows and exception lists are real data.

The practical difference: with the add-in, the model works on the cells directly, so what it looks at leaves the laptop. For a workbook of budget assumptions that may not matter. For a payroll register or a customer master, it does.

Which one, for which job

A working rule: one open workbook you trust, use the add-in. Many files, a repeatable job, an audit trail, or data too sensitive to send whole, use Claude Code and a script.

The job Better fit Why
"What does this formula on the Summary tab do?" Add-in One workbook, already open; it answers with cell citations.
Fix a #REF! someone left in a template Add-in Interactive, one file, you watch it change.
Stack 12 monthly exports from three ERPs Claude Code Many files; a script records every cleaning rule.
Bank rec with 1,400 lines, every month Claude Code Repeatable, large, and the script is the reviewer's evidence.
Check every formula in a 14-tab inherited model Claude Code A script reads all of them and lists issues by cell; the add-in is then handy for walking through what it finds.
Payroll, customer master, bank details Claude Code, script pattern Only headers and results need to be sent.
A board chart tweak five minutes before the meeting Add-in, or just Excel Small, visual, one file.

Use both, in order

The two combine well. Let Claude Code do the heavy, repeatable part and write a checked workbook with formulas and a tie-out sheet. Then open that output in Excel and use the add-in to explore it, explain a number to a colleague, or try a what-if. The script stays the record of how the numbers were made.

A Claude Code prompt for the first half might read:

This folder has GL_Detail_Q3.xlsx and Budget_FY26.xlsx. Do not read them in full. Write and run a Python script that prints the sheet names, headers and first 3 rows of each, then stop. After I confirm, write variance.py to produce Variance_Q3.xlsx with a Variance sheet by account and a Tie-out sheet showing row counts and totals for each input against the output, with formulas, not pasted values.

Prompts for the add-in

These are typed into the add-in's panel inside Excel, not into Claude Code. They are written to suit the features Anthropic documents. Check what comes back before you rely on it.

Walk me through how the EBITDA figure on the Summary tab is calculated, starting from the inputs. Cite each cell you use, and tell me if any step uses a typed number instead of a formula.

Find the cause of the #REF! errors on the Intercompany tab. Show me each broken formula and what it probably referred to before. Don't fix anything yet; list the fixes you propose first.

On the Assumptions tab, change the Q3 freight cost per order from $18.50 to $21.00 and tell me which totals on the P&L tab change, and by how much. Don't overwrite any formulas.

This is the output of our reconciliation script. Without changing anything, tell me in plain English what the Exceptions tab shows, which three items are largest, and whether the Tie-out tab shows zero differences.

How to check the result

The checks differ a little by tool.

With the add-in: go to each cell it cites and look for yourself. When it changes an assumption, confirm the formulas it said it kept are still formulas (Formulas, Show Formulas). Save a copy before a session that edits widely, and note in the file what you asked for; the add-in warns before it overwrites data, but a warning is not a change log. Read the confirmations it asks for before risky operations.

With Claude Code: open the output in Excel and confirm the tie-out shows zero differences after the workbook has calculated. Tie at least one figure to something outside the workbook, such as the trial balance. Recompute a few rows by hand from the source files. Ask Claude Code to show you the lines of the script that hold the rules, and confirm they say what you asked. Copy figures from the workbook, not from the chat.

Limits

Anthropic's own documentation says the add-in is not recommended for final deliverables without human review, for audit-critical calculations without verification, or for highly sensitive or regulated data without proper controls. That is good advice for both tools.

The documentation also warns that spreadsheets from outside sources, such as downloaded templates or vendor files, can contain hidden instructions that try to make the add-in extract data or change records, and advises using it only with trusted spreadsheets. The same caution applies to files you put in a Claude Code folder.

Treat a workbook's contents exactly as you would a file you were about to attach to a chat. If it holds data your company would not send, use the script pattern, or work on a copy with that data removed.

Not affiliated with or endorsed by Anthropic or Microsoft.

From the book

This guide is a short version of one method in Excel + AI for Finance Teams. Chapter 4 of Excel + AI for Finance Teams walks through it end to end on practice files with an answer key.

More free guides