Bookkeeping
What QuickBooks transaction will be created?
The implementation must choose and test an estimate, sales receipt or invoice. SalesPro Hub does not assume that every field order has the same accounting outcome.
All integrations
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.
Do not buy implementation work until the source of truth, idempotency key, failure owner and reconciliation process are written down.
QuickBooks Online customer APIQuickBooks Online integration evidence
Connect the operating records—not just the brand names
A useful QuickBooks Online connection needs stable identities, explicit ownership and a visible exception path. These are the SalesPro Hub records the implementation must map and reconcile.
Written and maintained by Paul · Updated 28 July 2026
Give bookkeeping a reviewable hand-off
The source order and resulting accounting transaction should retain enough common identity for finance to investigate a difference.
Bind the intended accounting company
The custom connector must handle consent, selected company identity, access-token expiry, refresh-token rotation and revocation.
Choose the transaction type before mapping
A field order does not automatically determine whether QuickBooks should receive an estimate, sales receipt or invoice.
Make policy an implementation input
Document customer identity, item lookup, tax, account, currency and approval choices before development starts.
Keep identities stable through retries
The connector should distinguish a safe replay from a conflicting request and never silently relink an order to another document.
Prove the actual company workflow
A representative pilot should include the buyer’s real products, taxes, customer types, approvals and exception cases.
Architecture and ownership
Design the QuickBooks Online operating contract before the data flow
QuickBooks Online requires a custom Intuit OAuth client and an explicit accounting-entity decision. A submitted field order could become an estimate, sales receipt or invoice depending on credit, fulfilment and approval policy. The connector maps the stable QuickBooks company and customer identities, validates ItemRef and tax details, submits only the approved transaction, and returns the external ID and document number to the field order.
QuickBooks owns the selected accounting transaction, company identity, Customer.Id, ItemRef, tax and official document state.
SalesPro Hub owns the mobile field order, source order number, visit context and operational status before the hand-off.
Customer and item changes need one declared owner; DisplayName and email are not safe identity keys.
Inventory quantities require a separate source-of-truth decision and should not be inferred from a posted sales transaction alone.
Security review boundary
The OAuth client must bind the correct QuickBooks company, protect access and refresh tokens server-side and handle revocation. SalesPro Hub API keys remain tenant-scoped and least-privilege. The connector should log the realm/company identity, source operation and external result without recording credentials or unnecessary accounting payloads.
Failure recovery
Decide what happens when the happy path stops
A useful QuickBooks Online integration is not defined by one successful demo. It is defined by what remains durable, what can be replayed safely, what must stop, who sees the exception and how both systems are reconciled.
| Failure or conflict | Required response |
|---|---|
| OAuth refresh or revocation | Stop posting, preserve pending work and require a controlled reconnect when the refresh grant is no longer valid. |
| Duplicate DisplayName | Use the immutable QuickBooks Customer.Id and the approved external mapping instead of guessing from names. |
| Wrong transaction policy | Reject the operation before creation if estimate, receipt or invoice rules are incomplete or contradictory. |
| Stale entity version | Refresh the relevant QuickBooks entity and apply the vendor concurrency contract instead of overwriting blindly. |
| Lost response or retry | Use the source order identity and connector result store to find the existing transaction before creating another. |
Acceptance plan
Tests to run with the buyer’s real edition and workflow
A sandbox proves API syntax. Production readiness requires representative identities, accounting or CRM rules, failures and reconciliation. Record the result against the exact product edition and adapter release; do not transfer evidence from a different vendor version by assumption.
- Authorise the exact QuickBooks company, rotate tokens and exercise revocation and reconnect.
- Map renamed customers and duplicate-looking display names through stable entity IDs.
- Test the approved estimate, sales receipt or invoice policy and reject disallowed alternatives.
- Post discounts, tax, multiple line items and an unknown ItemRef.
- Replay an identical order and submit a conflicting order with the same source identity.
- Reconcile source total, tax, QuickBooks transaction ID, DocNumber and returned field-order reference.
Delivery lifecycle
From QuickBooks Online discovery to a supportable steady state
Treat the connection as a small operational product with owners, release evidence and a lifecycle. These phases stop a promising prototype from becoming an invisible production dependency that only one developer understands.
- 1
Discover the real workflow
Name the exact QuickBooks Online product, edition, company or tenant, licensed interface and deployment. Follow one representative customer and order from field capture to its final external state. Record current manual checks, approval points, cut-off times, volumes and the people who resolve errors. Brand-level assumptions are not a technical scope.
- 2
Write the data contract
List required and optional fields, types, formats, allowed values and stable identities. Declare a source of truth for customers, outlets, products, prices, tax, stock, documents and status. Define create, update, deactivate and delete behaviour separately. Include the idempotency key, cursor or event identity and the external reference returned after a successful commit.
- 3
Build the exception contract
Classify authentication, rate-limit, connectivity, validation, mapping, conflict and external-service errors. Decide which faults retry, how often and with what backoff; which stop immediately; and where exhausted work becomes visible. Assign a named business or technical owner and define the evidence needed to replay, correct, reject or manually reconcile an operation.
- 4
Prove a controlled pilot
Use representative South African customers, addresses, SKUs, rand values, VAT rules, discounts, warehouses and approval cases. Include duplicates, missing mappings, offline or network loss, service restart, expired credentials and a lost response after external commit. Reconcile counts and commercial totals in both systems; a green API response alone is not acceptance.
- 5
Release with a rollback plan
Version the mapping, adapter and configuration together. Record the approved package, supported architectures, required runtime, database or API prerequisites and the previous known-good state. Start with a bounded customer or order cohort, monitor exceptions and keep a tested way to pause new work without deleting the durable queue or losing reconciliation evidence.
- 6
Operate and review
Monitor reachability, authentication, latency, retry and dead-letter trends, external rate limits, installed version and reconciliation differences. Rotate credentials and exercise recovery before an emergency. Review vendor API or SDK changes and the adapter support matrix before upgrades. Retire obsolete credentials, mappings and data under the agreed security and POPIA operating process.
South African procurement note: confirm the parties’ POPIA roles, purposes, access, retention, operator terms and incident process during procurement. Hosting and subprocessors should be confirmed from current contractual evidence. Product controls can support a lawful implementation, but an integration page cannot certify the buyer’s operating practices or replace legal and security review. Before expanding the pilot, agree measurable release criteria: the maximum acceptable age of a pending operation, expected daily reconciliation window, alert response owner, acceptable mapping-error rate, retry ceiling and the evidence required to close an incident. Keep deployment, configuration and mapping versions beside the reconciliation result so a later difference can be traced to the exact operating state. Review those criteria when order volume, product range, warehouses, tax treatment or the external vendor version changes. A technically healthy connector can still create the wrong commercial result if ownership or mapping assumptions have drifted. Keep the sign-off, evidence and named operational owners accessible for every later support and change review.
Decision-maker intent
Questions different buyers ask about QuickBooks Online
Development
Is there a one-click QuickBooks app?
No. The current page documents a custom OAuth and API connection. A marketplace installation and complete Intuit token flow are not shipped claims.
Sales operations
Can customers sync before orders?
Yes. The SalesPro Hub Customer API can upsert against an immutable external customer identity before field orders use that account and outlet.
Professional includes scoped APIs and signed webhooks for custom, customer-operated middleware. A managed Windows connector, remote configuration, heartbeat/version monitoring and managed recovery require Enterprise—and only become available for this named system after its real adapter passes the published release boundary.
Buyer decision guide
Scope the QuickBooks Online connection before buying implementation
A good trial should prove the workflow with your data—not rely on a sales promise.
Strong fit when you need
- Teams that have already proved the SalesPro Hub field workflow with real data.
- Businesses able to assign an owner for mapping, credentials and exception handling.
- Integrations built around stable customer, order or product identifiers.
Confirm during the trial
- The exact QuickBooks Online product, edition and API access available to your account.
- The system of record for customers, stock, tax, status and accounting documents.
- Whether polling, signed webhooks or middleware best fits your network and support model.
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.
Connected buying journey
Compare every SalesPro Hub integration path
Review the managed runtime, ERP, accounting, CRM and automation options before choosing a delivery model. Every page publishes its current support boundary, required custom work and Enterprise plan status.
Enterprise integration operationsManaged Windows ConnectorsEnterprise only — managed runtime live; vendor adapters require release approvalERP and accountingSage & PastelGuided API recipe — custom setup requiredERP and distributionSAP Business OneEnterprise controlled preview — activation and acceptance approval requiredERP and manufacturing distributionSYSPROEnterprise integration plan — managed SYSPRO adapter not releasedERP and accountingSage 300Enterprise integration plan — managed Sage 300 adapter not releasedCRMHubSpotCustomer sync API — custom workflow requiredAccountingXeroCustom API connection — Xero OAuth client requiredAutomationZapierDeveloper trigger endpoints — no public marketplace app
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.