Rating as a processor
The Rating processor in Zuora Mediation is used to calculate the rated amount for each usage event by evaluating usage quantity against the configured pricing in Zuora’s product catalog. It transforms raw usage data into billable rated records.
The Rating processor is currently in the Early Availability Phase. Please contact your Zuora account representative to enable this feature.
Rating output
The Rating processor produces billed usage events that include calculated charges based on the Zuora pricing configuration. Ensure that all identifiers and quantity fields are mapped correctly to avoid rating errors.
You can use the Audit Trail Download feature to track and debug rated outputs.
Rating processor for tiered-pricing model
In the tiered pricing model, the Rating processor must receive cumulative usage as a Pricing Quantity, grouped by charge number and/or account number. Without this, tier rates may be applied incorrectly for each event.
For example:
Day 1 = 10 units, Day 2 = 5 units
Day 2’s Pricing quantity must be 15, not 5.
For tiered pricing, the Price Quantity in the Rating Operator needs to reflect the total accumulated usage up to the processed event. This accumulation should be grouped by Charge Number. If your system ensures that the Charge Number is unique across all accounts (e.g., a globally unique identifier for each charge instance), then grouping by Charge Number alone may be sufficient.
Accumulated usage for tiered pricing
Accumulated usage is critical for a tiered pricing model as it evaluates the total consumption within a defined period to determine the applicable price tier. If the Price Quantity only reflects the current event's usage, the system will incorrectly apply rates, leading to under- or over-billing. By accumulating usages, the Rating Operator can accurately determine which tier the total consumption falls into.
- Zuora recommends using natural month billing periods (for example, calendar months: starting from the 1st to the end of the month) for rate plan charges when using the Rating processor. Mediation does not have access to the billing cycle day (BCD) from the subscription. Therefore, using non-standard billing periods may result in rating misalignment. Aligning to calendar months ensures accurate and consistent rating.
- Mediation and Billing do not automatically synchronize data. Any changes made in Billing are not reflected in Mediation unless you explicitly rerun the events, as Mediation does not auto-update.
-
The Rating processor only supports the following charge models:
-
Per Unit Pricing (Both Batch Mode, and Streaming mode meter)
-
Tiered Pricing (Both Batch Mode, and Streaming mode meter)
-
Volume Pricing (Batch Mode only)
-
Tiered with Overage Pricing (Batch Mode Only, and Streaming mode meter)
-
-
The Rating operator with Volume charge is not supported unless the correct priceQuantity is provided for streaming meters. The priceQuantity is essential to determine the correct slab for each transaction. Without it, the system cannot evaluate slab boundaries accurately, which may result in incorrect rating outcomes or failed charge calculations. To ensure accurate behavior, always provide the appropriate priceQuantity so the system can identify and apply the correct volume tier.
Configure a Rating processor
To configure a Rating processor:
- Navigate to Mediation > Meters.
- Create a new Custom meter.
- Select and drag the Rating processor type on to the meter stream page.
- In the Rating settings page, enter a Name for the processor.
- Specify the field mappings.
Field mappings define the join logic, how event records should be matched to reference data. - After specifying the mapping, click Save.
Field mapping
You can map the following fields during processor configuration:
Field |
Required |
Description |
---|---|---|
Subscription Number | No | Identifier for the subscription. |
Charge Number | No | Unique identifier of the charge. |
Quantity | Yes |
The amount of usage to be rated. |
Price Quantity | No | Cumulative usage to determine the correct tier in tiered/volume pricing models. Mandatory for tiered/volume pricing models, otherwise optional. |
Event Time | No | Use a field value from the event to accurately identify the applicable charge segment. If left blank, the latest timestamp will be used to determine the event time. |
Date Time Format | No | Date time format corresponding to the Event Time. |
Sample Date Time formats
Format Pattern | Sample Value | Notes |
---|---|---|
yyyy-MM-dd | 2025-09-08 | ISO-like date, safest and most common |
M/d/yyyy | 9/8/2025 | Allows single-digit month/day |
dd-MM-yyyy | 08-09-2025 | Day-Month-Year with dashes |
yyyy/MM/dd | 2025/09/08 | Year/Month/Day with slashes |
yyyyMMdd | 20250908 | Compact numeric date |
yyyy-MM-dd HH:mm | 2025-09-08 14:30 | Date + hour:minute (24h) |
yyyy-MM-dd HH:mm:ss | 2025-09-08 14:30:59 | Date + time to seconds |
yyyy-MM-dd'T'HH:mm:ss | 2025-09-08T14:30:59 | ISO-8601 style with T separator |
yyyy-MM-dd HH:mm:ss.SSS | 2025-09-08 14:30:59.123 | Includes milliseconds |
MM/dd/yyyy hh:mm a | 09/08/2025 02:30 PM | US-style date with 12h clock + AM/PM |