How an AI agent for QuickBooks works

An AI agent for QuickBooks connects to QuickBooks Online through OAuth 2.0, with no API keys, and reads or drafts work such as unbilled jobs and overdue invoices. Tokens expire (one hour for access, 100 days for refresh), webhooks carry only record IDs, and updates replace the whole record. Your office manager or bookkeeper should approve anything that changes the ledger or reaches a customer.

An AI agent for QuickBooks is a program that reads your books through Intuit's API, notices what needs a human (an invoice 30 days past due, a finished job nobody billed, a customer who paid but still shows open) and drafts the next step for your office manager to approve. For a service company the books are where field work turns into money, so the useful agents sit between QuickBooks and the software your crew uses all day. The one rule that matters most: a person approves anything that changes the ledger or goes to a customer.

This guide covers what QuickBooks already includes, how an outside agent connects, the technical limits that trip up builds, and what to keep with your bookkeeper.

What QuickBooks already does

Check this first so you don't pay twice. Intuit has added AI agents to QuickBooks Online. According to a vendor's rundown of the agents, there is an Accounting Agent that categorizes transactions and flags anomalies, and a Payments Agent that predicts late payments and sends invoice reminders. Which agents you get depends on your plan. The same article says the agents work inside the ledger and do not update your field service software or message your team, and that bookkeepers still advise "trust, but verify."

That article is written by a company that sells an AI assistant, and the plan details come from Intuit's marketing, so check them in your own account. The takeaway is simple: reminders and categorizing are covered. The gaps are across systems.

Where the built-in tools stop

QuickBooks sees invoices. It does not see that a job finished on Tuesday and nobody created the invoice, because that fact lives in ServiceTitan, Jobber or Housecall Pro. For a trades company the expensive gaps are these:

Unbilled work. Completed jobs with no invoice. See unbilled work.
Slow collections. A reminder that goes out on a schedule and ignores the customer who just called about the balance. See invoice reminders.
Two sources of truth. The field system says paid, QuickBooks says open.
The owner's morning view. Cash in, money owed, jobs done but not billed, in one place.

How an agent connects to QuickBooks

QuickBooks Online uses OAuth 2.0 only, according to one developer guide. There are no API keys. The company owner (or an admin) approves the connection once, and the agent then holds tokens.

Three details matter in practice:

Tokens expire. Intuit's own sample code says the access token is valid for one hour and the refresh token for 100 days before you must re-authorize. The developer guide adds that the refresh token changes each time you renew, so a build has to store the newest one. A connection that nobody watches simply dies, and the agent goes quiet.
Limits. One guide puts the cap at about 500 requests per minute per company, with batches of up to 30 operations, and says going over returns an HTTP 429. Those numbers are approximate, so read Intuit's current limits page before you size a build.
Webhooks are thin. The developer guide says notifications cover 24 entity types (including invoices, payments, estimates and customers) and that "webhook payloads only contain entity IDs and operation types," so the agent has to fetch the record afterward. The limits guide recommends pairing webhooks with periodic checks because notifications can be delayed or duplicated.

Connecting ChatGPT to QuickBooks

We found no direct ChatGPT connector from Intuit in our research. An assistant would need the OAuth connection above and a place where your bookkeeper approves what it drafts. Without that second part, a chatbot with access to your books is a risk, not a helper.

What an agent does around QuickBooks

These are illustrations of the pattern, not a client story.

Agent	Starts when	Reads	Drafts	Person approves
Unbilled work finder	A job is complete in the field system with no matching invoice	Job records, QuickBooks invoices	A list of jobs to bill, with the likely invoice	Office manager
Collections follow-up	An invoice passes a set number of days overdue	Invoice, balance, last contact	A personal reminder, or a call note	Office manager
Payment match	A payment arrives	Payment, open invoices	A suggested match	Bookkeeper
Owner cash report	Every morning	Invoices, payments, aging	One summary	None, it only reads

Setup steps and what you need

A QuickBooks admin who can approve the app connection.
A read-only start. Let the agent read for two weeks and compare what it says with your own numbers before it drafts anything.
Access to the field system and phone provider, so the agent can see what QuickBooks can't.
One person per agent approving drafts, usually your office manager or bookkeeper.

Updates in QuickBooks replace the whole record, according to the developer guide, which says partial updates are not supported and that each change must carry the record's current version number. An agent that edits an invoice from stale data can wipe out fields. This is one reason we start with agents that read and draft, not agents that write to the ledger.

Limits and risks

Money moves stay human. Writing off a balance, issuing a credit or voiding an invoice is the owner's or bookkeeper's call.
Accuracy is a real problem. In the Federal Reserve's survey of small firms already using AI, 46% named accuracy as a top challenge. That is a reason to review drafts, not to avoid them.
Double reminders. If QuickBooks sends its own payment reminders and an agent also writes to the customer, pick one for each stage.
Upkeep. Tokens expire, limits change and fields get renamed. Someone has to own that, which is the reason for managed AI operations.

Where Cortex fits

Cortex builds AI agents that work inside the software you already run, with a person approving anything that changes your books or reaches a customer. We are not an Intuit partner, and we'll say so when QuickBooks' own tools are enough. See what we connect on integrations, and read how the same pattern works for Jobber. The approval model is explained under human-in-the-loop AI.

The free AI Operations Audit looks at your field software, phones and books in 30 minutes and tells you which job to hand an agent first.

Questions people ask

Does QuickBooks have AI built in?

Yes. A vendor's rundown describes an Accounting Agent that categorizes transactions and a Payments Agent that predicts late payments and sends reminders, with access depending on plan. Check your own account for what your plan includes.

Does QuickBooks Online have an API?

Yes. It uses OAuth 2.0 only, with no API keys, according to a developer guide. The owner or an admin approves the connection once, and the app then holds tokens that must be refreshed.

Can I connect ChatGPT to QuickBooks?

We found no direct connector from Intuit. An assistant would need the OAuth connection and a place where your bookkeeper approves what it drafts, because a chatbot with write access to your books is a risk.

Does QuickBooks support webhooks?

Yes, for 24 entity types including invoices, payments, estimates and customers. Payloads carry only record IDs and the operation, so the agent fetches the record afterward. Notifications can be delayed or duplicated.

How do I keep an AI agent from changing the wrong thing in my books?

Start read-only for two weeks, compare its output to your own numbers, then let it draft while a person approves. QuickBooks updates replace the whole record, so edits from stale data can erase fields.