Already have an account? Sign in

Intacct (v1)

Intacct integration summary

Stitch’s Intacct integration relies on Intacct’sData Delivery Service (DDS) for Amazon S3. Intacct DDS exports reports in CSV format to Amazon S3, which Stitch will then replicate usingKey-based Incremental Replication.

While DDS supports other export targets, Stitch only supports replicating Intacct data through Amazon S3 at this time.

For more info about DDS,refer to Intacct’s documentation.

Note: This integration does not use the Intacct API. Only data available via DDS will be available for replication through Stitch.

Intacct feature snapshot

A high-level look at Stitch's Intacct (v1) integration, including release status, useful links, and the features supported in Stitch.

Connecting Intacct

Intacct setup requirements

To set up Intacct in Stitch, you need:

• An active subscription to Intacct’sData Delivery Service (DDS). Stitch’s Intacct integration currently only replicates data from Amazon S3 buckets used by this Intacct feature.

• An existing Amazon S3 bucket where Intacct publishes data via DDS. Stitch will not create a bucket for you.

• Permissions in AWS Identity Access Management (IAM) that allow you to create policies, create roles, and attach policies to roles. This is required to grant Stitch authorization to your S3 bucket.

Step 1: Set up an Intacct Cloud Storage Target and automatic data delivery

In this step, you’ll set up a Cloud Storage Target and automatic data delivery in Intacct.

• Step 1.1: Configure Amazon S3 access for Intacct

• Step 1.2: Define a Cloud Storage Target in Intacct

• Step 1.3: Set up an automated data delivery in Intacct

Step 1.1: Configure Amazon S3 access for Intacct

1. Sign into your Amazon Web Services account.
2. Navigate to the Amazon S3 bucket you want to use as the Cloud Storage Target for Intacct.
3. Follow the instructions inStep 1 of Intacct’s documentation to enable Intacct to access the bucket.

Step 1.2: Define a Cloud Storage Target in Intacct

1. Sign into your Intacct account.
2. Follow the instructions inStep 2 of Intacct’s documentation to create the target in Intacct.

Step 1.3: Set up an automated data delivery in Intacct

In this step, you’ll create anautomatic delivery schedule in your Intacct account.

1. In your Intacct account, navigate toCompany > Data Delivery Service > Automatic.
2. Click theAdd button.
3. In theFile attributes section, define the settings as follows:
   • Delimiter: Commas
   • Text qualifier (delimiter): Double quote (")
   • Encryption: Do not encrypt
4. In theDelivery options section, define the settings as follows:
   • Cloud storage destination: Select the Amazon S3 Cloud Storage Target you created inStep 1.2.
   • Frequency: Select the frequency you want to use to trigger a data export in Intacct.
5. In theObjects section, select the objects you want to include in the export. These objects will then be available for selection in Stitch.
6. Save the schedule.

Step 2: Retrieve your Amazon Web Services account ID

1. Sign into your Amazon Web Services (AWS) account.
2. Click theuser menu, located between thebell andGlobal menus in the top-right corner of the page.
3. ClickMy Account.

4. In theAccount Settings section of the page, locate theAccount Id field:

   

Keep this handy - you’ll need it to complete the setup.

Step 3: Add Intacct as a Stitch data source

1. Sign into your Stitch account.

2. On the Stitch Dashboard page, click theAdd Integration button.

3. Click theIntacct icon.

4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

   For example, the name “Stitch Intacct” would create a schema calledstitch_intacct in the destination.Note: Schema names cannot be changed after you save the integration.

5. In theCompany ID field, enter the company ID you use to sign into Intacct.
6. In theS3 Bucket field, enter the name of the bucket where the Intacct Data Delivery Service (DDS) outputs data. Enter only the bucket name: No URLs,https, or S3 parts. For example:intacct-stitch-bucket
7. In theAWS Account ID field, paste the AWS Account ID you retrieved inStep 2.
8. Optional: In thePath field, enter the path configured in Intacct for use in the S3 bucket.

Step 4: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Intacct integration. This means that dataequal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Intacct’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.

Step 5: Create a replication schedule

In theReplication Frequency section, you’ll create the integration’sreplication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Intacct integrations support the following replication scheduling methods:

• Replication Frequency

• Anchor Scheduling

• Advanced Scheduling using Cron (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 6: Grant access to your bucket using AWS IAM

Next, Stitch will display aConfigure Your Intacct Integration page. This page contains the info you need to configure bucket access for Stitch, which is accomplished via an IAM policy and role.

Note: Saving the integration before you’ve completed the steps below will result in connection errors.

• Step 5.1: Create an IAM policy

• Step 5.2: Create an IAM role for Stitch

• Step 5.3: Check and save the connection in Stitch

Step 6.1: Create an IAM policy

An IAM policy is JSON-based access policy language to manage permissions to Intacct resources.

For more info about the permissions the auto-generated policy Stitch IAM policy grants, click the link below.

To create the IAM policy:

1. In AWS,navigate to the IAM service by clicking theServices menu and typingIAM.
2. ClickIAM once it displays in the results.
3. On the IAM home page, clickPolicies in the menu on the left side of the page.
4. ClickCreate Policy.
5. In theCreate Policy page, click theJSON tab.
6. Select everything currently in the text field and delete it.
7. In the text field, paste the IAM policy from theConfigure Your Intacct Integration page in Stitch.
8. ClickReview policy.
9. On theReview Policy page, give the policy a name. For example:stitch_intacct
10. ClickCreate policy.

Step 6.2: Create an IAM role for Stitch

In this step, you’ll create an IAM role for Stitch and apply the IAM policy from the previous step. This will ensure that Stitch is visible in any logs and audits.

To create the role, you’ll need theAccount ID,External ID, andRole Name values provided on the StitchConfigure Your Intacct Integration page.

1. In AWS, navigate to theIAM Roles page.
2. ClickCreate Role.
3. On theCreate Role page:
   1. In theSelect type of trusted entity section, click theAnother AWS account option.
   2. In theAccount ID field, paste the Account ID from Stitch.Note: This isn’t your AWS account ID from Step 1 - this is the Account ID that displays in Stitch on theConfigure Your Intacct Integration page.
   3. In theOptions section, check theRequire external ID box.
   4. In theExternal ID field that displays, paste the External ID from the StitchConfigure Your Intacct Integration page:
   5. ClickNext: Permissions.
4. On theAttach permissions page:
   1. Search for the policy you created in theprevious step.
   2. Once located, check the box next to it in the table.
   3. ClickNext: Tags.
5. If you want to enter any tags, do so on theAdd tags page. Otherwise, clickNext: Review.
6. On theReview page:

   1. In theRole name field, paste the Role Name from the StitchConfigure Your Intacct Integration page:

      Remember: Role names are unique to the Stitch Intacct integration they’re created for. Attempting to use the same role for multiple integrations will cause connection errors.

   2. Enter a description in theRole description field. For example:Stitch role for Intacct integration.
   3. ClickCreate role.

Step 6.3: Check and save the connection in Stitch

After you’ve created the IAM policy and role, you can save the integration in Stitch. When finished, clickCheck and Save.

Step 7: Set objects to replicate

The last step is to select the tables and columns you want to replicate.Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

• Selection options
• Individual tables and columns
• All tables and columns

Initial and historical replication jobs

After you finish setting up Intacct, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Intacct replication

Stitch uses Key-based Incremental Replication to replicate data from Intacct integrations. To identify new and updated data for replication, Stitch will use file modification timestamps asReplication Keys and store them on a per-table basis. This means that only files dumped from a new Intacct data sync will be selected for replication.

While data from Intacct integrations is replicated usingKey-based Incremental Replication, the behavior for this integration differs subtly from other integrations.

The table below compares Key-based Incremental Replication andReplication Key behavior for Intacct to that of other integrations.

Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.