QuickBooks Desktop and ServiceTitan integration

What moves between them

The main flow moves from ServiceTitan into QuickBooks Desktop. Invoices and payments are synced on a schedule determined by your QBWC configuration interval (minimum 1 minute, typical 5 to 15 minutes). ServiceTitan inventory bills are read-only, so ml-connector reads them and posts corresponding AP entries into QB without attempting to write back. Vendor and customer records are synchronized bidirectionally to keep both systems aligned. Because QB is local-only and QBWC is synchronous, the polling interval determines sync latency; data from ServiceTitan reaches QB within minutes of creation.

How ml-connector handles it

ml-connector runs QBWC-compliant SOAP request handlers that receive the customer's credentials, return a session token to QBWC, and then process queries in the session. For each ServiceTitan invoice and payment received via webhook or polled from the ServiceTitan API, ml-connector constructs QBXML requests that add the corresponding Invoice or Check record in QuickBooks. Before every Modify operation, ml-connector re-queries the QB object to capture the current EditSequence, preventing collision errors if the same record is edited locally in QB. ServiceTitan AP bills are mapped to QB Vendor Bills with line items routed to the correct GL accounts and class codes if configured. Rate-limit handling: if ServiceTitan returns 429, ml-connector backs off and retries. QB session timeout (approximately 60 seconds per request) is handled by queuing large multi-record syncs and retrying individual requests if the QB session drops. Every record sync is logged with a full audit trail, including the QB transaction ID on successful post.

A real-world example

A mid-size plumbing and HVAC contractor runs ServiceTitan for dispatch, job scheduling, and field invoicing across 12 service trucks and 20 technicians, and uses QuickBooks Desktop for accounting on an office Windows machine. Before the integration, the office manager spent two hours each day exporting job invoices from ServiceTitan and re-entering them into QB, then reconciling material costs from purchase orders against AP. With ServiceTitan and QuickBooks Desktop connected via ml-connector, job invoices post to QB automatically when the technician completes them in ServiceTitan, material purchases sync as AP bills, and the cash flow statement reflects field revenue the same day. Month-end reconciliation that used to take three days now takes one, and the AP ledger is never out of sync with ordered materials.

What you can do

• •Sync ServiceTitan invoices and payments into QuickBooks Desktop automatically on the QBWC polling schedule, with full GL posting.
• •Map ServiceTitan inventory bills to QB vendor bills and post them to the correct accounts and cost centers.
• •Handle the QBWC session-token authentication handshake and retry when the QB session is temporarily busy.
• •Prevent concurrent-edit collisions by re-querying the current EditSequence on every QB record modification.
• •Maintain a complete audit trail of every synced record, including QB transaction IDs, for reconciliation and replay on failure.

Questions

How often do invoices and payments sync between ServiceTitan and QuickBooks Desktop?

Sync latency is determined by the QBWC polling interval you configure in the QBWC setup dialog. The minimum is 1 minute; most deployments use 5 to 15 minutes. ml-connector processes all pending ServiceTitan invoices and payments within that window and posts them to QB in the same batch, so the entire day's field revenue is typically in QB within 15 minutes of job completion.

Can ServiceTitan AP bills be modified or deleted in QuickBooks?

ServiceTitan AP bills are read-only in the ServiceTitan API; ml-connector posts them to QB as Vendor Bills but does not attempt to modify them if they change in ServiceTitan. Any amendments to AP bills must be made directly in QuickBooks or back in ServiceTitan, and the systems will reconcile on the next sync cycle.

What happens if the customer's QuickBooks is closed when QBWC tries to sync?

If QuickBooks is not running or not logged into the company file when QBWC calls ml-connector, the sync will fail for that cycle. ml-connector logs the failure and retries on the next QBWC interval. QB must be running continuously for reliable real-time sync; if downtime is expected, the QBWC interval can be configured to poll more frequently during business hours.