Cannot void this transaction" with serialized items in Sage 50
Sage 50 blocks the void because the items were not serialized when the transaction was posted, so the history no longer matches.
You are seeing this message: “You cannot void this transaction because it contains serialized items that were not serialized when the transaction was entered.”
In plain terms, Sage 50 is refusing the void because the item records have changed since the transaction was posted. At the time you entered it, the items were not tracked by serial number. They are now. Voiding would force Sage 50 to remove serial numbers that were never recorded, and it will not do that. The block is a safety measure, not a bug.
Why Sage 50 refuses
Serial tracking is history-sensitive. When a serialized item is sold or received, Sage 50 writes the specific serial numbers into the transaction itself. If the item was not serialized at entry time, the transaction holds only quantities.
Turning serialization on later does not reach back and fill in those serial numbers. The old transaction still says “quantity only.” When you try to void it, Sage 50 checks for serial records, finds none, and stops rather than guess. The result is a transaction you can view but not void through the normal command.
What to do instead of voiding
The usual workaround is to reverse rather than void. Post an offsetting entry that mirrors the original: the same items, the same quantities, the opposite effect. This clears the financial impact while leaving both transactions in the audit trail.
Check your version’s help for the exact wording of the void or delete command, because the available options depend on whether the transaction is in an open or closed period. If the period is closed, you will need to reopen it first, which may require accountant access.
If the item was serialized by mistake
Sometimes the real problem is the opposite: serialization was switched on accidentally, and now older transactions are stuck. In that situation, the question is whether serial tracking can be turned back off without damaging history. That depends on the file, on how many transactions exist since the change, and on whether any serial numbers have actually been recorded. We cannot answer it in the general case.
When the transaction has to go
If the entry is genuinely wrong and a reversal will not do, for example because it distorts a report you must file, the transaction may need to be removed at the data level. That is not something to attempt with generic database tools. Sage 50 company files are sensitive to direct edits, and a wrong change can make the whole file unusable.
Our engineers handle this kind of correction as part of our Sage 50 database repair service. If you would rather move the whole company to QuickBooks and leave the problem behind, see our Sage 50 to QuickBooks conversion.
A practical next step
Before anything else, make a fresh backup of your company file and note the transaction number and date. Then try the reversing entry. If Sage 50 blocks that too, or if the item list itself seems inconsistent, send us the file for a free evaluation and we will tell you exactly what is possible before you commit to anything.