Claude for Excel: Every Way to Get Claude Working Inside Your Spreadsheets (2026)

Guide · Updated July 2026 · ~12 min read

You have seen Claude explain an inherited formula better than the person who wrote it, and now you want it inside Excel — reading the actual workbook, not a pasted fragment of one. Search "Claude for Excel" and you find an official Anthropic add-in, marketplace plugins, API tutorials and vendor landing pages, each quietly describing a different product with the same name on it.

They are not interchangeable. The routes differ on the three questions that decide whether AI in a spreadsheet is useful for accounting work or a toy: does Claude see the whole workbook or only what you hand it, does it apply changes or merely describe them, and can it reach the ledger the numbers came from? This post walks through six real routes, what each costs, and where each one breaks — the same test we applied to the wider field in AI in Excel for accountants, narrowed here to Claude specifically.

The six routes

1. Anthropic's official Claude for Excel add-in — a sidebar from Anthropic itself, tied to a paid Claude plan.
2. No add-in at all — upload the workbook to claude.ai and get analysis, or a new file, back.
3. Marketplace add-ins with a formula function — the =GPT() class of Office add-ins, with Claude selected as the model.
4. Claude inside Microsoft 365 Copilot — real, but narrower than the headlines suggested.
5. Call the Claude API yourself — VBA or Office Scripts against api.anthropic.com.
6. Desktop add-ins that bundle Claude with workbook and ERP context — the route built for accounting work specifically.

Route 1: Anthropic's official Claude for Excel add-in

Anthropic launched Claude for Excel in late October 2025 as a research preview, initially for Max, Team and Enterprise subscribers behind a waitlist, with access widening since. It arrived as part of Anthropic's financial-services push, and the demo workloads were telling: financial models, not shopping lists. Check Anthropic's site for where the rollout stands now rather than trusting a months-old page — including this one.

What it is: a task pane docked in Excel that you sign into with your Claude account. The difference from pasting into a chatbot is context — it reads the open workbook itself: sheet structure, cell values and the formulas behind them, not a flattened text dump. That makes the previously impossible questions answerable. "Why does the March column disagree with the summary sheet?" requires tracing precedents across sheets, which a copy-paste chatbot cannot do and this can.

What it does well, on Anthropic's own positioning: explain an unfamiliar model sheet by sheet, trace and repair broken references, modify a workbook or draft a new one, and — the detail accountants should care about most — track the changes it makes at cell level so you can review each edit before trusting it. That review trail is the difference between an auditable change and a mystery.

The limits that matter for finance work:

• It needs a paid Claude plan. There is no free tier for the add-in itself, and access has been plan-gated since launch.
• It reads the workbook, not your accounting system. As of 2026 there is no QuickBooks, Xero or Zoho Books connector inside it — check Anthropic's current documentation, since connector support is exactly the kind of thing that gets added. The workbook must already contain the data, which means you are still doing the export dance first — the problem covered in connecting QuickBooks and Xero to Excel.
• It shipped as preview software. Work on copies until you have watched it behave on your own files. That is not a criticism; it is what "research preview" means.

Route 2: no add-in — upload the workbook to claude.ai

The zero-install route: attach the .xlsx to a chat at claude.ai. Claude reads the sheets, and since Anthropic added file creation in late 2025, paid plans can get a finished workbook back, not just prose — ask for a cleaned version of a messy export and download the result.

This is genuinely useful for one-off jobs: a structural review of a model someone left behind, a first pass at reorganising a badly laid-out export, drafting a template you will finish by hand. It fails as a monthly process for three reasons. The file leaves your environment, which for client transaction data is a data-handling decision your engagement letter may not cover — anonymise first, or use a plan whose terms you have actually read. There is no live link: what comes back is a new file you must check and re-import, and next month you start again. And a returned workbook's formulas deserve the same scepticism as a junior's first draft — mostly right, checked anyway.

Route 3: marketplace add-ins with a Claude-powered function

A class of Office add-ins from AppSource — GPT for Excel is the best-known — put an AI function in the grid and a small sidebar next to it. Most are model-agnostic: you pick Claude from a model list and either bring your own Anthropic API key or buy the vendor's credit packs. Because they are built on the Office add-in framework, they run in Excel on Windows, Mac and the web alike.

The fit is bulk cell-level text work. Classifying 2,000 bank narrative lines into expense categories is one formula filled down a column — a real job, done cheaply. At the standard API rates published as of 2026, Claude Sonnet 5 runs $3 per million input tokens and $15 per million output, so a few thousand short classifications costs pennies rather than pounds — check Anthropic's pricing page before budgeting, since rates, models and introductory offers all move.

Three hazards, all structural:

• Formulas recalculate. Every recalculation of an AI function is a fresh API call — new cost, and potentially a different answer, because model output is not deterministic. Convert results to values the moment you accept them.
• The function sees the range you pass it, nothing else. No workbook context, no cross-sheet awareness. This route answers "classify this cell", never "why doesn't this sheet tie out?".
• Key handling is on you. An API key pasted into an add-in's settings is only as safe as the vendor's storage and the workbook's audience.

Route 4: Claude inside Microsoft 365 Copilot

In September 2025 Microsoft announced Anthropic models coming to Microsoft 365 Copilot: the Researcher agent gained a Claude option, and Copilot Studio let organisations build agents on Claude models. Real, shipped, and worth knowing about if your firm already pays for Copilot.

But read the small print before calling this "Claude in Excel". The Excel Copilot pane offers no end-user model picker — as of writing you cannot pin the pane that summarises your table to Claude; Microsoft routes models as it sees fit, and the Anthropic options live in Researcher and Copilot Studio, both admin-gated. So this route gets you Claude near Excel rather than in it. The pane's own constraints for accounting work — and the workaround for each — are catalogued in Microsoft Copilot in Excel: what it can't do for accountants.

Route 5: call the Claude API yourself from VBA

For teams with a developer, the direct route: Claude's API is one HTTPS endpoint, and VBA can reach it.

Dim http As Object
Set http = CreateObject("MSXML2.XMLHTTP.6.0")
http.Open "POST", "https://api.anthropic.com/v1/messages", False
http.setRequestHeader "x-api-key", apiKey
http.setRequestHeader "anthropic-version", "2023-06-01"
http.setRequestHeader "content-type", "application/json"
http.Send "{""model"":""claude-sonnet-5"",""max_tokens"":1024," & _
    """messages"":[{""role"":""user"",""content"":""" & prompt & """}]}"
MsgBox http.responseText

That genuinely works — and then the real work starts. VBA has no native JSON parser, so reading the response cleanly means a parser class or fragile string surgery. The prompt must be JSON-escaped or the first quotation mark in your data breaks the request. The API key has to live somewhere, and "in a cell on a hidden sheet" is how keys end up in files emailed outside the firm. And Claude still only sees what your code sends: workbook context is a serialisation problem you now own.

One trap to rule out early: Python in Excel cannot make this call. As of 2026 it runs in Microsoft's cloud sandbox with no outbound internet access, so requests to any API fails by design — check Microsoft's current documentation if that ever appears to have changed. The DIY route is VBA or Office Scripts, not the Python pane. If you are weighing whether building this beats buying it, that make-or-buy line is the theme of Excel automation for finance teams.

Route 6: add-ins that give Claude the workbook and the ledger

Every route so far shares one gap: Claude can see the spreadsheet, but not the accounting system the spreadsheet came from. For an accountant that is the wrong half of the problem. The numbers live in QuickBooks Online, Xero, Zoho Books, Odoo, FreshBooks or Sage; the workbook is where you reconcile and report on them. An AI that cannot reach the ledger is working from whatever stale export you fed it.

A small class of paid desktop add-ins closes that gap: an AI panel inside Excel with full workbook context, wired to ERP connectors, so "pull last month's unpaid invoices and age them" is one instruction rather than an export, an import and a formula session.

Where HISAB 360 fits

HISAB 360 is a paid Excel add-in in that last class: a chat panel docked inside desktop Excel that reads the open workbook and applies real changes — formulas written into cells, reports built on sheets — rather than handing you text to copy. It connects to six accounting systems (QuickBooks Online, Xero, Zoho Books, Odoo, FreshBooks and Sage) with read and write: pull invoices, bills, GL and customers into sheets; create invoices, bills and journal entries back in the ERP after you review them. Beyond chat, it generates and tests VBA macros and custom ribbons from a prompt, builds Power Query queries and Power Pivot models with DAX measures from a description, runs bundled Python for analysis, and automates bank reconciliation and PDF statement extraction.

For readers of this post the relevant design choice is the pricing model: you can bring your own AI provider key — your Anthropic key included — from $7/month, which is precisely what many "Claude for Excel" searchers are trying to arrange. Alternatively $10–20/month with HISAB AI credits, or $199 perpetual.

Honest limits: Windows desktop Excel only — Microsoft 365 or 2016+, 64-bit — not Mac, not Excel on the web. It is paid; the 15-day trial covers every feature with 50 credits and no card, but there is no free tier after it. And every ERP write deserves review before you approve it.

Three tasks, six routes

Concrete beats abstract, so here is how the routes handle three jobs from an ordinary month.

Task 1: "monthly spend per supplier." The formula itself, with suppliers down column A and month-start dates across row 1:

=SUMIFS(Ledger[Net], Ledger[Supplier], $A2,
        Ledger[Date], ">="&B$1, Ledger[Date], "<"&EDATE(B$1,1))

Any route produces this text — a free chatbot included. The routes separate on what happens next. Routes 1 and 6 place it in the grid against your actual table and column names; routes 2–5 hand you a formula written against column names the model guessed, and you place, adapt and fill it yourself.

Task 2: "build the debtor aging report." Now context is everything: the model must find the invoice table, know which column is the due date, and build buckets — for the 61–90 bucket, something like:

=SUMIFS(Invoices[Outstanding], Invoices[Customer], $A2,
        Invoices[DueDate], "<="&TODAY()-61, Invoices[DueDate], ">="&TODAY()-90)

The official add-in and route 6 build this in place from the real table. The claude.ai upload returns a new workbook to check and merge. A cell function cannot do it at all, and DIY means serialising your invoice table into every request.

Task 3: "which Acme invoices are unpaid and over 60 days?" — asked of the ledger, not a sheet. Only route 6 answers without leaving Excel, because only route 6 is connected to the accounting system. Every other route needs you to run the export first, which was the chore you were trying to retire.

The comparison, in one table

Choosing

• Already on a paid Claude plan, workbook-only needs: the official add-in first. It is the strongest pure-workbook option and the change tracking suits review-minded users.
• One-off structural cleanup, nothing confidential: upload to claude.ai and take the returned file as a draft.
• Bulk text classification in cells: a marketplace function add-in with your own API key, results converted to values immediately.
• Firm already licenses Copilot: use what you have, know its pane is not Claude, and keep expectations calibrated.
• A developer on staff and unusual requirements: DIY against the API, with the key kept out of the workbook.
• The data comes from an accounting system and goes back to one: the workbook-plus-ERP class is the only route that covers the whole loop.

Frequently asked questions

Try HISAB 360 on your own workbook

HISAB 360 is an AI assistant inside Excel for accountants and finance teams — it writes macros, Power Query and formulas from plain English, and connects two-way to QuickBooks, Xero, Zoho Books, Odoo, FreshBooks and Sage. The 15-day trial is the full product, no card required.