# Rating Validation

By default, subscription rates are validated based on publication, delivery schedule, delivery method, and date. If a rate is not valid for all of these elements, it is considered an invalid rate for a subscriber in Customer Service—it will not default for the subscriber, appear in an F2 lookup, or be validated when exiting the rate code field.

Using Rating Validation, you can include one or more additional fields when validating subscription rates in Customer Service and iServices. Some of them are used only during certain transactions, or are applied differently depending on whether the subscriber’s payment type is being changed. The table below lists the fields that can be used during validation for each transaction type.

<table><thead><tr><th width="258">Transaction type</th><th>Rate codes can be validated against...</th></tr></thead><tbody><tr><td>Billing Changes</td><td>publication, delivery schedule, delivery method, date, occupant type, payment type, AAM zone, Zip code, Zip extension, city, county, state, country<br>Note: If the payment type is not being changed, then only publication, delivery schedule, delivery method and date will be used for billing changes.</td></tr><tr><td><p>New Starts</p><p><br>Delivery Schedule Changes</p><p><br>iServices Campaign New Starts</p></td><td>publication, delivery schedule, delivery method, date, source, reason, occupant type, payment type, AAM zone, Zip code, Zip extension, city, county, state, country</td></tr><tr><td>All other Customer Service transactions</td><td>publication, delivery schedule, delivery method, date, occupant type, payment type, AAM zone, Zip code, Zip extension, city, county, state, country</td></tr><tr><td><p>iServices Payments</p><p><br>iServices Autorenewals</p></td><td>publication, delivery schedule, delivery method, date, source, reason, occupant type, payment type, AAM zone, Zip code, Zip extension, city, county, state, country<br>Note: If the payment type is not being changed, then only publication, delivery schedule, delivery method, and date will be used for these transactions.</td></tr><tr><td><p>Payment entry/processing</p><p><br>Billing change processing</p><p><br>Route returns</p><p><br>Draw changes</p><p><br>Subscription Rate report</p></td><td>publication, delivery schedule, delivery method, date</td></tr><tr><td>Campaign Setup</td><td>publication, delivery schedule, source, reason, date<br>Note: Rates can be validated against source and reason for new starts and delivery schedule changes, but not billing changes.</td></tr><tr><td>Utilities</td><td>publication, delivery schedule, delivery method, date</td></tr></tbody></table>

For example, if the subscriber’s rate must be valid for the reason code entered in order to be a valid rate, you would check Should Rates be Validated Based on the Reason Code? in Rating Validation.

#### To set up rating validation:

1. Select Rating Validation from the Subscription Rates menu to display the Rating Validation screen.

   <figure><img src="/files/8Cfp3FaaHXUamxcgrXxk" alt=""><figcaption></figcaption></figure>
2. Click the Add icon and enter the fields described in the table below.

   <table><thead><tr><th width="177.33333333333334">Field</th><th width="88">Type</th><th>What to enter</th></tr></thead><tbody><tr><td>PRODUCT</td><td>setup</td><td>Enter the product ID.</td></tr><tr><td>OCCUPANT TYPE</td><td>yes/no</td><td>Check this field to validate rates based on occupant type.</td></tr><tr><td>SOURCE CODE</td><td>yes/no</td><td>Check this field to validate rates based on source code.<br><strong>Note:</strong> <em>Applies only to new starts, delivery schedule changes, campaign setup, and iServices payments and auto renewals.</em></td></tr><tr><td>REASON CODE</td><td>yes/no</td><td>Check this field to validate rates based on reason code.<br><strong>Note:</strong> <em>Applies only to new starts, delivery schedule changes, campaign setup, and iServices payments and auto renewals.</em></td></tr><tr><td>PAYMENT TYPE</td><td>yes/no</td><td>Check this field to validate rates based on payment type.</td></tr><tr><td>AAM ZONE</td><td>yes/no</td><td>Check this field to validate rates based on AAM zone.</td></tr><tr><td>ZIP CODE</td><td>yes/no</td><td>Check this field to validate rates based on Zip code.</td></tr><tr><td>ZIP EXTENSION</td><td>yes/no</td><td>Check this field to validate rates based on Zip extension.</td></tr><tr><td>COUNTRY</td><td>yes/no</td><td>Check this field to validate rates based on country.</td></tr><tr><td>STATE</td><td>yes/no</td><td>Check this field to validate rates based on state.</td></tr><tr><td>COUNTY</td><td>yes/no</td><td>Check this field to validate rates based on county.</td></tr><tr><td>CITY</td><td>yes/no</td><td>Check this field to validate rates based on city.</td></tr></tbody></table>
3. Click OK to save the rating validation for this product in the database, or Add Another to save the existing record and add rating validation for another product.

### Overriding Rate Validation

Users who have been granted rate override security privileges (using the “RateCdOverride” transaction security item) are not affected by this rating validation setup. By default, no users are set up with this privilege. This override security, however, does not apply to Campaign setup or to any transactions entered in iServices.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.navigaglobal.com/circulation-setup-manual/accounting/subscription-rates-menu/rating-validation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
