QuickBooks Integrations
Resplendent supports multiple QuickBooks connection types. Choose the one that matches the source you are managing.
Supported versions
Section titled “Supported versions”| Integration | Connection method | New connections | Notes |
|---|---|---|---|
| QuickBooks Online Integration | Cloud-to-cloud OAuth | Yes | Native, read-only, US QuickBooks Online Companies only |
| Legacy QuickBooks Online Integration | CData-backed OAuth | No | Existing legacy connections remain manageable |
| QuickBooks Desktop | Resplendent Sync Agent | Yes | Requires QuickBooks Desktop and the CData Desktop Gateway |
QuickBooks Online Integration
Section titled “QuickBooks Online Integration”The QuickBooks Online Integration is the native cloud integration for new QuickBooks Online connections. It is read-only and supports US QuickBooks Online Companies only.
Step 1: Connect to QuickBooks
Section titled “Step 1: Connect to QuickBooks”- Go to Settings → Integrations
- Find QuickBooks Online and click Connect on the card
- Click Connect with QuickBooks
- You’ll be redirected to Intuit’s login page, then sign in and select your company
- Click Authorize
Step 2: Choose Datasets
Section titled “Step 2: Choose Datasets”Pick the tables you want to sync. Common choices:
InvoicesInvoiceLineItemsPaymentsCustomersAccounts(Chart of Accounts)BillsandBillLineItemsReceivableApplicationsandPayableApplicationsAccountingEntries
Parent and child Datasets are selected independently. Selecting Invoices does not automatically select InvoiceLineItems, and selecting a line-item Dataset does not require selecting its parent Dataset.
The native catalog does not expose provider-formatted Profit and Loss, Balance Sheet, Cash Flow, Trial Balance, or aging reports. Build those views in Resplendent from reusable facts instead:
AccountingEntriescontains one row per debit or credit posting, for both accrual and cash accounting methods. It includes the posting date, QuickBooks transaction and account identities, counterparty, memo, debit, credit, and signed net amount.ReceivableApplicationslinks customer payments and credits to invoices.PayableApplicationslinks bill payments and vendor credits to bills.
This keeps dashboard date filters in Resplendent. Profit and Loss, General Ledger, and Cash Flow queries filter the selected range; Balance Sheet and Trial Balance queries accumulate through the selected end date; aging queries calculate the open amount as of the selected end date.
Sync behavior
Section titled “Sync behavior”Datasets with an Intuit update timestamp sync incrementally. The first pull loads the configured first batch (default 1,000 source records) and replaces the warehouse. Remaining pages continue through history crawls until the source is exhausted or the configured history limit is reached. Nightly and manual resync use that same first-page-then-crawl path for every incremental Dataset, including Accounts, Customers, PurchaseLineItems, invoices, bills, payments, and Recurring transactions. They do not query every source page in one job.
Resplendent overlaps each update window, applies QuickBooks CDC deletions where the API supports them, and replaces the child rows for every changed parent transaction. This keeps invoice, bill, payment, purchase, deposit, journal-entry, and other transaction line Datasets consistent with their parent records. Truncated CDC stays incremental without deletion IDs; a later resync recovers missed deletes by replacing from page 1 and crawling again.
QuickBooks does not offer reliable update timestamps or CDC for every resource. Snapshot-only Datasets such as tax lists (TaxAgency, TaxCodes, TaxRates), CreditCardPayments, and ReimburseCharges still reconcile as complete snapshots on their configured schedule. Recurring transactions use updated-time queries for fast changes. Hard deletions are recovered by the nightly first-page replace and history crawl because Intuit does not include RecurringTransaction in its CDC endpoint.
AccountingEntries is the only report-backed transport. Resplendent requests bounded three-month General Ledger windows with explicit debit and credit columns, then stores canonical posting facts. The first sync loads the current window for Accrual and Cash. During a history cycle, every one-minute step refreshes both current windows and adds one older Accrual or Cash report, walking as far back as the Dataset lookback (default two years). After the cycle completes, the current windows refresh on the configured schedule. A completed walk prunes postings that disappeared from QuickBooks. A manual or nightly resync restarts that history cycle without replacing existing rows. It is not a cached QuickBooks statement: changing a dashboard date filter only queries the already-synced posting rows.
Attachments
Section titled “Attachments”Attachables and AttachableRefs sync attachment metadata only, such as file name, content type, size, category, note, and linked entity references. Resplendent does not download or store QuickBooks attachment file contents.
Payments
Section titled “Payments”QuickBooks has several similarly named resources:
Paymentsare QuickBooks Online Accounting receivable payment transactions.CreditCardPaymentsare Accounting payments toward credit-card account balances.PaymentMethodsare QuickBooks Online Accounting payment-method records, such as cash, check, or card labels used on accounting transactions.
QuickBooks Payments Charges are not synced as Datasets. Resplendent does not create QuickBooks Payments charges, refunds, eChecks, receipts, payment tokens, or QuickBooks Payments platform method metadata.
Accepted CData parity exceptions
Section titled “Accepted CData parity exceptions”The native QuickBooks Online Integration is not a CData driver replacement. These differences are expected:
- No new Legacy QuickBooks Online connections.
- No provider-formatted financial report Datasets and no arbitrary report endpoint or report parameter support.
- No arbitrary SQL, arbitrary GraphQL, arbitrary URLs, or arbitrary HTTP methods.
- No attachment file contents.
- No QuickBooks Payments method metadata, charges, refunds, eChecks, receipts, or complete payment-history Datasets.
- No custom-field metadata or custom-field value Datasets.
- US QuickBooks Online Companies only.
- No
TaxPaymentDataset (the Intuit resource is limited to non-US locales) orJournalCodeDataset (not available to US companies).
Legacy QuickBooks Online Integration
Section titled “Legacy QuickBooks Online Integration”Existing Legacy QuickBooks Online connections remain visible as QuickBooks Online (Legacy). You can manage, test, disable, and delete those existing connections according to normal integration permissions.
New Legacy QuickBooks Online connections are not available. Use the QuickBooks Online Integration for new QuickBooks Online connections.
QuickBooks Desktop setup
Section titled “QuickBooks Desktop setup”Desktop is a local app, so it needs extra components: the CData QuickBooks Desktop Gateway and the Resplendent Sync Agent.
The setup involves:
- Installing a sync agent on a Linux VM in your network
- Installing the CData Gateway on your Windows machine with QuickBooks
- Configuring the connection in Resplendent
For the full walkthrough, see the QuickBooks Desktop On-Premise Setup Guide.
Common use cases
Section titled “Common use cases”- Revenue recognition: Compare “Hours Worked” (from your PSA) against “Amount Invoiced” (from QuickBooks)
- Accounts receivable aging: Build charts showing outstanding balances by client
- Profitability by customer: Join service costs with QuickBooks revenue to see true margin per client