Unlike in Accounts Payable and Accounts Receivable, the General Ledger allows you to create a new Batch even if the session date does not exist in the Fiscal Calendar with the posting date defaulting to the current fiscal period. It does not even gives you a warning that the batch will be created with a date outside the fiscal calendar. Transactions therefore are posted in the wrong fiscal period and you don't often discover the error until later.

Comments

  • No they're not. You can't post to non-existent period, you get an error batch. You're completely mistaken about this.

  • He is right. i have that type of issue where transaction were posted to wrong fiscal period and date that does not exist in the database