ChatGPT for Excel Add-in: Every Real Way to Get ChatGPT Into Excel (2026)

Guide · Updated September 2026 · ~14 min read

You searched for a ChatGPT for Excel add-in because you want the thing that explains your formulas to be inside the workbook, not in a browser tab you paste into. What comes back is a jumble: OpenAI's own add-in, a dozen marketplace plugins with near-identical names, API tutorials, and vendor pages all promising the same sentence. They are different products, on different meters, with different failure modes.

Here is what actually exists in September 2026, what each route costs, and where each breaks — judged on the three questions we apply to everything in this category: does it see the whole workbook or only what you hand it, does it apply the change or just describe it, and can it reach the system the numbers came from. The wider field is in AI in Excel for accountants; the Anthropic equivalent of this post is getting Claude working inside Excel.

The five routes to getting ChatGPT into Excel

1. OpenAI's own ChatGPT for Excel add-in — first-party, a sidebar, gated by your ChatGPT plan.
2. Marketplace add-ins that put a =GPT() function in the grid — your OpenAI key or the vendor's credits.
3. VBA or Office Scripts calling the API yourself — total control, and every problem becomes yours.
4. Power Query calling the API during a refresh — possible, and usually the wrong tool.
5. Desktop add-ins that bundle a model — and, in the accounting ones, connect to the ledger.

Route 1: yes, there is an official ChatGPT for Excel add-in now

For a long time the honest answer to "is there an official OpenAI Excel plugin?" was no: OpenAI shipped a web chatbot and an API, and everything inside Excel was third-party. Plenty of blog posts still say exactly that, and they are out of date.

OpenAI launched ChatGPT for Excel in beta in March 2026, extended it to Google Sheets in April, and made it generally available across plans in May 2026. You install it from the Microsoft Marketplace like any other Office add-in and sign in with the OpenAI account attached to your plan; organisations that cannot reach the store can have an admin deploy it from the manifest. Because it is packaged to the Microsoft 365 add-in standard, it runs where Office add-ins run — desktop Excel on Windows and Mac, and Excel in the browser.

What you get is a sidebar working on the open workbook rather than a copy of it: build a sheet from a description, update an existing model, ask what a block of formulas is doing. It behaves agentically, taking several steps and editing in place, which is the real difference from pasting a range into chat.

The limits worth knowing before you build a process on it:

• It is metered against your plan, not free. Free and Go tiers get limited access; Plus and Pro draw on the plan's agentic usage limit, which is shared with other agentic features rather than reserved for spreadsheets, and a large multi-step edit eats far more of it than a one-line question. The free preview for Business, Enterprise, Edu and K-12 ran to 2 June 2026, after which usage follows each plan's credits and usage terms.
• Charting is basic. Multi-element dashboards and dynamic KPI layouts are not what this is for yet.
• It reads the workbook, not your accounting system. The export from QuickBooks, Xero or Zoho Books still has to be in the file before the add-in can see it.
• Admin controls apply. Access varies by plan, region, workspace settings and tenant policy, so check OpenAI's help centre page for where it stands on your plan rather than trusting any third-party summary — including this one.

One clarification, because the two get conflated constantly: this is not Microsoft Copilot. Copilot is Microsoft's own pane, licensed through Microsoft 365 and routing across model providers on its own terms; the OpenAI add-in is a separate product you install and sign into separately. What Copilot in Excel can't do for accountants covers that side of the fence.

Route 2: the =GPT() class of ChatGPT Excel plugin

The first-party add-in is conversational. It is not a worksheet function, and if what you actually want is Excel GPT as a formula — one prompt filled down two thousand rows — you need a third-party add-in.

GPT for Work is the best-known of these. It installs from the Microsoft Marketplace, exposes =GPT() and companion functions in the grid, and is built for bulk: the vendor advertises up to 1,000 rows a minute and up to a million rows in a single run, writing results straight into the sheet. It runs on the vendor's own credits by default — free credits to start, then credit packs from $29 valid twelve months, or a subscription from $25 a month — with your own OpenAI API key an option, in which case you pay OpenAI directly for the tokens and the vendor charges a small per-token platform fee on top. Check their pricing page before budgeting; these numbers change.

That default matters more than it looks. If nobody at your firm wants to manage an API key, vendor credits are the safer arrangement; if you already have a key with a spend cap on it, bringing your own is cheaper at volume.

A worked example: classifying 2,000 bank narrative lines

This is the job the function class is genuinely good at. Column A is the date, column B the bank narrative, column C the amount. You want a category in column D.

=GPT("Classify this bank narrative into exactly one of: Travel, Software,
Bank charges, Payroll, Supplier payment, Transfer, Other.
Reply with the category name only.", $B2)

Fill down, wait for the column to settle, then — before anything else — select D2:D2001, copy, and Paste Special > Values over itself. Sanity-check the distribution with =COUNTIF($D$2:$D$2001, F2) against your seven categories listed in column F. If "Other" is 40% of the rows, the prompt is wrong, not the data.

The better pattern, once you have done this twice, is not to classify 2,000 rows at all. Strip the variable tail off each narrative — card reference, date stamp, trailing digits — and you will usually find 120 to 200 distinct stems behind 2,000 transactions. Classify the stems, review that short list like a human being, and apply it with XLOOKUP:

=XLOOKUP(TRUE, ISNUMBER(SEARCH(Rules[Stem], $B2)), Rules[Category], "REVIEW", 0, 1)

You review 150 rules instead of 2,000 labels, it costs a fraction as much, and — the part that matters for a workpaper — it reproduces exactly next month. The matching problem next door is covered in reconciling a bank statement in Excel with AI.

The three hazards of an AI function in the grid

1. Recalculation re-bills you, and can change the answer. An AI function is a live formula. Every recalculation fires a fresh API call — open the file in November, press F9, and you have paid again. Worse, model output is not deterministic: the same narrative can come back "Bank charges" today and "Other" in December, and nothing in the sheet will tell you it moved. That is why the Paste Special step above is not housekeeping but the control itself. A figure going into a statement or a workpaper must be a value, not a prompt waiting to re-run.

2. The function only sees the range you pass it. =GPT("...", $B2) sees B2. Not your chart of accounts on the next tab, not the supplier master, not the sign convention two columns over, not the fact that this client codes all fuel to motor expenses. If the categorisation depends on a list, that list has to be in the prompt or in a second range argument. So this route answers "classify this cell", and never "why does this sheet not tie out?" — that second question belongs to a sidebar with whole-workbook context, which is routes 1 and 5.

3. API keys. A key pasted into an add-in's settings is exactly as safe as that vendor's storage, and a key stored in the workbook — hidden sheet, defined name, VBA module — travels with the file the moment somebody emails it to a client. Three rules cover most of it: never put the key in the workbook; issue a separate restricted key per use with a spend cap on it, so a runaway fill-down costs a few pounds rather than a few hundred; rotate it when whoever set it up leaves. If your firm has nowhere sensible to keep a key, use vendor credits and accept the markup.

Route 3: call the API yourself from VBA or Office Scripts

If you have a developer, the 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.openai.com/v1/chat/completions", False
http.setRequestHeader "Authorization", "Bearer " & apiKey
http.setRequestHeader "Content-Type", "application/json"
http.Send "{""model"":""gpt-5-mini""," & _
    """messages"":[{""role"":""user"",""content"":""" & prompt & """}]}"
Debug.Print http.responseText

That works, and then the real work starts. VBA has no native JSON parser, so reading the reply cleanly means a parser class or string surgery. The prompt must be JSON-escaped, or the first quotation mark in a supplier name kills the request. The key has to live somewhere. And the model sees only what your code sends.

Office Scripts is the modern-looking alternative, and Microsoft does document fetch from a script — but read the platform limits first. Microsoft's external-calls page states plainly that "There is no way to sign in or use OAuth2 type of authentication flows. All keys and credentials have to be hardcoded (or read from another source)" and "There is no infrastructure to store API credentials and keys." It also warns that "External API calls fail when a script is run through Power Automate", and that external calls are unsupported for scripts stored on a SharePoint site. So the two things a finance team would want — a scheduled run, and a key that is not sitting in the script — are the two this route does not give you.

One trap to rule out early: Python in Excel cannot make the call. It runs in Microsoft's cloud sandbox without outbound internet access, so an HTTP request to any API fails by design. Check Microsoft's current documentation if that ever looks to have changed, but do not plan on it.

Route 4: Power Query calling the API

Power Query can post to an API during a refresh. The shape looks like this:

let
    Body = Json.FromValue([
        model = "gpt-5-mini",
        messages = {[ role = "user", content = "Classify: " & Narrative ]}
    ]),
    Response = Json.Document(Web.Contents("https://api.openai.com", [
        RelativePath = "v1/chat/completions",
        Headers = [#"Content-Type" = "application/json"],
        Content = Body
    ]))
in
    Response

Note the shape: a constant base URL with the variable part in RelativePath, which is the arrangement credentials and refresh are designed around — build the whole URL by concatenation and you will meet a refresh error later.

But be honest about the fit. Every refresh re-runs every call, so "Refresh All" on a 2,000-row table is a full re-bill, and a query that feeds prompt text from another query will fight the formula firewall and privacy-level rules. Bearer tokens are awkward too: the usual workaround is an explicit Authorization header with anonymous credentials, which puts the token in the query text where anyone with the workbook can read it. Power Query is excellent at the work either side of the AI step — loading the export, trimming the narratives, joining the result back on — and that is where to use it. Power Query for beginners covers the shaping; leave the calls to a route built for them.

Route 5: desktop add-ins that bundle a model

Every route so far shares one gap: the AI can see the spreadsheet, but not the 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. A smaller class of paid desktop add-ins bundles the model access with the connectors, so there is no key to paste and the assistant can pull the data itself.

Where HISAB 360 fits

HISAB 360 is one of those. It docks a chat panel in desktop Excel, reads the open workbook and applies the work rather than describing it — formulas into cells, Power Query queries, PivotTables, Power Pivot models and DAX measures, charts and VBA — and holds OAuth connections to those six accounting systems with read and write access, so "pull last month's unpaid invoices and age them" is one instruction instead of an export, an import and a formula session.

For readers of this post the relevant detail is the key question: you can bring your own provider key, your OpenAI key included, from $7/month or $60/year — precisely the arrangement many people searching for a ChatGPT Excel add-in are trying to assemble by hand. Otherwise $10–20/month on HISAB's own credits, or a $199 perpetual licence.

The limits, stated plainly: Windows desktop Excel only (Microsoft 365 or 2019 and later, 64-bit) — not Mac, not Excel on the web, which is exactly where the official OpenAI add-in does work. It is paid; the 15-day trial is the full product with 50 credits and no card, but there is no free tier afterwards. Every write back to a ledger should be reviewed before you approve it. And if your work is entirely inside one workbook and never touches an accounting system, route 1 is the cheaper answer — take it.

The five routes, side by side

What it costs, roughly

Three different meters. The official add-in has no separate bill — it draws down the allowance of the plan you already pay for. Marketplace add-ins sell credits or a subscription, in the region of $25 to $29 to get started. Your own API key is billed per token, and for bulk classification the small models are the right choice: at rates published in September 2026, gpt-5-mini sat at around $0.25 per million input tokens and $2.00 per million output, against roughly $5.00 and $30.00 for the flagship GPT-5.5.

Put numbers on the worked example: 2,000 narratives at about 60 input and 5 output tokens each is roughly 120,000 input and 10,000 output tokens — about five cents on the small model, under a dollar on the flagship. The cost is not the constraint; the recalculation you forgot to freeze is. Check OpenAI's current pricing page before you budget — model names and rates here change every few months, and the figures above are a snapshot, not a quote.

Choosing

• You already pay for ChatGPT and work inside one workbook: the official add-in first. Strongest general-purpose option, nothing extra to try it.
• One prompt applied to thousands of rows: a =GPT() marketplace add-in, results converted to values the moment you accept them — and classify the distinct stems, not every row.
• A developer and an unusual requirement: the API direct, with the key kept out of the workbook and a spend cap on it.
• You were about to build this in Power Query: use it for the shaping and something else for the calls.
• The data comes from an accounting system and goes back to one: the bundled-model, ledger-connected class is the only route that closes that loop — at the cost of being Windows-only and paid.

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.