home

Zuora Platform

Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies
Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies

Welcome to Zuora Product Documentation

Explore our rich library of product information

Show Contents

thumbnailZuora Platform

Configurations in connector

Run Revenue connector for NetSuite ERP

Learn how to run the connector.

  1. From the connector Execution tab, select the solution instance from the dropdown list.
  2. Click the gear icon.
  3. Choose either On-Demand or Scheduled execution mode for each solution instance.
  4. Click Run or Schedule.
  5. If you selected scheduled mode of execution, choose the desired frequency.
  6. To see the status of the run, open the execution link.

    The Run details window is displayed, and each task in the connector flow is listed indicating success or error.

    Currently the connector follows an "All or None" approach to ingest all the transactions from the NetSuite dataset. There is no partial ingestion like some transactions are successfully ingested and some are not.

  7. Click the download icon to download the summary log.

Upon completion, you receive an email notifcation with an attachment that provides high-level details of:

  • Connector execution status

  • Object type

  • Revenue transaction file template name and details

  • Upload file name

  • Number of transactions ingested into Revenue along with fields that are mapped per each object

Validate transactions in Zuora Revenue inbound staging. See Validate transactions in Zuora Revenue after connector run .

The connector does not update the transaction records in NetSuite. For this purpose, you can create a workflow inside NetSuite to update the transactions. Based on the information available in Revenue Inbound Transaction staging, you can leverage Revenue APIs to validate the transactions that are successfully ingested into Revenue and the transactions that caused errors.

Last updated: November 27, 2025