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.

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

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.

   
2. Click the Add icon and enter the fields described in the table below.

   Field	Type	What to enter
   PRODUCT	setup	Enter the product ID.
   OCCUPANT TYPE	yes/no	Check this field to validate rates based on occupant type.
   SOURCE CODE	yes/no	Check this field to validate rates based on source code. Note: Applies only to new starts, delivery schedule changes, campaign setup, and iServices payments and auto renewals.
   REASON CODE	yes/no	Check this field to validate rates based on reason code. Note: Applies only to new starts, delivery schedule changes, campaign setup, and iServices payments and auto renewals.
   PAYMENT TYPE	yes/no	Check this field to validate rates based on payment type.
   AAM ZONE	yes/no	Check this field to validate rates based on AAM zone.
   ZIP CODE	yes/no	Check this field to validate rates based on Zip code.
   ZIP EXTENSION	yes/no	Check this field to validate rates based on Zip extension.
   COUNTRY	yes/no	Check this field to validate rates based on country.
   STATE	yes/no	Check this field to validate rates based on state.
   COUNTY	yes/no	Check this field to validate rates based on county.
   CITY	yes/no	Check this field to validate rates based on city.

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.