Sage 50: "The income period cannot cross over fiscal year ends
Sage 50 is rejecting a date range that starts in one fiscal year and ends in another; split the entry or report at the year end.
If Sage 50 has just stopped you with “The income period cannot cross over fiscal year ends.”, the program is objecting to a date range, not reporting damage. Somewhere on the screen you came from, a starting date and an ending date straddle a fiscal year boundary: the period you asked for begins in one fiscal year and finishes in the next. Sage 50 (sold as Peachtree in the US and Simply Accounting in Canada) keeps income activity inside one fiscal year at a time, so entries, allocations, and reports whose period crosses the year end are refused outright.
Why Sage 50 refuses the entry
Typical triggers:
- A charge, contract, or allocation whose from and to dates span the year end, for example a service billed from December into January.
- A report or budget with a custom date range that crosses the fiscal year end.
- A transaction dated in a year that is closed, or a session date set in a different year than the entry.
- Year-end cleanup, where an adjustment that belongs to a closed year can no longer be posted as an income entry.
The message is a validation rule. In most cases the file itself is fine; the dates simply do not fit.
Split the work at the year end
The safest fix is to divide the entry or report into two pieces, each inside a single fiscal year. Post the December portion of a December-to-February charge in the old year and the remainder in the new year. Run a report twice, once per fiscal year, or end the range on the last day of the year. This risks nothing, and it usually matches how the income should be recognized anyway.
Verify the fiscal year end itself
If the dates look right to you, the year end stored in the company file may not be what you expect. Check the fiscal year settings in your company and confirm the year end date. If it was entered incorrectly when the company was created, correcting it can clear the message, but changing a fiscal year in a file that already holds transactions affects reporting and prior-year comparisons. Make a verified backup first, and review the change with your accountant where the accounting treatment matters.
Closed years and prior-period adjustments
When the message appears during work on a previous year, Sage 50 is often telling you, indirectly, that the year is closed. Rather than forcing history open, the usual approach is to book the correction in the currently open year. Which route is correct depends on the entries involved and on how your books are maintained.
If it appears during a conversion
The same rule can surface when moving Sage 50 data into QuickBooks and the chosen date range spans fiscal year ends. Our Sage 50 to QuickBooks conversion service handles this by aligning or splitting the range so each piece lands cleanly in one year, and by carrying the fiscal structure across so reports tie out afterwards.
When the file needs professional attention
If the dates sit inside one fiscal year, the fiscal year settings are correct, and Sage 50 still refuses the entry, the company file may be damaged rather than merely strict. In that case, stop retrying: repeated attempts against a damaged data set can make recovery harder. Our engineers can examine the file, and our Sage 50 database repair service covers exactly this kind of refusal with no logical cause.
Before anything else, write down the exact dates you entered and your fiscal year end date. If those check out and the message persists, send us the file for a free evaluation. We will tell you what is actually wrong and what a fix involves, with a free quote; the answer depends entirely on the file.