Accounting
Xero Field Sales API Integration
Custom API connection — Xero OAuth client requiredSalesPro Hub exposes the customer, submitted-order, inventory and signed-webhook building blocks needed for a custom Xero connection. Your connector must still authenticate with Xero, map contacts and accounting documents, and choose tax and stock policies. SalesPro Hub does not currently claim a native Xero OAuth connector or automatic invoice posting.
Test the field workflow firstSupport level: Custom API connection — Xero 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
A typical integration keeps field capture fast and offline-capable while using Xero as the accounting system. Submitted orders are transformed only after validation, and the resulting Xero document number is written back as the external reference for office and field teams.
Available in SalesPro Hub today
- Read submitted orders with line quantities, prices, discounts and VAT
- Upsert SalesPro Hub customers against immutable Xero contact IDs
- Write the Xero document number back to the field order
- Return fulfilment status through a replay-safe endpoint
- Use signed order webhooks or reliable polling
- Publish inventory quantities when Xero-connected stock is authoritative
Custom work and limitations
- Xero OAuth, tenant consent and token refresh must be implemented by your connector.
- SalesPro Hub does not automatically create Xero invoices, payments or credit notes.
- Account codes, tax rates, tracking categories and document policy remain implementation decisions.
Implementation flow
How the connection works
- 1
Authorise Xero
Your middleware completes Xero OAuth and securely stores the selected Xero tenant relationship.
- 2
Map contacts
Persist the Xero contact ID as the SalesPro Hub external identity so renames and email changes never create a second customer.
- 3
Transform submitted orders
Read only non-draft SalesPro Hub orders, validate the mapping, and create the chosen Xero document with an idempotency record.
- 4
Return the reference
Acknowledge the SalesPro Hub order with the Xero reference, then reconcile fulfilment and stock under one declared source-of-truth policy.
Field mapping starting point
| SalesPro Hub field/event | Xero equivalent | Implementation note |
|---|---|---|
| customer.external_id | Xero ContactID | Stable contact identity. |
| order_number | Reference | Recommended connector deduplication key. |
| external_reference | Xero document number/ID | Returned after successful creation. |
| items[].sku | ItemCode | Validate before automated posting. |
| vat_rate / vat_amount | TaxType and calculated tax | Confirm inclusive/exclusive policy. |
Xero integration questions
Does SalesPro Hub connect natively to Xero?
Not currently. SalesPro Hub provides the REST and webhook foundation, while a custom connector must handle Xero OAuth and accounting entity mapping.
Can field orders become Xero invoices?
A custom connector can transform submitted SalesPro Hub orders into the chosen Xero document. Automatic posting is not built into SalesPro Hub itself and must follow your approval, tax and account-code policy.
How are Xero contacts matched?
Use the immutable Xero ContactID as the external customer identity. Do not merge on company name or email because both can change.
Can Xero own stock quantities?
A Xero-connected inventory source can publish absolute quantities to SalesPro Hub by SKU. The implementation must prevent a delivery from being deducted twice.
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.