How to Troubleshoot Execute Rating Errors in ZoneBilling

This article explains common Execute Rating errors in ZoneBilling, what usually causes them, and how to resolve them safely. It helps you troubleshoot subscription rating failures, understand why rating is blocked, and know when to correct data versus when to contact Support.

Note: Clicking on the images within this guide will enlarge them for better viewing.

Use this article when Execute Rating fails for a Subscription or Subscription Item. If you need general background on rating behavior, price books, or rate types, refer to your existing ZoneBilling billing and subscription documentation.

Prerequisites

Before troubleshooting rating errors, make sure you have access to the records involved and enough context to review the rating period.

• Access to the affected Subscription and any related Subscription Items
• Access to Customer, Item, Location, Subsidiary, and charge records
• The exact error message returned by Execute Rating
• The date range or rating period you are trying to rate

Rating can be influenced by subscription setup, charge generation, item and subsidiary compatibility, and whether charges in the same period have already been billed. Review the full transaction context before making changes.

How to troubleshoot Execute Rating errors

Please use the process below each time a rating fails. These steps help you confirm the scope of the issue, identify the record causing the failure, and decide whether the issue can be corrected directly or should be escalated.

1. Capture the exact error message from the Execute Rating action.
2. Open the affected Subscription and review its active Subscription Items, dates, customer, subsidiary, and location.
3. Review the charges in the rating period and confirm whether charges exist, whether a parent charge exists, and whether any charges in that period have already been billed.
4. Check related master data such as the Customer, Item, Location, and Subsidiary records for inactive status or incompatible setup.
5. If the error points to unsupported configuration or NetSuite governance limits, do not continue rerating repeatedly. Open a support case with details of the subscription, error text, and affected period.

Common errors and how to resolve them

No charges found to be rated

Error message: “No charges found to be rated” when executing rating for a Subscription or Subscription Item

This error means ZoneBilling could not find valid charges to rate for the selected period. In many cases, the charges are missing, the subscription item dates are invalid, or a required parent charge no longer exists.

Common root causes

• The Subscription Item End Date is before its Start Date
• The Customer linked to the Subscription is inactive
• The parent charge record has been deleted

How to fix it

1. Open the Subscription Item and confirm the End Date is the same as or later than the Start Date.
2. Open the Customer record linked to the Subscription and confirm the status is Active.
3. Review charges in the intended rating period and confirm the parent charge exists. The parent charge is the charge with a null value in the Created From Charge ID field.
4. If the parent charge is missing, regenerate the forecast charges before attempting to rate again.

Some charges in rating period have already been billed. Period is closed for rating.

Error message: “Some charges in rating period have already been billed. Period is closed for rating.”

This error means part of the charge period has already progressed to billing. Once charges in that period have been billed, ZoneBilling does not allow remaining charges in the same period to be rated independently.

Common root causes

• Parent charges for the period have already been billed
• Charges were manually manipulated so some charges were billed before others in the same period

How to fix it

1. Review the charges and invoice activity for the affected period.
2. Confirm whether the parent charge for that period has already been billed.
3. If rerating is required, credit and rebill the invoice for the affected period so the parent charge is reopened for rating.

INVALID_FLD_VALUE for item

Error message: “INVALID_FLD_VALUE: You have entered an Invalid Field Value XXXX for the following field: item”

This error indicates that the item used during rating is not valid in the current transaction context.

Common root causes

• The Item record is inactive
• The Item is not associated with the Subsidiary used on the Subscription or Subscription Item
• The selected Item is a Tax Group
• A required Rate or Price Value has not been defined

How to fix it

1. Open the Item record and confirm it is Active.
2. Verify the Item is available for the Subsidiary used by the Subscription or Subscription Item.
3. Confirm the Item is valid for use on transactions and is not set up as a Tax Group for this use case.
4. Check the Subscription Item and confirm a Rate, Usage Rate, or Overage Rate is populated when required, especially if the Item does not have default pricing.

INVALID_FLD_VALUE for location

Error message: “INVALID_FLD_VALUE: You have entered an Invalid Field Value 871 for the following field: custrecordzab_c_location”

This error means the location on the subscription context cannot be used for rating.

Common root causes

• The Location record is inactive
• The Location is not associated with the Subsidiary used on the Subscription

How to fix it

1. Open the Location record and confirm it is Active.
2. Verify the Location is compatible with the Subsidiary on the Subscription.

INVALID_FLD_VALUE for subsidiary

Error message: “INVALID_FLD_VALUE: You have entered an Invalid Field Value XXXX for the following field: Subsidiary”

This error usually means the subsidiary on the transaction context is no longer valid for rating.

Common root cause

• The Subsidiary record is inactive

How to fix it

1. Open the Subsidiary record and confirm it is Active.
2. If needed, review whether the Subscription or related setup points to the correct Subsidiary.

Could not rate charge id XXXXX | submitFields: Missing a required argument: id

Error message: “Could not rate charge id XXXXX | submitFields: Missing a required argument: id”

An unsupported feature combination, rather than a simple data issue, typically causes this error.

Common root causes

• Charge Item Mapping for Included Units is being used together with an RPSM that has Charge Consolidation enabled
• Prepaid rate types such as PPD Item Qty or PPD Subscription are being used together with an RPSM that has Charge Consolidation enabled

How to fix it

1. Review the rate plan and rating setup used by the affected subscription.
2. Confirm whether Charge Consolidation is enabled on the RPSM.
3. If 1 of the unsupported combinations above is in use, adjust the design or open a support case to review a safe alternative configuration.

Important: At this time, these combinations are not supported. Repeated rerating attempts will not resolve the issue until the setup is changed.

Attempted to rate Subscription without Subscription Items

Error message: “Attempted to rate Subscription [ID] without Subscription Items / Could not rate charge id”

This error means the subscription does not have active subscription items available for rating.

Common root cause

• The Subscription is missing active Subscription Items

How to fix it

1. Open the Subscription and review its related Subscription Items.
2. Confirm there is at least 1 active Subscription Item for the period being rated.
3. If items are missing or inactive, correct the subscription setup before retrying rating.

SSS_INSTRUCTION_COUNT_EXCEEDED / Script Execution Statement Count Exceeded

Error message: “SSS_INSTRUCTION_COUNT_EXCEEDED / Script Execution Statement Count Exceeded”

This error indicates that NetSuite hit its instruction governance limit during rating. It is usually related to complex processing rather than a single incorrect field value.

Common root cause

• NetSuite instruction governance cap reached during complex rating calculations

How to fix it

1. Capture the exact error message, subscription ID, and rating period.
2. Do not continue repeated retries without review.
3. Open a support case with the ZoneBilling support team for investigation.

SSS_TIME_LIMIT_EXCEEDED / SSS_SEARCH_TIMEOUT / ABORT_SEARCH_EXCEEDED_MAX_TIME

Error message: “SSS_TIME_LIMIT_EXCEEDED / SSS_SEARCH_TIMEOUT / ABORT_SEARCH_EXCEEDED_MAX_TIME”

This error means the rating process exceeded NetSuite time limits, often because of large data volume or a search scope that is too broad.

Common root cause

• Large volume of usage or count records, or a broad saved search scope, causing processing to exceed NetSuite time boundaries

How to fix it

1. Capture the exact error message, affected subscription, and time period.
2. Review whether the rating run includes unusually large usage volumes or broad search criteria.
3. Open a support case with the ZoneBilling support team for review.

Safe rerating guidance

When investigating rating failures, it is important to understand when rerating is safe and when it can create billing issues.

• Safe rerating usually starts with correcting setup or record status issues first, then retrying rating for the intended period.
• If charges in the period have already been billed, do not assume you can rate remaining charges independently.
• If parent charges are missing, regenerate forecast charges before attempting rating again.
• If the error involves unsupported feature combinations or NetSuite governance limits, involve support before making structural changes.

Related articles

• ZAB Charge Statuses
• ZAB Charges
• Charge Period Dates
• Rating Overview
• Rate Types
• Charge Schedules
• Ad Hoc Billing
• Introduction to Credit/Rebill

FAQ

Can I rerate charges after billing?

Not directly in the same period if charges in that period have already been billed. Review whether a credit and rebill process is required.

What should I do if the error points to a missing parent charge?

Confirm the parent charge is missing by reviewing charges in the rating period and checking for a charge with a null Created From Charge ID. If it is missing, regenerate forecast charges.

When should I contact support?

Contact support for governance errors, timeout errors, or unsupported setup combinations such as certain prepaid or included-unit configurations used with Charge Consolidation.