Background
If you are reviewing this document, your organization is evaluating the Recurrency ERP Automation platform.
By adopting Recurrency, your organization can significantly reduce manual work associated with optimizing purchasing decisions, enhance data visibility, and uncover valuable trends that are often difficult to identify. Organizations that use Recurrency are frequently able to decrease their operating costs through more informed purchasing decisions, and increase their revenue by helping their sellers identify timely opportunities to sell additional products.
During the evaluation process, Recurrency will establish a connection with your ERP system to assess the feasibility of our platform for your organization. Additionally, this connection will grant you access to our free reporting suite.
In order to configure this integration, we need your help to establish a secure connection between Recurrency’s systems and NetSuite’s REST API.
💡 If you are not using Oracle NetSuite, there is another version of this guide that is better suited for you. Reach out to [email protected] if you have questions.
Requirements
Before diving in, here is what you need in order to complete this integration:
You must have administrator access to your NetSuite instance.
You must have received an invitation to the Recurrency Secure Integration Portal. If you have not, please contact your sales representative or [email protected] to get access.
You will need about 20 minutes to complete the whole process.
Optional: We recommend having a NetSuite user license available if you do not already have a dedicated integrations employee. However, if this is not possible you can use an existing employee at no additional licensing cost.
Overview
This guide contains the following steps:
Enable the correct REST API and Authentication features
Install the Recurrency Integrator bundle to create the Recurrency integration and role
Locate and securely submit your Account ID
Create a Recurrency Integration employee or assign the appropriate permissions to an existing employee
Create an access token for Recurrency and securely submit the Token ID and Token Secret
Once those steps are completed, the integration will be complete and the initial data sync will occur outside of business hours. If your business has abnormal operating hours, please let us know.
Enable Rest API Features
To establish a connection with NetSuite, Recurrency uses the SuiteTalk Web Services REST API. This feature is available for free on all NetSuite instances, but may need to be enabled. From the top navigation, go to the Setup menu and select Setup -> Company -> Enable Features:
From the Enable Feature screen, select the SuiteCloud tab:
Scroll to SuiteTalk (Web Services) and enable REST WEB SERVICES if it is not already enabled:
Scroll to Manage Authentication and enable TOKEN-BASED AUTHENTICATION if it is not already enabled:
Scroll back to the top of the page and press the Save button in the top left:
Install the Recurrency Integration Bundle
Next we will install the Recurrency Integrator bundle through NetSuite’s SuiteBundler in order to create the correct role and integration for Recurrency. Navigate to Customization -> SuiteBundler -> Search & Install Bundles:
Search for “Recurrency”:
Select the Recurrency Integrator bundle and press Install:
From the preview page, you can see the integration and role objects that will be installed. Press Install Bundle to proceed:
You may see a pop up asking for confirmation, press OK to proceed with installation:
You will now be redirected to the Installed Bundles page, where you can see the Recurrency Integrator bundle with Status “Pending…” (you may have to scroll to it):
The installation process is automatic but can take a few minutes. While this is happening, feel free to proceed to the next section. In a few minutes, press the Refresh button and you should see that Status has changed to a green checkmark:
If instead the status is a red cross, please mouse over the cross and send the error message to your sales representative.
Securely Submit Account ID
You should have received an email from Recurrency to “Join your team on Recurrency.” The email will be sent from [email protected]. If you have not, please contact your sales representative or [email protected] to get access.
Open the email and click on the Activate Account button.
This will take you to the Recurrency Integration Portal where you will set a password for your account.
Next, you will be asked to log in using the password you just created.
You will then be taken to a Secure Integration Portal page where you will securely submit the credentials you generate during this integration.
You’ll reference this page a few more times during the setup process.
Once logged in to the Secure Integration Portal, open NetSuite again in another window or tab and navigate to Setup -> Integration -> SOAP Web Services Preferences:
In the top left corner of this page you should see your Account ID:
Copy this value and paste it into the Database Name field of the form on the Secure Integration Portal. Click this button:
And then use this field so submit your Account ID value from NetSuite:
Creating or Configuring an Employee
If you have not already, please ensure that the Recurrency Integrator bundle now shows a green checkmark status. You can return to the bundles page by going to Customization -> SuiteBundler -> Search & Install Bundles -> List:
This next step has two options. In order to access the REST API, Recurrency needs an employee record in NetSuite:
When possible, we recommend using a dedicated employee record for integrations, as it maximizes clarity in audit logs and permissions management. However, if you do not already have a license in use for integrations then this approach does require an additional user license.
If you do not yet have a dedicated integration employee but you would like to make one, please follow the section below for Option 1.
If you already have a dedicated integration employee that you use for other integrations, we recommend using this employee for the Recurrency integration as well. Follow the section below for Option 2 to adjust that employee’s permissions accordingly. Note that in the step after this we will configure the token so that Recurrency will not have access to permissions used for any other integrations; it will only have the permissions granted by the Recurrency Integration role.
If you do not have an existing employee record dedicated to integration and you do not have an available user license, you can configure the Recurrency integration using an existing employee. That employee will have the Recurrency Integration role added to their account, and the token created for Recurrency in the following step will only be able to access that specific role even if the user has other roles as well. Follow the section below for Option 2 to adjust that user’s permissions accordingly.
Option 1: Creating a new employee
To create a new employee for the Recurrency integration, navigate to Lists -> Employees -> Employees -> New:
From here, fill out any required fields as you would for a new employee. We recommend:
Name: Recurrency Integration
Email: [email protected]
Use your best judgement for any other fields that are required for your specific instance. If you have any questions you can contact your sales representative or [email protected].
Scroll down, go to the Access tab, and ensure that GIVE ACCESS and SEND NOTIFICATION EMAIL are checked:
At the bottom of the page under the Roles tab search for the Recurrency Integration Role, select it, and press Add:
Finally, press Save:
Now you can skip the instructions for Option 2 below and proceed to the next section, Creating Access Token.
If you see the following error about Full Access licenses, consider using an existing user instead by following Option 2 below:
Option 2: Configuring integration permissions for an existing employee
If you already have a dedicated employee record for integrations, or you do not have an additional user license available to dedicate to an integration employee, you can navigate to Lists -> Employees -> Employees:
From here, scroll to your existing integration employee or a user that you would like to add the Recurrency Integration Role to. If you are selecting an employee, please select someone who 1) has access to your NetSuite instance, 2) you trust with visibility of your inventory, planning, and purchasing information, and 3) is not likely to leave your organization any time soon. If they do leave in the future and their account is deactivated, please notify the Recurrency team so we can help you adjust the integration accordingly.
Scroll to this employee and select Edit:
Scroll to the bottom of this user’s profile and under the Roles tab search for Recurrency Integration Role and press Add:
Press Save to update the user’s permissions accordingly:
In the next step we will create an access token that is restricted to this specific role, so Recurrency will not have access to any other roles that this user has granted.
Creating Access Token
The final step is to create an access token linking the integration, role, and user created in the previous steps. This is the token that Recurrency will use to access the NetSuite REST API. Navigate to Setup -> Users/Roles -> Access Tokens -> New:
Now select the records created in previous steps:
Application Name: Recurrency Integration
User: Recurrency Integration (or the existing user you modified in the previous step)
Role: Recurrency Integration Role
Token Name: Leave this as the automatically filled value or you can set it to “Recurrency Integration Token”
Once you press Save, you will see a section called Token Id/secret appear. This contains the values that Recurrency will use to securely connect to your instance. You will only be able to see these values once so do not leave the page until you have copied them or entered them into the Recurrency Secure Integration Portal:
Copy the TOKEN ID value and paste it into the Secure Integration Portal. Then copy the TOKEN SECRET and do the same:
Paste the TOKEN ID value into the Username field and the TOKEN SECRET into the Password field.
Waiting for Initial Sync
Once you have submitted your Account ID, Token ID, and Token Secret, the Recurrency team will review and verify the connection is working properly. We will reach out with confirmation or questions if there are any issues.
Within a few days of confirming that your integration is properly configured, Recurrency will run an initial sync after hours to sync your NetSuite instance with our system. Following the initial sync, we continue to pull incremental changes from your instance to keep NetSuite in sync with Recurrency’s systems.
Frequently Asked Questions
1. How does the Recurrency service securely communicate with your services?
Recurrency encrypts all data in transit and at rest. In transit, we use HTTPS with at least TLSv1.2 to communicate with the Recurrency service. Any users interacting with our web-based application will also use HTTPS with at least TLSv1.2. At rest, data is encrypted using AES-256.
2. What are the resource requirements for the Recurrency service? Should we be worried about it impacting the performance of our ERP?
The Recurrency service is designed to be lightweight and consumes few resources. We also implement rate limiting within our services to ensure we do not overload your ERP.
3. I don’t feel comfortable giving Recurrency write access, can I proceed with read permission only?
Unfortunately, due to the way NetSuite’s REST API is designed, in order to read information about a record we must have edit level permissions on that record. All requests that Recurrency makes are tracked in the NetSuite audit log. We are also happy to discuss any specific permissions that you are uncomfortable with granting access to. Read more about NetSuite’s REST API permissions requirements here:
https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/chapter_1540391670.html#subsect_1544786455
4. Just in case, how do I uninstall the Recurrency integration if I would like to in the future?
If at any point you would like to disconnect your Recurrency integration, you can remove the integration by:
Deleting the access token created above
If you created an employee for Recurrency, removing that employee’s access
Uninstalling the Recurrency Integrator bundle
Any one of the above steps is enough to remove access, but you must perform all three to fully undo the integration.
If you have any questions, please reach out to your dedicated Account Executive, [email protected], or [email protected].