Skip to main content

​
Overview

Employee imports stop safely when the file, mapping, or any row has a blocking issue. Teamper shows those problems before save so you can correct the import without changing employee records.

​
Common causes

  • Empty CSV files or malformed CSV formatting
  • More than 200 employee rows
  • Missing required mappings for Full name, Email, Department, or Opening balance
  • The same source column mapped to more than one Teamper field
  • No active leave type selected, or a selected leave type that cannot be used
  • Invalid opening balance decimals
  • Duplicate employee ID values in the CSV
  • Duplicate email values in the CSV
  • Employee ID and email matching different employees
  • An existing employee email being changed through import
  • Archived employees included in the import
  • Start date values not in YYYY-MM-DD
  • Department or holiday calendar names that do not match Teamper
  • The employee leave policy not including the selected leave type
  • No active default leave policy
  • An imported opening balance belonging to an older balance period

​
Step-by-step guide

  1. Go back to Map your columns or the preview page that shows the error.
  2. Fix every required mapping and remove any duplicate source-column mappings.
  3. Confirm that the selected leave type is active and that employees being updated use a leave policy that includes that leave type.
  4. Correct row-level data issues in the CSV, such as duplicate employee IDs, duplicate emails, invalid dates, or invalid opening balance decimals.
  5. Confirm that departments and holiday calendars already exist in Teamper with matching names.
  6. Re-upload the corrected CSV or run the preview again.

​
Troubleshooting

​
Teamper says a required mapping is missing

Open Map your columns and make sure Full name, Email, Department, and Opening balance each point to a source column.

​
Teamper says the same source column is mapped twice

Each source column can map to only one Teamper field. Remove the duplicate mapping, then preview again.

​
Teamper says the leave type is missing or invalid

Choose one active leave type before you analyze the file. If the leave type is no longer active, go back and select another active leave type.

​
A row shows duplicate employee ID or duplicate email

Check the CSV for repeated values. If you are re-importing existing employees, prefer Employee ID as the stable match key.

​
Teamper says an archived employee cannot be changed by import

Restore the employee first if you need to update that record. Archived employees cannot be changed through this import flow.

​
Teamper says a department or holiday calendar does not match

Check the exact names already configured in Teamper. Update the CSV value or create the missing department or holiday calendar before importing again.

​
Teamper says a default leave policy is required

Create and activate a default leave policy before importing employees.

​
Teamper says the employee leave policy does not include the selected leave type

Assign the employee to a leave policy that includes that leave type, or choose a different leave type for the import.

​
Teamper says the imported opening balance belongs to an older balance period

Do not keep retrying the same row through import. Use a manual leave balance adjustment instead.

​
The preview says Import is blocked

Review the rows marked Needs fixing and correct every blocking issue before you click Confirm import. Teamper keeps confirmation disabled until the preview has no blocking rows.

​
The preview asks you to re-select the CSV

Uploads are not stored between steps. Choose the same CSV file again on the preview page, then continue your review before you confirm the import.

​
The import result is missing

Start a new import review from the CSV upload page. The result page is only available for the import that just completed.

​
Safe retry guidance

  • Nothing is saved until you click Confirm import.
  • Fix the mapping or CSV first, then preview again.
  • Rows marked Needs fixing must be corrected before import can continue.
  • If the browser asks for the file again, choose the same CSV before you confirm.
  • If the result page is missing, start a new review from Import CSV.
  • Use the preview to confirm the rows now show a clear outcome before you continue.