Sage 50 Import Error: "Transaction header required before any details
Sage 50 stopped the import because it found a transaction line before the row that starts the transaction, leaving the line with nothing to attach to.
When Sage 50 shows “Import Error: Transaction header required before any details.”, it means the file being imported contains transaction lines before it has seen the row that opens the transaction they belong to. Sage 50 reads an import file from the top down: a header row starts a transaction (the date, the vendor or customer, the reference), and each line row under it supplies an amount, account, or item for that transaction. When a line arrives with no header above it, there is no open transaction to attach it to, so the import stops. The problem is almost always in the layout of the import file, not in Sage 50 or in your company data.
Why it happens
The common causes:
- The file begins with line rows because the first transaction’s header row is missing or was deleted.
- A header row is present but gets ignored, because a required field such as the date or reference is blank or in a format the importer does not recognize. The next line row then becomes the first orphan.
- The columns no longer match the template: a column was added or removed, or the file was saved in a different layout, so the importer misreads which rows are headers.
- The rows were reordered. Sorting a spreadsheet by amount or account, or filtering it and copying the visible rows, separates lines from their headers.
- The file was built for the wrong template, for example a lines-only file fed to an import that expects headers plus lines.
Check the first data row
Open the import file in a spreadsheet and look at the first row of data. It should be the header that starts the first transaction, not a line. If it is a line, the header was lost somewhere between export and import; the safest fix is to regenerate the file from the original source rather than to type a header in by hand.
Check every header, not just the first
The error points at the first orphan line the importer met, not the only one. Scroll through the file and confirm that every block of rows begins with a header, and that required fields on each header are filled in and formatted consistently. Blank rows in the middle of a block can also break the pairing, so remove any that sit between a header and its lines.
If the file came from another program
This message often appears when moving data into Sage 50 from another accounting package, or when preparing Sage 50 data for a move out to QuickBooks. The export or mapping step is usually at fault, not the accounting itself. Our engineers handle the header and line pairing as part of a managed Sage 50 to QuickBooks conversion, and the same applies to Simply Accounting and Peachtree data, where a conversion service sidesteps the template problem entirely.
If the file keeps failing
If you regenerate the file and the error persists, or the import file came from an export of a Sage 50 database that is itself damaged or partially recovered, the file needs professional attention. We can examine the import file and the data behind it and tell you exactly what is wrong; the evaluation is free and you receive a written quote before any work starts. If the source data turns out to be the issue, Sage 50 database repair is the relevant service.
The most useful next step: open the import file beside the template it was built from and compare the first ten rows. In most files that fail with this message the problem is visible on the first screen, and the fix is a small edit. If it is not, send us the file for a free evaluation rather than reshaping it by trial and error, because each failed attempt risks introducing new mismatches.