
Claude or Anthropic shows up in 624 accounting and finance job postings in our database, and ChatGPT or OpenAI in 378. That's out of roughly 65,000 live postings, so both numbers are small, but employers who bother to name a tool name Claude more often. I wrote up the full count in which AI tools accounting job postings actually name.
Usage is already near-universal. Karbon's State of AI in Accounting 2026 survey of 593 accounting professionals found 98% use AI and say it saves them about 60 minutes a day, while only 21% work somewhere with an AI policy or strategy. So most people reading this already use one of these tools. What they're missing is a rule for which tool gets which job, and a rule for what the reviewer checks.
I use both. Here's how I split the work, what each plan costs, and where the line sits for client data.
Use Claude for rule-bound, document-heavy work where it has to follow your written policy, and use ChatGPT when you need to crunch a big flat export or get a formula fast. That's my read from daily use, and you should test it on your own files before you standardize on it. I haven't found an accounting benchmark from either vendor, and the third-party "tests" floating around are one person's prompts on one person's files.
The reasons I land there are mostly product features you can check. Claude has a native Claude for Excel add-in that works across multi-tab workbooks, keeps formula relationships intact and cites the cells it used, and it runs reusable Skills inside that add-in. ChatGPT's data analysis environment runs Python on uploaded spreadsheets and CSVs (spreadsheet files cap at roughly 50 MB), which makes it quick at reshaping a messy export.
| Task | My default | What the reviewer checks |
| AP first-pass GL coding | Claude for strict written coding rules; ChatGPT for a huge CSV batch | Vendor overrides, prepaid vs expense thresholds, sales and use tax |
| Month-end flux commentary | Claude | Every dollar and percent ties to the locked trial balance; unexplained variances stay open questions |
| Technical memo drafts (ASC 606, 842) | Claude | Every ASC paragraph, IRC section or case cite opened in the primary source |
| Excel formulas and CSV cleanup | ChatGPT for formulas; Claude for Excel for live workbooks | Off-by-one ranges, hardcoded values, silently dropped rows |
| Policy and credit agreement summaries | Claude | Tables split across pages, defined terms quoted verbatim |
One thing I'll complicate my own take with: Anthropic's own Excel docs say the add-in isn't recommended for audit-critical calculations without verification, and they warn about prompt injection from external files. I agree with them. Whichever tool drafts it, the human tie-out doesn't go away.
The consumer plans run $20 a month on both sides (Claude Pro is $17 a month billed annually), and none of the consumer tiers belong anywhere near unredacted client files. For firm work you want Claude Team or ChatGPT Business, both $25 per standard seat per month billed monthly or $20 billed annually, with premium seats at $125 and $100. Prices are from Claude's pricing page and OpenAI's business pricing.
The training defaults are why the tier matters:
So my rule is simple: personal accounts get banned for client work, the firm buys seats with SSO, and even on a commercial plan staff swap client names for tokens like Client_A whenever the task doesn't need the real name.
Both give you a persistent workspace for your chart of accounts, coding rules and materiality thresholds, so the real difference is how you package a repeatable procedure. Claude Skills are folders of instructions plus resources like scripts, they run in chat and in the Excel add-in, and Team and Enterprise owners can provision them for everyone. Custom GPTs are standalone assistants with up to 20 knowledge files.
For a multi-step close procedure I prefer Skills, because the same packaged instructions follow the reviewer from chat into the workbook. File limits are close enough not to matter: Claude takes files up to 30 MB in Projects and up to 500 MB in chat, ChatGPT takes up to 512 MB per file. The bigger gap is PDFs. Claude reads text and visuals on the first 100 pages of a PDF and text only after that, per its file upload docs. ChatGPT analyzes the text in a PDF and skips embedded images, so a scanned invoice pack goes to Claude.
Every one of these follows the same shape: the AI drafts into a staging table or workpaper, flags what it can't support, and a named person signs off. Here's the prompt skeleton I use for each.
This is the safest starting point. In our data, 228 of 2,063 live AP postings list invoice coding as a duty, and I covered the setup in why GL coding is the safest place to start with AI in AP. Attach your coding rules (say, a $2,500 capitalization threshold and a prepaid rule for multi-month software terms) and the invoice batch, then ask for:
Split it into computing the variance and writing about it. Give it the comparative trial balance, GL detail for the flagged accounts and your thresholds (for example, balance sheet moves over $25,000 and 10%, P&L moves over $10,000 and 10%). Ask it to tie every movement to the trial balance, name the top three drivers by entry ID, write two or three sentences per account, and insert an open question for the account owner wherever the detail explains less than 80% of the move. My longer playbook is how to automate flux and variance analysis with AI.
Let it draft background, contract facts and the issues to evaluate, each fact cited to a page and section of the contract. Leave the conclusion blank, mark every ASC paragraph it mentions for verification in the Codification, and have it list missing terms for legal or sales. More on that boundary in using AI on a technical memo without handing it the conclusion.
Describe the sheet layout exactly (column letters, row ranges, date formats) and ask for one copyable formula plus a check column that proves the row sums back to the invoice total within a cent. Then test it on ten rows you've done by hand before you trust it on 5,000.
Ask for a covenant checklist with the exact formula and definitions, the threshold, testing frequency and the section and page number. Make it quote defined terms verbatim, check both pages when a definition spans a page break, and list any schedule the PDF references but doesn't include.
The AI drafts and a qualified person decides - that's the whole rulebook, and the regulators have now written it down. The IRS Office of Professional Responsibility's June 2026 guidelines for responsible AI use in tax practice say blind reliance on AI output may be unreasonable reliance, apply the Circular 230 diligence and competence duties to AI, and tell practitioners to handle client data only in secure, enterprise-approved AI.
The reviewer card I'd tape to every monitor:
For CPA firms, four rules stack on top of that:
Neither wins every task, so I assign them by workflow: Claude for applying written coding rules, long PDFs, memo drafts and live work inside Excel; ChatGPT for Python on large flat exports and quick formulas. Either way a person verifies every figure and citation before anything posts.
Only on a commercial plan (Claude Team or Enterprise, ChatGPT Business or Enterprise) with a confidentiality agreement and reasonable assurance about the provider's safeguards, or with the client's specific consent. Tax return information also needs Section 7216 consent analysis, and personal accounts should be banned for client work.
Both are $25 per standard seat per month billed monthly, or $20 billed annually, with $125 and $100 premium seats. Consumer Pro and Plus are $20 a month and aren't appropriate for client files.
Claude, for packs up to 100 pages: it reads both text and visuals on those pages, and text only from page 101 to 1,000. ChatGPT analyzes the text in a PDF and doesn't read embedded images, so scanned invoices and charts get missed.
Use them to organize facts and frame the questions, then verify every cite in authoritative research software. The IRS OPR guidance says blind reliance on AI output may be unreasonable reliance under Circular 230.
If you want to see which AI skills employers actually ask for, the skills data on Audit Friendly jobs breaks it down by role. Then pick one of the five tasks above, write the prompt against your own coding rules this week, and run it next to your normal process for one close. You'll know within a month whether it earns a permanent spot.