Recurly for Oracle NetSuite Advanced FAQs

The purpose of this page is to describe answers to questions that advanced users may have with Recurly for NetSuite.

How does the sync process work? Please go into detail.

The integration is broken into a 3 step approach: Accounts, Plans, & Transactions.


Recurly to Oracle NetSuite Sync Diagram

We first sync the Accounts to ensure your customer is ready to be used for upcoming transactions

Then we sync the plans to insert into the relevant transactions. Plus it is in these records we persist the relevant revenue recognition data set up.

Finally, we sync the transactions to ensure your financial data is accurate based on your billing system.

If you have more detailed questions or want to see more information, please reach out to your CSM/AM to get our data sheet.

What is the cadence of the syncs?

It is scheduled every hour at the top of the hour. For more details, please reach out to [email protected]

Do you sync over parent accounts as customers as well?

Yes, we do

Can we use serialized inventory items as the destination for plans/items?

Not at the moment. We only support non-inventory items

How do we manage external ids among customers, plans & transactions?

We enable multiple ways to manage your external id for customers. You can leverage our out of the box account id as one method. Create your own unique account code or insert a new id value into our custom fields. The downside with this method is that uniqueness and prevention of collisions will be dependent on the merchant. Also, this does not work for parent-child account setups.

For plans and items, you can leverage the out of the box ids (plan id or item id respectively). Otherwise, you can leverage the plan code or item code but that requires the merchant to own the uniqueness of the values. For add-ons, you have to use distinct add-on code.

For transactions, we always use the associated id for that record (for example, invoice id for invoices) to insert the value into NetSuite's external id field.