Year-end processing
A finance manager or system administrator should perform year-end processing functions at the end of your company's financial year, whether that is fiscal or calendar. This topic describes the preliminary tasks involved for the Distribution SX.e modules that update General Ledger.
Preliminary tasks
Perform these preliminary tasks to prepare your company for year-end processing:
- Create a plan that outlines the order in which you will run year-end reports and other functions that affect the year-end process. Plan for all batch processes to be run, purchase orders received and costed, sales orders entered and invoiced, and warehouse transfers shipped and received. This ensures that your General Ledger accurately reflects your complete current year figures. It also ensures that your year-to-date balances in Customer Setup, Vendor Setup, and Product Warehouse Product Setup are accurate.
- Run year-end procedures in your test company before affecting your live data to familiarize yourself with the functions.
- Complete month-end procedures before you perform year-end procedures, including running Sales Cash Drawer Balance Report to close any batch journals.
- Ensure that everyone is logged off the system. You can use SA Connection Inquiry to view active user sessions and confirm that no one is connected to CloudSuite Distribution.
- Check for any open Sales Entry Invoice Processing Report journals that might require recovery. This ensures that your accounts balance properly. Use GL Journal Entry to identify open invoice processing journals and run SA Administrator Journal Recovery Report to recover those journals.
- If you have any recurring group batches set up in GL Batch Setup that may be scheduled to run during the time you plan to perform GL Administrator Year End Report, then disable them and handle those postings manually. This ensures that postings for the new year are made after year-end processing is completed.