Not a live Xero App Store push — staged OAuth + dry-run only
Accounting
Xero for workshops — dry-run today, live push next
AU owners rightly treat Xero as table stakes (MechanicDesk and Workshop Software ship native). Our stance: repair orders, estimates, and operational invoices stay authoritative in the workshop system; ACCREC payloads stage and dry-run push today; remote sandbox push is a gated live path next. This page stays Dry-run — never “Connected” — until code and sandbox proof exist.
- →Status: Dry-run — stage ACCREC + dryRunPush; connected:false by default in API status
- →Staged OAuth shell may store tokens; exportMode remains dry_run unless product-gated live
- →Gated live sandbox push is the next honesty step — still not marketed Connected until evidence
- →GST line mapping and inclusive/exclusive tenant settings ride with the adapter
- →Prefer Xero before MYOB for the first AU accounting port (MYOB is Dry-run boundary / Planned live)
- →US peers are QBO-first with rare Xero — QBO is US later, not day-one
- →Until live push: operational GST invoices + AR run in Wrench; books stay in Xero via your normal export habits
Is Xero connected today?
No. API status reports connected:false and mode:dry_run. We stage invoices and can dry-run push payloads. A production OAuth marketplace listing and remote push are not claimed — gated live path only when product-enabled.
How does this compare to MechanicDesk Xero?
MechanicDesk ships native Xero on their versions — that is the AU day-one bar we respect. Wrench differentiates on board/portal/PWA workflow, open APIs, and transparent packaging while the Xero live push catches up.
Will you claim “Connected” early?
No. Marketing badges match the catalog: Live, Stub, Dry-run, or Planned. Dry-run never becomes Connected on a brochure, even if a gated sandbox path exists in code.
Related: GST invoicing · All integrations · MechanicDesk alternative · Competitive compare