A completed import is part of the organization’s recorded history. Correct the affected records with an authorized update; do not try to erase the completed import.

Before you begin

You need the import type’s viewing permission to open its history or files. Correcting records requires the matching management permission, such as Manage positions, Manage employees, Manage labor budgets, or Manage actual compensation. Running a replacement import also requires the Run batch imports permission and all-department coverage.

Review what changed

Open the import summary, review its issue summary and row sample, and open the original submitted file if needed. Identify the affected record, field, earlier value, new value, and effective date.

Do not begin by uploading the same file again. First determine:

  • whether the import completed;
  • which rows were created, updated, unchanged, or skipped;
  • whether the problem is a wrong value, wrong date, wrong record, or unintended population;
  • whether later authorized work already changed an affected record; and
  • whether the correction belongs on the record page or in a new import.

Protect the original source file and completed summary as part of the review evidence.

Contain a material mistake

When a completed import exposes protected information incorrectly, changes a broad population, or affects active business work:

  1. stop preparation of any related duplicate import;
  2. tell the responsible organization owner what completed;
  3. limit further use of any incorrect exported or downloaded files;
  4. identify all affected departments and records;
  5. review active requests, assignments, financial results, or reports affected by the change; and
  6. contact Support before another broad update when the safe correction is unclear.

Do not delete or rewrite activity in an attempt to hide the mistake.

Choose the correction

Use a new update import for a consistent bulk correction. Use the record page when only a few records need attention and the available correction action matches what happened. Keep position control, labor budget, and actual compensation corrections in their own areas.

What happened Correction approach
A value or effective date was recorded incorrectly Correct the existing record using the action provided for that information
A valid value should change later Add a later dated business change rather than rewriting the earlier period
A record should never have been created Use the remove or void action when the page confirms it matches the situation
Many rows need the same safe correction Prepare a new Update file with only the affected rows
The affected set or correct dates are uncertain Stop and contact Support before another broad file

Example: wrong future department date

An import moved 40 positions to Finance beginning June 1, but the approved date is July 1.

If the June 1 date was never valid, prepare a correction that restores the accurate timeline, using the position correction action supported by the template or record page. Do not add another Finance change on July 1 while leaving the false June period in history.

Review active requests and department-based access that may have been affected during the incorrect period.

Validate the correction as carefully as the original file, then review the affected records and activity.

For employee compensation, use correct when the recorded values or dates were wrong, end when a valid row should stop, and remove when the row should never have existed.

Example: valid rate ends

An employee compensation record was valid through September 30 but should not apply beginning October 1. Use end with October 1 as the first date it no longer applies. Do not use remove, because the earlier record was valid.

Validate and verify the correction

  1. Include only the records that need correction.
  2. Download a fresh Update template.
  3. Confirm stable identifiers and dates.
  4. Validate the file and compare each preview change with the intended correction.
  5. Review warnings and active requests again.
  6. Apply once.
  7. Review a date before and after the corrected period.
  8. Run new reports after related results finish updating.
  9. Review Activity to confirm the original import and correction form an understandable sequence.

A completed report prepared before the correction will not change. Preserve it when it is needed for review and run a new report for the corrected result.

If the scope is unclear

Contact Support before applying another large file when you cannot determine every affected record or the correct dated action.

Include the import number, type, mode, completion time, affected departments, approximate row count, example records, and the intended business result. Do not include passwords or unnecessary protected values.