A Connectify-owned Xero adapter, not a packaged connector
The runtime takes care of it by keeping the Xero adapter inside our own runtime, monitored by our SRE rotation and updated as Xero Limited ships breaking changes. That means the field maps, sync cadences, and replay rules are shaped to your exact data model — including Multi-currency aware posting and FX revaluation and Webhook-driven sync for instant statement updates. For teams in Mesa, the difference shows up the first time the upstream API throws a 500 — the adapter retries, journals the failure, and never silently swallows a transaction.
