The job record number of the transaction line is not valid" in Sage 50
Sage 50 is reporting that a transaction references a job record that no longer exists or is internally inconsistent, indicating data corruption.
When Sage 50 tells you “The job record number of the transaction line is not valid,” it means a transaction in your company file is trying to link to a job (project) that the database cannot correctly identify. The message sounds like a configuration problem, but it is almost always a sign that the internal data linking transactions to jobs has been damaged.
What the message actually means
Sage 50 stores each transaction line as a set of references: which account it posts to, which customer or vendor it involves, and, if it is a job-related transaction, which job record it belongs to. Each job has an internal ID number that the database uses to keep things connected. When Sage 50 says the job record number on a transaction line is “not valid,” it has looked up that ID and found either nothing, a mismatched record, or a corrupted entry. The software stops processing because posting the transaction would create a broken link in your books.
Why this happens
The most common cause is file corruption introduced during an improper shutdown: a power outage, a crash, a network drop while Sage 50 was writing to the file, or backing up a file that was open and in use. It can also appear after a failed data conversion or an interrupted Sage 50 update. In some cases the job record itself was deleted or merged, but the transactions that referenced it were not cleaned up properly, leaving orphaned references behind.
What to try first: restore from backup
If you have a recent backup from before the message appeared, the safest and most reliable fix is to restore that backup. This avoids any risk of further damaging the file or losing additional data. Before restoring, make a copy of your current damaged file and store it somewhere safe, because once you overwrite it with a backup, the data in the damaged file is gone.
What to try next: Sage 50’s built-in maintenance
Sage 50 includes maintenance tools (Check Data Integrity and File Maintenance in most installations) that can sometimes detect and repair broken internal links. Run a full check first to see what Sage 50 reports. If it finds errors it can fix, let it try. If it reports errors it cannot repair, stop there: running maintenance repeatedly on a badly corrupted file can make the damage worse.
When professional repair is needed
If no usable backup exists and Sage 50’s maintenance tools cannot resolve the error, the file needs professional attention. Continuing to work in a file with broken job references risks propagating the corruption into other transactions, and the problem will not resolve itself over time.
Our engineers repair damaged Sage 50 (Peachtree and Simply Accounting) company files by rebuilding the broken internal references at the database level, preserving your transactions, jobs, and history. Because the extent of the damage depends entirely on your specific file, we offer a free evaluation and quote so you know exactly what can be recovered before committing to anything.