Finance & ERP · Integration
QuickBooks
Add QuickBooks to your product for your customers, and give your AI agents governed access to it.
Small businesses keep their books in QuickBooks Online, so an embedded QuickBooks integration is usually what stops your customers exporting from your product and typing it all in again. Your app can raise invoices, record bills and expenses, match payments, and read customers, items, classes and the chart of accounts a company file actually uses. Practical details bite here: each connection is scoped to a realm id, the sandbox does not behave like production, tax handling varies by country edition, and the API is versioned by minor version so fields can appear or change under you. fastn holds the per-company tokens, refreshes them, and tracks those version changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each small business connect their own QuickBooks company file so your product invoices from work it already tracked.
Record bills and expenses as they happen, so nobody re-keys them during the month-end close.
Read the chart of accounts, classes and items so your product codes a transaction the way the bookkeeper would.
Match incoming payments against open invoices and show the business what is still outstanding.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists overdue invoices for one company file and drafts the chase email for a human to send.
An agent creates an invoice from your product's data, with the account it coded to visible in the audit trail.
An agent answers a cash question from current AR and AP balances rather than from a stale export.
Example prompt
Which invoices in this company file are more than 60 days overdue, and what do they total?
Set up QuickBooks in 4 steps
- 01Enable the QuickBooks connector from your fastn dashboard.
- 02Have each customer authorise their own QuickBooks account, so calls run under their credentials rather than a shared key.
- 03Decide which invoices, payments and vendors your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the QuickBooks integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a QuickBooks integration without building it. Your customers connect their own QuickBooks account inside your product and work their invoices, payments and vendors there, with no per-customer code on your side.
- Handle the part that actually costs time: financial writes must be idempotent and reconcilable, because a duplicate is an accounting problem rather than a bug. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a QuickBooks update is not your on-call problem.
- One integration serves your product and your agents. The same governed QuickBooks connection powers in-product features and gives AI agents scoped, audited access, so you move financial records without hand-keying them between systems without wiring it twice.
Used by these teams
Compare with
Xero
FreshBooks
BillOften used alongside
Tools the same teams tend to run next to QuickBooks, across other categories.
Shopify
Stripe
BigCommerce
AfterShipQuickBooks integration FAQ
How do I add a QuickBooks integration to my product?
Enable the QuickBooks connector in your fastn dashboard, then let each customer authenticate their own QuickBooks account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no QuickBooks client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own QuickBooks account?
Yes. Every connection is scoped to the individual customer, so each authorises their own QuickBooks account and only ever sees their own invoices, payments and vendors. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this QuickBooks integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent lists overdue invoices for one company file and drafts the chase email for a human to send.
Who maintains the QuickBooks integration?
fastn does. When QuickBooks changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the QuickBooks integration safe for financial writes?
Writes are idempotent, so a retry after a timeout does not post a document twice, and every call is logged per tenant so an entry can be traced back to the event that created it. That matters more in finance than anywhere else, because a duplicate is a number somebody has to explain.
Can it handle each customer's own chart of accounts?
Yes. ERP deployments are configured to the business, so account structures, required fields and fiscal calendars differ per customer. Those are mapped per tenant as configuration, not hard-coded.
What about QuickBooks rate limits during a first import?
Backfills are throttled deliberately. ERP limits are often account-wide rather than per-integration, so an unthrottled import can exhaust a customer's allowance and disrupt their other integrations.
What can I build with the QuickBooks integration?
A common starting point: let each small business connect their own QuickBooks company file so your product invoices from work it already tracked. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the QuickBooks integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding QuickBooks does not change your per-connector cost. You can start free with 3 connected accounts.
Add QuickBooks to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.