Microsoft Dynamics GP Year End Release 2015 General Ledger

By Tracey BrinkmanCompany, General Ledger, Microsoft Dynamics GP, With 0 comments

Microsoft Dynamics GP Year End Release 2015 General Ledger

The 2015 Year End Update does not contain any changes for the General Ledger Year-End Closing process.

There were new features added to the GL Year-End Closing routine window in Microsoft Dynamics GP 2013:

If you are on Microsoft Dynamics GP 2013 R2 or higher versions, you will now see the option entitled Reverse Historical Year in the Year-End closing window.

If your GL Year-End close process fails, we still recommend that you restore to your backup first!

Note: Some users have been using the Reverse Historical Year function to un-do a failed year-end. There is no guarantee it will work!

You can try it and verify, but you will be on your own if you do it this way.  Be sure to do it in a Test company first and verify.  However, it is  still recommend to restore to your backup immediately if your GL Year-End close process fails.

This new functionality was designed to reverse out a GL year that was successfully closed, not a failed year in which data may be damaged.

GL_Year End Closing

The Year-End Closing window has a new checkbox for Maintain Inactive Accounts.  If this is unmarked, then any inactive GL accounts without any activity or a balance will be removed during the YEC process (See KB 2452542 for criteria).  If you mark this checkbox, then you have the option to keep All Inactive Accounts, or just those With Budget Amounts.

  • A progress bar was added to the Year-End Closing window signifying 7 steps in the process.  Hopefully having a progress bar will allow the user to see that it is still running, so they can just let it run to completion.
  • Also now in the Unit Account Maintenance window, there is a new checkbox to Clear Balance During Year-End Close, so you can have the unit account balances automatically cleared for you instead of doing it manually.  (KB 857582 will still work as well, but why do it manually when you can have this process automatically done for you?)
Clear Balance During Year-End Close

Clear Balance During Year-End Close

When should the Year End Close for General Ledger be done?

The Year-End Close (YEC) process for General Ledger should be done after you have completed the Year End close process for all other modules.  (See KB 888003 for additional information regarding the suggested order to close the modules.)

Complete the year-end closing procedures for each module in the following order:

      1. Inventory
      2. Receivables Management
      3. Payables Management
      4. Fixed Asset Management
      5. Analytical Accounting

 

What does the Year End Close Process do and / or affect?

The GL Year-End Close process closes all Profit and Loss accounts to the Retained Earnings account.  All Balance Sheet account balances are rolled forward to the New Year by having Balance Brought Forward (BBF) entries created.  All GL open records (GL20000) are moved to the historical table (GL30000).   Inactive GL accounts without a balance and no historical transactions are removed.  The Year that was just closed is marked as historical.   If installed and activated, the Analytical Accounting (AA) module is also automatically closed along with GL.

What steps should I take to close the year?

Print and follow the checklist available for the Year-End close process for General Ledger in KB 888003Year End closing procedures for General Ledger in Microsoft Dynamics GP.   This article provides great information for all aspects of the Year End Close process, links to sub-module KB articles, the suggested order to close the sub-modules, as well as a valuable Frequently Asked Question section at the end of the article which addresses many common customer concerns with YEC.

  1. Complete the posting procedures and the closing procedures for other modules.
    Note: This step is only required if General Ledger is integrated with other modules.
  2. Post the final adjusting entries in General Ledger.
  3. Print an account list to verify the posting type of each account.
  4. Close the last period of the fiscal year.
    Note: This step is optional.
  5. Optional: Perform file maintenance on the Financial series group of modules.
  6. Verify the settings in the General Ledger Setup window.
  7. Make a backup.
  8. Print a final Detailed Trial Balance report.
  9. Print the year-end financial statements.
  10. Set up a new fiscal year.
  11. Close the fiscal year.
  12. Close all the fiscal periods for all the series.
    Note: This step is optional.
  13. Adjust the budget figures for the new year, and then print the financial statements.
  14. Make a backup.

 

Key points to remember:

  • ALWAYS have a current backup before you close the year!  If you receive any errors during the year-end close process, make a screen print of the error message, and restore to your backup immediately.
  • Have all users out of Dynamics GP when you perform the YEC process.
  • Perform the YEC process at the server.
  • Make sure there is enough room for the files to double in size at one point during the YEC process.
  • Follow the checklist and suggested order to close the modules as listed in KB 888003.  Review the FAQ section at the end of this document for common issues.
  • By far the greatest numbers of support cases have to do with the Account Posting Types (i.e. Balance Sheet or Profit & Loss) not being set correctly before the YEC takes place. It may be time-consuming task to review all GL account types beforehand, but this is essential to avoid an unwanted balance getting closed or carried forward or an incorrect Retained Earnings amount getting generated because of the incorrect account type.
  • It is always recommended to perform a test run of the GL close in a TEST Company first to determine if there will be any unexpected errors or warning messages during the close (such as running out of processing space or getting a message to Move Data to History in the Analytical Accounting module, etc.). It also lets the user gauge how long the actual close will take. The resulting YEC report can then be reviewed for accuracy and account balances can be verified by the accounting team.  If the close is not correct in the TEST company, the user can then adjust the Account Posting Type settings in the LIVE company and help avoid post-close account adjustments (or SQL corrections) that may raise inquiry in future audit-type activity.
  • The second most common support case is the user not letting the YEC process run to completion.  GP 2013 users now have the progress bar, so be sure that completes all 7 steps.  For GP 2010 and prior versions, the system might appear to hang or stop processing and the user may be unsure if the process is still running.  The majority of the YEC activity is being performed at the SQL server, where the table data is getting created, cleared and moved at a rapid rate.  The last step is to print the YEC report so is the best indicator that the process has completed.  So make sure to just LET IT RUN to completion no matter how long it may take.
  • Another common issue is when if the user clicks the ‘Close Year’ button twice on the YEC window and two years get closed by mistake.  Although the user is likely to get prompted by a default warning (open batches exist or the next fiscal year has not been created) that will allow them to stop the close, we do see several incidents where the second closing is accidentally started in error and then stopped by the user. This often leaves invalid data in the tables as well as incorrect historical year assignments that may need to be corrected with SQL data-fixing activities. In this circumstance it is best to immediately restore to the backup made before the close and restart the closing process again for the correct year and insure the second close-out is avoided.  If there is no backup, a consulting service will be needed to reopen the year.
  • First priority is always to make Backups (and kept in a separate location) for the pre-close and post-close company databases. This recommendation is just in case something does go wrong during the close that may not be immediately recognized by the accounting team afterward.  Having the pre/post close databases will allow the user to recreate the close again in a TEST environment and better determine if there was a processing issue during the close or if there was faulty data present in pre-close environment that has just recently been detected in the LIVE data.
  • Please note that there is not a utility or SQL scripting option available to “re-open” a closed year (prior to GP 2013 R2) through the regular support channels to make a historical year change. Unfortunately, we have been seeing more instances of Bootleg-type of SQL scripting being made available to users to re-open the closed year independently. We need to stress this is not recommended or even supported through our regular support channels.  Microsoft does offer a ‘GL Year-End Undo’ service for to reopen a closed year.  If needed, please make the request through a regular support case or contact the Partner Assist Team at Napa@Microsoft.com .  (Please note that Partner Advisory Hours (PAH) will be decremented to pay for the service.)
  • An issue with GL Year End Close in regards to Multicurrency. If you are not using Multicurrency and NOT closing to divisional accounts, you need to not only insure that Close To Divisional Account Segments is not selected in the General Ledger Setup window (Microsoft Dynamics GP menu | Tools | Setup | Financial | General Ledger), you need to insure the GL Setup Table (GL40000) holds this distinction correctly.  If you mark and unmark it, the SQL table may still hold the incorrect setting for this checkbox, which causes issues with the non-Multicurrency version of the YEC report and the Retained Earnings amount may display incorrectly (even though the actual YEC JE was created correctly). Please note that this issue was fixed in Microsoft Dynamics GP 2013.  However, if you just upgraded, be sure to check this as follows:

In order to avoid such result in this circumstance, you can run the following SQL script against the company database to insure the GL40000 is set correctly before the close:

update GL40000 set DIVACTSG = 0

  • Last, the YEC report does not have a reprint capability.  If the user needs to regenerate this report the best option would be to restore the backup made prior to the close into a TEST environment, repeat the close in the TEST environment to regenerate the report. The report should be identical to the actual YEC report.

Assistance for General Ledger Year End Close

  • Microsoft Dynamics GP Blog – https://community.dynamics.com/gp/b/dynamicsgp/default.aspx
  • Microsoft Dynamics Community – https://community.dynamics.com/default.aspx
  • Microsoft Dynamics Support – https://mbs.microsoft.com/support/newstart.aspx (This will require your CustomerSource login.
  • Reach the proper support team for your questions directly related to General Ledger by using the follow categories when logging the support incident:
  • -Support Topic: General Ledger
  • –Sub-Topic: Year End Closing

Please be sure to enter a detailed description of the issue you have or a screen print of the error received.

Details for this blog are from the Microsoft Dynamics GP Community Blogs:

Title: Microsoft Dynamics GP Year-End Release 2015: General Ledger – by Cheryl Waswick

You can view the original blog at: https://community.dynamics.com/gp/b/dynamicsgp/archive/2015/11/10/2015gpyecgl 

If you are an iSolutions Partners customer and have questions regarding Microsoft Dynamics GP Year End Release 2015 General Ledger, please contact us at: support@iSolutionsPartners.com

You can view our previous blogs at: http://www.isolutionspartners.com/resources/dynamics-gp-blog-for-indiana-and-wisconsin/