Connect and sync QuickBooks
Authorize the intended QuickBooks company, import a bounded history, and keep source records current.
On this page
Connect a company
- Open the merchant's QuickBooks integration and confirm the Carden environment.
- Start the Intuit consent flow, or invite the company's QuickBooks administrator to complete it.
- On Intuit's consent screen, select the intended company and approve the requested accounting access.
- After consent, verify the company name, realmId, and connection state in Carden.
- Wait for the initial import and review rejected records or missing dependencies before linking a payment destination.
Connection invitations are sensitive, expiring links. Replace an expired or misdirected invitation instead of forwarding it. Completed consent confirms provider access; import status separately shows whether invoice data is available.
Understand the sync model
The initial import covers a bounded history. Carden then persists a checkpoint for incremental refreshes and runs scheduled reconciliation to recover missed or changed objects. QuickBooks webhooks are refresh triggers, not a complete source of record changes.
| State | Meaning | Next action |
|---|---|---|
| queued or active | Background work was accepted or is running. | Wait or inspect progress; do not start overlapping full imports. |
| succeeded | The requested import work completed. | Review invoice readiness and exceptions. |
| partially_succeeded | The run completed with rejected records or reconciliation exceptions. | Inspect the affected records before preparation. |
| failed | The run stopped because of provider, authorization, source, or system failure. | Correct the cause and retry the sync operation. |
Review imported invoices
- Confirm identity, currency, totals, balance, and invoice state against QuickBooks.
- Review Item and Preferences dependencies used by the mapper.
- Resolve missing factual product codes or units through QuickBooks or an approved item mapping.
- Keep tax-inclusive invoices, group lines, deposits, unsupported freight, unsupported fractional quantities, and invalid arithmetic in exception review.
The stored mapper currently supports USD, CAD, EUR, GBP, AUD, and NZD and accepts up to 1,000 source lines before a payment adapter's narrower limit is applied. These limits are reasons to block unsupported records, never to truncate or alter them.
Production checklist
- Authorize the intended live company rather than reusing a sandbox connection.
- Verify scheduled reconciliation and outbound job dispatch are operating in the deployed environment.
- Confirm tenant membership, integration permissions, and encrypted token configuration.
- Run a limited source review before enabling a payment workflow.
- Retain source timestamps, sync run IDs, and safe request IDs for support without logging OAuth tokens.