Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Image RemovedImage Added

The Zuora Usage Record Forwarder is used to send usage data to Zuora Billing using the Zuora Post Usage API or with the Active Rating Post Usage API. You map fields from a source to specific target fields, and Zuora Usage Record Forwarder then compiles and forwards the mapped fields accordingly.

The options are available under the Parameters and Configuration tabs. The Parameters tab allows you to set the values for how the Zuora Usage Record Forwarder would behave when communicating with the Zuora Billing system. The Configuration tab allows you to configure options to send the usage data and allows you to enable the use of Active Rating on the Zuora Usage Record Forwarder.

Parameters

Under Parameters, you get the Environment, Credentials, and Entity options to configure your connection settings.

Parameters.png

Environment

Field

Description

Tenant

The name of the Zuora environment. The following endpoints are available for selection:

US DC1 Production: https://rest.na.zuora.com/
US DC2 Production: https://rest.zuora.com/
US DC1 API Sandbox: https://rest.sandbox.na.zuora.com/
US DC2 API Sandbox: https://rest.apisandbox.zuora.com/
US Central Sandbox: https://rest.test.zuora.com/

EU Production: https://rest.eu.zuora.com/
EU Sandbox: https://rest.sandbox.eu.zuora.com/
EU Central Sandbox: https://rest.test.eu.zuora.com/

Custom - Use this option to access your own custom tenant environment. Specify the URL for your endpoint.

Credentials

Field

Description

Secrets Wallet

Secrets Wallet

Choose from a list of Zuora secret wallet passes.

Entity

Field

Description

Multi-Entity

If you have the Zuora Multi-entity feature enabled, you can specify the name of the entity you want access to. Zuora Multi-entity provides the capability to create and manage multiple entities within a single Zuora tenant.

For more information on Zuora Multi-entity, refer to https://knowledgecenter.zuora.com/Billing/Tenant_Management/Multi-entity .

Configuration

Under Configuration, you get the Request, Field mapping, Required fields, Optional fields, Operational Settings, and Response handling options to set for the Zuora Usage Record Forwarder. The configuration fields will be different if you have toggled on Use Active Rating described below.

Request

To send usage data to a Zuora Billing system, toggle off Use Active Rating. The Active Rating option is only applicable to Zuora customers that have the Active Rating feature activated, and the Use Active Rating toggle should always be off if this is not the case.

Rw ui tabs macro
Rw tab
titleNon-Active Rating
Non Active Rating.png

Required fields

In Required fields, the field mapping is done for the mandatory fields for the usage record. You must specify the Source Field based on the input from the previous function for the appropriate Required fields. There are three Required fields that must be mapped to the source fields: Quantity, StartDateTime, and UOM.

Optional fields

In Optional fields, you add the remaining optional fields or you may add additional fields to compile the usage record. There are eight Optional fields and those are AccountId, AccountNumber, ChargeId, ChargeNumber, Description, EndDateTime, SubscriptionId, and SubcriptionNumber. To add a custom field mapping, type the custom field name into Add field. Added custom fields will automatically be appended with the suffix ___c, you do not need to include this suffix in the field name.

Note

Note!

Either AccountId or AccountNumber must be specified together with Required fields to successfully send usage records

Operational settings

In the Operational settings, you can take the following optional steps to configure the Zuora Usage Record Forwarder:

  • You can toggle on the Retry on fail functionality, allowing the service to retry the operation when an error has occurred. You can specify the number of retries in the Number of retries box, where the retries will be attempted inside the dynamically adjusted period of retry time.

Note

Note!

The maximum number of allowed retries is 12 and all retries will be attempted in a total span of approximately 68 minutes.  

Info

Use Case Scenario

The Retry on fail functionality can be used when servers respond with error codes such as 500 or 503 due to intermittent server issues. The retry on fail option allows users to retry sending the requests a set number of times. This is only useful for 5xx error codes.

  • You can choose to either Ignore or Stop the stream when requests still fail after specified retries have been executed.

Response handling

Toggling the Response handling on will allow you to Select Interconnect receiver. The Zuora Usage Record Forwarder has a built-in Interconnect Sender which will forward the status ID, request and records details received from Zuora. A second stream can use the Interconnect Receiver to accept the status ID, request and records details forwarded by the Zuora Usage Record Forwarder to track the status of the submitted usage record in Zuora. If the stream fails for any reason, Zuora Usage Record Forwarder will not send anything through the Interconnect Sender.

Note

Note!

  • 40 requests will be sent asynchronously to Zuora

  • Each request contains one record

Rw tab
titleActive Rating
Active Rating.png

Required fields

In Required fields, the field mapping is done for the mandatory fields for the usage record. You must specify the Source Field based on the input from the previous function for the appropriate Required fields. There are three Required fields that must be mapped to the source fields: accountNumber, tag, unitOfMeasure, startDateTime, and quantity.

Optional fields

In Optional fields, you add the remaining optional fields or you may add additional fields to compile the usage record. There are three Optional fields and those are description, groupId, and uniqueKey. To add a custom field mapping, type the custom field name into Add field. Added custom fields will automatically be appended with the suffix ___c, you do not need to include this suffix in the field name.

Operational settings

In the Operational settings, you can take the following optional steps to configure Zuora Usage Record Forwarder:

  • You can toggle on the Retry on fail functionality, allowing the service to retry the operation when an error has occurred. You can specify the number of retries in the Number of retries box, where the retries will be attempted inside the dynamically adjusted period of retry time.

Note

Note!

The maximum number of allowed retries is 12 and all retries will be attempted in a total span of approximately 68 minutes.  

Info

Use Case Scenario

The Retry on fail functionality can be used when servers respond with error codes such as 500 or 503 due to intermittent server issues. The retry on fail option allows users to retry sending the requests a set number of times. This is only useful for 5xx error codes.

  • You can choose to either Ignore or Stop the stream when requests still fail after specified retries have been executed.

Response handling

Toggling the Response handling on will allow you to Select Interconnect receiver. The Zuora Usage Record Forwarder has a built-in Interconnect Sender which will forward the status ID, request and records details received from Zuora. A second stream can use the Interconnect Receiver to accept the status ID, request and records details forwarded by the Zuora Usage Record Forwarder to track the status of the submitted usage record in Zuora. If the stream fails for any reason, Zuora Usage Record Forwarder will not send anything through the Interconnect Sender.

Note

Note!

  • 40 requests will be sent asynchronously to Zuora

  • Each request contains 5 records