Sage Intacct
Get started with the Sage Intacct target!
Connector Details
| Name | Value |
|---|---|
| Platform | Sage Intacct |
| Auth Type | API Key |
| Direction | Bidirectional |
| API version | XML API |
| Testing Account | Trial Account Available |
| Unified Schema | Supported in the Accounting Schema |
Connector Versions
| Name | Version | Status | Description |
|---|---|---|---|
| Sage Intacct | v2 | GA | Supports Sage Intacct unified accounting schema |
| Sage Intacct | v1 | Deprecated | Supports Sage Intacct raw schema |
Configure the Credentials
The Sage Intacct target requires the following fields:
| Field Name | Description |
|---|---|
| Company Id | Your Sage Intacct Company Id |
| Sender Id | Your Sage Intacct Sender Id |
| Sender Password | Your Sage Intacct Sender Password |
| User Id | Your Sage Intacct User Id |
| User Password | Your Sage Intacct User Password |
How to find your Sage Intacct credentials
To learn more on how to access your Web Service credentials review Intacct docs.
If your tenants have a Sage Intacct Web Services developer license, they can provide their own sender id and sender password. If they do not have this license, you can use your own Sender ID/Password, which tenants will need to approve in Intacct settings.
Now you can insert the api keys into your hotglue Sage Intacct target settings:
That's it!
Supported Data
Below is a list of the accounting entities currently supported by the Sage Intacct target:​
| Entity | Status | Payload |
|---|---|---|
| Customers | 🟢 Supported | Customers Unified Schema |
| Vendors | 🟢 Supported | Vendors Unified Schema |
| Bills | 🟢 Supported | Bills Unified Schema |
| Payments | 🟢 Supported | |
| Items | 🟢 Supported | Items Unified Schema |
| Invoices | 🟢 Supported | Invoices Unified Schema |
| Journal Entries | 🟢 Supported | Journal Entries Unified Schema |
Don't see an entity you're looking for? Let us know
Sample Postman Collection
Use the below Postman collection to access sample payloads for the Sage Intacct target. Note: the samples are formatted to work with the API Source.
Updated 6 days ago