Importing employment history
Bring in past changes to position, unit, manager and pay, dated when they happened.
Written By Karl
Last updated 1 day ago
The employment history import fills each employee's History tab with changes from before you started using Evenpay, for example earlier positions, managers or pay. Use it after connecting an HR system, because that history starts on the day you connect.
Who can do this: Administrators.
Where: Settings β People & data β Data management β Data Import β Employment History
Before you import
An imported value can update an employee's current data when its effective date is the latest for that field in the file and is not earlier than the latest change already recorded for that field. Older entries are handled as history; being the newest row in an upload does not automatically make a value current.
For example, if a field already has a change dated September, importing history for that field ending in June does not make the June value current. Check both the imported history and the employee's current profile after importing.
Your file
Each row describes one person on one Effective Date (required). Columns can include:
Employee Number or Email, to find the person. Employee Number wins if both are given. Terminated employees are matched too.
Reason, Status, Position, Org Unit, Manager Email, Worksite, Employment Type, Working Hours.
Agreed: (component name) columns with the monthly amount of each pay component.
Custom fields.
Steps
Download the Template from the Employment History tile.
Fill in one row per person per date. Leave a cell blank when that field didn't change.
Upload, map the columns, review and import.
Good to know
A blank cell means "unchanged", not "cleared".
Rows dated in the future are skipped with a warning.
The employment history export uses the same layout, so you can export, correct and re-import the file as is. See Exporting your data.
If an import is interrupted, review the result and the affected employees before retrying. Check which rows succeeded, failed or were skipped; do not assume that submitting the file again proves every row was saved. Contact support if you cannot establish the completed changes.
Related articles
Was this helpful?
More in Data & integrations
Importing employees from a CSV fileHow imports create job architectureCurrencies in importsConnecting your HR systemStill need help? Share an idea