Payroll Setting
Every client wants the payroll screens to behave slightly differently: this field must be filled in, that one must not be touched, that other one should not be on the screen at all. This is where you say so, for one legal entity, without changing the product.
What it is for
A field is normally compulsory or optional because the product says so. When one client needs a remark to be compulsory on every loan, or needs a date to be read only because their process fills it elsewhere, that is a decision about this client and not about PeopleNest.
This screen holds those decisions, one record per legal entity. Each line names a payroll screen, then a field on that screen, then what should be different about it: compulsory, read only, hidden, or filled with a starting value. Nothing is coded and nothing is upgraded away.
The second tab is for extra checks. A special validation is a rule written for the client that runs when a payroll document is saved, and the line here says which screen it applies to. The rules themselves are prepared in advance, so you pick one from the list rather than writing it.
Use it sparingly. A hidden compulsory field is a document nobody can save, and the reason will not be obvious to the person stuck in front of it.
Every field, in plain words
Basic Data
| Field | What it means | What to put in it | Notes |
|---|---|---|---|
| Legal Entity | The company these settings apply to | PK01 | Required. Pick from the list. One record per legal entity |
| Required Pay Channel | Whether a pay channel has to be chosen on the payroll documents of this company | Leave it clear unless the client runs a second payment channel |
Field behaviour
One line per field you want to change.
| Field | What it means | What to put in it | Notes |
|---|---|---|---|
| Line # | The line number | Fills itself | Leave it |
| Process Code | The payroll screen the rule applies to, picked by name from the list of screens | Employee Loan Request | Pick from the list |
| Object No | The field on that screen, picked by its label from the list | Remarks | Pick from the list. Only fields of the screen you chose are offered |
| Value | A starting value for the field | 0 on a numeric field the client wants defaulted | Leave it empty unless you want the field pre filled |
| Mandatory | The field cannot be left empty at this company | Tick it to make the remark compulsory | |
| Disable | The field is shown but cannot be typed in | Tick it on a field another process fills | |
| Hidden | The field does not appear on the screen | Tick it on a field this client never uses | Never tick Hidden and Mandatory on the same field |
Validation
| Field | What it means | What to put in it | Notes |
|---|---|---|---|
| Line # | The line number | Fills itself | Leave it |
| Process Code | The payroll screen the extra check runs on | Employee Payroll Loan | Pick from the list |
| Special Validation | Which prepared check to apply | Pick from the list | The checks themselves are set up in advance, you only attach them here |
How to configure it
- Create one record for the legal entity, if there is not one already. There should never be two.
- On the field behaviour tab, add a line. Pick the screen, then pick the field by its label.
- Tick exactly what you need: Mandatory to force it, Disable to lock it, Hidden to remove it. Leave the rest clear.
- If the client wants a field pre filled, type the starting value instead of ticking anything.
- Save, then open the screen you changed and check the field behaves as you intended before you tell the client it is done.
- Add validation lines only when a prepared check exists for what the client asked for.
Scenarios
"Our auditors want a reason typed on every ad hoc deduction"
One line. The screen is the additional payment or deduction screen, the field is the remark, Mandatory ticked. Nobody can save that document without a reason from then on, at this company only.
"Nobody should be able to change the payment date on a loan, we set it centrally"
One line with Disable ticked on that field. It still shows, with whatever value the process put there, and it cannot be typed in.
"We do not use the second pay channel and the field confuses people"
One line with Hidden ticked for each screen it appears on. Make sure the field is not compulsory before you hide it.
What it is connected to
- Applies only to the legal entity named on the record. A second company needs its own record, and its own lines.
- Changes how the payroll screens behave for everybody at that company, from the next time the screen is opened.
- Does not change any amount or any calculation. It only changes what a user may type.
If something looks wrong
- "A payroll document cannot be saved and the message makes no sense" - a field has been made compulsory here and may also be hidden. Check the lines for that screen.
- "A field we made compulsory is still optional" - the line names a different screen from the one being used, or the record belongs to another legal entity.
- "The setting works for one company and not the other" - these settings are per legal entity. Add the lines to the second company's record as well.