The everyday problem
An import is not complete when most rows have loaded. The rejected or uncertain records need an owner and a clear next action, otherwise staff may repeat the whole file or forget a small but important group of items.
A workable process
Record the source row, identifying code, error message and proposed resolution. Separate formatting problems from missing business information. Correct a small set and confirm the retry method supported by your import tool before processing the remaining exceptions.
A practical example
If 480 of 500 item rows succeed, importing all 500 again could create confusion depending on how the tool matches existing records. A log of the 20 exceptions lets the team focus on unresolved rows and verify whether a targeted retry is appropriate.
Before you finish
Retain the original file and the corrected version with clear names. Close each exception only after checking the resulting record, and compare the final accepted count with the intended import scope.
Try this check with your team
For a trial of 20 source rows, record how many were accepted, rejected or left unresolved. Retain the source row identifier and reason for each exception. Before rerunning corrected rows, inspect what already exists in the destination.
What the result tells you
Success means the complete source set is accounted for, not merely that most rows loaded. A controlled exception list makes retries deliberate and reduces the chance of duplicating successful records while fixing the failures.
See this workflow in Speed Plus.
Bring a sample transaction and your questions to a product demo.
Book a free demo ↗