A common misunderstanding is that when a transaction is created for the current month where the A/P or A/R module is already locked, no further activity can be posted to that period. However, users often find that transactions dated in the same month can still be posted successfully. On the other hand, if the Accounting Period itself is closed, the transaction will be rolled forward and posted to the next month instead.
It is a common misconception that locking a sub-module immediately prevents all entries for that month. Here is the technical breakdown of how the system handles these scenarios.
1. Closing an A/R and A/P Module vs. Locking the Period
Completing the A/R and A/P period close checklist task does not necessarily stop all activity for that month. It simply means that specific sub-ledger is finished.
The General Ledger often remains "Open" for a few extra days to allow for final adjustments. If the Accounting Period is not officially Locked, the system will allow JEs to post to that month.
2. Automatic "Roll Forward" Logic
If you attempt to run an entry like an amortization schedule and the target month is already Fully Locked, the system follows a safeguard:
- If the Status is Open, the JE posts to the intended or current month.
- If the Status is Locked, the JE will automatically be posted to the next available open month.
The system behaves as expected by protecting your closed books. If an entry posts to the "new" month, it is because the "old" month was already finalized and locked for GL entries at the moment the transaction was created.
We’d love to hear your thoughts – please feel free to share any insights or experiences you have in the comments or post a discussion in the NetSuite Admin Corner and let's continue learning together!