A Connectify-owned Sage Intacct adapter, not a packaged connector
The runtime takes care of it by keeping the Sage Intacct adapter inside our own runtime, monitored by our SRE rotation and updated as Sage ships breaking changes. That means the field maps, sync cadences, and replay rules are shaped to your exact data model — including PDF rendering for AP bills + statement reconciliations and PDF rendering for AP bills + statement reconciliations. For teams in Dallas, 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.
