Stay current on the latest news, events and industry updates

Employment state/jurisdiction settings update now live

We have expanded how the software can collect employment jurisdictions so that rather than only collecting the employment state, there are now new additional options for collecting the county and city.
As data providers begin requiring more information, this will allow you to continue using the vendors you prefer. This also helps get some of the foundations in place as we begin planning for more system updates that will allow you to send more dynamic disclosures based on the jurisdiction.
Read below on how your settings have changed.

In the Required Fields table:

When you go to Admin >> Manage Required Fields, this setting will now be labeled as “Employment Jurisdiction” instead of “Employment State.”
As before, you will be able to set this as required, hidden, or optional. Your previous settings will be unaffected, so whatever you had the employment state set to, it will still be the same with the label change.

In the order wizard:

When a CRA or client user is creating an order, after picking the state, you will have additional fields to be able to choose the county and city from dropdown lists.
Based on how you have configured this setting, in your Required Fields settings, you will see slightly different behavior:

  • If the employment jurisdiction is set to hidden, everything will be hidden
  • If the employment jurisdiction is set to optional, the state, county, and city will all be available to select but optional
  • If the employment jurisdiction is set to required, the state will be required as before, but the new county and city fields will still be optional.
software menu with an employment county search

Because the options that are available in the dropdown are dependent on the previous setting, you must set them in the order they appear: state, county, then city. A county cannot be chosen until the state has been set, and the city cannot be selected until the county has been set.

In QuickApp orders:

If a CRA or client is setting up the order as a QuickApp, they will have the same options as above. When the applicant receives the QuickApp, they will see the jurisdiction information that was filled in during the order creation, but they will not be able to edit it. This is consistent with how this setting already behaves and does not reflect any changes to the system.
If an employment jurisdiction was not entered during order creation, and you have QuickApp disclosures set up that ask the applicant where they will be employed (example below), the state from the disclosure questions will be used for the employment jurisdiction as well.

city and state notice that includes options for current residence and future employment states

If the employment jurisdiction is not filled out by the CRA or client when placing the order, and there are no jurisdictional questions included in your QuickApp disclosures for the applicant, this field will be left empty.

In the report results:

The Employment State under the applicant information section will be renamed to match the new label in the Required Fields table, and will show all jurisdictional information entered rather than just the state, according to how it was gathered in the order wizard or QuickApp.

Emp. Jurisdiction: HI, KAUAI COUNTY, LIHUE

Questions? Feedback? Let us know in the comments below!

Share on facebook
Share on linkedin
Share on twitter