Sage Intacct Integration

Overview

Your Alpine database can be customized to seamlessly integrate with your Sage Intacct account. This integration is push-only, meaning that Humanitru Alpine will push Actions into Sage Intacct, but not pull information from it. However, the integration does fetch the chart of accounts, locations, departments, classes, and custom fields to be able to generate campaigns that can be applied to Actions that will be pushed to Sage Intacct. The primary goal is to push transactions (donations, memberships, tickets) as journal entries into Sage Intacct. This enables nonprofits to ensure that every transaction-based Action in Humanitru is accurately reflected in their accounting platform.

What We Pull From Sage Intacct

While the Sage Intacct integration is primarily push-only for transactional data, When the sync runs each night, Alpine will fetch and store your chart of accounts as well as optionally Locations, Departments, Classes, and Custom Fields from Sage Intacct. These fields will be used to auto-create Campaigns that can be applied to Actions that are pushed to Sage.

What We Push Into Sage Intacct

The Humanitru Alpine database will push all transactions as journal entries into your Sage Intacct account EXCEPT Actions that have the [System] Auto-Generated: Exclude from Sage Intacct campaign applied to them

Data Mapping

Every Humanitru Alpine transaction that is pushed will correspond to a journal entry in Sage Intacct. The integration aims to provide detailed information within the journal entry:

 

Description: This field will be populated with the Alpine URL of the Action, the constituent's name, and a human-readable summary of the Action (action.summary) that includes the Action type, Action Date, Constituent Name and a URL to the Action in Humanitru.

 

Sync Details Timing

The integration will run nightly and will only include Actions that were created after the last_sync_at timestamp.

Transaction Syncing

• Batching: If the user chooses “Batching” all transactions within a batch will share the same posting date (the start_time of the sync).
• Individual Sending: If the user chooses Individual Sending each transaction will have a posting date that is the (happened_at) date on the Action

Excluding Transactions from the Sync

• If a user wants transactions that do not originate in Humanitru (eg: ACME tickets) to be excluded from the sync, they should apply the [System] Auto-Generated: Exclude from Sage Intacct campaign to them

Error Handling

• Invalid Actions (those missing both a debit and credit campaigns for Account, Location, Department, Class, or Custom Field) will be flagged with a "System Needs Review" campaign and skipped.
• If there are invalid Actions detected when the sync begins to run, it will halt the entire process and no journal entries will be created in Sage Intacct.
• If the integration fails, Humanitru staff will be able to identify it internally and will reach out to the customer to inform them. Customers can also set up a notification for actions that have the System Needs Review campaign applied.

 

Setup

The following setup must happen in Sage Intacct before configuration can begin in Humanitru.

Sage Intacct Setup

Step 1: Subscribe to Web Services

1. Navigate to Company > Admin > Subscriptions.
2. Locate "Web Services" and click Subscribe.

Step 2: Authorize the Humanitru Sender ID

1. Go to Company > Company Info.
2. Click Edit.
3. Select the Security tab.
4. Under Web Services Authorizations, add the Sender ID: HumanitruMPP.

Once the Sage setup is complete, we can start setting up the integration in Humanitru

Humanitru Setup

1. Let your Customer Success Manager (CSM) know you would like to set up the Sage Intacct Integration.

Enter Credentials in Alpine

The customer can now enter the following values into the settings page. This will establish the initial connection with Sage.  

  

There are also 4 fields (Locations, Departments, Classes, Custom Fields) that can be configured as Require, Available, or Exclude. The following is how those settings are defined:

• Require: The integration will auto-create campaigns and categories for the attribute. Every Action that is pushed to Sage must have both a credit and debit campaign applied for that attribute
• Available: The integration will auto-create campaigns and categories for the attribute. Every Action that is pushed to Sage may optionally have campaigns for this attribute applied. If they have one applied, they must have both a credit and debit campaign applied
• Exclude: The integration will not auto-create campaigns for this attribute and Actions will not be required to have campaigns for this attribute in order to be pushed to Sage

After Clicking connect, Humanitru will create the following Campaigns:

• In the [Sage Intacct] Accounts Category: one CR and one DR campaign for each account available in the chart of accounts
• If any of the additional attributes are set to required or available, the following campaigns and Campaign Categories will be created
  • Locations: In the [Sage Intacct] Locations Category: one CR and one DR campaign for each location in Sage Intacct
  • Departments: In the [Sage Intacct] Departments Category: one CR and one DR campaign for each department in Sage Intacct
  • Classes: In the [Sage Intacct] Classes Category: one CR and one DR campaign for each class in Sage Intacct
  • Custom Field: If a Custom Field is configured on the settings page, a Category will be created named for that Custom field ([Sage Intacct] <custom field name> and one CR and one DR campaign will be created for each value available in Sage Intacct for that field
    
    If Locations, Departments, Classes, or Custom Fields are made required or available, the user that is configured for the integration must have sufficient access to all possible attributes so that the necessary campaigns can be autocreated using data pulled from Sage.