AI Tools Review

Claude for Excel Review: 7 Real Tests and Honest Results

Ahmad Hussain By AI specialist and finance professional
  • Published
  • Updated
  • 19 min read
Claude for Excel review: real dashboard built by Claude during our 7 tests, with bank reconciliation and pivot table checks
Table of contents

We gave Claude for Excel a broken month-end workbook and four hidden mistakes, then watched what it did. It reconciled a bank account, traced a wrong net profit back to its source, fixed the formulas, built a real pivot table and a manager dashboard, and told us plainly when a request was outside its limits.

This review is not a feature list rewritten from a press release. Every result below comes from tests we ran ourselves on 31 October 2026, with screenshots, timings and the mistakes it made. Where we did not test something, we say so and point you to Anthropic’s own documentation instead.

The verdict in 60 seconds

It is the most useful AI add-in we have tested for real accounting work. It found every error we planted, explained its reasoning with clickable cell references, and asked permission before changing anything. It still made small mistakes, so treat it as a fast, careful junior who needs a reviewer, not a replacement for one.

Here is the full scorecard.

TestTaskResultTime
1Bank reconciliationPass: all 5 differences found, both sides agreed at $13,897.40About 1 minute
2Trace net profit to the source dataPass: found all 4 planted errors without being told they existed45 to 60 seconds
3Find and fix broken formulasPass: 4 fixes plus 2 useful model improvements, with permission first69 seconds to finish the audit
4Build a pivot tablePass: a genuine PivotTable, every figure correctNot timed
5Build a manager dashboardPass: KPI tiles, 3 charts and live insights, all formula drivenAbout 2 minutes
6Write and add a VBA macroCannot add VBA, but wrote tailored code and setup stepsNot timed
7Create a What-If data tableCannot create a native data table, but built a formula based gridNot timed

Our bottom line: if you already pay for Claude Pro and spend your days in Excel, install it. If you need it to run unattended, sign off on numbers or handle macros, it is not there yet.

The workbook we gave it

We built a test file for a fictional wholesaler called Cedar Lane Trading, so no real client data went anywhere near an AI tool. It had five sheets: a management Summary, a Cash Ledger, a Bank Statement, 33 income and expense Transactions for July to September 2026, and a Budget vs Actual report for September.

Then we planted four mistakes of the kind we see in real workbooks:

  1. A hardcoded number. September rent was typed in as $4,000 instead of pulling the real $4,200 from the transactions.
  2. A divide by zero. The variance % column had no zero guard, so the unbudgeted Software line showed #DIV/0!.
  3. The wrong denominator. Gross margin divided gross profit by cost of goods sold instead of revenue, showing a silly 131%.
  4. A short SUM range. Total operating expenses stopped one row early and left out Marketing.

Together, errors 1 and 4 made September look $3,300 better than it really was. The workbook reported a net loss of $180. The true figure was a loss of $3,480.

We also built the bank reconciliation so it had one of everything an accountant expects: an outstanding cheque, a deposit in transit, a bank fee, interest, and a transposition error.

Test setup:

ItemDetail
ExcelOffice LTSC 2024 on Windows
Claude planClaude Pro
Model shown in the add-inOpus 5.5, Medium
Test date31 October 2026
MethodA new chat for every test, prompts pasted exactly, results checked against our own answer key

Test 1: Can Claude for Excel reconcile a bank account?

Yes. Asked to reconcile the Cash Ledger against the Bank Statement, it found all five differences, labeled each one correctly, and brought both sides to the same adjusted balance of $13,897.40 in about a minute. It also cited the exact cells it used and did not touch the workbook.

Claude for Excel reconciling a cash ledger against a bank statement with cell citations

The prompt asked it to list every difference, classify it and show adjusted balances for both sides. Here is what it returned, compared with our answer key.

ItemClaude’s classificationCorrect?
Cheque 1045, $1,450, not yet clearedOutstanding chequeYes
Receipt REC-304, $3,400, not yet on the statementDeposit in transitYes
Monthly service fee, $35Bank chargeYes
Interest credited, $12.40InterestYes
Cheque 1041: $540 in the ledger, $450 at the bankLedger transposition error, $90Yes
Claude showing adjusted bank and ledger balances agreeing at 13,897.40

The part that impressed us most was its judgment on the $90 difference. It explained that 540 and 450 look like swapped digits, so it treated the ledger as wrong, and then added a caveat we would expect from a careful senior: check the cheque stub or supplier invoice, because if the cheque really was written for $540, the bank made the error and you should raise it with them.

Every cell reference in the answer was a clickable chip. Clicking “Cash Ledger E15” jumped straight to the $1,450 cheque, which makes checking its work far faster than with a chatbot in a browser tab.

Clicking a Claude cell citation selects cell E15 in the Cash Ledger sheet

The one slip: it dated cheque 1045 as 29 September. The ledger says 28 September. The amount and cell were right, so the reconciliation was unaffected, but it is a reminder that a confident answer can still contain a small wrong detail.

Test 2: Can it explain where a number comes from?

Yes, and this is where it stood out. We asked it to trace net profit back to the source data and say if anything looked wrong. Without being told any errors existed, it found all four planted mistakes, recalculated the correct loss of $3,480, and showed every step with clickable cell references.

Its trace went from the Summary sheet, through Budget vs Actual, down to the individual transaction rows. For revenue, for example, it pointed to the two September invoice rows ($30,000 and $25,200) that made up the $55,200 total. All of its row references were correct.

Claude tracing net profit through the Summary and Budget vs Actual sheets

Then it listed what looked wrong:

  • Total operating expenses summed B10:B14 and missed Marketing, understating costs by $3,100.
  • September rent was a typed $4,000 while the transaction showed $4,200, which also created a false $200 “saving” in the variance report.
  • Gross margin divided by COGS instead of revenue, so 131% should have been about 56.7%.
  • The Software line had a $0 budget, which caused the #DIV/0!.
Claude listing the formula errors it found in the workbook

It went one step further than our answer key. It noticed that September’s $1,450 software charge was an annual licence renewal, compared with $300 in earlier months, and pointed out that booking a full year in one month makes September look worse than it is. That is a prepayment point an accountant would raise in a month-end review, and we had not planted it.

Test 3: Will it find and fix broken formulas?

Yes. It audited the whole workbook in 69 seconds, listed six issues with the correct formula for each, and asked which fixes to apply before touching anything. After we approved, it fixed every planted error, re-read the changed cells to confirm no errors remained, and left the cash sheets alone.

Claude asking which formula fixes to apply before editing the workbook

The four planted errors came back fixed exactly as an accountant would fix them:

CellBeforeAfter
Summary B8, gross margin=B7/B6, showing 131%=B7/B5, showing 56.7%
Summary B16, total opex=SUM(B10:B14)=SUM(B10:B15), now $34,780
Budget vs Actual C8, rentTyped 4000A formula like the other rows, now $4,200
Budget vs Actual E9, variance %#DIV/0!Shows “n/a”
Summary sheet after Claude fixed the gross margin and operating expense formulas

It also suggested two improvements we had not asked for. First, it moved the hardcoded “Sep 2026” out of every SUMIFS formula into a single blue input cell, so rolling the report forward to October means changing one cell. Second, it replaced the typed Month column on the Transactions sheet with a formula that builds the month from the date. Both are genuine good modelling habits.

Budget vs Actual sheet with a new period input cell after Claude's fixes

After the fixes, net profit read a loss of $3,480 and net margin read negative 6.3%, both matching our answer key. It finished by listing what was still open: the cheque 1041 difference and whether a $0 software budget was intentional.

Test 4: Can it really build a pivot table?

Yes, in our test it did. Some guides say Claude can only talk you through building a PivotTable, but when we asked for costs by department and month, it created a genuine Excel PivotTable on a new sheet. The PivotTable Analyze tab and field list appeared, and all twelve figures matched our answer key.

DataCamp’s Claude in Excel tutorial says Claude can guide you through PivotTables but that you need to create them yourself. Anthropic’s documentation says it can “edit pivot tables”. The add-in is updated often, so both may have been accurate when written. Here is what happened when we tried it.

DepartmentJul 2026Aug 2026Sep 2026Total
Admin$10,500$10,500$11,650$32,650
Operations$27,310$28,740$31,990$88,040
Sales$11,650$12,180$15,040$38,870
Grand total$49,460$51,420$58,680$159,560
PivotTable created by Claude showing costs by department and month

It excluded revenue with a Category filter, as asked. It also caught a problem on its own: because the Month column was text, the pivot sorted the months alphabetically as Aug, Jul, Sep. It added a date based “Month Start” helper column to the Transactions sheet so the months appear in calendar order.

Two details are worth knowing. That helper column is a change to your source data, so check you are happy with it. And Claude was honest about its checking: it said it verified one cell by hand (Admin in July: $4,200 + $6,000 + $300) and had not checked every other cell. We checked them all, and they were right.

Test 5: Can it build a dashboard a manager would use?

Yes. In about two minutes it built a one-page dashboard with five KPI tiles, three charts and a “Key insights” box. Every number was linked to the source sheets by formulas, every figure matched our answer key, and it even wrote the insights as formulas so their wording updates when the data changes.

Management dashboard built by Claude with KPI tiles and three charts

Here is what the dashboard contained:

  • KPI tiles: September revenue $55,200, gross profit $31,300, net loss $3,480, gross margin 56.7% and net margin negative 6.3%. Each tile showed the budget figure and variance underneath, which we had not asked for, and loss figures turned red automatically.
  • Monthly revenue vs total costs for July to September as a column chart.
  • Q3 costs by department as a column chart.
  • September budget vs actual by line as a bar chart.
  • Four key insights, all correct when we checked them.

The insights were the best part. One read that from July to September revenue rose 15.0% while total costs rose 18.6%, leaving a Q3 net loss of $4,860. We recalculated each figure from the transactions, and all of them were right. That is a genuinely useful observation for a business owner.

Key insights box written as formulas on the Claude dashboard

It also reported that our Excel regional setting was displaying the dollar amounts as AED, and switched the dashboard’s number formats to US dollars. And it reminded us, again unprompted, about the unresolved cheque 1041 difference from Test 1.

Test 6: Will it write and add VBA macros?

No, it cannot add VBA to a workbook, and it said so immediately. It explained it can edit cells, formulas and formatting only. Instead of stopping there, it wrote a macro tailored to our sheet’s exact layout, with clear steps for saving as .xlsm and adding a button. That matches Anthropic’s documentation, which lists macros and VBA as unsupported.

Claude explaining it cannot add VBA and providing macro code instead

The code was specific to our file: headers in row 4, data from A5, amounts in column F. It found the last row automatically so new transactions would be included, and it warned that a normal .xlsx file cannot store macros, a step many people miss. It also offered a simpler option: if you only need the sheet sorted once, it could sort it immediately with no macro at all.

We reviewed the code and it is sound, but note that we did not run it in this test. If macros are a big part of your work, our comparison of the best AI tools for Excel VBA macros covers which assistants write code that runs first time.

Test 7: Can it create a What-If data table?

No, not a native one. It explained that Excel’s built-in Data Table function cannot be created from an add-in, which matches the documented limits. It then built a sensitivity grid where each cell has its own formula, and all nine results matched our own calculations.

We asked how September net profit changes if revenue moves by 10% either way and COGS by 5% either way. The base case sat in the center, highlighted in yellow, and matched the reported loss of $3,480.

COGS changeRevenue down 10%Revenue unchangedRevenue up 10%
Down 5%($7,805)($2,285)$3,235
Unchanged($9,000)($3,480)$2,040
Up 5%($10,195)($4,675)$845
Sensitivity grid built by Claude in place of a native What-If data table

It added a useful conclusion: September only turns a profit if revenue rises by 10%, and at that level it stays profitable even with COGS up 5%. It also explained how to build a native Data Table yourself if you prefer one.

Where Claude slipped

Claude made no serious errors in our tests, but it was not flawless. These are the smaller problems we found, and they are exactly why every output needs a human review before anyone relies on it.

  • A wrong date. In Test 1 it dated a cheque 29 September instead of 28 September.
  • A formula that depends on your language settings. In Test 3 it rebuilt the Month column with =TEXT(A5,”mmm yyyy”). Month names from TEXT depend on Excel’s language and regional settings, so on a non-English setup the result could stop matching the “Sep 2026” period cell and break the SUMIFS totals. It worked on our English setup.
  • An input cell in an awkward place. The new “Period” input cell went into the header row of the report table. It works, but most modellers keep inputs in a separate, clearly marked area.
  • Cut off labels. On the dashboard, some labels in the supporting data block below the charts, such as “Departmen”, were cut off by narrow columns.
  • An accessibility flag. After the dashboard was added, Excel’s status bar changed to “Accessibility: Investigate”, which usually points to items such as charts without alt text.
  • Changes to source sheets. For the pivot table and dashboard it added helper data and a helper column. It told us each time, but it is still a change to your workbook.

None of these changed a reported result. All of them are things a reviewer would catch in a couple of minutes, and that is the right way to think about the tool.

Does it change your data without asking?

Not in our tests. Before editing, it asked twice: first which fixes we wanted, then with a detailed list of every pending edit and a red warning when existing data would be overwritten. The risk is one button, “Dangerously always allow”, which turns those checks off for future edits.

In Test 3, the second permission screen read “Claude wants to continue running a script”, described the job as “Apply all six fixes and verify”, flagged “Potential data loss: Auto-fill range B5” in red, and listed each pending edit cell by cell. We had three choices: Deny, Dangerously always allow, or Allow once.

Claude permission screen listing pending edits with a potential data loss warning

We used “Allow once” every time, and we recommend you do the same. Anthropic’s documentation says the add-in warns you before overwriting existing data, and our tests confirmed it, but that protection only helps if you leave it switched on and actually read the list.

Setup in 3 minutes: plans, versions and install

You need a paid Claude plan, a supported version of Excel, and about three minutes. Install the add-in from Excel’s Add-ins menu, sign in with a short code in your browser, and the Claude panel opens beside your sheet. The free Claude plan does not include it.

Which Claude plans include it?

Anthropic’s documentation says the add-in is available on the Pro, Max, Team and Enterprise plans. Prices below were checked on Claude’s pricing page on 31 October 2026.

PlanPriceNotes
Free$0Does not include the Excel add-in
Pro$17 a month billed annually ($200 up front), or $20 billed monthlyWhat we used for every test
Max$100 a month5x Pro usage
Ultra$200 a month10x Pro weekly usage
Enterprise$20 per seat per month plus usage at API rates, billed annuallyAdds admin controls and custom data retention

The add-in draws on the same usage limits as the rest of your Claude account. Spreadsheet work can be heavy, so if you hit limits often, splitting big jobs into smaller requests helps.

Which versions of Excel does it work on?

According to Anthropic’s documentation, the add-in supports Excel on the web, Excel on Windows with a Microsoft 365 subscription, and Excel on Mac version 16.46 or later. It does not run on Excel 2016 or 2019 perpetual or volume licenses, Excel on iPad, or Excel on Android.

Our finding on Office LTSC 2024: Office LTSC 2024 does not appear on either list. We ran every test in this review on Office LTSC 2024 for Windows, and the add-in installed, signed in and worked throughout. Because it is not officially listed, we would not rely on that continuing for business critical work. If something fails on LTSC, try the same task in Excel on the web, which is officially supported. Our guide to installing Office LTSC 2024 explains how that version differs from Microsoft 365.

Claude for Excel sign-in panel showing a code and Continue in browser button

How to install it and sign in

  1. In Excel, go to Home, then Add-ins, and search for Claude. Add the “Claude for Microsoft 365” add-in.
  2. Open the Claude panel from the ribbon. It shows a short sign-in code.
  3. Click Continue in browser. If the browser does not open, use Copy the sign-in link and paste it into any browser.
  4. Sign in with the Claude account that has your paid plan, enter the code and approve.
  5. Return to Excel. The panel becomes a chat box, ready to use.

The code expires after a short time. If it does, go back and request a new one. Make sure you approve in a browser signed in to your paid account, because a free account will not unlock the add-in.

Claude for Excel vs Copilot in Excel

We did not test Copilot for this review, so this is a comparison of facts rather than performance. The biggest practical difference is availability: Copilot is tied to Microsoft 365 subscriptions, while Claude runs as an add-in on a Claude plan, which is why it worked for us on Office LTSC 2024, a version that does not include Copilot.

Claude add-inCopilot in Excel
Made byAnthropicMicrosoft
How you get itAdd-in, with a Claude Pro, Max, Team or Enterprise planBuilt into Microsoft 365 plans that include Copilot
Business price checked 31 Oct 2026Pro from $17 a month billed annuallyMicrosoft 365 Copilot Business add-on from $18 per user a month paid yearly (a promotional first year price; usually $21), or Microsoft 365 Business Standard with Copilot at $23.50 per user a month paid yearly
Works with Office LTSC 2024Worked in our tests, though not officially listedMicrosoft says Office LTSC 2024 does not include the cloud-backed features of Microsoft 365 Apps, such as AI-driven automation
Clickable cell citationsYes, confirmed in our testsNot tested

Copilot prices come from Microsoft’s Copilot business pricing page. Microsoft also says Copilot in its apps is available with Microsoft 365 Personal and Family subscriptions.

If your firm already pays for Microsoft 365 with Copilot, try it first, since you have already paid for it. If you use Claude for other work, or you are on Office LTSC, Claude is the more practical option. Our wider comparison of ChatGPT vs Claude for accountants covers how the two assistants handle finance tasks outside Excel.

Is it safe to use with client files?

It can be, with care. Anthropic says conversations, including the workbook content Claude reads, are sent to Anthropic, and backend inputs and outputs are deleted within 30 days except in specific cases. Chat history stays on your own device. The bigger risk is opening untrusted files, which can hide instructions that try to manipulate the add-in.

Here is what Anthropic’s data storage documentation and the Excel guide say:

  • What leaves your device: your messages, attachments and the spreadsheet content Claude is asked to work with go to Anthropic’s model service.
  • What stays local: chat history is stored in your device’s browser storage, does not sync between devices, and keeps the 50 most recent conversations per Office app. On Excel on the web, Anthropic advises treating chat history as temporary.
  • Training: on consumer plans such as Pro and Max, Anthropic’s model improvement privacy setting controls whether new chats can be used for future model training. You change it in Claude under Settings, then Privacy.
  • Not recommended for: final client deliverables without human review, audit critical calculations without verification, and highly sensitive or regulated data without proper controls.

The prompt injection warning matters most for accountants, because we receive spreadsheets from clients, banks and suppliers all the time. Anthropic warns that files from outside sources can contain hidden instructions that try to extract data or change records. Use the add-in on workbooks you trust, and read every permission screen. Our guide to AI agent security for small businesses explains this risk in plain terms.

If you are a tax professional, check what your regulator allows before any client data goes into an AI tool. Our IRS AI risk checker helps you decide whether a specific task is safe.

What it can’t do, and how big a file it can handle

Anthropic lists data tables and macros as unsupported, and our tests confirmed both. Claude reads up to 2,000 cells with data at a time, and Anthropic says workbooks under about 1 million used cells work well. Above 5 million, it calls the risk your own.

From the performance and limits documentation:

LimitValue
Cells Claude reads in one step2,000 cells with data, so large sheets take several steps
Wait for a step where Claude runs code90 seconds
Wait for other steps, such as writing cells5 minutes on desktop, 2 minutes on the web
Workbook size that works wellUnder 1 million used cells
Higher risk1 to 5 million used cells
Use at your own riskOver 5 million used cells

Anthropic’s advice for big files is sensible: close workbooks you are not using, name the exact sheet and range you want Claude to work on, and ask for large changes one step at a time. If Claude reports a timeout, Office may still be working, so wait, save, then ask for a smaller step.

Our verdict as accountants: who should use it

Claude for Excel is worth installing if you review, reconcile or explain spreadsheets for a living and already pay for Claude Pro. It is not a substitute for professional review. In our tests it worked like a fast, thorough junior: right almost every time, honest about its limits, and occasionally wrong on a small detail.

Use it if you:

  • Inherit workbooks from colleagues or clients and need to understand how they work.
  • Run month-end reviews and want a second pair of eyes on formulas and variances. Our Claude prompts for month-end close and FP&A give you ready-made requests to start with.
  • Build management reports and want a solid first draft of a dashboard in minutes.
  • Use Office LTSC and cannot get Copilot.

Skip it, or wait, if you:

  • Need macros or native What-If data tables.
  • Want AI to produce final numbers that nobody checks.
  • Work mainly with spreadsheets from untrusted outside sources.
  • Only use the free Claude plan.

What surprised us most was not the accuracy, which was high, but the judgment. It questioned a transposition instead of assuming, spotted an annual licence that distorted a month, and kept reminding us about an unresolved bank difference. Those are habits of a good accountant, and they are why we would keep using it. We would still review every change before it reaches a client.

Frequently asked questions

Is Claude for Excel free?

No. Anthropic makes the add-in available on the Pro, Max, Team and Enterprise plans, not the free plan. As of 31 October 2026, Claude Pro costs $17 a month billed annually ($200 up front) or $20 billed monthly. We ran every test in this review on a Pro plan.

Does it work on Mac?

Yes. Anthropic lists Excel on Mac version 16.46 or later as supported, along with Excel on the web and Excel on Windows with a Microsoft 365 subscription. It does not run on Excel for iPad or Android.

Does it work with Excel 2019 or Office LTSC 2024?

Excel 2016 and 2019 perpetual or volume licenses are officially unsupported. Office LTSC 2024 is not mentioned either way in Anthropic’s documentation. In our tests on Office LTSC 2024 for Windows, the add-in installed and worked for every task, but because it is not officially listed, results may change.

Can Claude for Excel create pivot tables?

In our test, yes. We asked for total costs by department and month, and it built a genuine Excel PivotTable on a new sheet with every figure correct. It also added a helper column so the months sorted in calendar order. Anthropic’s documentation says it can edit pivot tables.

Can it write or run VBA macros?

It cannot add or run macros inside a workbook. Anthropic lists macros and VBA as unsupported. When we asked, it wrote a macro tailored to our sheet and gave step-by-step instructions for saving the file as .xlsm and pasting the code in ourselves.

Does it work in Google Sheets?

No. Claude’s add-in is built for Excel only, and Anthropic’s documentation lists only Excel builds: Excel on the web, Excel on Windows with Microsoft 365, and Excel on Mac.

Why did my Claude chat history disappear?

Chat history is stored only on your device and does not sync. Anthropic keeps the 50 most recent conversations per Office app, deletes older ones automatically, and says to treat history on Excel on the web as temporary. On Windows, history is linked to the Office account you are signed in to, so check that first.

How large a workbook can it handle?

Claude reads up to 2,000 cells with data at a time, so large sheets take several steps. Anthropic says workbooks under about 1 million used cells work well, 1 to 5 million carry higher risk, and anything over 5 million is at your own risk.

Is it safe to use with client data?

Use it carefully. Workbook content Claude reads is sent to Anthropic, and Anthropic warns against using it on untrusted files because of prompt injection. Avoid highly sensitive or regulated data without proper controls, check your privacy settings, and review every change before it reaches a client.

Will it change my spreadsheet without asking?

Not by default. In our tests it asked which fixes to apply, then showed every pending edit and flagged possible data loss before running. Choosing “Dangerously always allow” removes those checks, so we recommend clicking “Allow once” each time.

Share this article
Ahmad Hussain
Written and tested by

Ahmad Hussain

AI specialist and finance professional

Ahmad works in accounting, financial reporting and tax preparation, and tests AI tools on that same work. Every test on this site starts with an answer key, and every price is checked on the official pricing page. He also runs IdeaToWeb.