JTSTech Services
← All articles

Strategy · November 19, 2026 · 10 min read

ChatGPT can now create invoices, record payments and manage payroll in QuickBooks from a chat window. Xero said no. The difference is a decision your ledger vendor made for you.

On 18 November OpenAI launched ChatGPT for Accounting: one plugin that knows how to do bookkeeping, and eight partner plugins that reach into the books themselves. Read the eight listings side by side and they do not agree. Xero, BILL and FreshBooks let ChatGPT look and nothing else. QuickBooks lets it manage invoices, estimates, payments, customers, products and payroll from the chat. OpenAI's safety model is that ChatGPT respects the permissions of whoever connected it. In a twenty-person company that is the owner, and the owner's login does everything. Here is what launched, what each plugin can actually do, what the day-before Sales launch adds, and the four decisions to make before anyone on your team clicks Connect.

Written by Jeremy Souffir Founder, JTS Tech Services

The direct answer first. On 18 November OpenAI switched on ChatGPT for Accounting, and the thing to understand about it is that it is two layers, not one. The top layer is an Accounting plugin written by OpenAI. It carries the instructions: how to draft entries from invoices and receipts, how to tie a bank statement to the general ledger, how to check a month-end workbook for broken formulas and double counting. The bottom layer is eight partner plugins written by the accounting vendors, and that layer is where the data lives and where the writing happens. The eight are Intuit QuickBooks, Xero, BILL, FreshBooks, NetSuite, NetSuite QuickStart, Rillet and Campfire. Read their listings on OpenAI's own site and you find that they made different decisions. Xero's plugin, in Xero's words, connects with read-only access. FreshBooks says its plugin answers questions and does not make changes on your behalf. BILL says access is read-only and runs as each signed-in user. QuickBooks says you can manage invoices, estimates, payments, customers, products, and payroll directly from chat. Campfire says that with the necessary access you can create, update, and delete supported accounting records. Same chat window, same Accounting plugin on top, and underneath it either a window onto your books or a pen in them, depending on which ledger you happen to run. If your business is on QuickBooks Online, which most of the Shopify and WooCommerce stores we talk to are, you are on the pen side, and the only thing between the chat and your ledger is the permissions of the person who connected it.

What did OpenAI actually launch?

  • A plugin with a process in it. OpenAI's page for the Accounting plugin describes an accounting assistant for work in your software and workbooks, from everyday bookkeeping to reporting and audits, with explanations grounded in your records and a clear account of changes it makes. The ChatGPT for Accounting page lists four jobs: prepare draft entries from invoices and receipts with suggested account coding, gather invoices, statements and payment records from email, files and accounting apps, compare workpapers with supporting records and draft review notes, and save templates and review checks as reusable skills to apply to each month's records.
  • Eight plugins with the data in them. The launch post on the ChatGPT account names QuickBooks, Xero, Oracle NetSuite, BILL, FreshBooks, Rillet and Campfire; the product page adds NetSuite QuickStart. OpenAI's description of the split is one sentence: the accounting plugin adds guidance for invoice processing, reconciliation, and reporting, while computer use lets ChatGPT help in apps that aren't available through a plugin. Read that second clause twice. If your ledger has no plugin, the fallback is not nothing. It is ChatGPT operating the app's screen.
  • A worked example that writes. The invoicing example on OpenAI's page is a prompt a contractor might type: find the latest jobs ready to invoice in my email. Create the invoices with @Intuit Quickbooks for my review. Flag anything unclear. The invoices are created in QuickBooks. The review is yours.
  • A control model in three sentences. Under the heading Keep control of your data and decisions, OpenAI says: workspace admins choose which apps are enabled. Users connect their own accounts, and ChatGPT respects their existing app permissions. And then: you make the final call. Review supporting records, calculations, and suggested coding before approving entries or reports. Every word of that is true. The post below is about what it means when the admin, the user and the person with every QuickBooks permission are the same human.
  • Who can have it. OpenAI's plugin pages all carry the same line: availability depends on the plugin, your plan, and workspace settings, and some connections require admin setup or approval. The install flow points at the desktop app and ChatGPT Work. OpenAI does not name a country for the package, and we have not found an Intuit statement on whether the QuickBooks plugin reaches Canadian QuickBooks Online accounts. Xero's own announcement says its expansion is currently available in the US. FreshBooks, which is Toronto-based, says its plugin is available in the United States, Canada and the United Kingdom.

The day before: the same pattern for sales

ChatGPT for Accounting is the second of these in two days. On 17 November OpenAI launched ChatGPT for Sales: a Sales plugin from OpenAI plus more than 30 new and expanded partner plugins, among them Salesforce, HubSpot, Close CRM, monday CRM, Apollo, Clay, Gong, Docusign and PandaDoc. The pattern is identical, an OpenAI plugin that knows the job and partner plugins that hold the data, and so is the direction of travel: with connected tools like Attio, OpenAI says, you can save the next step to your CRM from ChatGPT. The Sales announcement also says the plugins can be delegated to your dot, OpenAI's always-on agent, which can prepare meeting briefs, track deal updates and proactively bring you relevant changes. We wrote about dots on 1 October, when they had their own computer and 4,000 app connections. They now have your pipeline and, if you let them, your invoices. The one line in the Sales post that matters most for this one is the instruction to admins: review access to the required apps and the actions they can use. OpenAI is telling you where the decision sits.

Why do eight plugins from one launch behave differently?

Because OpenAI did not decide what they do. Each vendor wrote its own plugin and chose how far to let the chat reach. The listings on OpenAI's site are the vendors' own words, and they sort into three groups. Nothing in the Accounting plugin on top changes which group you are in.

  • Read-only, by the vendor's choice. Xero: ChatGPT connects with read-only access, any data retrieved is used only to respond to your questions and is never stored between sessions. Xero's US plugin page goes further: no creating, editing, approving, reconciling, paying or posting journals, and its 19 November blog post about joining ChatGPT for Accounting keeps the same line, the review starts in ChatGPT and the action happens back in Xero, where the ledger lives and where every change stays traceable. FreshBooks: the FreshBooks app is read-only, it answers questions about your business, it doesn't make changes on your behalf. BILL: access is read-only and runs as each signed-in user, same data, same access, same permissions as BILL itself.
  • Read and write, inside the ledger's own rules. Campfire's listing is the most explicit in the set: with the necessary access, you can create, update, and delete supported accounting records and manage budgets, tags, and custom fields, and existing permissions, applicable approval requirements, and closed-period controls govern changes. OAuth tool calls are recorded in your connection audit history. NetSuite's listing says its connector maintains NetSuite's existing role-based security model, so what ChatGPT can do is what the connecting role can do.
  • Read and write, with the fence described as yours. The QuickBooks listing: generate accounting-compliant profit and loss, cash flow statements, balance sheets, and AR/AP aging reports in minutes, and manage invoices, estimates, payments, customers, products, and payroll directly from chat. Its bundled skills include chase-overdue-invoices, email-to-estimate-invoice and analyze-payroll-cost. The listing does not describe an approval queue, a draft state or a closed-period lock on the plugin side. What governs it is the sentence on OpenAI's page: ChatGPT respects their existing app permissions. Whose? The user who connected it.
The two layers, left to right. A chat window feeds one plugin that carries the method, which fans out to the ledgers underneath. The upper row accepts only a one-way beam through a pane, a window the agent can look through. The lower row accepts a two-way connection through an open frame, with a pen at the end of it. The gate on each line is not drawn by OpenAI. It is the user account the connection was made with, and it is exactly as wide as that account.
The two layers, left to right. A chat window feeds one plugin that carries the method, which fans out to the ledgers underneath. The upper row accepts only a one-way beam through a pane, a window the agent can look through. The lower row accepts a two-way connection through an open frame, with a pen at the end of it. The gate on each line is not drawn by OpenAI. It is the user account the connection was made with, and it is exactly as wide as that account.

What does "respects existing permissions" mean in a twenty-person company?

In a large firm it means something reassuring. The accounts-payable clerk connects QuickBooks or NetSuite with the clerk's login, the clerk cannot approve a journal or run payroll, and so neither can the chat. The controller connects with the controller's login and gets the controller's reach. The fence is already there, built by years of someone deciding who may do what in the ledger, and the plugin inherits it. In the businesses we work with it means the opposite. A Shopify brand with fifteen staff has one QuickBooks Online company file and one person who set it up, usually the founder or the operations lead, and that login is the company administrator because somebody had to be. The bookkeeper may have a second login. There is rarely a third. When that founder installs the Accounting plugin and clicks Connect on QuickBooks, which OpenAI's page describes as users connect their own accounts, the chat inherits a login that can create and delete invoices, record payments, change customer records and reach payroll. OpenAI's control model is working exactly as designed. The ledger's permission model was never designed for this, because the only user with every permission was the one person who was never going to hand the keyboard to anything else.

  • The approval is a reading, not a lock. OpenAI's you make the final call is an instruction to you, to review supporting records, calculations and suggested coding before approving entries or reports. It is good advice and it is where the safety lives. It is not a mechanism in QuickBooks that holds an entry until someone else signs it. For QuickBooks the listing describes no such state, and OpenAI's own example creates the invoices for my review without saying whether they exist in the ledger before or after the review. We do not know, and neither will you until you try it on a copy.
  • Deletion is in the verb list. QuickBooks' listing says manage; Campfire's says create, update, and delete and then names the controls that govern it. A plugin that can create an invoice from an email can, with the same login, void or delete one. Campfire tells you its closed-period controls apply. For QuickBooks you are relying on whatever close-the-books setting you turned on, if you turned it on.
  • The chat is not the only hand. The Sales launch says dots can use the same plugins. A dot is an agent that runs when you are not in the conversation. A plugin connected with an administrator login, available to an always-on agent, is the configuration to think about before the convenience of the invoice example makes the decision for you.
  • Where the record lives. Campfire writes OAuth tool calls to a connection audit history. Xero keeps every action in Xero. For the rest, the trail of what the chat did is the ledger's own audit log, which shows the connected user's name, not the fact that a chat made the change. If three people share one QuickBooks admin login, which is more common than anyone admits, the log will say the same name for all of them and for the agent.
The same connection in two companies. Top: a large firm, where the chat connects through a small account with a narrow gate and the big accounts stay behind their own locks. Bottom: a small one, where the only account is the owner's, the gate is the full width of the ledger, and the chat walks through it carrying the owner's name. Nothing in the chat or the plugin is different between the rows. Only the shape of the account it was given.
The same connection in two companies. Top: a large firm, where the chat connects through a small account with a narrow gate and the big accounts stay behind their own locks. Bottom: a small one, where the only account is the owner's, the gate is the full width of the ledger, and the chat walks through it carrying the owner's name. Nothing in the chat or the plugin is different between the rows. Only the shape of the account it was given.

The two reactions that both get this wrong

Nobody here is connecting ChatGPT to the books

The install is a plugin in a desktop app, on plans a growing company already pays for, and the first worked example OpenAI chose is a contractor turning emails into invoices. That is the busiest person in a small business being offered the end of their least favourite hour. Someone on your team will try it, and on OpenAI's model they are entitled to: users connect their own accounts. The admin control exists, OpenAI says workspace admins choose which apps are enabled, but it has to be set, and it only exists at all if your ChatGPT is a Business or Enterprise workspace rather than a collection of personal accounts. On personal accounts, every employee is their own admin. The decision is not whether the connection happens. It is whether the account it uses was chosen or inherited.

Block it, like Xero did

Xero's read-only line is a reasonable product decision for Xero, and it gives Xero customers something QuickBooks customers do not get for free: a hard fence. But copying it by refusing the plugin leaves the problem and loses the benefit. OpenAI's second clause, computer use for apps without a plugin, means a person who wants the chat to enter invoices can get it to do so by letting it drive the screen, with no plugin, no admin toggle and no audit entry anywhere but the ledger's. The read-only vendors made the agent's reach narrow on their side. On QuickBooks the narrowing is yours to do, and refusing the plugin is the one way to make sure it is done by nobody.

The encouraging part

Every control you need already exists and costs nothing. QuickBooks Online lets you add a user with less than administrator access. OpenAI lets a workspace admin choose which apps are enabled and, per the Sales launch, review the actions they can use. QuickBooks has a close-the-books date that stops edits to past periods. The Accounting plugin, by OpenAI's own description, saves your templates, instructions and review checks as reusable skills, which means the review step you want can be written into the process once rather than remembered every month. None of this is new technology. It is the ordinary discipline of giving a new member of staff their own login with the access their job needs, applied to a member of staff that happens to be a chat window.

What to decide this week

  • Find out whose account the chat would inherit. Open your ledger's user list. If the only administrator is a founder or operations lead and that is the account that would be used to connect, that is the finding. For QuickBooks Online, count how many people know that login.
  • Make the agent its own user. Before anyone connects QuickBooks to ChatGPT, create a dedicated user in the ledger for the connection, with the least access the first workflow needs. Invoices and estimates for an invoicing workflow. Reports only for a reporting one. No payroll, no banking, no user management, until a workflow that needs them has been designed and reviewed. The audit log will then say the agent's name, which is the whole point.
  • Decide which plugins are enabled, as an admin, in writing. If your ChatGPT is a Business or Enterprise workspace, go to the admin console and set which finance plugins members may install, as OpenAI's own Sales instructions describe. If your company runs on personal ChatGPT accounts, this control does not exist, and that is a reason to move the people who touch money onto a workspace before the plugins arrive on their own.
  • Test the write path on a copy. Before the first real invoice, run OpenAI's own example against a QuickBooks sandbox or a test company, and look at what state the invoice is in when you are asked to review it. Draft, sent or posted. The answer decides whether your review is a gate or a receipt.
  • Turn on the close. Set the close-the-books date in QuickBooks and give the password to the bookkeeper, not to the account the chat uses. Campfire enforces closed periods on its side; for QuickBooks, you do.
  • Pick one workflow and write its checkpoint. OpenAI's four jobs are a good menu: draft entries, gather records, check workpapers, reuse the process. Choose one, say exactly what the chat may create and what it may only propose, and put the human check where the risk is, which for most small businesses is anything that moves money out, changes a customer's details or touches payroll.
  • If you are on Xero, BILL or FreshBooks, read the line you have been given. Read-only today is the vendor's decision, and vendors change decisions. Xero's blog post already describes moving from insight to action back in Xero. Treat the current fence as a head start on the above, not a reason to skip it.

Why this is worth getting help with

The invoicing example on OpenAI's page is a genuinely good workflow for a small business, and the time it saves is real; OpenAI's own testimonials put a controller's reporting at five to six hours a month saved and a business owner's subcontractor invoicing at five to six hours a week. The difficulty is that the shortest path to that time is the owner's login, and the safe path is a dozen small decisions that nobody on a fifteen-person team has done before: which user the agent gets, which actions, which plugins, where the checkpoint goes, how to test the write path, and what the audit trail must show. That is the shape of our AI Ops Automation Sprint. We take one named workflow, in this case the one your finance person most wants rid of, design it with human-in-the-loop checkpoints where money moves, build it into the tools you already run, including the ledger permissions and the workspace settings above, and hand it over working in about three weeks. One workflow done properly is how a company finds out what the second one should be. If you read the step about the administrator login and recognised your own company, that is the conversation to have before anyone clicks Connect.

Sources

Keep reading

AI Ops Automation Sprint

The invoice workflow is worth automating. The owner's login is not the way to do it.

In about three weeks we take one finance workflow, give the agent its own account with the access that job needs, put the human checkpoint where money moves, wire it into the ledger and workspace you already run, and hand it over working. One workflow, done properly.