Can you automate invoice processing in QuickBooks Online?
Yes. QuickBooks Online reads bills you upload or forward and queues them for review. For line items, duplicate checks, approvals or several inboxes, a workflow on n8n, Zapier or Make extracts, checks and creates each bill through the QuickBooks API.
In QuickBooks, a supplier's invoice is entered as a bill, so "QuickBooks AP automation" and "automating invoice processing in QuickBooks" describe the same job: getting supplier invoices from the inbox into QuickBooks as correct, unpaid bills without retyping them. This guide covers the QuickBooks side of that job in detail: what QuickBooks does on its own, how a connected workflow creates bills, the API limits and fees, and the duplicate-bill trap. The extraction step itself, and what it costs per 1,000 invoices on each AI service, is covered on our AI document processing and invoice automation page.
Looking for sales invoices instead? Sending invoices to your own customers on a schedule is a different task. This page is about bills from suppliers (accounts payable). Answers on sales invoices are in the questions at the end.
What does QuickBooks Online do on its own with supplier bills?
QuickBooks Online lets you upload bill files or forward them to a private @assist.intuit.com address. It pulls out details such as dates, amounts and vendor, and puts the result in a For review list, where a person checks it before it becomes a bill.
Intuit's own help articles, checked October 30, 2026, describe two intake routes:
- Upload. You can upload bill files from your computer in PDF, JPEG, JPG, GIF or PNG format. Bills you upload, or receive through the network, land in the For review tab. Bills you type in by hand go straight to Unpaid and need no review (Intuit: enter and pay bills).
- Forward from email. An admin sets up a custom address ending in @assist.intuit.com under Receipts. Each user can register one email, must be given permission, and must send from the address they sign in with. Attachments must be PDF, JPEG, JPG, GIF or PNG, between 46 KB and 20 MB, with one receipt or bill per file. Intuit says QuickBooks "automatically pulls dates, amounts, vendor, and last four digits of the credit card from the image" (Intuit: email your receipts to QuickBooks Online).
For a business that receives a modest number of bills from known suppliers, this may be all you need, and we say so on a free call. What the articles do not describe is line-item capture, matching against a purchase order, a rule that holds bills above an amount, or posting the same document anywhere other than QuickBooks. Those are the gaps a workflow fills.
When is the built-in capture enough, and when do you need a workflow?
Built-in capture is enough when bills arrive from one place, a person reviews each one anyway, and you only need header details. A workflow earns its cost when you need line items, automatic checks, approvals, several inboxes or data going to other systems too.
| Your situation | QuickBooks upload or forward | Workflow on n8n, Zapier or Make |
|---|---|---|
| A few bills a week, one person enters them | Usually enough | Rarely worth building |
| Bills need line items split across expense accounts or items | Not described in Intuit's articles; test it on your own bills | Extracts each line and maps it to an account or item |
| Bills arrive in several inboxes, a portal or a shared drive | One forwarding address per user | Watches every source and saves each original first |
| Some bills must match a purchase order | No PO matching described | Compares quantities and prices with the PO before posting |
| Bills above an amount need a second person | Approvals depend on your plan and Bill Pay level | Holds them in a review queue (Slack, Airtable or Sheets) |
| The same bill data must also reach a CRM, job system or project tracker | QuickBooks only | Writes to each system in the same run |
Intuit's article notes that "depending on your bill pay subscription level, you may have additional approvals", and a dedicated accounts payable tool may cover approvals well. A custom workflow fits best around what those tools do not touch: odd document types, other systems, or checks specific to your business. That is the kind of business process automation we usually build around accounting.
How do you build QuickBooks AP automation with n8n, Zapier or Make?
Connect your QuickBooks company, watch the inbox, extract each bill with an AI model, find the vendor, check for a duplicate, create the bill, attach the original PDF and store the bill ID. Anything that fails a check waits for a person.
From supplier email to a bill in QuickBooks
- Connect QuickBooks. In n8n you create your own app on the Intuit developer portal, copy its Client ID and Client Secret into the credential, and choose Sandbox or Production; n8n's docs advise starting in the sandbox (n8n QuickBooks credentials). Zapier and Make connect through their own sign-in screens.
- Watch the intake. A shared inbox such as bills@ or a Drive folder. Save the original file before anything else, so a failed step never loses a bill. On n8n this is usually an email or webhook trigger; our guide to setting up an n8n webhook covers the webhook route.
- Extract. Send the file to an OCR or AI service (our FAQ on OCR vs AI extraction explains which layer you need) and ask for a fixed set of fields: vendor name and tax ID, bill number, bill date, due date, currency, subtotal, tax, total, PO number and each line.
- Find the vendor. Look the vendor up in QuickBooks before creating anything. Match on tax ID or a stored alias first and name second. No single match means review, never a new vendor created by guesswork.
- Check for a duplicate. Search QuickBooks for a bill with the same vendor and bill number. Our own store of processed files catches resends of the same PDF.
- Create the bill. Use the bill number from the document, the vendor's ID, the dates, and one line per expense account or item.
- Attach the PDF. Upload the original to the bill so anyone reviewing it in QuickBooks sees the source.
- Record the result. Store the bill ID QuickBooks returns against the file, so a retry can never post it twice.
The QuickBooks actions each platform lists for these steps, checked October 30, 2026:
| Step | n8n QuickBooks Online node | Zapier QuickBooks Online | Make QuickBooks |
|---|---|---|---|
| Find the vendor | Vendor: Get, Get All | Find Vendor; Find or Create Vendor | Check the module list in your scenario |
| Check for a duplicate | Bill: Get All with a filter | No bill search listed; keep your own log | Check the module list in your scenario |
| Create the bill | Bill: Create | Create Bill (Item Based) or (Account Based) | Create a Bill |
| Attach the PDF | Not in the node; HTTP Request to the upload endpoint | Attach File(s) or Note | Check the module list in your scenario |
Sources: n8n QuickBooks Online node, Zapier QuickBooks Online integrations, Make QuickBooks integration. Make's public page shows only part of its module list, so we mark the rest as unconfirmed.
The attachment step is where n8n needs a direct API call. Intuit's upload endpoint takes a multipart request of one or more files, up to 100 MB in total, links each file to a transaction through an Attachable object, and accepts PDF, JPEG, PNG, TIFF and a list of office formats (Intuit: attach images and notes). Calls like this are the kind of work on our API integration page. If you are still choosing a platform, our n8n vs Zapier comparison covers the trade-offs; for AP work on n8n specifically, see our n8n automation builds.
What do the QuickBooks API limits and fees mean for bill automation?
For most businesses, nothing that blocks them. QuickBooks allows 500 requests a minute per company, creating bills is a free Core call, and the free Builder tier includes 500,000 metered CorePlus calls a month. Four calls per bill uses a small share.
QuickBooks API numbers that shape the build
Intuit's documentation, checked October 30, 2026, sets these limits for the QuickBooks Online API: 500 requests per minute per company file, 10 requests per second per company and app, HTTP 429 when throttled with a 60-second wait before retrying, and a 120-second timeout per request (Intuit: API call limits and throttles).
Since the Intuit App Partner Program started, calls are also split into two kinds. Intuit's FAQ says Core calls "cover most data-in operations such as creating or updating invoices, bills, customers, vendors" and are unmetered and uncharged. CorePlus calls cover "most data-out operations such as reading accounts, querying company information, and fetching reports" and are metered. Every app starts in the uncharged Builder tier with 500,000 CorePlus calls a month, and calls above that are blocked until you upgrade (Intuit App Partner Program FAQ).
Here is how the bill workflow above uses those allowances. Our assumptions: four API calls per bill (vendor lookup, duplicate search, create bill, upload PDF); the two searches count as CorePlus because they read data out; create and upload count as Core because they put data in. Intuit's full call breakdown is the final word on any single endpoint.
| Bills per month | CorePlus calls (2 per bill) | Share of Builder's 500,000 | Core calls (2 per bill, uncharged) |
|---|---|---|---|
| 500 | 500 x 2 = 1,000 | 0.2% | 1,000 |
| 5,000 | 5,000 x 2 = 10,000 | 2% | 10,000 |
| 50,000 | 50,000 x 2 = 100,000 | 20% | 100,000 |
The rate limit is the tighter constraint during bursts. At four calls per bill, 500 requests a minute allows at most 125 bills a minute for one company, so a month-end upload of a few hundred bills needs a queue that spaces the calls, plus a retry that waits 60 seconds on HTTP 429. The bigger CorePlus risk comes from other apps and reports reading the same company file, so we keep searches narrow and never poll QuickBooks on a timer when a stored ID will do.
How do you stop QuickBooks from getting duplicate bills?
Check vendor plus bill number in QuickBooks before you create a bill, keep a log of every file already posted, and treat QuickBooks error 6140 (Duplicate Doc Num) as "already there, check it" instead of retrying with a new number.
QuickBooks Online has a company setting, Warn if duplicate check/bill number is used, under Settings, Account and Settings, Advanced. With it on, an API call that creates a bill with a number already used for that vendor fails with "Duplicate Document Number Error: You must specify a different number" (Ramp support article). Intuit lists it as error 6140, Duplicate Doc Num: "The specified number is already in use" (Intuit: error codes).
Some sync tools tell you to switch the setting off so their sync stops failing. We leave it on. The error is a free second check, and the workflow should catch it and send the bill to review, never rewrite the number to force it through.
| Symptom | Likely cause | Fix |
|---|---|---|
| Same bill appears twice | Supplier sent it twice, or a retry ran after a timeout | Search vendor plus bill number first; log the file hash and bill ID; skip anything already logged |
| Error 6140 on create | Bill number already used for that vendor | Send to review with a link to the existing bill; do not change the number |
| Bill lands on the wrong vendor | Name match on "ABC Ltd" vs "ABC Limited" | Match on tax ID or an alias table; ambiguous matches go to review |
| Bills stop arriving with no alert | Expired QuickBooks connection, or HTTP 429 not retried | Error workflow with alerts, a 60-second wait on 429, and a daily count of bills created |
| Metered calls blocked late in the month | CorePlus allowance used by searches, reports or other apps | Fewer searches per bill, no polling, stored IDs; check usage before month end |
| Bill totals do not match the PDF | A line missed on page two, or tax counted twice | Lines plus tax must equal the total before posting; failures go to review |
The checks that decide whether a bill posts on its own (totals, vendor, duplicates, PO match, amount thresholds) are the same ones we use for every document type, and they are set out on our AI workflow automation page.
What does QuickBooks AP automation cost to run and to build?
Running costs are your QuickBooks plan, your automation platform and extraction, a few dollars per 1,000 one-page bills on most AI models. Creating bills through the API is uncharged. At the time of writing, our build of two or three workflows is about $1,000.
- QuickBooks API. Creating bills, vendors and attachments are Core calls, unmetered and uncharged. Searches draw on the free 500,000 CorePlus allowance shown above.
- Automation platform. n8n, Zapier and Make price differently; our n8n and Zapier pricing research works through real monthly costs.
- Extraction. The per-service arithmetic for 1,000 invoices is on our document processing service page.
- Our build. At the time of writing, the strategy call and audit are free; a small build of two or three workflows, such as intake, extraction with checks, and bill creation in QuickBooks, is about $1,000; larger systems get a fixed price after the audit. Fixes to what we built are free for 6 months, and monthly support from $200 is optional after that. The workflows, the Intuit app and every key stay in accounts you own; our FAQ on who owns automations and data explains how to check that.
More questions about QuickBooks AP automation
Does QuickBooks Online have AP automation built in?
Yes, in part. QuickBooks Online can extract details from bills you upload or forward to an @assist.intuit.com address and place them in a For review list, and Intuit's help article mentions an Accounts Payable Automation feature for bills received through its network. Approvals depend on your Bill Pay subscription level. Line items, PO matching and posting to other systems need a workflow or a separate AP tool.
Can QuickBooks read line items from a supplier invoice?
Intuit's forwarding article says QuickBooks pulls dates, amounts, vendor and the last four card digits. The help articles we read on October 30, 2026 do not describe line-item capture, so test it on a sample of your own bills. If you need each line mapped to its own expense account or item, an AI extraction step in a workflow gives you that control.
Can Zapier create bills in QuickBooks Online?
Yes. Zapier's QuickBooks Online integration lists Create Bill in item-based and account-based versions, Find Vendor, Find or Create Vendor, and Attach File(s) or Note. It does not list a bill search, so a Zap that must block duplicates keeps its own log of bill numbers already posted, for example in a Zapier table or a Google Sheet.
Can n8n attach the PDF to a QuickBooks bill?
Not with the QuickBooks Online node alone: its documented operations cover bills, vendors, invoices and other records, but no attachments. We add an HTTP Request step that calls Intuit's upload endpoint with the file and an Attachable object pointing at the new bill, using the same QuickBooks credential, so the original PDF sits on the bill.
Does this work with QuickBooks Desktop?
Everything on this page applies to QuickBooks Online: the forwarding address, the Online Accounting API, its limits and the n8n, Zapier and Make connectors. QuickBooks Desktop connects in a different way, so a Desktop build needs its own plan. Tell us which edition you run on the free call and we check what is possible before quoting.
How do I automate sales invoices in QuickBooks Online instead?
That is the receivables side, a separate job from supplier bills. The same platforms cover it: the n8n QuickBooks Online node can create, send and void invoices, and Zapier lists Create Invoice and Send Invoice actions. A common build creates the invoice when a deal closes in your CRM or a job is marked done, then sends it from QuickBooks.
Should I switch off the duplicate bill number warning so my sync stops failing?
We advise against it. The warning is what turns a duplicate into error 6140 instead of a second bill you might pay twice. A well-built workflow searches for the bill number first, so the error should be rare, and when it does fire, the bill goes to a person with a link to the existing one.
How long does a QuickBooks bill automation build take?
A small build typically takes days once we have access to the QuickBooks company, the inbox and a sample of 20 to 50 real bills. Most of the time goes into testing against your awkward bills and a parallel run with your team. Our FAQ on how long an automation build takes explains what speeds it up.
Sources and further reading
- Intuit: Enter and pay bills in QuickBooks Online (For review and Unpaid tabs, upload formats), checked October 30, 2026
- Intuit: Email your receipts and bills to QuickBooks Online (forwarding address, file limits), checked October 30, 2026
- Intuit Developer: API call limits and throttles, checked October 30, 2026
- Intuit Developer: App Partner Program FAQ (Core and CorePlus calls, Builder tier), checked October 30, 2026
- Intuit Developer: Attach images and notes (upload endpoint, file types), checked October 30, 2026
- Intuit Developer: Error codes (6140 Duplicate Doc Num), checked October 30, 2026
- n8n: QuickBooks Online node and QuickBooks credentials, checked October 30, 2026
- Zapier: QuickBooks Online integrations and Make: QuickBooks integration, checked October 30, 2026
- Ramp support: Duplicate Document Number Error in QuickBooks Online, checked October 30, 2026
