How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Sage Intacct adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
Is this a packaged Sage Intacct connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Fort Worth, Texas. After go-live, the Sage Intacct adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
How long does the Sage Intacct integration take to ship?
Our standard window is thirty days from signed scope to live Sage Intacct adapter in production, plus a one-week monitored stabilization phase. For Fort Worth, Texas, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Does it work with our existing Sage Intacct licenses?
Yes — the adapter rides on top of your existing Sage Intacct subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
What happens if Sage Intacct changes their API after we go live?
Our SRE team monitors Sage Intacct change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.