Custom fields
Add your own fields to employees, positions and job architecture, and use them in analysis.
Written By Karl
Last updated About 9 hours ago
Custom fields hold information Evenpay doesn't have a built-in field for, such as a collective agreement, a shift pattern or a cost centre. You can filter, group, export and analyse by them, and use them as pay factors.
Who can do this: Administrators.
Where: Settings β People & data β Custom fields
Create a custom field
Select to add a field and give it a name.
In Apply To, choose Employee, Position, Job Level, Job Grade, Job Family or Organization Unit.
Choose a type: Text, Rich Text, Number, Percentage, Currency (with Decimal places), Single Select, Multi Select or Yes/No.
For select fields, add the options.
Set the options below if you need them, and save.
Options
Computed field: the value is calculated with a formula. Set a Fallback value for when the formula can't be calculated.
Hidden field: not shown on profiles, but still used in calculations, pay factors and exports.
Can be used as a pay factor: makes the field available in pay factors. For select fields, say whether the options are categories or an ordered scale.
You can also create a custom field during an import, from a column that isn't mapped yet.
Remove a custom field
Delete Field deactivates the field and keeps its data. Reactivate Field brings it back.
Delete Permanently removes the field and all its data.
Good to know
Changing a Multi Select field to Single Select keeps only the first value for each record.
Custom fields can be used in work of equal value groups, pay band rules and merit cycle rules.
If your organisation uses entities, custom fields are always shared across the group.
Related articles
Was this helpful?
More in Data & integrations
Importing employees from a CSV fileHow imports create job architectureCurrencies in importsImporting salary (payroll) historyStill need help? Share an idea