Phase record number of the transaction line is not valid" (Sage 50)
Sage 50 is reporting internal data corruption in a transaction line, usually meaning the file has structural damage needing repair.
When Sage 50 tells you “The phase record number of the transaction line is not valid,” it is reporting that a transaction line in your company data references an internal record that does not exist or is unreadable. Despite the word “phase,” this has nothing to do with payroll phases or project phases. It is a low-level data-integrity message: the database engine found a pointer inside a transaction that points to garbage, and it is refusing to process the entry.
What the message actually means
Sage 50 stores each transaction as a header record with one or more line records beneath it. Each line record carries an internal sequence number so the database knows how the lines connect to the header and to each other. When one of those sequence numbers is missing, duplicated, or out of order, Sage 50 cannot reconstruct the transaction and throws this error. The transaction itself may look fine on screen, but underneath it the structural linkage is broken.
Why it happens
The most common causes are an interrupted save (a power loss, a forced shutdown, or a network drop while Sage 50 was writing), a file that grew too large for its database engine to manage cleanly, or gradual corruption from storing the company file on a network share that has intermittent connectivity. In some cases the damage is limited to a single transaction; in others it spreads across many records and the error appears repeatedly.
What to try first: restore from backup
If you have a recent backup from before the error started, restore it and check whether the problem transaction is present and intact. This is the safest path because it replaces the damaged data rather than trying to patch it. If your backup is several days old, note which transactions you would need to re-enter so nothing is lost in the gap.
Check and repair the database
Sage 50 includes database maintenance tools that can sometimes resolve minor structural issues. Running the built-in check and repair on the company file may clear the bad pointer if the surrounding data is otherwise intact. If the repair tool itself fails or reports additional errors, stop and do not force it: repeated repair attempts on a badly damaged file can make recovery harder.
When professional repair is needed
If the error blocks you from opening the file, posting entries, or running reports, and the backup is too old or also damaged, the file needs professional attention. Continuing to work in a file with broken transaction linkage risks propagating the corruption to other records. Our engineers regularly repair damaged Sage 50 and Simply Accounting databases, rebuilding the internal record structure so transactions post correctly again.
Next step
Send us your file for a free evaluation. We will inspect the damage, tell you exactly which transactions are affected, and provide a no-obligation quote so you can decide whether repair or conversion to QuickBooks is the better path for your situation.