A good QuickBooks integration developer will ask you about duplicate invoices before they ask about deadlines. That is the test. Connecting your app, booking tool or field-service system to QuickBooks Online is not hard to start, and it is easy to get subtly wrong: double-posted invoices, payments that never sync back, and a 3am error nobody sees until month-end close.
Here is what the job involves, what Intuit charges, and how to tell a developer who has done this from one who is about to learn on your books.
Key Takeaways
- Most data going into QuickBooks (invoices, customers, bills) is free and unmetered under Intuit's partner program; reading data out is what gets metered.
- Every QuickBooks company is capped at 500 API requests a minute and 10 a second, so a careless sync can lock itself out.
- A solid two-way invoice and payment sync is usually around 100 hours of work, about $4,500 at an assumed $45 an hour.
- Under roughly a thousand simple transactions a month, a no-code connector is often cheaper than a custom build.
What a QuickBooks Integration Developer Should Know Cold
Intuit publishes the limits for the QuickBooks Online API. Anyone you pay should be able to tell you these without looking them up:
| Limit | What it means for you |
|---|---|
| 500 requests per minute per company | A sync that re-reads everything every minute will hit the wall |
| 10 requests per second per company and app | Bursts need a queue, not a loop |
| 40 batch requests per minute | Batching helps, within limits |
| HTTP 429 when throttled, wait 60 seconds | The code must back off and retry, or data gets dropped |
| Queries return at most 1,000 records | Large customer lists need paging |
| Requests time out after 120 seconds | Long jobs must be split up |
The same limits apply in Intuit's sandbox, so a developer who tests properly will find these problems before your accountant does. QuickBooks Online uses OAuth 2.0 to connect, which means your customer clicks "connect" and the integration has to store and refresh access safely.
What Intuit Charges for API Access
Intuit's App Partner Program guide (March 2026) splits API calls in two. "Core" calls cover most data going in, like creating invoices, bills, customers and vendors, and the guide says they are "unmetered and uncharged." "CorePlus" calls are mostly data coming out, like reads and reports, and those are counted.
| Tier | Monthly fee | CorePlus credits included |
|---|---|---|
| Builder | No charge | 500,000 |
| Silver | US$300 | 1 million |
| Gold | US$1,700 | 10 million |
| Platinum | US$4,500 | 75 million |
On the free Builder tier, CorePlus calls above the included credits are blocked, not billed. For a typical small business integration that mostly writes invoices and checks payment status, Builder is plenty. A developer who designs the sync to read only what changed keeps you there.
Questions That Expose an Inexperienced Developer
- "How do you stop the same invoice posting twice if a request times out?" You want to hear about checking for an existing record before creating one.
- "What happens when QuickBooks returns a 429?" The answer is a wait and retry, plus logging.
- "How do you map our products to QuickBooks items and tax codes?" There should be a written mapping table before any code.
- "Where are the connection tokens stored?" Encrypted, in your account, never in a spreadsheet.
- "Who gets alerted when a sync fails?" If the answer is nobody, you find out at month-end.
A Concrete Version
A plumbing company sends about 600 invoices a month from its scheduling app and wants payments to flow back so the office stops re-typing them.
Creating 600 invoices is Core work, so it is free and uncounted. Checking payment status on open invoices once a day is the metered part: even at 600 open invoices checked daily for 30 days, that is 18,000 reads a month, far under Builder's 500,000 credits.
The build, at an assumed $45 an hour:
| Piece | Hours |
|---|---|
| Connect and token handling | 12 |
| Customer and item mapping | 16 |
| Invoice sync | 24 |
| Payment sync back | 16 |
| Retries, logging, alerts | 16 |
| Sandbox testing with real data | 16 |
| Total | 100 hours, about $4,500 |
The Honest Counterpoint
Plenty of businesses don't need a developer for this at all. Zapier's Professional plan covers 750 tasks a month for $19.99 billed annually. Zapier counts a task per completed action, so pushing this plumbing company's 600 invoices fits under it, but adding payments flowing back roughly doubles that to about 1,200 tasks, which puts it on the 2,000-task tier at $49 a month billed annually. Still far cheaper than a build. If your invoices are simple and one-directional, start there, and read our take on Zapier versus custom software before you pay anyone.
Custom starts to win when the mapping logic gets messy (multiple tax codes, partial payments, job costing), when volume outgrows the connector plan, or when you need the sync inside your own product for your customers. It also wins when a failed sync costs you real money and you need alerts and an audit trail, which is the part connectors are weakest at.
Frequently Asked Questions
How much does a QuickBooks integration developer cost?
For a two-way invoice and payment sync, budget roughly 100 hours. At an assumed $45 an hour that is about $4,500; a one-way invoice push can be half that.
Does the QuickBooks API cost money?
Most data going in, like invoices and customers, is free under Intuit's partner program. Reading data out is metered, and the free Builder tier includes 500,000 of those calls a month before they are blocked.
Can I connect my app to QuickBooks without a developer?
Often, yes. For simple, low-volume syncs a connector like Zapier works. Hire for the integration when mapping gets complicated or mistakes get expensive.
The Bottom Line
The job is less about connecting to QuickBooks and more about never posting the same invoice twice. If you are not sure whether you need a connector or a build, Sol's free Honest Read gives you a straight answer and the full report is yours to hand to anyone. If it needs building, our software factory builds the integration at a fixed price, you own the code, and you get 90 days of free bug fixes after delivery. For the hiring side, see how to hire an API integration developer, and for what happens next, what happens after your app is built.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
