QuickBooks Desktop and Deel integration

What moves between them

The primary flow runs from Deel into QuickBooks Desktop. New contractors on Deel create bills in QB, and contractor invoices from Deel become bill records in QB allocated to the contractor vendor account. Employee records from Deel (hires, status changes, terminations) synchronize into QB employee accounts so QB headcount matches your global payroll. Cost allocations and departments embedded in Deel records are mapped to QB account codes and classes. QB data does not flow back to Deel; this is a pull-only integration because Deel is the system of record for contractor and payroll compliance across jurisdictions.

How ml-connector handles it

ml-connector stores the QuickBooks Desktop SOAP endpoint URL per customer and the Deel API token encrypted. On the QB side, it performs the SOAP authentication handshake on each poll, receiving a session token from your authenticate() method, then issues ModifiedDateRangeFilter queries to detect changes since the last poll. It reads the current EditSequence on each vendor and employee record before updating to prevent concurrent-edit conflicts (a QB requirement). On the Deel side it accepts webhook events for contract and employee changes, verifies the HMAC-SHA256 signature against the registered webhook secret, and refreshes the bearer token if a call returns 401. Contractor invoices from Deel are mapped to QB bill line items with the department and cost center from the invoice embedded in the QB line detail. The integration tracks the QB QBXML version to match the customer's installed QB release and respects the list-entry ceiling (14500 for Pro/Premier, 100000+ for Enterprise). Because QuickBooks Desktop does not support bulk idempotency keys, ml-connector tracks which Deel records have already been sent to QB and deduplicates locally before submitting.

A real-world example

A consulting firm with 30 core staff and 15 active contractors uses QuickBooks Desktop for accounting and Deel for global contractor management and EOR in four countries. Before the integration, the finance team received contractor invoices from Deel, manually checked them against the contracts in QB, and re-entered the amounts into bills by hand, a process that introduced typos and delays. Employee cost reconciliation at month-end required exporting headcount from Deel and cross-checking it against QB payroll accounts. With QuickBooks Desktop and Deel connected, each contractor invoice appears as a bill in QB within minutes of creation, and employee hires, terminations, and status changes flow into QB automatically. The manual entry step disappears, and month-end reconciliation starts with accurate, up-to-date headcount and invoices.

What you can do

• •Sync Deel contractor invoices into QuickBooks Desktop bills, automatically allocating to the correct vendor account based on contractor records.
• •Keep QuickBooks Desktop employee accounts in sync with Deel hires, terminations, and status changes using real-time webhooks.
• •Map Deel cost centers and departments to QuickBooks Desktop account codes and classes so invoices land on the correct GL account.
• •Authenticate with QuickBooks Desktop via SOAP session tokens and with Deel via bearer token or OAuth2, with automatic token refresh and HMAC-SHA256 webhook signature verification.
• •Poll QuickBooks Desktop on a configurable schedule while accepting real-time push events from Deel, with deduplication and EditSequence conflict detection.

Questions

Which direction does data move between QuickBooks Desktop and Deel?

The primary flow is Deel into QuickBooks Desktop. Contractor invoices, employee records, and hires and terminations from Deel appear as bills and employee accounts in QB. QB data does not flow back to Deel because Deel is the system of record for contractor and employee compliance across 150+ countries. If QB is modified by a user, those changes are not overwritten by the integration.

How does the integration handle QuickBooks Desktop's requirement for EditSequence and concurrent-edit detection?

Before updating any QB vendor or employee record, ml-connector fetches the current EditSequence value (QB's version counter) and includes it in the update request. If another user in QB has modified the record since the fetch, QB rejects the request with an EditSequence mismatch error. ml-connector catches this, re-fetches the record, merges the Deel changes with QB's latest state, and retries, preventing data loss.

What happens if the QBWC polling interval is very short or Deel webhooks arrive out of order?

ml-connector deduplicates on both sides. On the QB side it tracks which Deel IDs have already been sent to QB and skips retransmission even if QBWC polls within seconds. On the Deel side it uses webhook timestamps and record IDs to detect out-of-order events and applies them in the correct sequence, discarding duplicate or stale updates, so the final state in QB is always consistent with the latest Deel record.