Yes. A QuickBooks AI agent in Insulin can create an invoice, email it to your customer, record the payment against it, and void or delete it, if its access to QuickBooks allows each step. One setting per agent decides that, Read-only, Edit or Full, and no QuickBooks action waits for a person to approve it first, wherever the agent is asked. So the decision that matters is made before anyone asks: which agent gets which level.
This is about an outside agent reaching into your books. Intuit also builds AI into QuickBooks Online itself, described in its overview of Intuit AI in QuickBooks Online, and runs its own QuickBooks MCP server, which you can add as a separate connection. Tools from an MCP server you add get their level from their names, not from the table below.
Who should get which QuickBooks access?
Most people’s agents should only read QuickBooks, one organization agent should edit it for the receivables team, jobs should only read, and no agent should hold Full. The level decides which of the integration’s 16 tools an agent receives. The full tool list gives each one’s level; the table below puts them where they matter.
| Who gets QuickBooks | Access level | What that level adds in QuickBooks | What waits for a person | The record it leaves |
|---|---|---|---|---|
| A member who connects their own QuickBooks and changes nothing | Full, the default | Every tool, including void-invoice, delete-invoice and deactivate-customer | Nothing, in a web chat, a Slack DM or Teams | The tool calls in that member’s own conversations |
| The built-in assistant and personal agents, once narrowed | Read-only | Look-ups only: list-invoices, list-customers with open balances, get-report (aged receivables, profit and loss and more), query (one SELECT), get-entity, get-account | Nothing needs to | The tool calls in that member’s own conversations |
| One organization agent for accounts-receivable staff | Edit | Create and change customers, invoices and items; send-invoice emails the customer; create-payment records a payment | Nothing | The tool calls in each asker’s own conversation |
| Any job that touches QuickBooks | Read-only, set on the agent that creates it | Look-ups for a scheduled report | Nothing; a job run never pauses | The run’s Steps tab, which only the job’s owner can see |
| Nobody | Full | void-invoice, delete-invoice, deactivate-customer | Nothing would | A voided invoice stays in QuickBooks at zero; a deleted one is gone |
The first row is the one to fix first, and nobody chose it.
Does anything wait for approval before an agent writes to QuickBooks?
No. Posting a Slack message is the only action that pauses for approval; creating, changing, voiding or deleting a QuickBooks record never does. The approval card appears in a solo web chat on its main thread, in a Slack DM with the assistant, and in a Slack channel where someone @mentions it. Even there it guards a Slack post, because other people can read it the moment it is sent. For a channel mention, the docs spell it out: creating or changing a record doesn’t wait, and “what bounds them is the access you gave each connection.”
Four surfaces show no card at all, and the action isn’t held back:
- an Insulin channel, where every member who can send messages can address the agents in it;
- a Microsoft Teams DM with the assistant;
- a reply inside a sub-thread in the web workspace;
- a job run.
What that leaves to you: there is no second approver for an agent’s writes, so the access level is the control, and a review of what agents did in QuickBooks is yours to run.
Which agents have Full access that nobody chose?
Any agent with QuickBooks that nobody narrowed. An integration left alone runs at Full, for custom agents and for the built-in assistant alike. When a member connects their own QuickBooks under User Integrations, the assistant can reach it at once, in the web workspace, in Slack and in Teams, with void-invoice and delete-invoice among its tools. A Slack DM saying “void Globex’s March invoice, it went out twice” is enough, and nothing waits.
QuickBooks narrows nothing on its side either. Only QuickBooks Online admin users can connect and manage apps, Intuit says, so whoever authorized a connection, personal or organization-wide, was an admin. There’s no limited QuickBooks user to connect with instead. The agent’s access level is the only narrowing there is.
To narrow the assistant, open a chat with it, click the pencil in the conversation header and set QuickBooks to Read-only under Integrations (where the assistant’s levels are set). The levels narrow the assistant for you alone, so every member who connects QuickBooks has to do it for themselves. On a custom agent, the select beside QuickBooks in its Integrations list starts at Full as well; set it before the first chat.
What does one Edit grant let an agent do in QuickBooks?
Run the whole receivables cycle: create the customer and the invoice, email the invoice, and record the payment, with no second person anywhere in it. Edit adds seven tools to the look-ups: create-customer, update-customer, create-invoice, update-invoice, send-invoice, create-payment and create-item. Three of them behave in ways to know before you grant them:
send-invoiceemails the invoice to the customer from QuickBooks, “optionally to a different address.” A wrong address in the request,ap@globex.exampleinstead ofbilling@globex.example, sends your invoice to whoever reads that inbox.update-invoicechanges only the fields given, but “lines, when given, replace all of the invoice’s lines.”create-paymentrecords a customer payment, optionally applied to invoices, and “whatever isn’t applied stays as a credit.”
One safeguard is built in: the create tools accept a request ID, so a create sent again unchanged after a timeout returns the record it already made instead of a second invoice.
Because one grant holds every step, an Edit agent is the case segregation of duties exists for. There’s no maker-checker step for agent actions (segregation of duties for AI agents maps which duties are separated and which aren’t), so the separation comes from who can use the agent:
- Make it an organization agent. Only org admins create one, and only an org admin can change its integrations, so nobody can quietly raise its QuickBooks level. It uses the organization’s connection, with the access of the Intuit user who authorized it.
- Set QuickBooks to Edit, not the default Full.
- Share it by name, as USER, with the people who raise invoices. Not org-wide: an organization agent shared with everyone can be added to an organization channel by anyone who can use it, and in a channel every member can ask it to write, with no card.
It’s the setup recommended for an AI agent for Stripe that answers a team’s questions, with more at stake here: those Stripe tools read and preview tax, while these write to the ledger and email your customers.
Why should a scheduled QuickBooks job only read?
Because a job run never pauses, and only one person can see what it did. A job runs as the agent that created it, with that agent’s access, so a job set up through an Edit agent can write with Edit. Its runs never show an approval card. What a run did lands on its Steps tab, every tool call with its Args and its Result or Error, and a job is private to its owner, organization administrators included.
So create QuickBooks jobs from an agent whose QuickBooks access is Read-only. A weekly receivables summary needs nothing more: “Every Monday at 9, list unpaid invoices more than 30 days past due, by customer, with the aged receivables total” uses list-invoices and get-report. Anything that writes belongs in a web chat, where the person who asked sees each call and can expand its inputs and outputs.
Why should no agent void or delete in QuickBooks?
Because Full’s three extra tools remove records, and one of them can’t be reversed. Full adds:
void-invoice: the invoice “stays on record, but every amount becomes zero. This cannot be undone.”delete-invoice: deletes the invoice permanently. To keep a record of it, the tool’s own description says, void it instead.deactivate-customer: makes a customer inactive, “QuickBooks’ delete for customers”: hidden from lists and forms, with its history kept. Its name doesn’t say delete, which is why the access-level table names it among Full’s tools.update-customer, an Edit tool, reactivates it.
Voids and deletes are corrections to the books, and a correction is a step for a person in QuickBooks, not a request in a chat. How to stop an AI agent from deleting records makes the same case for every integration, including the tools whose names hide a delete.
An app built on QuickBooks follows the same three levels. A grant to an app starts at Read-only, and in QuickBooks Online voiding or deleting a record, a batch request, and any change to the company’s preferences or company info need Full, even where they look like edits.
What does the QuickBooks connection carry?
One company, with the access of the Intuit user who authorized it, and per Intuit that user is an admin. The rest follows from that:
- One company per connection. Each connection reaches the company chosen when it was authorized, and every tool works only there. To switch companies, disconnect and connect again.
- The authorizer’s account matters. The organization’s connection works “with the access of the Intuit user who authorized it” and stops if that person loses access to the company, so authorize it with an account that will stay with the company.
- Disconnecting removes access, not records. It takes the tools from every agent straight away and changes nothing in QuickBooks: customers, invoices and payments the agents created stay. The authorization at Intuit stays too, until an admin disconnects the app in QuickBooks under Integrations → Manage integrations, then Action → Disconnect.
- It isn’t a revenue sync. The connection gives agents and apps tools for one company’s records, and every write is one an agent or app makes on request. It doesn’t map marketplace transactions or payouts into your ledger; ERP reconciliation runs on Oracle NetSuite.
Integrations, access levels and sharing sit together on every agent; the agents overview shows how they fit.
Sources
Primary sources for the platform rules cited above. Last verified November 12, 2026. Providers change their products, prices and terms without notice — check the source before relying on a detail.
- Fours docs: QuickBooks integration — Overview: one QuickBooks company per connection, every tool working only on that company; Org-Level vs User-Level: organization agents an admin gives QuickBooks to using the org connection with the access of the Intuit user who authorized it, and each person's own connection used by their own agents and the Insulin assistant; Prerequisites: prefer an account that will stay with the company, the connection stopping if the authorizing person loses access, and connecting an org-level integration admin-only; Edit Integration: connecting a different company means disconnecting and connecting again; Delete Integration: agents losing their QuickBooks tools straight away, nothing changed in QuickBooks, and the authorization on Intuit's side removed only from the company's connected apps; Fours AI Tools: the 16 tools by Read-only, Edit and Full, including send-invoice optionally to a different address, update-invoice lines replacing all lines, create-payment leaving what isn't applied as a credit, void-invoice keeping the invoice at zero and not reversible, delete-invoice permanent, deactivate-customer as QuickBooks' delete for customers reactivated by update-customer, and the request ID that returns an existing record instead of a duplicate; the tip on Intuit's own QuickBooks MCP server
- Fours docs: Integrations, Agent access levels — Agent access levels: Read-only, Edit or Full set per integration on a custom agent and in the built-in Insulin assistant for each integration you connected yourself; an integration never narrowed running at Full; deactivate-customer named among the Full tools as how QuickBooks deletes a customer; tools from an MCP server you add yourself judged by their names
- Fours docs: Insulin Agents — User-Level vs Org-Level Agents: only org admins create org-level agents, which use only org-level integrations; Integrations and Knowledge Bases: Read-only, Edit and Full per integration, Full the default, editing an organization agent's integrations requiring org administrator access; What the Insulin assistant may do with your integrations: every connection reachable, narrowed from the pencil in the conversation header, an integration left alone staying at Full, the levels narrowing it for you alone; Sharing Agents: ADMIN, EDITOR and USER, org-wide sharing as EDITOR or USER; Tool Calls: inputs and outputs expandable; Tool Approvals: posting a Slack message the action that pauses, the card offered in a solo web chat on the main thread and in Slack, and not offered, the action not held back, in an Insulin channel, a Microsoft Teams DM, a sub-thread reply or a job run; What Insulin can do when mentioned in a channel: only posting a Slack message waits, and creating or changing a record doesn't, bounded by the access given each connection; Microsoft Teams: no approval card
- Fours docs: Insulin Channels — Organization channels taking only org-level agents; Adding Members: an agent shared with the whole organization addable by anyone who can use it, any other organization agent only by its owner or someone with ADMIN on it; sending messages needing USER or higher; How Agents Participate: the tool-approval card not appearing on channel turns
- Fours docs: Insulin Jobs — How Jobs Are Created: a job runs as the agent that created it, with that agent's access to integrations, and is private to its owner, organization administrators included; Runs: the Steps tab's tool-call transcript with each call's Args and Result or Error
- Fours docs: Insulin Apps, Connected Integrations — Connected Integrations: QuickBooks Online among the services an app can be granted, a new grant starting at Read-only, and in QuickBooks Online voiding or deleting a record, a batch request and any change to the company's preferences or company info needing Full
- Fours docs: MCP (Model Context Protocol) — Intuit QuickBooks in the catalog of MCP servers you can add
- Fours docs: Stripe integration, Fours AI Tools — Both Stripe connections give Fours AI the same tools, which read the account and preview tax, the comparison drawn in the Edit section
- Fours docs: ERP Reconciliation — Oracle NetSuite the native ERP integration for reconciliation; QuickBooks Online giving AI agents tools for one company's records but not mapping marketplace transactions or payouts into the ledger
Keep reading
Stay Updated
New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.
Follow Fours on LinkedIn