Ship deep QuickBooks integrations in days

QuickBooks Online keeps invoices, bills, payments, and journal entries behind its Accounting API and its own query language, and every company sets up its own accounts, items, and classes. With Ampersand, you can get this integration live for your customers in days.

Schedule a demo See QuickBooks guide

Build a custom data model to handle complex configurations

No two QuickBooks companies are the same. Every customer has their own chart of accounts, items, classes, and custom fields. AI agents need infrastructure that understands QuickBooks at the per-tenant level.

3 / 4 customers

3 / 8 customers
  • Customer A: Customer (standard), Invoice (standard), Class (standard)
  • Customer B: Vendor (standard), Bill (standard), Purchase Order (standard)
  • Customer C: Invoice (standard), Estimate (standard), Department (standard)

Enable software and agents to take bi-directional action

With Ampersand, your engineers don’t need to learn the QuickBooks Accounting API, its query language, or Intuit’s OAuth setup. Simply declare the actions you want your agents to take: read, write, proxy.

Example. Read: “Sync every invoice that changed since the last run.”

  1. Ampersand refreshes this customer’s OAuth 2.0 token.
  2. Ampersand queries only the invoices updated since the last sync.
  3. The changed invoices come back, page by page.
  4. Ampersand applies this customer’s field mappings, custom fields included.
  5. Ampersand sends the invoices to your product.

Ensure your QuickBooks integration is always available

  • Managed auth

    Fully offload Intuit OAuth. Ampersand stores and refreshes tokens for every customer’s QuickBooks company.

  • Incremental reads

    After a full historic backfill, each sync reads only the records that changed, so your integration moves less data on every run.

  • Sandbox to production

    Build and test against a QuickBooks sandbox company with the sandbox connector, then switch to production when you go live.

Not all QuickBooks integrations are created equal

QuickBooks is where many small and mid-sized businesses keep their books. With Ampersand, your developers can create a best-in-class QuickBooks integration.

In-House DIY Build Unified APIs Embedded iPaaS Ampersand
Data schema that works for all customers Lots of switch statements and special casesOnly access standard objects and fieldsBuild customer-specific workflows Flexible model with mappings
Object coverage Write and maintain a client for every QuickBooks entity you needOnly common models and their standard fieldsLimited to the objects its prebuilt actions cover Sales, purchase, and accounting objects, from invoices to journal entries
Schema drift protection Manual incident debuggingNot supportedNot supported Get notified about schema changes
OAuth token custody You own the tokens, but you also have to manage refreshesVendor lock-inVendor lock-in Export at any time via API
Integration workflow Imperative custom codeSingle API clientDrag-and-drop, not integrated with Git Declarative manifest you can version control
Build vs. Buy Unified API vs. Ampersand

The QuickBooks objects your agents can read and write

Ampersand reads and writes the QuickBooks Online sales, purchase, and accounting objects, reads tax and reference data, and writes inventory adjustments.

Objects What’s included Read Write
Sales
  • Customers
  • Invoices
  • Estimates
  • Payments
  • Sales receipts
  • Credit memos
  • Refund receipts
Supported Supported
Purchases
  • Vendors
  • Bills
  • Bill payments
  • Purchases
  • Purchase orders
  • Vendor credits
Supported Supported
Accounting
  • Accounts
  • Journal entries
  • Deposits
  • Transfers
  • Budgets
  • Credit card payments
  • Recurring transactions
  • Attachables
Supported Supported
Lists and people
  • Items
  • Classes
  • Departments
  • Terms
  • Payment methods
  • Company currencies
  • Tax agencies
  • Journal codes
  • Employees
  • Time activities
Supported Supported
Tax and reference data
  • Tax codes
  • Tax rates
  • Tax payments
  • Exchange rates
  • Customer types
  • Reimburse charges
Supported Not supported
Inventory and tax setup
  • Inventory adjustments
  • Tax codes, through the tax service
Not supported Supported

Reads include a full historic backfill, then incremental reads of only the records that changed. Custom fields come with customers, vendors, invoices, estimates, sales receipts, credit memos, refund receipts, purchase orders, and bills.

See every object in the docs

Questions people ask before they book a demo

  • Which QuickBooks objects can I read and write?

    You can read and write customers, invoices, estimates, payments, vendors, bills, purchase orders, accounts, journal entries, items, employees, and more. Tax codes, tax rates, tax payments, exchange rates, customer types, and reimburse charges are read-only, and inventory adjustments are write-only.

  • Does Ampersand read only the records that changed?

    Yes. After a full historic backfill, Read Actions pick up only new and changed records on the schedule you set.

  • Can I test against a QuickBooks sandbox?

    Yes. QuickBooks comes as two connectors with the same objects and actions: quickbooksSandbox for your Intuit sandbox companies, and quickbooks for production. Each uses the matching client ID and secret from your Intuit app.

  • Does Ampersand offer a unified API?

    Ampersand doesn’t offer a unified API. It works with QuickBooks’s own objects and fields as each customer sets them up, which differs from how a unified API works. We also give you the primitives to build your own unified data model.