Workshop-controlled OAuth
The workshop authorises its own Xero organisation without giving Workshop HQ its Xero password.
Opening Workshop HQ
Loading your workspace…
This guide covers connection, account mapping, the exact invoice and payment boundary, safe retries, troubleshooting and disconnection for Australian workshops.
The workshop authorises its own Xero organisation without giving Workshop HQ its Xero password.
Finalised invoices and fully paid payments move from Workshop HQ to Xero.
Visible errors and duplicate checks support a safe retry after the underlying issue is corrected.
Setup sequence
Do not treat the green Connected state alone as completion. Confirm the organisation, save both account mappings and run a controlled end-to-end test.
Sign in to Workshop HQ as an owner or authorised manager. Open Settings, choose Integrations, then choose Xero accounting.
Choose Connect Xero, sign in through Xero and authorise the organisation that belongs to this workshop. Workshop HQ never asks for or stores the workshop's Xero password.
After returning to Workshop HQ, check that the green Connected panel names the expected Xero organisation. Disconnect and start again if the wrong organisation was selected.
Choose the Xero revenue account used for invoice lines and the bank or clearing account used for matching payments. Save the mapping before relying on automatic sync.
Create a clearly identifiable test customer and repair order, finalise one GST-inclusive invoice, then confirm the authorised sales invoice, contact, totals and vehicle reference in Xero.
Released sync rules
This is the current production boundary. It is deliberately narrower than a generic claim that everything is synchronised.
Troubleshooting
Return to Settings, Integrations, Xero accounting and choose Connect Xero again. The authorisation request uses a short-lived security state and cannot be resumed.
Start the connection again and authorise only the organisation used by this workshop. Workshop HQ deliberately refuses an ambiguous multi-organisation result.
Confirm the signed-in Xero user can access the intended organisation, then repeat the connection and approve the requested access.
Refresh the page and choose an active Xero revenue account plus an active bank or payment-enabled clearing account. Archived or incompatible accounts cannot be used.
Review the tax treatment of the selected Xero sales account. Workshop HQ stops the payment handoff when Xero's amount due differs from the Workshop HQ invoice total.
Read the visible Xero error on the invoice or settings page, correct the account or authorisation issue, then use Sync finalised invoices now. The retry checks local and Xero records before creating anything.
Choose Connect Xero again. Workshop HQ uses an offline refresh token, but a revoked or invalid connection must be authorised again by the workshop.
Email the workshop ID, affected Workshop HQ invoice number and exact visible error to [email protected]. Never send a Xero password, access token or client secret.
Open Settings, Integrations, Xero accounting and choose Disconnect. Workshop HQ asks Xero to remove the live organisation connection, then removes the saved connection and encrypted authorisation credentials for that workshop.
Historical Workshop HQ invoice identifiers and audit context may remain so the workshop can understand previous accounting handoffs. Disconnecting does not delete invoices, contacts or payments already created inside Xero.
The released flow does not claim two-way invoice editing, separate partial-payment transfer, supplier bills, purchase orders, credit notes, payroll, bank feeds, reconciliation or BAS lodgement.
See every integration statusNo. Drafts remain in Workshop HQ. A Xero sales invoice is created only after the workshop finalises the invoice.
Not as separate payments in the current release. The matching Xero payment is created when the Workshop HQ invoice becomes fully paid.
No. The released connection is one-way from Workshop HQ to Xero and does not claim two-way invoice editing.
It stores the returned Xero identifiers, searches Xero for the Workshop HQ invoice number before creating a record and uses stable idempotency keys for contact, invoice and payment requests.
Workshop HQ asks Xero to remove the active connection, then removes the saved connection and encrypted authorisation credentials for that workshop. Historical invoice identifiers and audit context may remain on the workshop records.
Email [email protected] with the workshop ID, the affected Workshop HQ invoice number and the exact visible error. Do not send Xero passwords, access tokens or client secrets.