Billing Connector for Netsuite GL
Zuora manages complex subscriptions like the NetSuite hosted General Ledger (GL) System. This is an optional solution that leverages the core capabilities of both the Zuora and NetSuite applications.
The NetSuite Connector documentation describes how to install, configure, and use NetSuite Connector. In addition, it contains reference and troubleshooting information.
Use cases
NetSuite Connector can help you solve the following business concerns:
-
You are using Salesforce, and want to launch new recurring business.
-
You have a front-end application that manages user interaction.
-
You have high-volume, complex requirements or require usage processing.
-
You are using NetSuite for one line of your business, but you want to leverage Zuora for subscriptions.
-
You have customized NetSuite for subscriptions, but you have reached the limit of the NetSuite customization.
-
You are using QuickBooks and want to upgrade your accounting system.
Considerations and limitations
When deciding whether the NetSuite Connector is the right solution for your organization, consider the following:
-
NetSuite Connector is not compatible with the Prepaid Drawdown Zuora Connect app.
-
NetSuite Connector is not compatible with Automated Revenue Management (ARM).
-
Zuora does not recommend that you create orders from NetSuite to Zuora because it can cause potential problems.
-
Netsuite’s integration ID is not synchronized on invoice items when Invoice settlement is enabled.
-
NetSuite Connector cannot sync adjusted accounting codes from the Invoice Item Adjustment (IIA) to Netsuite.
-
NetSuite Connector does not support the “Fortis Bundle” NetSuite feature.
-
You cannot sync existing custom fields or add custom fields to the synced objects.
-
Avoid using double quotation mark (
") and comma (,) in Account Name because these symbols can cause data sync issues. -
NetSuite Connector can support syncing a maximum of 6,000 credit memos in a single job run.
-
Unsupported charge models include high water mark, pre-rated, and multi-attribute pricing. For more information, see Charge Models.
When NetSuite refunds are synced to Zuora, the connector maps the NetSuite tranDate to the Zuora Refund Date. In some cases, due to timezone conversion, the datetime returned by NetSuite's SOAP API can resolve to a date earlier than the payment effective date in Zuora. When this occurs, Zuora rejects the refund with the error "Refund Date cannot be earlier than Payment Effective Date", and the refund sync fails. This behavior is related to differences in how datetime values are returned by NetSuite and evaluated during date-based validation in Zuora. To prevent this error, ensure that the refund date in NetSuite is at least one day later than the corresponding payment effective date in Zuora.