Reverse transaction cannot be in the last period of the second year" in Sage 50
Sage 50 blocks a reversing entry dated into the second fiscal year; the date and the open-year rules are the real problem.
“Reverse transaction cannot be in the last period of the second year” is Sage 50’s way of saying the reversal date you picked falls in a period the program will not accept. It is a dating and fiscal-calendar restriction, not a sign that your file is damaged.
What the message actually means
Sage 50 lets a transaction reverse automatically in a later fiscal year. That mechanism has limits. One of them is that the reversal cannot land in the final period of the second year ahead. When you enter a reversing transaction and set the reversal date there, the program refuses and shows this message.
In plain terms: the date is too far forward, and in a position the reversing engine does not support. The transaction itself is usually fine. Only the reversal date is wrong.
Why Sage 50 does this
Reversing entries create a linked pair. The original posts now, and the mirror entry posts in a later period. Sage 50 keeps both years’ ledgers consistent when it does this, and it only supports that linkage across a limited window. The last period of the second year sits at the edge of what the program can reconcile, so it is excluded.
The exact cutoff depends on your fiscal calendar and how many years are open in your company file. We cannot give a universal date because every file is configured differently.
Fix it by changing the reversal date
The safest fix is the simplest one. Move the reversal date to an earlier period, typically the first period of the next year, and post the transaction. If the entry genuinely belongs in that far-off period, enter it manually when the period arrives instead of relying on automatic reversal.
Check your fiscal-year setup at the same time. If the year was opened or rolled forward incorrectly, the valid reversal window may be shorter than you expect, and correcting the calendar resolves the message on its own.
When the file itself is the problem
Occasionally this message appears on dates that should be valid. That points to a damaged transaction or a fiscal-structure fault inside the data file rather than a user error. If a date well inside the allowed window is still rejected, or the message appears alongside other odd behavior, the file needs professional attention. Our engineers repair damaged Sage 50 and Simply Accounting databases, and we can tell you quickly whether yours is affected: see our Sage 50 database repair service.
If the goal is to leave Sage 50 entirely
Some readers hit this wall while cleaning up years of entries before a move to QuickBooks. If that is your situation, the dating rules stop mattering once the history is converted. We handle Sage 50 to QuickBooks conversions, including Peachtree and Simply Accounting data, and the reversal restrictions do not carry over.
A useful next step
Before anything else, write down the exact reversal date that triggered the message and your fiscal year end. Then try the same transaction with a reversal date one period earlier. If that posts cleanly, the issue was the date and you are done. If it still fails, send us the file for a free evaluation and we will identify the cause.