Accounting
QuickBooks Field Sales API Integration
Custom API connection — Intuit OAuth client requiredSalesPro Hub provides retry-safe customer, order and inventory APIs that a custom QuickBooks Online connector can consume. The connector must implement Intuit OAuth, entity mapping and accounting policy. There is no one-click QuickBooks marketplace app in the current product.
Test the field workflow firstSupport level: Custom API connection — Intuit OAuth client required. The workflow below separates shipped SalesPro Hub capabilities from connector work your implementation must provide.
What this solves
One operational hand-off, with explicit ownership
The integration boundary separates field execution from bookkeeping: reps capture customers and orders, the connector validates submitted records, and QuickBooks remains responsible for the selected accounting transaction. External IDs and references make retries auditable.
Available in SalesPro Hub today
- Map customers by immutable QuickBooks entity ID
- Read submitted orders without exposing in-progress drafts
- Acknowledge orders with QuickBooks references
- Return delivered or cancelled status safely
- Poll inventory and customer changes with stable cursors
- Retry outbound automation deliveries independently
Custom work and limitations
- Intuit OAuth and token lifecycle are not provided by SalesPro Hub.
- The connector must choose whether an order becomes an estimate, sales receipt or invoice.
- Payments, credit notes, tax-code mapping and multi-currency policy are custom implementation scope.
Implementation flow
How the connection works
- 1
Connect the QuickBooks company
Your middleware handles Intuit OAuth and binds one SalesPro Hub tenant to the intended QuickBooks company.
- 2
Synchronise customer identity
Store the QuickBooks customer ID as the external identity and update operational contact fields idempotently.
- 3
Import approved field demand
Poll submitted orders, validate SKU/customer mappings, and create the accounting entity selected by the business.
- 4
Reconcile references and status
Write the QuickBooks reference back, then process fulfilment callbacks and stock under a documented ownership policy.
Field mapping starting point
| SalesPro Hub field/event | QuickBooks Online equivalent | Implementation note |
|---|---|---|
| customer.external_id | QuickBooks Customer.Id | Immutable merge key. |
| customer.name | DisplayName | Attribute only; not a dedupe key. |
| order_number | PrivateNote/custom reference | Use in connector idempotency storage. |
| items[].sku | Item.Sku / ItemRef | Resolve and validate explicitly. |
| external_reference | Created transaction ID/DocNumber | Return after a successful commit. |
QuickBooks Online integration questions
Is there a native QuickBooks Online app?
No. The current support level is a custom API connection. SalesPro Hub ships the field-side APIs; your connector handles Intuit OAuth and QuickBooks entity mapping.
Which QuickBooks transaction does a SalesPro Hub order create?
That is an implementation choice. A connector can create an estimate, sales receipt or invoice depending on approval and fulfilment policy; SalesPro Hub does not assume one accounting workflow.
Are status retries safe?
Yes. Replaying the current SalesPro Hub status does not emit another event or apply inventory twice, and a conflicting external reference is rejected rather than overwritten.
Can customers be synced before orders?
Yes. The Customer API can upsert QuickBooks customers by their immutable external ID and optionally create the first outlet needed for route planning and order capture.
Validate the field workflow before connecting accounting
Import real products and customers, capture a representative order, then scope the integration against evidence instead of assumptions.