If you utilize either Conversational ATS configurations with Offers and Job Data Packages or Journey Targeting with the master feed and Offers, then you can set an internal and external pay rate validation for the Starting Pay Rate and Additional Pay Rate components used in offers. This validation will reference the Base Pay Minimum attribute, Base Pay Maximum attribute, or both, depending on the configuration set in the Offer builder. 

This data would be set in the job’s Job Data Package (Conversational ATS) or in the integrated ATS's master feed (Journey Targeting) for your team to safeguard the possibility of over/underpaying users.

Conversational ATS

Configuration

The default validation should already be configured Users with full access to Client Setup can configure this feature by completing the below steps.

1. Select All Apps in the top left corner of the header and then Settings in its drop-down menu.
2. When the Settings page opens, select Client Setup under the Paradox Tools section.
3. From the left panel, scroll down to and open the Forms & Offers section.
4. Under the Offer Management section, find the Default Validation field and select one of the following options listed here.
5. Save the page.

Update pay rate in Offer Builder

When editing a pay rate component within an offer letter, a slide-out drawer will then open and include the Validation field. This field will be unlocked and allow you to choose your preferred validation option. The option selected will be the validation used when sending an offer to a candidate from the Candidate Profile. This field will default to the option selected on the backend when configured, but it can be updated.

Once a selection is made, save and publish your offer.

Integrated ATS

Configuration: Setting pay rate via external feed

If you utilize an integrated ATS, the Base Pay Minimum and Maximum can be set via the external feed(s) being utilized to generate the ATS Master Feed. These values can be set at the feed processing level as custom fields from the feed. The following values are required to set the Min (i.e. 12.00) and Max (16.00) values as well as to aggregate the rate (i.e. $12.00 - $16.00/per hour):

• Pay Rate
• Billing Currency
• Billing Frequency

If mapping correctly, this will allow you to utilize Min and Max Pay Rate validation during the Send Offer stage of the candidate’s journey, which can be seen in the following section.

• Note: This will also allow you to use the #pay-rate, #base_pay_minimum, and #base_pay_maximum tokens as well, since those attribute values will be set with this processing model.

Feed requirements

• At a minimum, we need the Pay Rate in your feed (i.e. 12.00-16.00).
  • Note: If we receive only the pay rate with no mention of Currency and Frequency, we will default those fields to US Dollars ($) and Per Hour frequency.
• We can receive the Pay Rate, Billing Currency, and Billing Frequency as either separate nodes on your job feed or as an aggregated rate.

Pay rate experience in the Candidate Profile

If the Pay Rate validation was selected, then the existing minimum and maximum validations will display normally. However, if you select any other validation option, then an error message may display under the pay field notifying the user that they must enter a value between the job's minimum and maximum values.

Pay rate validation for sending offers

When an offer uses Base Pay Minimum, Base Pay Maximum, Offer Pay Minimum, or Offer Pay Maximum pay rate validation, Paradox evaluates the entered amount when the user selects Send Offer, not while they are entering or editing the value. 

When you select Send Offer, the system checks whether an active approval flow is configured for that pay amount.

• No active approval flow matches that pay amount: Paradox displays a validation error and prevents the offer from sending until the value falls within the configured range.
• An active approval flow matches that pay range or percentage: The maximum validation is bypassed and Paradox routes the offer to approval.

Additional notes

• Users can never save with no value or a value of zero.
• If the Base Pay Minimum and/or Maximum validation option(s) is(are) selected for the offer, but when sending the offer to a candidate, and the job is missing the relevant Job Attribute(s), then the system will default to the existing Pay Rate validation.
• The Offer Pay Minimum and Offer Pay Maximum Job Attributes are for internal use only to validate the offered pay rates versus the external pay range displayed to candidates.