QuickBooks AI agents: Native AI, API and Finance Automation
Understand QuickBooks native AI and build governed finance operations on Major, with eight documented API endpoints, review queues, approval workflows, and accounting controls.

QuickBooks AI agents include Intuit's built-in accounting assistants and agents you build to work across finance systems. This guide covers native AI, the QuickBooks Online API, and governed automation on Major, where deterministic apps hold the records and agents handle judgment.
For finance managers and controllers, the useful starting point is an exception queue, not unrestricted access to the books.
What QuickBooks does for finance teams
QuickBooks Online holds the accounting records that billing managers, bookkeepers, and controllers rely on: customer invoices, vendor bills, payments, and journal entries. The distinctions matter. A customer invoice records money owed to the business; a vendor bill records money the business owes a supplier. Intuit documents those as separate Invoice and Bill objects.
A professional-services billing manager needs approved time converted into accurate customer charges. An AP manager needs supplier liabilities recorded once, against the right vendor. A controller needs evidence explaining why operational records and the ledger disagree before approving an adjustment.
Major provides the deterministic app layer around those jobs. An agent can build a review app with managed database tables for source IDs, proposed matches, approvals, and posting outcomes, then run that software for repeatable checks. The agent interprets ambiguous descriptions or conflicting evidence. People review consequential changes through the app instead of reconstructing a conversation. QuickBooks remains the accounting system of record throughout.
QuickBooks AI agents built into the product
Intuit's native agent announcement names several capabilities worth evaluating before adding another process:
- Accounting Agent: automates bookkeeping and transaction categorization and assists with reconciliation.
- Payments Agent: predicts late payments, tracks invoices, and creates and sends invoices and reminders.
- Finance Agent: supports reporting, KPI analysis, forecasting, and scenario planning for growing businesses.
- Customer Agent: supports lead handling, personalized replies, meetings, and sales opportunities within Customer Hub.
These are useful inside Intuit's product experience. Availability depends on the product, market, and rollout; an announcement is not evidence that every company account includes every feature. Nor does a named product agent imply that its interface is exposed through the Accounting API.
Major adds a different layer when the evidence lives elsewhere. Approved Harvest time, a property work order, and an accounting record may need one shared review process. The Major agent assesses exceptions across that context; an app preserves the evidence and decision history; a workflow coordinates approvals and authorized actions. Start with the native capabilities already available, then build the cross-system control surface your finance team lacks.
How QuickBooks connects to Major
Major has a native QuickBooks connector (quickbooks). It is not a custom API connector. IT sets up the company connection once, stores credentials centrally in the connector vault, and scopes which apps, agents, and workflows may use it. Credentials never belong in application code or prompts.
The underlying Intuit authorization model uses OAuth 2.0 access and refresh tokens associated with an authorized QuickBooks Online company. The company realm ID belongs in the request context, not in an agent's guess about which business to update.
Major orchestrates QuickBooks; it never replaces it. Start with read operations for a specific company, then separately authorize the workflow actions that can change accounting records. Do not assume that every API operation documented below is automatically exposed to every agent through the connector.
SSO, RBAC, and audit logs cover the app, agent, and workflow. A finance reviewer can work from an exception queue without receiving the connector's credentials, while IT retains a central place to control access and investigate activity.
QuickBooks Online API guide
The entity reference lists production at https://quickbooks.api.intuit.com and sandbox at https://sandbox-quickbooks.api.intuit.com. The paths below preserve Intuit's placeholder spelling. Substitute the authorized company and actual record IDs.
Authorization, pagination, and operating limits
The accounting scope is com.intuit.quickbooks.accounting. Use the OAuth authorization-code flow, not an invented personal API key. Enforce narrower action permissions in Major rather than treating this as an invoice-only scope.
Data queries paginate with STARTPOSITION and MAXRESULTS inside the select statement. The documented maximum is 1,000 entities per query response. Persist page progress so a restarted import does not begin again blindly.
The same limits page specifies 500 requests per minute per realm and 10 requests per second per realm and app. HTTP 429 means wait 60 seconds before retrying. Remaining-quota response headers are not documented on that page; capture the documented response header intuit_tid for support correlation rather than inventing a quota counter.
Events and safe testing
Webhook configuration covers entity operations such as create, update, and delete, with support varying by entity. Verify the intuit-signature header against a Base64-encoded HMAC-SHA256 of the original payload, using the app's verifier token as the key.
Delivery guidance requires HTTP 200 within three seconds. Retries progress through 10, 20, and 30 seconds; five and 20 minutes; two, four, and six hours; then six-hour intervals. Queue processing separately, expect out-of-order delivery, and reconcile missed changes.
Use a sandbox company and development authorization before production, as described in the OAuth guide. Test duplicate notifications, expired authorization, partial failures, and approval changes, not only successful posting.
Create customer billing: POST /v3/company/<realmID>/invoice
Creates an Invoice for customer billing, with customer and line-item references validated against the actual company.
- App: stores the source billing group and resulting invoice ID.
- Agent: drafts descriptions from approved project work and flags unclear charges.
- Workflow: submits the reviewed invoice after a billing manager approves the payload.
Read an invoice: GET /v3/company/<realmID>/invoice/<invoiceId>
Retrieves an existing Invoice so review uses current accounting evidence rather than an old export.
- App: displays the invoice alongside its source billing packet.
- Agent: explains a difference between billed services and approved work.
- Workflow: refreshes the record before completing a reconciliation task.
Read customer identity: GET /v3/company/<realmID>/customer/<customerId>
Retrieves a Customer record for an established customer mapping.
- App: shows the linked accounting customer on a project review screen.
- Agent: assesses evidence when a trading name differs from a project label.
- Workflow: verifies the selected customer before invoice creation, stopping unresolved mappings.
Query records: GET /v3/company/<realmID>/query?query=<selectStatement>
Runs the supported query language against accounting entities, including JournalEntry.
- App: maintains a paginated accounting evidence cache with refresh timestamps.
- Agent: reviews a bounded set of candidate records for a disputed match.
- Workflow: imports the review period and persists the last completed page.
Read payment evidence: GET /v3/company/<realmID>/payment/<paymentId>
Retrieves a Payment, including its recorded transaction context.
- App: presents payment evidence next to the invoice being reviewed.
- Agent: explains an ambiguous payment allocation using the linked records.
- Workflow: refreshes payment evidence before routing a collections exception.
Record supplier liability: POST /v3/company/<realmID>/bill
Creates a Bill for accounts payable, distinct from customer invoicing and from paying the vendor.
- App: stores the source bill ID and approved QuickBooks mapping.
- Agent: evaluates a suspected duplicate or inconsistent vendor description.
- Workflow: posts an approved bill only after checking existing synchronization ownership.
Inspect a journal entry: GET /v3/company/<realmID>/journalentry/<journalentryId>
Retrieves a JournalEntry for review of its accounting lines and current version.
- App: preserves the entry snapshot used during close review.
- Agent: explains how an entry relates to operational evidence.
- Workflow: refreshes the entry before a reviewer signs off on an exception.
Post an approved adjustment: POST /v3/company/<realmID>/journalentry
Creates a JournalEntry whose debit and credit lines must balance.
- App: stores the proposed lines, approval, and returned entry ID.
- Agent: proposes treatment and explains uncertainty for the controller.
- Workflow: validates accounts and totals, obtains approval, and posts the authorized payload.
QuickBooks automation use cases on Major
Harvest time to customer billing
- App: maps approved Harvest entry IDs to a billing packet and QuickBooks invoice, preventing rebilling.
- Agent: groups work into readable descriptions and flags missing rates, approvals, or conflicting customer names.
- Workflow: runs at billing cutoff, checks completeness, requests manager approval, and submits the reviewed packet.
- QuickBooks endpoints: customer read, invoice create, and invoice read from the linked guide above.
Bill.com approval to AP review
- App: holds vendor mappings, source bill IDs, duplicate candidates, and posting status.
- Agent: distinguishes a repeated supplier invoice from a legitimate similar charge.
- Workflow: checks whether an existing sync already owns posting, then routes an approved new liability to QuickBooks only when appropriate.
- QuickBooks endpoints: query and Bill create. A supplier liability should not become a customer Invoice simply because both systems use the word invoice.
AppFolio maintenance to accounting evidence
- App: links the work order, completion evidence, supplier charge, and accounting record.
- Agent: explains discrepancies between completed work and the proposed liability.
- Workflow: collects evidence after completion and sends unresolved amounts to the controller; it does not treat a completed job as payment authorization.
- QuickBooks endpoints: query, Bill create, and journal-entry read. An adjustment uses journal-entry create only after separate approval.
These are design patterns grounded in finance operations, not claims that every source system exposes the same triggers or that its connector has every required action. Validate those permissions and API access during discovery.
How to build the QuickBooks review architecture on Major

QuickBooks and Harvest evidence enters a governed Major review process.
Build the review app before enabling writes. Its managed database should distinguish the source transaction, proposed action, approved payload, and confirmed accounting result. Those are different states, even when the happy path completes quickly.
- Connect: IT authorizes QuickBooks and the required source system with scoped credentials.
- Collect: a scheduled or event-triggered workflow fetches evidence and runs deterministic validation.
- Assess: the agent interprets the exceptions that identifiers, amounts, and existing mappings cannot resolve.
- Review: the app displays the evidence, recommendation, and requested approval.
- Execute: the workflow submits only the approved action and records the result.
Index records by company and source ID, not display name alone. Store approval status separately from posting status so a timeout cannot masquerade as success. Keep the run resumable when a reviewer returns tomorrow. Once the checks are implemented in software, repeated imports run the same logic without asking the agent to reason through every record again. Reason once. Run forever.
A worked billing example with numbers
For example, consider a services finance team reviewing 200 billing packets each month. This is illustrative arithmetic, not a customer result or a performance promise.
Before automation, assume each packet takes six minutes to assemble, compare, and enter. That is 200 × 6 = 1,200 minutes, or 20 hours. The repetitive work is finding approved hours, checking the customer mapping, and comparing totals.
With a Major review app, suppose 160 complete packets take one minute each for manager review. The remaining 40 need five minutes each because rates or descriptions conflict. Add 40 minutes for the monthly run check and follow-up. The new total is 160 + 200 + 40 = 400 minutes, or six hours and 40 minutes, a difference of 800 minutes, or 13 hours and 20 minutes.
The workflow still pauses every proposed invoice for approval. The agent explains the 40 exceptions; it does not invent missing rates. The app retains the source IDs and invoice mapping, so rerunning the month does not turn the illustrative time saving into duplicate revenue.
Governance and failure handling for accounting work

Exact checks and human approval take different paths, with shared audit state.
Let read-only checks and evidence collection proceed automatically. Require an accountable reviewer before creating liabilities, posting adjustments, changing accounting mappings, or sending consequential external communications. The agent must never approve its own proposal, change vendor banking details, or initiate payment as a side effect of bill review.
Make approval bind to the precise payload. If a rate, account, currency, or amount changes afterward, invalidate the approval. For updates, Intuit's JournalEntry reference documents SyncToken version checks; refresh stale evidence rather than overwriting another user's work.
Use company plus source ID for duplicate protection. After an uncertain write timeout, investigate whether the record exists before resubmitting. Back off on 429 responses, and send persistent authorization or validation failures to a visible queue.
Retain input references, deterministic check results, agent rationale, reviewer identity, approved payload, request correlation, and returned record ID. Follow Intuit's webhook reliability guidance with asynchronous handling and catch-up reconciliation rather than assuming every notification arrives once and in order.
QuickBooks AI Apps, Agents and Workflow Automations
Every published Major use case that works with QuickBooks, newest first. Each one names the QuickBooks API objects involved and shows the app, agent and workflow split.
- AI Agents for Business: 6 Workflows That Run Reliably: See practical AI agents for business, from lead routing to invoice review, and learn how Major makes repeatable work stateful, governed, and dependable.
- AI Agent to Reconcile Stripe Payouts in QuickBooks: Build an AI agent to reconcile Stripe payouts in QuickBooks Online: code matches the exact deposits, the agent explains ambiguous ones, and a person approves.
- AI Agents for Finance: Use Cases for FP&A and RevOps: Six finance agent use cases for FP&A and RevOps teams, and how to build the month-end close agent on Major with read-only access to QuickBooks, Stripe and Salesforce.
- AI Agents for Accounting: 6 Auditable Close Workflows: AI agents can reconcile, match invoices, and draft close commentary. The question accountants actually ask is whether they are auditable.
- Enterprise AI Agents: What "Enterprise-Grade" Actually Means: Enterprise-grade means deterministic execution, durable state, scoped credentials and audit trails at the point of action. Here is how to evaluate an agent and build one on Major.
Frequently asked questions
Does QuickBooks have its own AI agents?
Yes. Intuit documents Accounting Agent for bookkeeping and reconciliation assistance, Payments Agent for invoice tracking and collections, and Finance Agent for financial analysis. Availability varies by product and rollout. These native capabilities are distinct from agents you build on Major.
How do QuickBooks AI agents connect to Major?
Major has a native QuickBooks connector. IT configures the authorized company connection once, keeps credentials in the connector vault, and grants apps, agents, and workflows only the actions their process needs.
Which OAuth scope does the QuickBooks Accounting API use?
The documented accounting scope is com.intuit.quickbooks.accounting. Authorization produces access and refresh tokens tied to an authorized QuickBooks Online company. Enforce narrower read and write boundaries through Major permissions rather than assuming an invoice-only OAuth scope.
Can an AI agent post journal entries automatically?
The API supports creating journal entries, but this design requires controller approval before posting. The agent proposes the accounting treatment; deterministic checks validate balanced lines and permitted accounts, and the workflow submits only the approved payload.
Can QuickBooks automation create supplier invoices?
For accounts payable, use the Bill object for money owed to a vendor. Invoice represents customer billing. Confirm whether an existing integration already posts the source bill before enabling a second write path.
Does this guide apply to QuickBooks Desktop?
No. The endpoints, OAuth flow, company identifiers, and sandbox described here apply to QuickBooks Online. A QuickBooks Desktop integration needs separate technical discovery rather than reusing these REST paths.
Sources
Official Intuit pages used for the accounting model, API operations, native AI, and operating constraints:
- Invoice reference: customer billing, creation, and record retrieval.
- Bill reference: supplier liabilities and the accounts payable object.
- Customer reference: accounting customer identity and record retrieval.
- Payment reference: payment records and their transaction context.
- JournalEntry reference: balanced lines, queries, record retrieval, and version handling.
- OAuth 2.0: authorization, access tokens, refresh tokens, and development environments.
- Scopes: the QuickBooks Online accounting authorization scope.
- Data queries: supported select statements and positional pagination.
- Limits and throttles: request budgets, query maximums, and retry guidance.
- REST API features: request and response headers for accounting calls.
- Configure webhooks: subscriptions, supported operations, and signature verification.
- Webhook best practices: acknowledgment timing, delivery retries, ordering, and recovery.
- Intuit's virtual team announcement: named native agents and rollout context.
Start building on Major
Build a QuickBooks review app that holds billing evidence, gives agents bounded judgment work, and routes accounting writes through an approval workflow.
About the author
Ritvij Gautam is Head of Growth at Major.
Last reviewed November 19, 2026 by Ritvij Gautam.
Frequently asked questions
- Does QuickBooks have its own AI agents?
- Yes. Intuit documents Accounting Agent for bookkeeping and reconciliation assistance, Payments Agent for invoice tracking and collections, and Finance Agent for financial analysis. Availability varies by product and rollout. These native capabilities are distinct from agents you build on Major.
- How do QuickBooks AI agents connect to Major?
- Major has a native QuickBooks connector. IT configures the authorized company connection once, keeps credentials in the connector vault, and grants apps, agents, and workflows only the actions their process needs.
- Which OAuth scope does the QuickBooks Accounting API use?
- The documented accounting scope is com.intuit.quickbooks.accounting. Authorization produces access and refresh tokens tied to an authorized QuickBooks Online company. Enforce narrower read and write boundaries through Major permissions rather than assuming an invoice-only OAuth scope.
- Can an AI agent post journal entries automatically?
- The API supports creating journal entries, but this design requires controller approval before posting. The agent proposes the accounting treatment; deterministic checks validate balanced lines and permitted accounts, and the workflow submits only the approved payload.
- Can QuickBooks automation create supplier invoices?
- For accounts payable, use the Bill object for money owed to a vendor. Invoice represents customer billing. Confirm whether an existing integration already posts the source bill before enabling a second write path.
- Does this guide apply to QuickBooks Desktop?
- No. The endpoints, OAuth flow, company identifiers, and sandbox described here apply to QuickBooks Online. A QuickBooks Desktop integration needs separate technical discovery rather than reusing these REST paths.