Our NetSuite integration will allow you to connect your Chargify account directly to your NetSuite account to seamlessly sync your customers and the transactional data associated with them.
Our Chargify/NetSuite integration is a one-way integration with Chargify being the source of truth. Because of this, it’s recommended (with the exception of marking sales orders as fulfilled) that NetSuite records created by the integration not be edited or deleted from within NetSuite.
We currently support workflows for syncing invoices — one for invoices with inventory items and another for invoices with non-inventory items.
When an invoice containing inventory items is opened, we’ll create a sales order in NetSuite. Once the sales order has been marked as fulfilled (shipped), we’ll create an invoice and finally a customer payment when the invoice has been paid. If Chargify collects a payment before the sales order is fulfilled, we’ll create a customer deposit.
When an invoice containing no inventory items is opened, we’ll create a sales order and immediately bill it to create the associated invoice. When a payment is collected in Chargify, we’ll create a customer payment applied to the invoice in Netsuite.
Our integration represents tax amounts collected in Chargify as an additional line item on invoices in NetSuite. In addition, Chargify will include the tax amount charged per product/component on each associated line-item via a custom field. This is important to make note of this because you won’t see tax amounts in NetSuite’s designated invoice header-level tax field or line-item level tax fields.
During the integration setup, you’ll be asked to specify which NetSuite item you’d like Chargify to use to represent tax on invoices. It’s recommended that you create a non-inventory item in NetSuite for tax amounts specific to this integration. We’ll mention this again in the Integration Prerequisites section.
During integration setup, Chargify will create a discount item in NetSuite labeled “Chargify Discount” attached to your “Sales Discounts” Account. This discount item will be used to represent the total amount discounted on an invoice.
During integration setup, similar to discounts, Chargify will create a custom payment method in NetSuite labeled “Chargify Payment”. This payment method will be used whenever syncing Chargify payments to NetSuite customer payment records.
We use custom fields in NetSuite to store Chargify record metadata for reference purposes. Below is a list of custom fields created and populated by the integration.
|Customer||Chargify Customer ID||Contains the customer’s Chargify ID.|
|Customer||Chargify Subdomain||Contains the Chargify customer’s site subdomain.|
|Line Item||Chargify Line Item Tax||Contains the line item’s tax amount charged in Chargify.|
|Sales Order||Chargify Subdomain||Contains the Chargify site’s subdomain.|
|Sales Order||Chargify Invoice Number||Contains the Chargify invoice UID.|
There are a few checklist items that you’ll need to have completed before enabling our NetSuite integration.
Enable SuiteTalk Web Services
Navigate to Setup -> Company -> Enable Features -> SuiteCloud and check the SuiteTalk (Web Services) box.
Sales Discounts Account
Navigate to Lists -> Accounting -> Accounts. From here, verify that you have a ‘Sales Discounts’ Account (this will likely exist by default). We’ll use this account for discounts.
Create an Item for Tax
Navigate to Lists -> Accounting -> Items -> New. As mentioned in the Taxes section, it’s advised to create an non-inventory item designated for representing tax amounts on sales order and invoices.
Navigate to the ‘Integrations’ tab in your Chargify account and click the ‘NetSuite’ tab in the sidebar menu. Click ‘Enable NetSuite Integration’.
The first step of the NetSuite integration setup is to provide your NetSuite API credentials. This will allow Chargify to communicate with your NetSuite account. The goal of this section will be to obtain these five credentials:
- NetSuite Account ID
- Consumer Key
- Consumer Secret
- Token ID
- Token Secret
As a heads-up, this process is a bit lengthy. We recommend opening a notepad to copy and paste your keys as you obtain them. After the five credentials have been gathered, you’ll enter them in Chargify.
The following steps must be performed in NetSuite by a user with an administrator or “full access” role. To begin, log in to NetSuite.
- Navigate to your Company Information page. From the navigation menu, select Setup -> Company -> Company Information.
- Once on your company information page, you’ll see an ACCOUNT ID label, as shown below. This is your NetSuite account ID.
Next, we’ll create an integration record to identify the Chargify application in NetSuite’s system.
Navigate to Setup -> Integration -> Manage Integrations -> New.
On the New Integration form:
- Fill in the Name field with “Chargify”
- Make sure “Enabled” is selected in the State dropdown menu
- Check the TOKEN-BASED AUTHENTICATION checkbox
- Click Save
After the integration record has been saved, NetSuite will display a CONSUMER KEY and CONSUMER SECRET, as shown below. Copy and paste your key and secret to a notepad as NetSuite will not display these values again.
- Navigate to Setup -> Company -> Enable Features -> SuiteCloud
- Under the Manage Authentication section, check the TOKEN-BASED AUTHENTICATION checkbox and click Save.
Next, we’ll create a role. This role will hold the permissions needed by Chargify for the integration.
Navigate to Setup -> Users/Roles -> Manage Roles -> New.
Fill in the Name field with “Chargify Token Role”.
Then, under Permissions, add the following permissions for each section:
|Access Payment Audit Log||View|
|Invoice Sales Order||Full|
|Sales Order Approval||Full|
|Set Up Company||View|
|Access Token Management||Full|
|Custom Body Fields||Full|
|Custom Column Fields||Full|
|Custom Entity Fields||Full|
|Custom Transaction Fields||Full|
|Log in using Access Tokens||Full|
|User Access Token||Full|
- Navigate to Lists -> Employees -> Employees.
Then, locate your employee record and click “Edit”.
Under the Access section, assign the role that you created in the previous step, as shown below. Then, save your changes.
- Navigate to Setup -> Users/Roles -> Access Tokens -> New.
- Select “Chargify” in the APPLICATION NAME menu.
- In the USER menu, select the user that you modified in the previous step.
- Select “Chargify Token Role” in the ROLE menu.
- Click Save
One the Access Token has been saved, NetSuite will display a TOKEN ID and TOKEN SECRET, as shown below. Similar to the consumer key and secret, copy and paste these values to a notepad as NetSuite will only show them once.
You’ve made it to the final authorization step! Now, you’ll enter your NetSuite Account ID, Consumer token and secret, and your Token ID and secret in Chargify. When the form is submitted, Chargify will validate we can connect successfully to your NetSuite account.
On this step, you’ll specify which NetSuite item should be used for taxes. Then, you’ll map Chargify products and components with NetSuite items.
Below is a list of supported NetSuite item types:
If you use an item type not shown in this list, please let us know.
On this step, you’ll specify how you want to sync $0 invoices and failed payment attempts.
Customers in Chargify can be matched to NetSuite customers by either:
- Email address, or:
- Chargify customer reference ID and NetSuite customer external ID.
When matching customers during invoice sync, we use a find-or-create approach. For example, if the customer cannot first be found email address in NetSuite, we’ll create a NetSuite customer. For NetSuite customers created by the integration, we’ll store the customer’s Chargify ID and site subdomain on the NetSuite record via custom fields.
This step also allows you to sync historical invoices up to a specified past date.
Anytime an error occurs while the integration is enabled, we’ll pause the integration and display the error message(s) as well as action steps (if needed on the merchant’s part). After issues have been addressed, you’ll be able to re-enable the integration, at which point, failed sync tasks will be retried.