Sage 50 "Import file has errors and cannot be processed" fix
Sage 50 looked at your import file, found something wrong with its layout or contents, and refused to bring any of it in.
“Import Error: Import file has errors and cannot be processed.”
That is Sage 50’s way of saying it gave up before importing anything. Sage 50 opened the file you pointed it at, checked it against the import layout it expects, found something it did not like, and stopped. The frustrating part is the silence: the message almost never names the row, column, or value that caused the refusal, so the real task is narrowing down which part of the file is at fault.
Why it happens
A handful of causes cover most cases:
- Layout mismatch. The file’s columns, headers, or field order do not match what the selected import template expects. When the skeleton is wrong, Sage 50 rejects the whole file rather than skipping the odd row.
- Data that fails validation. Dates in a format the import does not recognize, text sitting in numeric fields, blank required cells, values that are too long, or stray commas and quotes that break fields apart.
- The wrong kind of file. A report, a backup, or an export saved in a different format than the one the import is designed to read.
- A damaged or incomplete file. An export that was interrupted, a copy that was cut short in transit, or encoding problems introduced when the file moved between programs.
- Damaged source data. If the file was exported from a company file that is itself compromised, the export can be structurally unsound no matter how carefully you clean it.
Step 1: Re-create the import file
The safest first move costs nothing. Go back to the source, re-export or re-save the import file, and open it in the program that made it, or in a spreadsheet, to confirm it is complete and readable. If the row count looks short, or the file will not open cleanly anywhere, the problem is upstream of Sage 50.
Step 2: Check the layout
Compare the file against the import template: same columns, same order, headers spelled the way the template wants them, one record per row. A single extra or missing column can fail the entire import.
Step 3: Hunt for bad rows
Scan for the usual suspects: blank required fields, inconsistent date formats, text in amount columns, very long notes, and invisible characters pasted in from a web page or PDF. Fix or remove what you find, save, and retry.
Step 4: Test with a small batch
Import a handful of rows first. If they fail, the problem is the layout. If they succeed, add rows in larger chunks until the failure reappears; the chunk you added last contains the offending record.
Step 5: Consider the source file
If the import file came out of a Sage 50, Simply Accounting, or Peachtree company file that is itself misbehaving, repair the source before exporting again. Our engineers repair damaged Sage 50 and Simply Accounting databases, and if the import file itself is a corrupt spreadsheet or database, its contents can often be recovered through a general file repair service.
If this is part of a conversion
If you are exporting Sage 50 data on the way into QuickBooks and hitting this wall on either side, a direct conversion sidesteps the import format entirely. We convert Sage 50 US (Peachtree) and Sage 50 Canada (Simply Accounting) company files straight to QuickBooks, lists and history included.
When to stop cleaning
If repeated test imports keep failing with the same generic refusal, or the source company file shows other signs of trouble, the file needs professional attention, and no amount of row-by-row editing will fix it.
Next step: send us the import file and, if you can, the company file it came from. We will examine both at no charge, tell you exactly why Sage 50 is rejecting the import, and quote any work before it is done.