A QuickBooks MCP server lets an AI assistant use tools to query or change QuickBooks Online records, depending on the server and its permissions. Intuit's local open-source server documents supplier Bill creation. Its hosted Claude connector is a separate connection whose current help page does not list supplier-bill creation.
That distinction matters when the job starts with invoices you receive. A QuickBooks Invoice records a sale to a customer; a Bill records money owed to a supplier. A Bill Payment records payment against that payable. A connector that creates customer invoices or imports general-ledger transactions does not establish that it can create supplier bills.
For document-to-bill entry, the assistant needs more than a connection: it needs the supplier document's data, references to the correct company's vendors and accounts, and your approval of the proposed records before creation. The setup below concerns QuickBooks Online; QuickBooks Desktop uses different integrations.
Which QuickBooks MCP connections document bill creation?
The comparison below reflects the providers' published documentation as of October 2, 2026. Choose by the accounting record you need to create, rather than by whether a service carries the QuickBooks or MCP name.
| Connection | Who operates it and how you connect | Documented accounting tasks | Controls relevant to bill entry |
|---|---|---|---|
| Intuit's hosted Claude connector | Intuit hosts the connection; connect in Claude and sign in to Intuit. | Reports, general-ledger imports, customer invoices and estimates. Supplier Bill creation and Bill Payment are not listed. | Intuit documents confirmation for destructive actions. That is distinct from reviewing each proposed supplier bill. |
| Intuit's open-source QuickBooks Online MCP server | You or a technical partner run a local server using an Intuit developer app. | Bill, Bill Payment, Vendor and customer Invoice operations. | Separate switches suppress create, update and delete tools. |
| Zapier MCP for QuickBooks Online | Zapier hosts the server; connect QuickBooks, select actions and connect your assistant. | Account-based and item-based Bill creation; file or note attachment. | You select which QuickBooks actions the assistant can use. Check the available action before adding another transaction type. |
| Pilot's Meridian connector | Pilot hosts the connection; sign in and authorise the QuickBooks companies you want to connect. | Its tool list includes Bill, Bill Payment, customer Invoice, Vendor Credit and attachment upload. | Read-only or read-write access can be selected separately for each company. |
For a hosted bill-entry connection, Zapier and Meridian both document the relevant write operation. Intuit's local server is another option if someone can maintain the developer setup. The hosted Intuit connector fits its listed reporting and sales tasks; general-ledger import should not be treated as a substitute for a documented Bill tool.
If your only goal is entering a few documents, compare the extra connection work with QuickBooks Online's built-in receipt capture. An agent becomes more useful when the job also requires collecting files, preparing a recurring batch, or resolving data against existing records across client companies.
For practices handling another accounting package alongside QuickBooks, NetSuite MCP vendor-bill setup and AP controls and Xero MCP connection options for draft supplier bills cover the equivalent platform-specific decisions.
Connect Claude to the right company with restricted tools
Connecting Claude's web app and connecting Claude Code are different setup paths. For Intuit's hosted connection, open Claude's Connectors menu, find QuickBooks, select Connect and follow the Intuit sign-in. You are authorising an existing hosted service, rather than installing Intuit's open-source server.
With Zapier, connect the QuickBooks account, select the actions needed for the job and add the generated MCP connection URL to your assistant. With Meridian, sign in, connect the relevant companies and connect your agent. Its per-company access setting is useful for a practice that wants to inspect several clients' books while allowing changes in only one.
Intuit's local server needs a developer app, client ID and secret, a company realm ID and OAuth tokens. Sandbox authorisation supports a localhost callback; initial production authorisation requires public HTTPS. Afterward it runs locally over stdio as a process launched by the assistant. Follow the repository's current authentication instructions for setup.
For read-only use, Intuit documents three separate tool switches: QUICKBOOKS_DISABLE_WRITE suppresses create tools, while QUICKBOOKS_DISABLE_UPDATE and QUICKBOOKS_DISABLE_DELETE suppress their respective categories. Disabling create alone leaves update and delete tools available. These switches restrict registered tools; they do not establish a read-only QuickBooks OAuth scope.
Before permitting bill entry, verify the connection through queries:
- Confirm the company name and identifier against the client file you intend to use. A successful login does not prove that the selected company is correct.
- Retrieve an existing vendor, the accounts or items used for its bills, and a known bill. Check the returned records against QuickBooks.
- Define the allowed operations for this task. Document reading, vendor/account lookup, duplicate checks, approved Bill creation and source attachment are separate from vendor creation, transaction deletion and payment.
Use the connector's controls and your assistant's tool permissions to enforce that boundary. Where a connection offers only broad read-write access, check whether the assistant can require approval for individual write tools before using it for the batch. An instruction in the conversation to avoid payments is useful context, but it does not remove a payment tool's permission.
Turn supplier documents into bill data and accounting references
A few clear supplier PDFs can be read in the assistant's conversation. For a recurring batch, the useful output is a consistent set of rows with source references, visible review issues and an account of any pages that failed. An agent reading invoices on its own can hallucinate a value, skip a page of a long PDF, or report success over a failure, and its owner never knows.
Invoice Data Extraction turns invoices and other financial documents into spreadsheets. Its invoice extraction for AI agents lets your agent process PDF, JPG and PNG files through a hosted MCP server using an API key. The agent uploads the files with its own tools and can read typed extraction rows or download a spreadsheet. A value or a row the panel of AI agents cannot agree on is flagged as Review Needed, with what to check. Failed pages are reported with their reasons.
The accounting handoff comes after extraction. Your agent uses its separate QuickBooks connection to find existing records and prepare the proposed bills. MCP servers for invoice and receipt extraction covers the extraction connection in more detail.
Keep two sets of data visible: what the document says and how that fact will be recorded in this company.
| From the supplier document | Resolve before Bill creation | Why the distinction matters |
|---|---|---|
| Supplier name, address and identifying details | Existing QuickBooks vendor reference | A printed name is evidence for a match, not a vendor ID or permission to create another vendor. |
| Original invoice number | Bill number supplied to the chosen tool | Preserve it for later searches and duplicate checks, including meaningful letters and leading zeros. |
| Invoice date, due date and payment terms | Transaction date and applicable due date or terms reference | An invoice date must not become its payment deadline. Hold conflicting terms for review. |
| Currency, net amount, tax and total | Company-appropriate currency and tax treatment | The printed tax amount does not by itself determine the company's tax code or recoverability. |
| Line descriptions, quantities, prices and amounts | Approved expense account or existing item for each line | Account-based expenses and item-based purchases need different references. A description alone does not settle either. |
| PO reference, department/site clues and notes | Applicable class/location dimensions and memo | These depend on company settings and accounting policy; they are not mandatory for every bill. |
Inspect the selected Bill tool's schema for its required inputs. Vendor and expense-line data form the core of the proposed record; tax, currency, terms and tracking dimensions depend on the transaction, company and tool. Source filenames, page numbers and reconciliation notes belong in the review evidence even when they are not inputs accepted by the creation tool.
For example, an invoice headed “Northside Industrial Ltd” might match an existing vendor displayed as “Northside Industrial.” Confirm the identity using the document and existing vendor details before using that vendor reference. If the bill includes both replacement parts and an annual maintenance charge, retain the two lines while applying the company's approved treatment to each. Sending both to an account guessed from “industrial” would discard the accounting judgment the workflow needs.
Leave unresolved vendor, account or item matches on hold. The proposed batch should show the extracted value beside the selected QuickBooks reference and the reason for any exception, so the person reviewing it can distinguish a document-reading issue from an accounting decision.
Review the proposed batch before creating bills
Ask the agent to produce an inspectable proposal before enabling creation. For each proposed bill, show the company, supplier and selected vendor, bill number, invoice and due dates, currency, line amounts and their accounts or items, tax, total, source filename/pages, and any exception. The person should be able to move from a proposed amount to the page supporting it without searching the original folder.
Review the batch at both document and accounting level:
- Reconcile the amounts. Check quantities and prices against line amounts, then reconcile the subtotal, discounts, freight, tax and invoice total. Account for tax-inclusive pricing and rounding before treating a difference as an error.
- Identify the transaction. A credit note needs credit treatment rather than a positive Bill. A supplier statement can list invoices already in QuickBooks; its balance is not a new supplier bill. Check whether an invoice marked paid already has a recorded transaction before creating another payable.
- Resolve extraction exceptions. Inspect Review Needed items against their source pages. If a page failed, determine which invoice it belongs to and hold any affected bill until the missing evidence is recovered. A partial invoice should not be approved because its first page produced a row.
- Check the ledger for duplicates. Search within the correct company and vendor using the original invoice number. Compare dates, currency, amounts and the source where a match is ambiguous. The same invoice can arrive as both a scan and a PDF, and two different vendors can legitimately use the same number.
For the native settings and their limits, use the guide to preventing duplicate bills in QuickBooks Online. Verify how those controls behave through your chosen connection rather than assuming an MCP write receives the same warning as manual entry.
Maintain an inventory of the source documents, not just a count of extracted rows. One file can contain several invoices; one invoice can occupy several pages. Give every identified document a disposition: ready for approval, held with a reason, already recorded, or excluded with its document type recorded. Reconcile that inventory with the extraction's failed-page report and the proposed bills. Otherwise, a batch with usable rows can still conceal a missing document.
Approve bill creation separately from payment
A created Bill is a ledger record. Calling it a draft in the assistant's reply does not make the QuickBooks transaction harmless. Review the proposal while it is still outside the ledger, then authorise the specific records to be created.
OWASP's guidance on confirmation for financial MCP actions recommends explicit user confirmation for financial operations and showing the user the full tool-call parameters. This is security guidance; MCP connectivity does not guarantee that a particular connector implements an approval gate.
For a batch, the approval should identify the company, each bill's vendor and number, amounts, currency, dates, accounts/items and applicable tax or tracking fields. A readable batch summary helps you review the work, but retain access to the complete per-bill parameters behind it. If the agent changes a vendor, amount or accounting reference after approval, return that bill for review.
Keep four decisions distinct:
- Reviewing the proposed batch: you decide whether the prepared document data and accounting choices are acceptable.
- Confirming the tool call: the assistant or connector asks permission to execute particular operations.
- Following QuickBooks' native approval process: your company's subscription, settings and entry path determine what happens inside QuickBooks.
- Authorising payment: you separately decide whether, when and how the payable should be paid.
Do not assume API-created bills enter a native approval queue. Check the behaviour of your chosen entry path against the company's actual setup; QuickBooks Online bill approval workflows explains the native workflow options.
Permission to create the reviewed bills should leave Bill Payment and unrelated writes outside the task. A missing vendor is an exception for a separate decision, rather than implied approval to create one. Changes to supplier banking details also need their own authorisation.
Attach source documents and recover partial writes
An attachment tool must do two jobs: upload the original file and link it to the correct Bill. A note containing a filename is not the source document. Intuit's open-source server lists Attachable operations, but an entity listing alone does not establish that a tool accepts file contents. Zapier documents file attachment, and Meridian lists an attachment-upload tool; inspect the selected tool's file-input and transaction-linking parameters before relying on either for your batch.
In particular, check how the agent supplies the file, whether uploading and linking require separate calls, and how the resulting attachment identifies the transaction. Do not assume that a tool accepting attachment metadata also accepts a local path, file bytes or a download URL. If the connection cannot complete the upload, attach the original through QuickBooks and record that remaining step.
Keep the complete source packet where it is needed to understand the charge. For a PDF containing several bills, retain the page references used in review so each created record can be traced to its own evidence.
After each approved creation, save the company identifier and returned Bill ID alongside the source reference. Read the bill back to check its vendor, number, dates, amounts and accounting lines. Verify the attachment separately: a successful upload does not prove that the file is linked to the intended bill.
Handle failures according to what actually succeeded:
- Bill created, attachment failed: finish or retry the attachment against the existing Bill ID. Do not recreate the bill to repair its evidence.
- Creation was definitively rejected: record the rejection and hold that document. Correct the stated problem before another approved attempt.
- Creation timed out or returned an error with an uncertain write outcome: search QuickBooks for the company/vendor/bill-number match and reconcile its details before resending. If the match remains ambiguous, leave it for the person to resolve.
Keep this outcome record outside the conversation so a restart does not erase which writes succeeded. Retry protection for a document extraction does not establish duplicate protection for a separate QuickBooks creation request.
A useful completion report accounts for the entire batch. For example: “12 supplier documents reviewed: 8 bills created with their QuickBooks IDs recorded; 2 duplicate copies excluded; 1 credit note held for separate credit entry; 1 invoice held because page 2 failed extraction. Source files attached to 7 of the 8 created bills; attachment pending for the remaining Bill ID. No bill payments requested.”