Period Closed: Managing Posting Errors
If your fiscal year or period has ended, you may suddenly start receiving errors such as Period Closed or Period Not Found when posting to General Ledger. These errors happen when transactions post to a hard-closed, soft-closed, or an undefined fiscal year. To resolve the error:
1. Review the Batch Validation or Pre-post Report to find the transactions that failed validation. You can find the exceptions in bold under the problem transaction. If you are posting a journal entry batch, the cursor stops in the date field of the transaction causing the error message.
2. If the post date is incorrect, change the post date of the transaction to a valid, open fiscal year. In Accounts Payable, if the Post date field is grayed out on a paid invoice, refer to How to edit the post date on a paid but unposted invoice.
3. If the post date is correct:
a. Verify the fiscal year was created. If it hasn’t been created, add the new fiscal year.
b. If the fiscal year exists and is soft closed, reopen the period.
c. If the fiscal year is hard closed, restore to a backup created before the fiscal year was closed or post to an open fiscal period.
Note: If you restore to a backup, any data entered after the backup was created will be lost.