Troubleshooting job matching fields
This section covers a series of potential issues you may run into when setting up or using fields in ChartHop to match payroll app requisition code, as well as their recommended solutions.
Does my job matching code have to use a custom field?
No, you can use a custom or built-in fields as long as the field type is a short text. We recommend using a custom field so that you can customize the name of your job matching field.
Can I have multiple open jobs with the same job matching code?
Yes. If you have multiple open jobs with the same job matching code, ChartHop will match the job with the req code set on it the earliest (note this may be different from which job was *created *earliest).
Does my custom field have a specific name like “req code”?
No. No, you can use any phrase to name your job matching code.
Why can’t I find the job matching code value on a person?
The requirements for the job matching code are that the field belongs to a job. When you set up the mapper from the remote system → [job matching code field], ChartHop works behind-the-scenes and uses the job matching code to find an open job for a new hire, then discards the value.
If you want to see the job matching code value saved on a person, you can create a separate field and mapper to track that.
Do I need to delete the job matching code value from the person on the HRIS once the matching is complete?
No. The job matching code is only used on new hires and won’t impact any employees who are already in ChartHop.
Note that changing the value in the HRIS will still update the value on the underlying job in ChartHop.
Why didn’t a(n) (existing) person transfer jobs when I changed their requisition code?
Code matching only applies to new hires and open jobs, not existing employees or internal transfers.