NetSuite Integration - ARM Connector
Designed to integrate seamlessly with NetSuite Advanced Revenue Management (ARM), Nue's NetSuite ARM Connector enables streamlined workflows for managing complex revenue recognition and advanced collection processes.
With this integration, Nue seamlessly synchronizes accounts, products, orders, change orders, invoices, and credit memos data to NetSuite in real time, while also processing payments, refunds and credits made in NetSuite. This comprehensive sync unlocks the following powerful capabilities:
- Automate Revenue Recognition: Ensure compliance with ASC 606 and IFRS 15 by integrating billing and subscription data, enabling accurate and timely revenue schedules.
- Optimize Collections: Leverage advanced dunning workflows, payment tracking, and reconciliation tools in NetSuite to improve cash flow and minimize receivables risk.
- Streamline Payment Management: Keep payments and refunds synchronized between Nue and NetSuite for seamless financial operations and improved accuracy across systems.
Overview
Nue's NetSuite ARM Connector supports the synchronization of the following objects:
| Nue Object | NetSuite Object | Direction |
| Customer | Customer | One-direction sync from Nue to Netsuite |
| Product | Item | One-direction sync from Nue to NetSuite |
| Order and Order Product | Sales Order and Return Authorizations (for Negative Change Orders) | One-direction sync from Nue to NetSuite |
| Invoice and Invoice Item | Invoice and Items | One-direction sync from Nue to NetSuite |
| Credit Memo and Credit Memo Item | Credit Memo and Items | Bi-direction sync between Nue and NetSuite |
The diagram below illustrates the synchronization flow. Note that products are stored in Salesforce but are synchronized to NetSuite using Nue’s GraphQL queries, which are automatically routed to Salesforce to fetch the required data.
Key Capabilities
The NetSuite ARM Connector offers the following key features:
Advanced Collections
Active invoices and credit memos generated in Nue are seamlessly transferred to NetSuite for collection management. NetSuite users can view invoices, process payments and refunds, and issue credits directly in NetSuite. Actions like canceling or reversing invoices in Nue are automatically synchronized with NetSuite. This feature implements Nue’s general collection use cases within the NetSuite ecosystem.
Fulfillment
Active orders, including change orders, are transferred to NetSuite to manage fulfillment processes efficiently.
ASC 606 Revenue Recognition
Active sales orders, change orders, recurring invoices, and credit memos are transferred to NetSuite in real time as Sales Orders, Return Authorizations, Invoices, and Credit Memos. These transactions are carefully orchestrated to enable the creation and updating of revenue arrangements, ensuring compliance with ASC 606.
Transaction Hub
Transactions in NetSuite are carefully orchestrated to maintain a clear relationship between Nue and NetSuite. For example, an invoice generated from multiple orders in Nue can be grouped into multiple invoices in NetSuite, with this linkage preserved in the Transaction Hub record. This record is accessible in Nue and Salesforce for easy visibility and traceability.
Integration Flows
The following diagram illustrates the data flow of Nue’s NetSuite Connector, enabling advanced collections and revenue recognition.
Key components include:
Accounts and Products
- Accounts in Salesforce are synchronized with NetSuite as Customers.
- Products in Salesforce are synchronized with NetSuite as Items.
Quotes and Orders
- Quotes and orders created in Nue are transferred to NetSuite as Sales Orders, which remain open for the lifetime of the subscription.
- Both initial orders and mid-term changes are seamlessly integrated into NetSuite ARM.
Invoices
- Invoices are generated in Nue (one per billing cycle) and synchronized with NetSuite for advanced collections.
- Linked to customer payments and deferred revenue in NetSuite for accurate tracking and reconciliation.
Revenue Recognition (NetSuite ARM)
- Sales orders, invoices, and credit memos are used to create Revenue Arrangements and Revenue Plans in NetSuite.
- Automatically generates Revenue Recognition Journal Entries (RevRec JEs) for compliance with ASC 606 and IFRS 15 standards.
Transaction Orchestration
- Transactions in Nue and NetSuite are carefully linked, ensuring accurate synchronization and visibility across both systems.
This integration flow ensures seamless data flow between Nue and NetSuite, enhancing financial management and enabling businesses to scale efficiently.
Setup NetSuite Connection
Please follow the steps outlined in this document to configure the connection between NetSuite and Nue.
Setup Fields Mapping
Users can use the Configuration Wizard of the NetSuite Connector in Nue to create field mappings for customers, products, and transactions (including orders, invoices, and credit memos). We support both standard field mapping and custom field mapping to meet various business needs.
Please refer to the steps outlined in this document to view the list of standard field mappings and set up custom field mappings.
Scenarios
The Nue NetSuite Connector supports the following business scenarios. Let’s take a closer look at these common use cases:
SYNC CUSTOMERS Sync customers to NetSuite when a customer is created or as part of the order sync process.
SYNC PRODUCTS Sync products to NetSuite by enabling custom flags and field mappings.
TRANSFER ORDERS Sync orders and their line items to NetSuite based on activation or payment rules.
TRANSFER CHANGE ORDERS Update NetSuite orders with changes made in Salesforce without disrupting billing processes.
TRANSFER RENEWAL ORDERS Generate new NetSuite orders for renewals without modifying the original orders.
TRANSFER INVOICES Transfer invoices and their items to NetSuite, grouped by related orders for clarity.
SYNC CREDIT MEMOS Transfer credit memos to NetSuite using Return Authorizations for proper recognition.
PAY INVOICES Transfer payment information from NetSuite to update invoice statuses dynamically in Salesforce.
APPLY CREDIT MEMOS Apply NetSuite credit memos to Salesforce invoices, accurately reflecting payment adjustments.
For detailed information about collections-related scenarios, please refer to the Collections Overview page.
Sync Customers
The Nue NetSuite Connector ensures that customers are seamlessly synchronized between Salesforce and NetSuite, supporting two primary use cases:
1. Sync customers from Nue to NetSuite when "Customer Since" is populated
2. Sync customers when an (active) order is transferred from Nue to NetSuite.
Transaction Hub
In both use cases, Nue ensures seamless synchronization by maintaining a transaction hub record that links the Nue Customer ID with the corresponding NetSuite Customer ID. This mechanism prevents the creation of duplicate customer records in NetSuite by verifying the existence of a mirrored Customer ID before any new record is created. If a potential duplicate is detected, the connector retrieves and uses the existing NetSuite Customer ID, ensuring data integrity and eliminating redundancy.
Default Customer Subsidiary
NetSuite requires every customer to be associated with a subsidiary. Using the Configuration Wizard, users can set up a default custom subsidiary to assign when creating customers in NetSuite.
Users can follow the steps below to setup the default customer subsidiary:
- Navigate to Nue App → Settings → NetSuite Integration
- Click 'Configure' to pen the Configuration Wizard and navigate to the Customer Page.
- Enter the Subsidiary ID in the field Default Customer Subsidiary.
NetSuite requires every customer to be associated with a subsidiary. Using the Configuration Wizard, users can set up a default custom subsidiary to assign when creating customers in NetSuite. In the near future, Nue’s entity will be mapped to the subsidiary in NetSuite. This means that if a customer is associated with an entity in Nue, the synchronized customer will automatically be created in the subsidiary mapped to that entity.
Scenario 1: Sync Customers When “Customer Since” is Populated
Nue includes a date field named "Customer Since" (Ruby__CustomerSince__c) on the Salesforce Account object, which tracks when an Account transitions from a prospect to an active customer. This field is populated automatically with the Order Placed Date when the account's first order is activated.
Alternatively, for specific workflows - such as marking an Opportunity as Closed-Won - a Salesforce flow can populate this field with a date. This enables the NetSuite Connector to sync the customer to NetSuite even if no transactions exist.
Users can follow the steps below to setup this scenario:
- Navigate to Nue App → Settings → NetSuite Integration
- Click 'Configure' to pen the Configuration Wizard and navigate to the Customer Page.
- Check the "Yes" checkbox for option "Sync Nue customers to NetSuite when the "Customer Since" field is populated?"
Once this option is enabled, every 5 minutes, the NetSuite Connector checks if the "Customer Since" field is populated for any customer. If the field is populated and the customer hasn’t been synced to NetSuite, the connector creates a corresponding customer in NetSuite.
Scenario 2: Sync Customers When an Active Order is Transferred
When an Order is transferred to NetSuite, if the Customer referenced by the Order does not exist in NetSuite, the NetSuite Connector automatically creates the Customer using configured values and mapped data.
More specifically, the following is the business flow:
- An Order is created and activated in Nue.
- The NetSuite Connector checks if the Customer is already mirrored in NetSuite.
- If not found, the connector creates the Customer in NetSuite and links the Order to the new Customer record.
Sync Products
Nue NetSuite Connector synchronizes products in Nue/Salesforce as items in NetSuite.
When transferring active orders from Nue to NetSuite, the NetSuite connector ensures that all products referenced by the order products are available as items in NetSuite. If a referenced item does not already exist in NetSuite, the connector will automatically create the item using pre-configured values and mapped data. This ensures seamless order processing without manual intervention.
When an order is created and activated in Salesforce and Nue, the connector begins the synchronization process to NetSuite. If the mapped item already exists in NetSuite, the sync process continues without any additional action. Otherwise, the connector creates a new item in NetSuite using the configured values and mapped fields data. The newly created item's record ID is then stored in the transaction hub for future lookup and reference.
If item creation fails due to a deplicate ID in NetSuite, the connector retrieves the record ID of the existing duplicate item, and then stored in the transaction hub to ensure proper synchronization and avoid further duplication issues.
Configure Tax Schedule ID
In certain scenarios, e.g., Advanced Taxes are enabled, or items are used in transactions requiring VAT or GST, users must configure a Tax Schedule ID when creating an item in NetSuite. In such scenarios, users can follow the steps below to configure a Tax Schedule ID, which will be used when items are created in NetSuite:
- Login to Nue App
- Navigate to Settings → NetSuite Integration
- Click 'Configure' to launch the Configuration Wizard.
- Navigate to the Products / Items configuration screen, and enter the Default Tax Schedule ID.
- Click Next until the Configuration Wizard finishes.
Record Type Mapping
In the Products / Items configuration screen in the Configuration Wizard, users can configure the default record type for each types of asset in Nue, as shown below. The SOAP NetSuite connector requires an Item Record Type to create items in NetSuite. Nue’s Activation Object determines downstream billing behaviors based on the product catalog types.
Mapping Path: Nue Product Catalog → Nue Activation Object → NetSuite Record Type
The default mapping relationships are as follows:
- Subscription: NonInventorySaleItem
- Entitlement: ServiceSaleItem
- Asset: InventoryItem
If the mapping is not configured properly, the NetSuite connector will use the Default Record Type when creating items in NetSuite.
Transfer Orders
When a Nue order is activated and satisfies the defined payment rules, NetSuite processes the order seamlessly within a single transaction. This ensures accurate data synchronization and the automated creation of required entities in NetSuite, streamlining order and asset management.
The NetSuite Connector first validates the order to ensure it meets the conditions specified in the payment rules. Once validated, if the referenced customer does not already exist in NetSuite, a new customer record is created using the pre-configured values and mapped data from Nue. Similarly, if any products associated with the order are not yet available in NetSuite, new product records are created based on the configured values and mapped fields.
After handling customer and product creation, a mirrored order is created in NetSuite along with its corresponding order lines. This ensures that all line-level details of the order are accurately represented.
NetSuite supports various asset types through this process, including subscriptions for recurring services or products, entitlements that grant rights to access or use specific products or services, and assets representing tangible or intangible products associated with the order.
Generate Revenue Arrangements
When a Sales Order is created in NetSuite, the fields custcol_nue_start_date and custcol_nue_end_date on the order line are mapped to the Start Date and End Date fields in NetSuite Advanced Revenue Management (ARM). This mapping ensures that the revenue recognition schedules are accurately aligned with the specified timeframes.
Please note that only order products with Line Item and Ramp Item line types are transferred to NetSuite as order lines, as they represent the actual transactional components of the order.
Based on this configuration, Revenue Plans are automatically generated for each associated Revenue Element, providing precise and compliant revenue recognition tracking, as shown in the screenshot below:
After the orders are successfully transferred in NetSuite, records will be created in Transaction Hub to record the Nue and NetSuite transaction mapping.
Example
Throughout this document, we will use an example to demonstrate how transactions—such as orders, invoices, and credit memos—are transferred to NetSuite and how they are linked within NetSuite to trigger the creation of revenue arrangements.
This example includes the following sequence of actions:
- A user creates and activates the first that generates subscriptions, billing the customer for the first billing period.
- The user then creates a second (change) order to update the quantity of the existing subscriptions activated by the initial order.
- Finally, the user creates and activates a third order to add a new subscription for the same customer and consolidates the billing for all orders associated with that customer.
The following diagram illustrates the process of creating and activating the 1st order in Nue and syncing it with NetSuite for the first billing period.
When Nue Order #1 is activated, it contains two order products: Nue Order Product #1 and Nue Order Product #2. These order products are transferred to NetSuite as part of a single sales order, labeled NetSuite Order #1.
Each product in the Nue order corresponds to an individual order line in the NetSuite sales order, ensuring that the details of the products are accurately reflected.
- Nue Order Product #1 is synced and represented as NetSuite Order Line #1.
- Nue Order Product #2 is synced and represented as NetSuite Order Line #2.
Transfer Change Orders
When a Nue change order is activated and meets the payment rules, NetSuite processes all necessary updates within a single transaction to ensure seamless integration. The process is designed to handle various change order types effectively, including Update Quantity, Update Term, Adjust Price, Renew and Cancel. These change types are integral to managing dynamic customer requirements and ensuring accurate updates in NetSuite.
Only the mirrored order lines in the original mirrored order are updated in NetSuite, with support for multiple asset types such as subscriptions, entitlements, and assets. To transfer a change order, only Line Item and Ramp Item line types are included, as these represent valid transactional order products. The connector retrieves the corresponding NetSuite Customer IDs and item details from the Transaction Hub, and use these values to associate with the order, and order lines.
Generate Revenue Arrangements
When a change order is created and activated in Nue to make modifications to an existing subscription, the NetSuite integration ensures that these updates are seamlessly reflected in the original NetSuite Sales Order. The process keeps the original NetSuite Sales Order open while appending new order lines corresponding to the changes in the subscription. For each Nue order product in the change order, a mirrored NetSuite order line is created and linked to the appropriate revenue arrangements.
The integration supports incremental updates to ensure that changes - such as adjustments to subscription terms, quantities, or pricing - are properly synchronized. Revenue arrangements associated with the original NetSuite order are automatically updated to reflect these changes, ensuring accurate revenue recognition.
Throughout the process, the connector logs the outcomes in the Transaction Hub. Updates are monitored for success or failure - errors encountered during order line updates are recorded with a “Failed” status for the affected order products, while successful updates are marked as “Transferred.” This ensures that all change types are handled efficiently and that the status of each change order is clearly tracked, maintaining transparency and data accuracy.
Nue Order #1 with 2 order products, Nue Order #2 changes these 2 order products, after that, the change type order products will be added to the original Order in NetSuite.
Example
Let's continue our example.
After creating the first order, the user initiates a change order to update the quantities of two existing subscriptions. This action generates a second order Nue Order #2 containing Nue Order Product #3 and Nue Order Product #4. Both order products are transferred to NetSuite and linked to the original Nue Order #1. In essence, order products are grouped together if they are associated with the same subscriptions, assets, or entitlements, ensuring proper organization and alignment in NetSuite.
Transfer Renewal Orders
When the “Merge Renewal Order” setting is unchecked in the NetSuite Connector Configuration Wizard, renewal changes do not modify the original order. Instead, a new order is created in NetSuite to reflect the renewal. By default, the “Merge Renew Order” setting is unchecked, ensuring that renewal orders are handled independently of the original orders. This process supports subscriptions as the primary asset type and ensures seamless handling of renewals.
Create a new order for renewals
When "Merge Renewal Order" option is not enabled, the flow is illustrated n the diagram below.
In this diagram, Nue Order #3 includes two order products: one representing a renewal change for an existing subscription and the other introducing a new product that establishes a new subscription. Upon transferring Nue Order #3 to NetSuite, a new order, NetSuite Order #2, is created, containing both mirrored order lines and representing a new contract.
Merge renewal line into the original order
When "Merge Renewal Order" option is enabled, the flow is illustrated n the diagram below.
In this diagram, Nue Order #3 contains two order products: one representing a renewal change for an existing subscription and the other introducing a new product that initiates a new subscription. When Nue Order #3 is transferred to NetSuite, a new order, NetSuite Order #2, is created to include only the new product line, signifying a new contract. Meanwhile, the renewal line (Nue Order Product #5) is merged into the original order (NetSuite Order #1), preserving its association with the original contract.
Transfer Invoices
In Nue, the Invoice Item Detail is considered a finance transaction. When a Nue invoice is activated and transferred to NetSuite, the NetSuite Connector processes invoice item details rather than transferring the entire invoice directly.
Each invoice item detail is grouped based on its association with the mirrored NetSuite Original Order. If all mirrored NetSuite order lines belong to the same NetSuite order, the corresponding invoice item details are grouped together as invoice line items within NetSuite.
If the following setting is enabled Settings → Invoices: Do not send invoices to collection systems with $0 total amount, invoices with a total amount of $0 will not be transferred from Nue to NetSuite.
Catch-up invoices generated as part of the Catch-up Billing Run, which are used to migrate historical invoices, will not be transferred to NetSuite.
Associate Invoices with Sales Orders
Nue establishes a well-defined and structured relationship between invoices and sales orders, as well as between invoice item details and order line items. This structured mapping enables seamless integration of Nue Billing with NetSuite ARM, ensuring smooth downstream processes for collections and revenue recognition.
An example is shown in the screenshot below.
This diagram below demonstrates the flow of orders, order products, and invoices between Nue and NetSuite, highlighting how transactions are managed and synchronized for revenue recognition purposes.
Order and Order Line Association
- Nue Order #1 includes two order products (Order Product #1) that generate 2 subscriptions and are synchronized as separate order lines in NetSuite Order #1.
- Nue Order #2 contains the change order products that update the quantities of subscriptions generated by Nue Order #1 (Order Product #3 and Order Product #4) that are also added to NetSuite Order #1, expanding it with corresponding order lines.
- Nue Order #3 introduces a mix of a renewal (Order Product #5) and a new product (Order Product #6). Order Product #5 renews an existing subscription, while Order Product #6 creates a new subscription. These updates result in the creation of a new NetSuite Order #2, with corresponding order lines to capture the new subscriptions and lifecycle changes.
- In this example, "Merge Renewal Orders" option is not enabled.
Invoice Synchronization and Revenue Recognition
- NetSuite Invoice #1 consolidates invoice item details from all order lines associated with NetSuite Order #1, ensuring that the billing reflects the correct grouping of orders and their corresponding subscriptions or changes.
- NetSuite Invoice #2 is created for NetSuite Order #2 and groups the invoice item details generated from Order Product #6. cpturing the new subscriptions and lifecycle changes introduced by the third Nue order.
Integration Highlights
In summary,
- Separate mirrored invoices are created in NetSuite for each Nue Subscription, Asset or Entitlement, associated with the original mirrored orders.
- Each mirrored invoice includes the corresponding invoice items related to the mirrored Order Lines.
The integration ensures that invoice item details from Nue are transferred as invoice items in NetSuite, maintains a structured 1:1 relationship between order products and order lines.
This integration ensures a structured 1-to-many relationship between sales orders and invoices in NetSuite, aligning with NetSuite’s Advanced Revenue Management (ARM) processes. In contrast, Nue accommodates a more dynamic many-to-many relationship between orders and invoices, reflecting the recurring and flexible nature of subscription billing in Nue Billing. This design allows for seamless synchronization while maintaining the distinct transactional frameworks of both systems, ensuring accurate tracking and alignment for billing, invoicing, and revenue recognition.
Transfer Credit Memos
Credit Memos and Negative Invoices in Nue are created as Credit Memos in NetSuite. When a Nue Credit Memo or a Negative Invoice is transferred to NetSuite, a mirrored Credit Memo is created in NetSuite and linked to a newly created Return Autorization.
This is illustrated in the following diagram:
Return Authorization for Revenue Recognition
For downstream revenue recognition, the Nue NetSuite solution creates a Return Authorization record in NetSuite for every Credit Memo, or Negative Invoices transferred from Nue. When the Return Authorization is approved in NetSuite, a Revenue Arrangement is generated.
Pay Invoices
The NetSuite Connector does a sync every 5 minutes to retrieve payments made in NetSuite within the past 5 minutes. Based on these retrieved payments, the corresponding invoices in Nue are updated to reflect the payment status.
Update Payment Status
For each payment retrieved:
- The payment is applied to the corresponding Nue invoice.
- The payment status of the invoice is updated to:
- “Paid” if the balance is fully cleared.
- “Partially Paid” if a balance remains.
Example: Processing a Payment in NetSuite
A payment of $250 is made in NetSuite to cover two open invoices:
- Payment item #1: $100 applied to NS Invoice #1.
- Payment item #2: $150 applied to NS Invoice #2.
|
NetSuite Invoice |
NetSuite Payment |
Nue Invoice |
|---|---|---|
|
NS Invoice #1 - Amount $100, Balance $100 |
Payment Amount: $100 |
Nue Invoice #1 - Balance: $0, PaymentStatus: Paid |
|
NS Invoice #2 - Amount $200, Balance $200 |
Payment Amount: $150 |
Nue Invoice #2 - Balance: $50, PaymentStatus: Partially Paid |
Apply Credit Memos
The NetSuite Connector also retrieves credit memo applications every 5 minutes and updates the corresponding records in Nue.
For each credit memo applied to invoices -
The payment status of the affected invoices is updated to:
- “Paid” if the balance is fully cleared.
- “Partially Paid” if a balance remains.
The credit memo’s status is updated to:
- “Applied” if fully applied.
- “Partially Applied” if partially applied.
Example: Applying a Credit Memo in NetSuite
A credit memo with a balance of $250 is applied to two open invoices:
- $100 is applied to NS Invoice #1.
- $150 is applied to NS Invoice #2.
|
NetSuite Invoice |
NetSuite Payment |
Nue Invoice |
Nue Credit Memo |
|---|---|---|---|
|
NS Invoice #1 - Amount $100, Balance $100 |
Applied Amount: $100 |
Nue Invoice #1 - Balance: $0, PaymentStatus: Paid |
Nue Credit Memo |
|
NS Invoice #2 - Amount $200, Balance $200 |
Applied Amount: $150 |
Nue Invoice #2 - Balance: $50, PaymentStatus: Partially Paid |
Putting it Altogether
The Nue and NetSuite Connector provides a seamless integration between the two platforms, enabling businesses to synchronize their subscription billing, financial transactions, and revenue recognition processes. By bridging the gap between Nue’s dynamic billing workflows and NetSuite’s robust ERP and Advanced Revenue Management (ARM) capabilities, this integration ensures data accuracy, streamlined operations, and compliance with accounting standards.
The key capabilities include:
Customer and Product Synchronization
Customer records in Nue are mirrored as NetSuite Customers, ensuring accurate mapping.
Nue order products are transferred to NetSuite as items, enabling detailed transaction tracking.
Order and Invoice Synchronization
Orders created in Nue are transferred to NetSuite as Sales Orders, preserving their lifecycle, including renewals, updates, and cancellations.
Invoices generated in Nue are synchronized as NetSuite Invoices, with detailed invoice item mappings for accurate billing and revenue recognition.
Payment and Credit Memo Processing
Payments processed in NetSuite are pulled into Nue every 5 minutes, updating the payment status of corresponding invoices.
Credit memos applied in NetSuite are reflected in Nue, with updates to payment status and balance tracking.
Change Orders and Renewals
Change orders in Nue, such as quantity updates, term adjustments, or new product additions, are seamlessly updated in NetSuite.
Renewals can either be merged with existing orders or created as new orders, based on configuration settings.
Revenue Recognition Integration
The integration supports Advanced Revenue Management (ARM) in NetSuite by transferring critical data such as invoices, credit memos, and return authorizations.
Revenue arrangements and plans are automatically generated in NetSuite for downstream compliance with ASC 606 and IFRS 15.
Custom and Standard Field Mapping
Users can configure field mappings through the Configuration Wizard to align data between Nue and NetSuite, with support for both standard and custom fields.
Real-Time Synchronization
The connector ensures data is updated every 5 minutes, reducing manual errors and keeping systems in sync.
By integrating Nue with NetSuite, businesses can enhance their billing and financial workflows, improve visibility into subscription metrics, and maintain compliance with financial reporting standards—all while reducing operational overhead and ensuring a seamless customer experience.