Sage Intacct
Sage Intacct resource coverage, dimensions, and incremental reads.
Eleven resource families across finance records, dimensions, and attachments. Each company authorizes the application separately and needs a Web Services user with access to every module you use.
Capability summary
The adapter implements OAuth authorization-code flow with refresh-token rotation and explicit company identity. Customer companies must separately authorize the application and grant a Web Services user permission to each required module.
| Resource | Operations |
|---|---|
| Companies | List, get |
| Contacts | List, get, create, update |
| Accounts | List, get |
| Tracking categories | List, get |
| Invoices | List, get |
| Payments | List, get |
| Bills | List, get |
| Bill payments | List, get |
| Purchase orders | List, get |
| Journal entries | List, get |
| Attachments | List, get |
Incremental reads use provider modification timestamps with a replay overlap. Provider record keys stay remote identities; relationships are translated to canonical AccountingKit IDs before anything is persisted, so a record recreated in Intacct does not silently become a second entity here.
Connect a company
Register the Sage Intacct app in the console, then create a connect session with
"provider": "sage_intacct". Each company must separately authorize the application and grant a Web
Services user permission to every module you intend to read or write; a missing module permission
surfaces as an authorization failure on first use rather than an empty result.