Our Adagio JobCost program has a feature where you can close particular date ranges (initially loaded from the Ledger, but can be customized to different ranges, even covering more than a single calendar/fiscal year). These ranges/periods are independant of the Fiscal Calendar in regards to open or closed status. Posting in Adagio JobCost can optionally adhere to these periods and refuse to post if any of these JobCost periods are closed.

Perhaps functionality like this might be what you are looking for?

I suppose part of this discussion hinges on when a controller considers the period Closed, what dates an AP clerk can enter transactions for, and whether it's more important to prevent the clerk from posting the batch, or allow them to post and have the controller force the entry into a different period.