Sync data from your warehouse to Sage Intacct to streamline your financial processes and gain comprehensive insights into your financial data.
Supported syncing
| Type | Description | Supported Sync Modes | API Reference |
|---|---|---|---|
| AR Adjustment | Sync data from any source to the AR Adjustment object | Insert | AR Adjustment docs |
| AR Payment | Sync data from any source to the AR Payment object | Insert | AR Payment docs |
| Contact | Sync data from any source to the Contact object | Upsert, Update, Insert | Contact docs |
| Customer | Sync data from any source to the Customer object | Upsert, Update, Insert | Customer docs |
| Invoice | Sync data from any source to the Invoice object | Update, Insert | Invoice docs |
| Journal Entry | Sync data from any source to the Journal Entry object | Insert | Journal Entry docs |
| Transaction | Sync data from any source to the Transaction object | Update, Insert | Transaction docs |
For more information about sync modes, refer to the sync modes docs.
Connect to Sage Intacct
Go to the Destinations overview page and click the Add destination button. Select Sage Intacct and click Continue. You can then authenticate Hightouch to Sage Intacct.
Enter the following required fields into Hightouch:
- Sender ID: Enter a valid Sender ID.
- Sender Password: Enter a valid Sender Password.
- Company ID: Enter a valid Company ID.
- User ID: Enter a valid User ID.
- User Password: Enter a valid User Password.
Sync configuration
Once you've set up your Sage Intacct destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Sage Intacct destination you want to sync to.
Syncing AR Adjustment
Sync data from any source to the AR Adjustment object
Field mapping
Hightouch lets you sync AR Ajustment fields via field mapping. You can map data from any of your model columns to the default AR Adjustment fields. Ensure your model columns data types match the data types of the fields you want to sync to.
Syncing AR Payment
Sync data from any source to the AR Payment object
Field mapping
Hightouch lets you sync AR Payment fields via field mapping. You can map data from any of your model columns to the default AR Payment fields. Ensure your model columns data types match the data types of the fields you want to sync to.
Syncing Contact
Sync data from any source to the Contact object
Record matching
You can match rows from your model to Contact in Sage Intacct on any column in your model and any field in Sage Intacct. Ensure the data types of the model column and Sage Intacct field you select match. Refer to the record matching docs for more information.
In Insert mode, Sage Intacct automatically generates an identifier for every new record synced, so there is no need to match an existing record.
Field mapping
Hightouch lets you sync Contact fields via field mapping. You can map data from any of your model columns to the default Contact fields. Ensure your model columns data types match the data types of the fields you want to sync to.
Delete behavior
The delete behavior you select dictates what to do when a row no longer appears in your model's query results. You have the following options:
| Behavior | Description |
|---|---|
| Do nothing | Keep the Contact in Sage Intacct with all its synced fields |
| Clear | Clear all the mapped fields, but keep the Contact in Sage Intacct |
| Delete | Delete the synced Contacts from Sage Intacct |
Syncing Customer
Sync data from any source to the Customer object
Record matching
You can match rows from your model to Customer in Sage Intacct on any column in your model and any field in Sage Intacct. Ensure the data types of the model column and Sage Intacct field you select match. Refer to the record matching docs for more information.
In Insert mode, Sage Intacct automatically generates an identifier for every new record synced, so there is no need to match an existing record.
Field mapping
Hightouch lets you sync Customer fields via field mapping. You can map data from any of your model columns to default and custom Customer fields. Ensure your model columns data types match the data types of the fields you want to sync to.
Delete behavior
The delete behavior you select dictates what to do when a row no longer appears in your model's query results. You have the following options:
| Behavior | Description |
|---|---|
| Do nothing | Keep the Customer in Sage Intacct with all its synced fields |
| Clear | Clear all the mapped fields, but keep the Customer in Sage Intacct |
| Delete | Delete the synced Customers from Sage Intacct |
Syncing Invoice
Sync data from any source to the Invoice object
Record matching
You can match rows from your model to Invoice in Sage Intacct on any column in your model and any field in Sage Intacct. Ensure the data types of the model column and Sage Intacct field you select match. Refer to the record matching docs for more information.
In Insert mode, Sage Intacct automatically generates an identifier for every new record synced, so there is no need to match an existing record.
Field mapping
Hightouch lets you sync Invoice fields via field mapping. You can map data from any of your model columns to default and custom Invoice fields. Ensure your model columns data types match the data types of the fields you want to sync to.
Delete behavior
The delete behavior you select dictates what to do when a row no longer appears in your model's query results. You have the following options:
| Behavior | Description |
|---|---|
| Do nothing | Keep the Invoice in Sage Intacct with all its synced fields |
| Clear | Clear all the mapped fields, but keep the Invoice in Sage Intacct |
Syncing Journal Entry
Sync data from any source to the Journal Entry object
Field mapping
Hightouch lets you sync Journal Entry fields via field mapping. You can map data from any of your model columns to the default and custom Journal Entry fields. Ensure your model columns data types match the data types of the fields you want to sync to.
Formatting entries
Hightouch recommends using the array builder inline mapper to map properties that the Sage Intacct SDK expects.
The Sage Intacct SDK automatically determines the TR_TYPE based on the AMOUNT of the entry, so there's no need to map this field. To represent whether an entry is a debit or credit, use a positive or negative AMOUNT value, respectively. The sum of all entries in the array will be zero. The absolute value of the AMOUNT should not be used.
Syncing Transaction
Sync data from any source to the Transaction object
Record matching
You can match rows from your model to Transaction in Sage Intacct on any column in your model and any field in Sage Intacct. Ensure the data types of the model column and Sage Intacct field you select match. Refer to the record matching docs for more information.
In Insert mode, Sage Intacct automatically generates an identifier for every new record synced, so there is no need to match an existing record.
Field mapping
Hightouch lets you sync Transaction fields via field mapping. You can map data from any of your model columns to default and custom Transaction fields. Ensure your model columns data types match the data types of the fields you want to sync to.
Delete behavior
The delete behavior you select dictates what to do when a row no longer appears in your model's query results. You have the following options:
| Behavior | Description |
|---|---|
| Do nothing | Keep the Transaction in Sage Intacct with all its synced fields |
| Clear | Clear all the mapped fields, but keep the Transaction in Sage Intacct |
Tips and troubleshooting
Common errors
To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . We're here to help.
Live debugger
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.
Sync alerts
Hightouch can alert you of sync issues via Slack, PagerDuty, SMS, or email. For details, please visit our article on alerting.