QuickBooks Integration With Custom Software: What to Know

Yes, custom software can connect directly to QuickBooks Online, and the integrations most small businesses want (pushing invoices, syncing customers, recording payments, pulling balances) are well supported by Intuit's API. The work is less about whether it is possible and more about three questions: how your data maps to QuickBooks' data, whether a no-code tool like Zapier is enough or you need a direct connection, and how to build it so it keeps working after launch.

One 2025 change is worth knowing before you budget. Intuit launched an App Partner Program in July 2025 that meters certain read calls. Every app starts on a free tier with 500,000 metered calls per month, far more than one company's integration will use, but it means a sloppy integration that polls too often now has a ceiling to hit. Below: what the API can and cannot do, the integrations we build most often, and what drives the cost.

What can the QuickBooks Online API do?

The QuickBooks Online API is a standard REST API. The business owner approves the connection once, and from then on your app can read and write the core accounting objects: customers, vendors, items, invoices, estimates, sales receipts, payments, bills, expenses, journal entries, and the chart of accounts. It can run standard reports such as profit and loss and receivables aging, and it can send webhooks when records change.

Intuit groups calls into two types. Core calls, mostly writes such as creating an invoice, are free and unlimited. CorePlus calls, mostly reads such as fetching invoices or running reports, count against the monthly allowance. The partner FAQ states that sandbox and failed calls are not metered and that the free Builder cap resets on the first of each month. Above the cap, calls are blocked until the next month or until you move to a paid tier, which Apideck's breakdown of the program lists at $300 per month for Silver.

Rate limits apply regardless of tier. Zapier's QuickBooks Online help article, updated in October 2026, summarizes them: 500 requests per minute per company, 10 concurrent requests per company per app, and 40 batch requests per minute. For a single business these are generous, and only bite if an integration is badly designed, such as re-syncing every customer every five minutes.

What can the API not do?

Payroll is not exposed. Pulling wages or running payroll from your own software is not an option.

Custom fields are limited. The same Zapier article notes that only the first three string-based custom fields appear in API responses, and number-type custom fields do not appear at all. If your workflow depends on a custom field, confirm it is one of those three first.

Bank feeds are off limits. Transactions sitting in "For Review" are not available until they are categorized and recorded.

Display names must be unique across customers, vendors, and employees. A customer and a vendor both named "Smith Construction" will collide, so your integration needs a rule for that on day one.

Webhooks tell you that something changed, not what changed, so your software then reads the record with a metered call.

None of these are deal breakers, but they belong in the requirements document rather than in a surprise email three weeks into the build.

What are the most common QuickBooks integrations?

Invoices from a portal or job system. When a job is complete in your software, an invoice appears in QuickBooks with the right customer, line items, tax, and due date, and payments flow back so your portal can show "paid." This is the most common request and the highest return, because it removes double entry.

Customer sync. A customer created in your CRM or portal becomes a customer in QuickBooks, and changes flow one way or both. The hard part is deciding which system owns each field. If your website forms already feed a CRM, this extends our post on connecting website forms to a CRM.

Payments and deposits. When a customer pays through your app, the payment is recorded against the QuickBooks invoice and the deposit matches what hits your bank. Done well, reconciliation becomes nearly automatic.

Reporting into a dashboard. Your dashboard pulls receivables or revenue by customer so owners stop asking the bookkeeper for numbers. This is read heavy, so cache results and refresh a few times a day rather than on every page load. For more places this kind of automation pays back, see our roundup of business process automation examples.

Zapier or a direct API connection?

Zapier and similar tools connect QuickBooks Online to hundreds of apps without code, with triggers such as an invoice balance reaching zero and actions such as creating a customer or an invoice. According to Zapier's help article, the connector requires Zapier's Professional plan or above and a paid QuickBooks subscription with admin permissions.

Zapier is the right answer when the integration is simple and low volume: one record in, one record out, no complex matching, and a person available to fix the occasional failed run. A contractor who wants every signed proposal to create a QuickBooks customer and draft invoice can set that up in an afternoon.

A direct API integration is the right answer when you need to match records (find the existing customer, do not create a duplicate), handle line items and tax codes precisely, sync two ways, process more than a few hundred records a month, or keep the integration inside your own software. Zapier also charges per task, so volume matters; we walked through that trade-off in our comparison of Zapier, Make, and custom integrations. A sensible middle path is to start with Zapier to prove the workflow is worth automating, then replace it with a direct integration once you know exactly what it should do.

How do sandbox testing and app approval work?

Intuit gives every developer a free sandbox company that behaves like a real QuickBooks Online file with fake data. Building and testing happen there, and your developer should show you the integration working in the sandbox before it touches your books.

Going to production is simpler than most people fear. If the integration is only for your own company, your developer creates production keys and connects your QuickBooks file; there is no public listing and no store review. The partner FAQ confirms the program applies to every production app whether or not it is listed on the Intuit App Marketplace, and the free allowance covers single-company use easily. If you plan to sell your software to other businesses who each connect their own QuickBooks, you will want a Marketplace listing, which involves Intuit reviewing your app, and usage across all those customers counts against the tier limits together. Budget for that separately.

What are the data mapping pitfalls?

Every QuickBooks integration that goes wrong goes wrong in the mapping. Settle these in writing first.

Which system owns the customer record? Pick one, and decide who wins when they disagree.

How do items map? Each invoice line must point to an item in QuickBooks' own list. Create the items first, store the QuickBooks item ID alongside your own, and never match by name alone.

How is sales tax handled? Your software can flag lines as taxable and let QuickBooks compute, or pass the tax amount explicitly. Mixing the two produces invoices off by a few cents, and bookkeepers notice.

How do you prevent duplicates? Store the QuickBooks ID of every record you create and look it up before creating anything. Retries after a network error are the top cause of duplicate invoices.

What happens when QuickBooks says no? A failed write (a validation error, a locked period, a rate limit) must land where a human sees it. An integration that fails silently is worse than none, because people trust it.

What drives the cost of a QuickBooks integration?

Five things move the number: how many objects you sync (invoices only is cheap; invoices plus payments plus customers plus items is several times the work), the direction (one-way push is simple, two-way sync is not), matching logic (create-only versus find-or-update), error visibility (a log page your office manager can read adds hours and is worth them), and whether the integration lives inside existing software or stands alone.

A one-way invoice push from an existing portal, with duplicate protection and an error log, is a small project measured in weeks. A two-way sync of customers, items, invoices, and payments with a reconciliation view is a mid-sized one. Zapier sits below both in build cost and above both in monthly fees.

At Premier Logic we build these alongside the portals and internal tools they connect to, and we scope them in hours returned: how many hours a week of re-keying and chasing payments disappear. If that number does not clearly beat the cost, we say so.

Quick answers

Can custom software connect to QuickBooks Online?

Yes. QuickBooks Online has a public REST API. Once the business owner authorizes the connection, your software can create and read customers, invoices, payments, bills, items, and reports.

Is the QuickBooks Online API free to use?

For a single company's integration, effectively yes. Every app starts on a free Builder tier with 500,000 metered read calls per month, and write calls are not metered. Paid tiers start at $300 per month and are aimed at apps serving many companies.

Should I use Zapier or build a direct integration?

Use Zapier for simple, low-volume, one-direction workflows where a person can fix a failed run. Build a direct integration when you need record matching, line-item precision, two-way sync, higher volume, or the integration inside your own software.

What is the biggest risk in a QuickBooks integration?

Duplicates and silent failures, and both come from weak mapping and error handling rather than from the API. Insist on stored QuickBooks IDs, find-before-create logic, and a visible error log in the scope.

Next step

Not sure whether your situation calls for a Zapier connection, a direct integration, or a rebuild of the tool that would feed QuickBooks in the first place? Book a free call with Premier Logic. Describe how invoices and payments move through your business today, and we will reply with a written recommendation: what to connect, in which direction, and roughly what it involves. It is yours to keep whether or not you hire us. Start the conversation here.