My import has errors

Find and fix rows that didn't import, using the review grid and the error report.

Written By Karl

Last updated About 9 hours ago

When some rows in a CSV import can't be saved, Evenpay tells you which ones and why.

Find the problems

Before importing, the review grid shows Needs your attention. Use the issue navigator (⌘/Ctrl+Enter) to jump between problems and fix cells in place.
After importing, the results show Errors. Select Download error report for a list of failed rows and reasons.

Problem	Fix
The file isn't CSV	Save it as CSV (UTF-8). Excel files aren't accepted directly.
Dates aren't read correctly	Choose the right Date Format for the column in the Fields step, for example DD.MM.YYYY or YYYY-MM-DD.
Values were skipped	In the Values step, map each value in your file, such as gender or contract type, to a value in Evenpay. Unmapped values are skipped.
Existing employees were added again	Check Match existing by. Employee ID is the most reliable choice.
Pay amounts look 12 times too big or small	Check Value in CSV (monthly or annual) for each pay column.
A column wasn't imported	It's listed under Not imported. Map it to a field, or turn it into a pay component or custom field.

Was this helpful?

Still need help? Share an idea