Connect QuickBooks Online to OLT Accounting

Authorize one QuickBooks Online company for your OLT organization, then pull the 11 supported entity types, including Estimates and Accounts. Ten mapped OLT record types expose separate QuickBooks-to-OLT pull and OLT-to-QuickBooks create-or-update controls; the chart of accounts remains an inbound reference mirror.

Setup requirements

Before you connect QuickBooks Online:

  • Invoices & Quotes must be enabled for your OLT organization.
  • An organization owner or admin connects one QuickBooks company to that organization.
  • The QuickBooks connector must be configured for your deployment.

Creating an OLT account does not establish the QuickBooks connection automatically.

Two synchronization directions

  • OLT → QuickBooks

    Create new QuickBooks records and update linked records from OLT.

  • QuickBooks → OLT

    Apply supported QuickBooks webhook changes to OLT, including create, update, void, delete, emailed, and merge events where applicable.

Connect one QuickBooks company first

Each OLT organization authorizes one QuickBooks Online company through OAuth. Owners and admins select that company before its organization-scoped sync settings, mappings, records, and review queues can be used.

First-connect setup

Match references before importing QuickBooks history

The guided setup keeps mirrored QuickBooks records separate from native OLT records until an administrator reviews the reference matches and starts the ordered transaction import.

  1. 1

    Confirm the prerequisites

    Connect one QuickBooks Online company to the OLT organization first. Setup requires an OLT organization owner or admin with Accounting write access, and the QuickBooks signer needs permission to authorize connected apps.

  2. 2

    Match reference data

    Review each reference before importing transactions. Link it to an existing OLT record, create a new record, or skip it so setup does not create an avoidable duplicate.

    • Customers
    • Vendors
    • Products
    • Tax codes
  3. 3

    Import transactions in dependency order

    After the reference decisions, OLT imports each not-yet-imported transaction type in the order its dependencies require.

    • Invoices
    • Estimates
    • Credit memos
    • Payments
    • Bills
    • Vendor credits
    • Bill payments
  4. 4

    Skip now or resume later

    Exit during setup and OLT keeps the current stage so you can return to it. If you choose Skip for now, reopen the wizard from QuickBooks Sync; previous links and imports remain, and a rerun handles only records still needing attention.

  5. 5

    Review unresolved imports

    A transaction that cannot resolve a required reference enters the QuickBooks Sync review queue for the existing fix-and-retry flow instead of becoming an incomplete OLT transaction.

Inbound customer receipts

Import complete QuickBooks customer receipts into OLT

Buyer value

Accounting teams can bring supported QuickBooks customer receipts into OLT while preserving unapplied customer credit and complete split-invoice allocation context.

Prerequisites

  • Inbound customer-receipt sync requires administrator opt-in for QuickBooks-to-OLT Payment sync.
  • Each inbound receipt must resolve to one linked OLT customer.

Current limitations

  • A receipt with no referenced invoice imports as an unapplied receipt and remains visible as a customer credit.
  • A split receipt imports only after every referenced invoice resolves.
  • Mixed invoice currencies or a missing required exchange rate are unsupported currency evidence; that evidence or any unresolved reference sends the complete receipt to review without a partial import.
  • Supplier disbursements follow a separate inbound path and still require one linked bill.

Reviewed 3PL invoice export

Create one QuickBooks Invoice from a reviewed 3PL customer invoice

Buyer value

3PL billing teams can carry a finalized OLT customer invoice into the connected QuickBooks company without re-entering its reviewed charge lines. The OLT invoice remains the unchanged operational record.

Prerequisites

  • 3PL mode, an active QuickBooks Online connection, and an organization administrator with WMS and Invoices write access.
  • A finalized sent invoice linked to exactly one active QuickBooks customer that uses the same currency.
  • Usable QuickBooks tax references and one active, synced QuickBooks Item selected for every charge line.

Review before creation

Start with the read-only preview, resolve every mapping, currency, amount, and tax blocker, then review the refreshed customer and total, select the confirmation checkbox, and explicitly create the invoice. If the invoice or mappings changed after preview, OLT rejects the stale confirmation and requires a new review.

Supported result

Confirmation idempotently creates one QuickBooks Online Invoice and refreshes its mirrored record in OLT. A safe retry returns the completed result instead of intentionally creating a duplicate, while the OLT invoice, charges, payments, balance, and customer link stay unchanged.

Current limitations

  • The export supports finalized sent invoices only and blocks invoices with payments, credits, write-offs, balance adjustments, shipping, or invoice-level discounts.
  • Customer and invoice currencies must match, stored amounts and tax references must reconcile, and every charge line must map to exactly one active, synced QuickBooks Item.
  • This attended, one-invoice-at-a-time workflow is unavailable in demo sessions and does not schedule or bulk-create QuickBooks invoices.

Supplier disbursement direction limits

QuickBooks BillPayment handling is intentionally different by direction: outbound OLT records must be ready for a provider write, while unsupported inbound link shapes remain available for administrator review.

OLT → QuickBooks: applied bill settlements

Outbound supplier disbursements represent applied bill settlements; OLT does not use this path for unapplied vendor deposits.

  • All applications need linked bills in one currency

    For a multi-bill settlement, every application must resolve to a linked QuickBooks bill, and every applied bill must use one currency. OLT sends one QuickBooks BillPayment line per application.

  • Unapplied vendor deposits are rejected

    A supplier disbursement with no applied bill is an unapplied vendor deposit, not a QuickBooks BillPayment. OLT rejects the outbound push until the deposit is applied to a bill.

  • A bank or card ledger is required

    The connected company must have a usable QuickBooks bank or credit-card ledger reference for the BillPayment's Check or CreditCard method before OLT can send it.

QuickBooks → OLT: unsupported link shapes stay in review

Inbound BillPayments are materialized automatically only through the supported single-bill path; the two unsupported bill-link shapes remain in transaction review.

  • Zero-bill records remain in review

    An incoming QuickBooks BillPayment with no QuickBooks Bill link remains in transaction review instead of becoming an OLT supplier payment.

  • Multi-bill records remain in review

    An incoming QuickBooks BillPayment with links to multiple QuickBooks Bills remains in transaction review instead of being split or materialized automatically in OLT.

Inbound, reviewed, attended, and configurable workflows

The connection keeps mirrored QuickBooks context distinct from reviewed native imports, while outbound work requires either an attended record-level action or administrator-configured per-entity automation.

  • Inbound mirror

    An initial or manual full sync refreshes the connected company's QuickBooks accounts and supported transaction snapshots inside its OLT organization. Those mirrors support detail, mapping, and review workflows; they become native OLT records only through a supported import or link.

  • Reviewed import into OLT

    Unlinked QuickBooks customers, vendors, and products enter an administrator review queue to import, link, or reject. Supported incoming transactions write to native OLT only after required dependencies resolve; otherwise they wait in transaction review.

  • Attended outbound sync

    Accounting users with write access can push, re-sync, or retry customers, vendors, products, quotes / estimates, invoices, bills, customer receipts, and supplier disbursements. QuickBooks-origin records remain read-only for this attended outbound action.

  • Configurable automatic sync

    Administrators configure OLT-to-QuickBooks and QuickBooks-to-OLT automation separately for each of the ten business-record types. Enabled outbound automation covers supported creates and later changes; enabled inbound automation handles supported QuickBooks change events.

Configurable two-direction sync matrix

OLT to QuickBooks creates new QuickBooks records and updates linked records from OLT. QuickBooks to OLT applies supported create, update, void, delete, emailed, and merge events where applicable. The table shows which controls start on and which require administrator opt-in; administrators can change either direction by record type.

  • Customers Customer OLT customers map to QuickBooks Customers. OLT to QuickBooks: Default on. QuickBooks to OLT: Default on.
  • Vendors Vendor OLT vendors map to QuickBooks Vendors. OLT to QuickBooks: Default on. QuickBooks to OLT: Default on.
  • Products Product / service (Item) OLT products map to QuickBooks Items. OLT to QuickBooks: Default on. QuickBooks to OLT: Default on.
  • Quotes / estimates Estimate OLT quotes map to QuickBooks Estimates. OLT to QuickBooks: Default on. QuickBooks to OLT: Administrator opt-in.
  • Invoices Invoice OLT invoices map to QuickBooks Invoices. OLT to QuickBooks: Administrator opt-in. QuickBooks to OLT: Administrator opt-in.
  • Bills Bill OLT supplier bills map to QuickBooks Bills. OLT to QuickBooks: Administrator opt-in. QuickBooks to OLT: Administrator opt-in.
  • Customer receipts Payment OLT customer receipts map to QuickBooks Payments. OLT to QuickBooks: Default on. QuickBooks to OLT: Administrator opt-in.
  • Supplier disbursements Bill payment OLT supplier disbursements map to QuickBooks BillPayments. OLT to QuickBooks: Default on. QuickBooks to OLT: Administrator opt-in.
  • Credit memos Credit memo OLT credit memos map to QuickBooks CreditMemos. OLT to QuickBooks: Default on. QuickBooks to OLT: Administrator opt-in.
  • Vendor credits Vendor credit OLT vendor credits map to QuickBooks VendorCredits. OLT to QuickBooks: Default on. QuickBooks to OLT: Administrator opt-in.

Inbound chart-of-accounts mirror

The account mirror supports connector setup, account selection, and mapping. It does not add account creation or editing to the configurable two-way business-record matrix.

  • Chart of accounts QuickBooks accounts are mirrored into the connected organization for account selection and mapping. Account creation and editing are not exposed as another configurable two-way record type.

Mappings and review come before ledger writes

Unlinked QuickBooks customers, vendors, and products go to an admin review queue to import, link, or reject. Incoming transactions need their required party, product, tax, and transaction links; unresolved dependencies or document-number conflicts stay in transaction review instead of silently changing an OLT ledger. Outbound records also need the applicable QuickBooks mappings and account defaults.

Retries are bounded and record-specific

Retryable automatic outbound failures run immediately and can retry after 5 seconds, 30 seconds, 5 minutes, and 30 minutes; terminal errors stop sooner. After the final error, correct the record or mapping and use its attended retry action. The general attended outbound route supports customers, vendors, products, quotes / estimates, invoices, bills, customer receipts, and supplier disbursements, but not credit memos or vendor credits. If a server restart interrupts a pending background retry, the record remains available for an attended retry. Inbound transaction review can retry all seven supported transaction types after missing links are fixed.

Enabled does not mean every record always synchronizes

A direction setting makes a record eligible for that path. Connection status, permissions, mappings, validation, record state, conflict review, and the QuickBooks response can still leave a record skipped, queued for review, or available for retry.

Outbound sync writes to the connected live company

A confirmed attended push or enabled automatic OLT-to-QuickBooks sync creates or updates records in the QuickBooks company selected for that organization; it is not a preview. Verify the connected company, mappings, account defaults, and source record before confirming a push or enabling automation.

Prerequisites and operating boundaries

Direction settings define eligible paths rather than unconditional bidirectional synchronization. Every attempted sync still follows the active connection, access, mapping, dependency, provider-default, retry, and provider-version rules below.

  • One active company connection Each OLT organization synchronizes through one active QuickBooks Online company connection. Disconnecting or replacing that connection stops the old company's records from participating in current sync work.
  • Relevant module access Connecting requires an organization owner or admin with Accounting access. Changing connector settings and running attended outbound actions also require the applicable Accounting write access.
  • Per-entity direction settings Administrators enable OLT-to-QuickBooks and QuickBooks-to-OLT eligibility separately for each business-record type; enabling one direction does not enable the other.
  • Required QuickBooks account defaults Applicable outbound records need the connected company's required QuickBooks income, expense, bank, tax, or other account defaults before a provider write can succeed.
  • Linked dependent records Transaction sync needs its required linked customer, vendor, product, invoice, bill, tax, and transaction records. OLT pushes supported outbound dependencies first and sends unresolved inbound dependencies to review.
  • Bounded retries Retryable automatic outbound failures use four delayed retries after the initial attempt; terminal errors stop sooner, and interrupted or exhausted work remains available for an attended retry after its cause is corrected.
  • Re-sync stale provider versions If QuickBooks rejects an update because its stored provider version is stale, re-sync the record to refresh that version before retrying. OLT does not automatically retry a stale-version write because QuickBooks may contain a concurrent change.

Record synchronization does not move funds

OLT creates the linked QuickBooks Payment record only after money arrives. It does not charge a card, withdraw or transfer money, or pay a bill.