Hi GP users!

It's time to start thinking about Year-End again!  The Microsoft Dynamics GP Support Team will be publishing blog articles again with year-end closing information to assist you with planning for a smooth year-end close.  These articles include general questions about year-end processes for that module, and any changes that may affect your Year-End processes for 2015.  It is recommended to install the 2015 Year-End Update.  Below is the schedule of upcoming blog posts that I hope will be useful to you:

October 27, 2015 - Microsoft Dynamics GP 2010 - Lifecycle and Upgrade Services

October 29, 2015 - Install and Upgrade

November 03, 2015 - Forms and Reports Upgrade

November 05, 2015 - Table and Column Changes in Year-End

November 10, 2015 - General Ledger

November 12, 2015 - Analytical Accounting

November 17, 2015 - Fixed Assets

November 19, 2015 - Payables Management

November 24, 2015 - U.S. Payroll

November 25, 2015 - Affordable Care Act (ACA)

December 01, 2015 - Receivables Management

December 03, 2015 - Inventory

December 08, 2015 - Canadian Payroll (ROE changes)

December 15, 2015 - W2 Self Service for U.S. Payroll (in GP 2015 R2)

Note:  The blog article will be directly linked to the above schedule as the articles are published. Dates may be subject to change.

How can I be notified when the above blog posts are published?

Click HERE to get yourCONNECTon!  You can utilize the CONNECT section on the Home Page in Microsoft Dynamics GP to get all the latest feeds and information as it is published.

When is the 2015 Year-End update expected to release?

The 2015 U.S. Payroll Year-End Update is currently targeted to release in mid/late November 2015.  

The 2015 Canadian Payroll Year-End Update is targeted for early/mid December 2015.

Where can I download the 2015 Year-End Update from?

You can bookmark and watch the pages below for the 2015 Year End Update to be released: 

U.S. Payroll:

Click HERE for U.S. Payroll Year End Update for Microsoft Dynamics GP 2015
Click HERE for U.S. Payroll Year End Update for Microsoft Dynamics GP 2013

Canadian Payroll:

Click HERE for the Canadian Payroll Year End Update for Microsoft Dynamics GP 2015
Click HERE for the Canadian Payroll Year End Update forMicrosoft Dynamics GP 2013

Note:  The Year-End Update will be an all-inclusive update and includes all prior service packs, hot fixes, etc.

Note:  There will not be a 2015 Year-End Update available for Microsoft Dynamics GP 2010.  Visit the Microsoft Support LifeCycle page for more information.

Where can I get a PowerPoint deck for the year-end information?

• Check out the new PowerPoint presentation for 'What's New in Year-End 2015'.  View updated slides for all the changes included in the 2015 year-end update.  (COMING SOON)
• Here is a link to the 'standard' Year-End Close Procedures that generally do not change from year to year. 

What are some of the cool new features that I should be aware of for Year-End this year?

• In Microsoft Dynamics GP 2015 R2 (14.00.0725), the Self-Service user can now view and print their own W2.  Click HERE to read more about this new feature in US Payroll.
• Click HERE to find out how to create a SmartList Designer report of your ACA information. 

Where can I find documentation and other resources for Microsoft Dynamics GP in general?

• Have you heard about the NEW Microsoft Dynamics GP Directory?  The Microsoft Dynamics GP Directory is a one-stop shop for what you are looking for around Microsoft Dynamics GP.  It provides a consolidated view of relevant documentation, videos, solutions to known issues, new features, blog links, installation guides, Hot Topics, community sites, and much, much more....  Be sure to check it out!

• For any general questions, you can also utilize the Microsoft Dynamics GP Partner Community Forum to ask your peers for tips.

I hope the information above will help you to have a smooth and successful year end!

Thank you!

Cheryl Waswick | Sr. Technical Support Engineer | Microsoft Dynamics GP Applications Support

There’s this awesome feature that can improve the performance of Microsoft Dynamics GP Web Client that I wanted to talk about.  Most of you probably already know about this and are using it, that’s great!  It has come to my attention though, that there are people using Web Client that may not be aware that this feature has to be manually enabled.  This blog is for you…

By default, Web Client will cache the forms at the user session level.  This means that you sign into Web Client and a session is created for you.  The first time that you open a form\window it is retrieved from the dictionary and then converted into a format that can be used by the Web Client.  It caches this form for you so that each subsequent time that you open it, it should be faster.

The Web Client Resource Cache allows caching at the machine level.  This means that the first time a user accesses a form in the web client, the form will be cached on the session host machine.  Every other user running a session on that machine will access the cached form from that point forward.

You can easily install this feature from the GP Setup.exe installation menu.  You will see this on the list of installation objects as ‘GP Web Resource Cache’.  You only need to install this on your Session Host servers.

There is a config file that allows you to specify the Interval that the cache is cleaned up and the max age of each form since it was last updated (this is optional).  All of this is covered in the WebClientInstallAdmin.pdf starting on page 101 (Chapter 17).  Go check it out if you want some more detailed information.

WebClientInstallAdmin.pdf

The purpose of this blog is to explain the functionality of an ‘Employee to Direct Manager’ Workflow in Microsoft Dynamics GP.  This has been a hot topic since it came into existence in GP 2013 R2 and GP 2015 so I wanted to help provide some clarity to help others wrap their heads around this new functionality. 

*You must be on version 14.00.0817 to use this functionality as there was a known issue on previous versions.

1. (Administration >> Setup >> Company >> Workflow >>Workflow Maintenance- Click the Lookup for ‘Assign To:’ under your workflow step)

a. Selection Type: Hierarchy

b. Start From: Employee

c. Assign To: Direct Manager

2. This functionality is only available for Payroll and Project Accounting Workflows.

3. It is dependent on the GP user also having a Windows Account assigned to them in User Setup. (Administration >> Setup >> System >> User – Click the ‘Active Directory Tab’)

Note: If the Windows Account is left blank, then transactions submitted by this GP user will go straight to the Workflow Manager that is assigned in Workflow Maintenance instead of the employee’s Direct Manager.

4. When a transaction is saved for an employee (or on behalf of an employee) they system will first look to the UPR00100 to find which GP user ID is assigned to that specific Employee ID.  This can also be found on the ‘Additional Information’ button that is on the Employee Card. (Cards >> Payroll >> Employee – Click Additional Information).

5. The GP user from Step 4 will be used to find the Windows User from step 3.  This will be checked against Active Directory and the manager listed in the ‘Organization’ tab for this user will be assigned to approve the Transaction that was submitted.

Note: If there is no manager listed, the approval will go to the Workflow Manager.

If for some reason the process of reaching out to Active Directory is interrupted or cannot be made, GP will assign the approval to the Workflow Manager. This is a fail-safe so that the transaction does not get stuck out there without any approvers.

Thanks for taking the time to read through this.  I hope you find this information helpful!

Isaac Olson
Sr Support Engineer
Microsoft Dynamics GP

The Microsoft Dynamics GP Support team is trying something new and we think you will like it!  Each month we will be publishing on demand videos of some of our favorite topics.  These webinars maybe around new features, walkthroughs of how to do something or our highest call volume support topics.  These will be short 30-40 min sessions that you can easily run through to get up to speed on what you need to know.  All of these sessions will be brought to you by the experts!

If you have questions on that specific topic we will have the comment section open to answer your questions.  Typically, the comment section will be available for a couple weeks after the video posts.

Here is the current list of videos we will be publishing:

If you have a topic you would like to see just post a comment below and this will be considered for a future release of Microsoft Dynamics GP On Demand Learning.

Enjoy,

Andy Sather

Sr Support Engineer

Microsoft

In this session we will cover the Setup and Overview of Human Resources and Payroll Workflow in GP 2015.  This feature allows employees to enter Payroll documents, Submit changes for Employee Profile/Skills/W4, and allow these documents to be submitted through workflow for approval. We will also cover the different options available in Workflow.

 (Please visit the site to view this video)

More information:

Employee to Direct Manager Workflow Process How it Works

Human Resource & Payroll Timecard Entry NEW to GP 2013 R2 

If you have any questions regarding the topics of this video feel free to post below.  We will be able to answer any questions regarding the video 2 weeks after the video has been published.  More videos from the Microsoft Dynamics GP On Demand Learning Series can be found HERE

Enjoy,

Andy Sather

Sr Support Engineer

Microsoft

Hello!

Every once in a while we receive Lifecycle questions in regards to different versions of Microsoft Dynamics GP.  This should help to answer some of those questions.

You will see engineers make reference to Mainstream Support and Extended Support.  Here is a chart that outlines the differences between Mainstream Support and Extended Support.

Microsoft Dynamics GP 10.0:
Microsoft Dynamics GP 10.0 is already in its' extended support lifecycle, which will end on 10/10/2017.


Microsoft Dynamics GP 2010:
Mainstream Support for Microsoft Dynamics GP 2010 ended on 10/13/2015 which means that you will no longer receive tax and year end updates.  Microsoft Dynamics GP 2010 is now in its' extended support lifecycle.  This will be ending on 10/13/2020.  
  

Microsoft Dynamics GP 2013:
Mainstream Support for Microsoft Dynamics GP 2013 will end on 4/10/2018 which means that at that point in time, you will no longer receive tax and year end updates.  Microsoft Dynamics GP 2013 will then move into Extended Support until 4/11/2023.

 
Microsoft Dynamics GP 2015:
Mainstream Support for Microsoft Dynamics GP 2015 and Microsoft Dynamics GP 2015 R2 will end on 4/14/2020 which means that at that point in time, you will no longer receive tax and year end updates.  Microsoft Dynamics GP 2015 will then move into Extended Support until 4/8/2025.

Extended support for Microsoft Dynamics GP is included in the customers and partners standard support plans.  Here is a link that provided more information as well on the Microsoft Dynamics GP Product Lifecycle:
http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=Dynamics+Gp&Filter=FilterNO 
 
With the information provided above, if you are currently on Microsoft Dynamics GP 2010 or earlier, you will want to have a plan in place in regards to upgrading to Microsoft Dynamics GP 2013 or Microsoft Dynamics GP 2015. Upgrade services through Advanced Product Support Services are available for upgrades to a supported version of Microsoft Dynamics GP according to the Microsoft Product Lifecycle Policy. For example, upgrade from Microsoft Dynamics GP 2010 to Microsoft Dynamics GP 2015. Customers: If you have any questions regarding upgrade services, please reach out to your Partner to get the ball rolling for a service request. Partners:  You can contact the NA Partner Assist Team at napa@microsoft.com to submit an upgrade service request.

Be sure to check back to the 2015 Year-End Blog Schedule page to review upcoming blog posts related to Year-End Closing for Dynamics GP and other helpful resource links.

 
Thank you!
Sarah Purdy | SR Technical Advisor | Microsoft Dynamics GP

Hello,

The year-end update is a key component to the year-end process. It is very important to ensure the year-end install and upgrade goes as smooth as possible.  Review the install and upgrade tips below to ensure your year-end update installation is successful!

Install and Upgrade Overview

1. The 2015 year-end release will be available for Microsoft Dynamics GP 2013 and Microsoft Dynamics GP 2015. 

The 2015 U.S. Payroll Year-End Update is currently targeted to release in mid/late November 2015.  

The 2015 Canadian Payroll Year-End Update is targeted for early/mid December 2015.

 2. Both the Microsoft Dynamics GP 2013 and Microsoft Dynamics GP 2015 releases are MSP files.

3. All MSP files are cumulative. All prior service packs, hotfixes, compliance, and year-end updates are included in the most recent release. For example, R2 is included in the most recent update for Microsoft Dynamics GP 2015.

4. The update must be installed at all servers and workstations that have a Microsoft Dynamics GP installation otherwise a version error will occur when launching Microsoft Dynamics GP.

Pre-Install and Upgrade Tips

1. Backup the DYNAMICS database and all company databases prior to installing the year-end update.

2. Export all modified reports and forms to package files.   (Microsoft Dynamics GP | Tools | Customize | Customization Maintenance).

3. Make a backup copy of the modified reports and forms .DIC files.  Refer to the Dynamics.set file for the path to the modified .DIC files.

4. Ensure that you have a working backup of any eConnect PRE and POST Procedures if they are customized.

5. Configure a test environment to test the upgrade prior to installing in the live environment. 
**It is highly recommended to test the year-end update first in a test environment.**

 Install and Upgrade Tips 
  
1. The user running the MSP update must have local admin rights on the workstation or server operating system.

2. When installing the update at the first machine, there are two components to the installation:
a. Upgrade the application install
b. Upgrade DYNAMICS and all company databases and all modified reports and forms in Microsoft Dynamics GP Utilities

3. Typically, the update is installed at the SQL Server first to upgrade the databases in Microsoft Dynamics GP Utilities. If a Microsoft Dynamics GP installation does not exist at the SQL Server, the databases can be updated from the first client workstation or Terminal Server.

4. Verify the Microsoft Dynamics GP installation used to upgrade the databases includes all additional product installations.  For example, if Project Accounting is used, verify that Project Accounting is installed at the machine where running Microsoft Dynamics GP Utilities for the database upgrade.

5. If the installation of the MSP fails, refer to the Windows Installer Log or Windows Event Viewer for more information. Refer to KB 2545723 for steps to create a Windows Installer Log.

KB 2545723 - How to Capture a Windows Installer Log
http://support.microsoft.com/kb/2545723

6. Open the Windows Installer Log in a text editor and search for “Return Value 3” to find the failure location in the log.

7. If the installation of the MSP fails, try installing via the command line. Refer to KB 912997 #13 for steps.

KB 912997 - Frequently Asked Questions about the Windows Install MSP files for Microsoft Dynamics GP
http://support.microsoft.com/kb/912997

8. Enable a Dexsql.log prior to upgrading the databases in Utilities. If an error occurs during the database upgrade, the Dexsql.log can be used to troubleshoot the issue.  Refer to KB 850996 for steps.

KB 850996 - How to Enable a Dexsql.log
http://support.microsoft.com/kb/850996

9. If the database upgrade fails, do not restore the databases as all troubleshooting can take place at the point of failure.

10. If a red X appears next to the company name in the Update Company window, the table conversion failed. Refer to the Support Information Section of the Upgrade Hot Topic for troubleshooting steps:

Upgrading to Microsoft Dynamics GP 2015
https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGP2015Upgrade 

 
Upgrading to Microsoft Dynamics GP 2013
https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGP2013Upgrade 
  

11. All modified reports and form dictionaries must be upgraded using the Update Modified Forms and Reports process at the Additional Tasks window in Microsoft Dynamics GP Utilities.

12. If all modified reports and form dictionaries are shared, only upgrade the dictionaries once.

13. The MSP file can be pushed out to client workstations using Automatic Client Update, Group Policy or other mass deployment tools.

Post-Install and Upgrade Tips


1. Backup the DYNAMICS database and all company databases following the upgrade.

2. Export all modified reports and forms to package files following the upgrade. (Microsoft Dynamics GP | Tools | Customize | Customization Maintenance).

Assistance for the Year-End Install and Upgrade 


1. Microsoft Dynamics GP Support and Services Blog
https://community.dynamics.com/product/gp/gptechnical/b/dynamicsgp/default.aspx

2. Microsoft Dynamics Community
https://community.dynamics.com/GP/default.aspx


3. Microsoft Dynamics Support
https://mbs.microsoft.com/support/newstart.aspx

If you are creating a case with the Technical Support Team, please refer to the routing below to ensure you are routed to the correct Professional for assistance.

1. Assistance with the install of the MSP
a. Support Topic Selection: System and Security Setup, Installation, Upgrade and Migrations
b. Sub-topic Selection: System Installation

2. Assistance with the database or report/form upgrade in Microsoft Dynamics GP Utilities
a. Support Topic Selection: System and Security Setup, Installation, Upgrade and Migrations
b. Sub-topic Selection: System Upgrade

3. Assistance with installing the tax table update in Microsoft Dynamics GP
a. Support Topic Selection: Payroll
b. Sub-topic Selection: Payroll Tax Update

4. Assistance with Payroll-specific issues related to the Year-End release and procedures
a. Support Topic Selection: Payroll
b. Sub-topic Selection: Year-End Procedures

KnowledgeBase Articles and Resources 
 
1. 2015 U.S. Payroll Year-End Update for Microsoft Dynamics GP 2015 Download Page
https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/usgpye2015

2. 2015 U.S. Payroll Year-End Update for Microsoft Dynamics GP 2013 Download Page
https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/usgpye2013

 
3. Microsoft Dynamics GP 2015 Upgrade Hot Topic 
https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGP2015Upgrade
  
4. Microsoft Dynamics GP 2013 Upgrade Hot Topic 
https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGP2013Upgrade 
  

5. KB 2545723 - How to Capture a Windows Installer Log
http://support.microsoft.com/kb/2545723

 6. KB 912997 - Frequently Asked Questions about the Windows Install MSP files for Microsoft Dynamics GP
http://support.microsoft.com/kb/912997

 7. KB 850996 - How to Enable a Dexsql.log
http://support.microsoft.com/kb/850996

Be sure to check back to the 2015 Year-End Blog Schedule page to review upcoming blog posts related to Year-End Closing for Dynamics GP and other helpful resource links.

 
Thank you!
Sarah Purdy | SR Technical Advisor | Microsoft Dynamics GP

Hello!

After applying the 2015 year-end release and upgrading your DYNAMICS and Company Databases, you need to remember that if you have any modified forms or reports.dic files, those need to be upgraded as well.  Here are the steps that you need to take to upgrade your modified forms and reports.dic files.

1.Make a backup of each reports dictionary or forms dictionary prior to the upgrade. The name of the reports dictionary for Microsoft Dynamics GP is Reports.dic and the name of the forms dictionary for Microsoft Dynamics GP is Forms.dic.   We recommend making a copy of the .DIC files as well as exporting the modified reports and forms to a package file under Microsoft Dynamics GP | Tools | Customize | Customization Maintenance.

2. Open the Microsoft Dynamics GP 2013 or 2015 (depending on what version of Microsoft Dynamics GP you are currently on) launch file (Dynamics.set) and verify that the paths to the modified reports and forms are correct. The paths must be the location of the reports dictionary and forms dictionary from the previous release.  For example, if your modified dictionaries are located out on a network share, the paths would look like the following:

:C:Program Files(x86)/Microsoft Dynamics/GP2015/Dynamics.dic
//server/dictionary_share/FORMS.DIC
//server/dictionary_share/REPORTS.DIC

3. Launch Microsoft Dynamics GP 2013 or 2015  (depending on what version of Microsoft Dynamics GP you are currently on) Utilities and click Next to get to the Additional Tasks window.  In the Additional Tasks window, select Update modified forms and reports and click Process. The Locate Launch File window appears.

4. Select the Microsoft Dynamics GP 2013 or 2015  (depending on what version of Microsoft Dynamics GP you are currently on) launch file (Dynamics.set) that you use to start Microsoft Dynamics GP on this client, then click Next. The Update Modified Forms and Reports window appears.

5. Select Microsoft Dynamics GP and any additional components whose modified forms and reports dictionaries you’re upgrading.

6. For each component, choose the Details button, if necessary, to open the Product Details window, where you can select the location of the original dictionary from the previous release, such as Dynamics.dic or HR.dic. For example, if you are upgrading from Microsoft Dynamics GP 2013, you would browse to the Dynamics.dic in the Microsoft Dynamics GP 2013 client folder for the Microsoft Dynamics GP dictionary upgrade.  If you are upgrading the Human Resources modified dictionaries, you would browse to the HR.dic from the previous release.  If you are upgrading the build of Microsoft Dynamics GP and not the version, you would browse to the Dynamics.dic in the code folder that you just applied the Year End Update to.  Click OK in the Product Details window.

7. In the Update Modified Forms and Reports window, click Update.

Your modified forms and reports dictionaries are upgraded, and a report named Update20XX.txt is generated, which contains information about upgraded modified forms. Be sure to review the report, located in the \Data folder, to verify that your modified forms have been upgraded correctly.

8. Click Next. The Additional Tasks window reappears.

At this point in time, you should know if your modified reports and forms upgraded successfully or not but to be sure you can review the Update20XX.txt and Update20XX.log, for more information about the modified forms and reports upgrade. I hope that this helps to answer your questions in regards to the steps required to upgrade your modified reports and forms dictionaries!

Be sure to check back to the 2015 Year-End Blog Schedule page to review current and upcoming blog posts and other helpful resource links related to Year-End Closing for Dynamics GP.

Thank you!
Sarah Purdy | SR Technical Advisor | Microsoft Dynamics GP

Hi Everyone! 

Please read through this article for the Year-End Close (YEC) procedures for General Ledger and use this as your checklist.

Does the Year-End Update include any changes for the General Ledger Year-End Closing process?

No, there are no changes in the 2015 Year End Update for the General Ledger year-end closing process.  

Is there any new functionality in Microsoft Dynamics GP 2013 or Microsoft Dynamics GP 2015 for the GL YEC process?

Nothing has changed for when you close a year in General Ledger.

Just a reminder that 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!  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.  However, some users have been using it to un-do a failed year-end, but we can't guarantee it will work for every scenario.  Therefore, 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, we still recommend to restore to your backup immediately if your GL Year-End close process fails.
• 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?)  

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 the suggested order to close the modules.)

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 888003 - Year 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. 

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 screenprint 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 we see have to do with the Account Posting Types (ie. 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 case we see in Support 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 users know to just LET IT RUN to completion no matter how long it may take.

• We have also see users click 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.

• We do stress that Backups be made (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.)

• One additional GL YEC item I would like to point out is an issue we have been seeing 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 toregenerate 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

• 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.

Resources:
A few additional KB articles that point out other common issues for the YEC process in GL are:

• 864913 – Changing the posting type on an account after you close the year in General Ledger in Microsoft Dynamics GP
http://support.microsoft.com/kb/864913

• 871679 - How to set up an adjusting period in General Ledger in Microsoft Dynamics GP
http://support.microsoft.com/kb/871679

• 850615 - How to use divisional retained earnings accounts in General Ledger in Microsoft Dynamics GP
http://support.microsoft.com/kb/850615

• 850741 - Error message when you try to perform the year-end closing process in General Ledger in Microsoft Dynamics GP: "Retained Earnings account not found”
http://support.microsoft.com/kb/850741

• 857582 How to clear beginning balances for unit accounts in General Ledger in Microsoft Dynamics GP
http://support.microsoft.com/kb/857582

• 856550 – Error message when you try to post a transaction in General Ledger in Microsoft Dynamics GP after the year is closed: “Year End Close is still in process and batches cannot be posted”
http://support.microsoft.com/kb/856550

• 2452542  - Inactive GL Accounts deleted during Year-End Close process for General Ledger in Microsoft Dynamics GP
http://support.microsoft.com/kb/2452542

Year-End Close Resources:

 • To check out the Year-End Close blog schedule and other YEC information, please click HERE.

 • Here is a link to the 'standard' Year-End Close Procedures that generally do not change from year to year.

Be sure to check back to the 2015 Year-End Blog Schedule page to review current and upcoming blog posts and other helpful resource links related to Year-End Closing for Dynamics GP.

We hope that you found this information helpful and that you have a successful Year-End!!  If there is any feedback or suggestions on this YEC blog series, please let us know.  Have a great year-end!

Thank you!
Cheryl Waswick | Microsoft Dynamics GP | Financials Support

Year-End is fast approaching and you will want to be sure to give yourself plenty of time to review the Analytical Accounting (AA) data before you run the Year-End close process for General ledger.  This will be an important step if your financial reports pull any data from AA tables.  Please review the information below to help the year-end process for AA be smooth:

Does the Year-End Update include any changes for Analytical Accounting?

There are no changes in the 2015 Year-End Update specifically for Analytical Accounting. 

Is there a separate Year-End close process to run for Analytical Accounting?

The Year-End close process for Analytical Accounting is automatically integrated with the Year-End close process for General Ledger.  So no, there are no 'separate' steps that you need to run in Analytical Accounting to close it.

What should I be aware of for AA with Year-end procedures?

If your Financial reports need to pull data from AA tables, (such as Management Reporter Data Mart),  be sure to give yourself plenty of time to go through all the information in this article before you close the GL year.

What is the impact if the AA data does not match GL data?

If the AA data does not match GL data, and financial reports are pulled from AA tables, this could skew your Financial reports (if your AA tables are not consistent with GL) and you won't balance to the GL Trial Balance reports.   Missing or duplicated data in the AA tables would skew the beginning balance entries created in the AA tables.  So the first step is to determine if your Financial reports use the AA tables or not.   If you use AA tables or Management Reporter, it is recommended to run through KB 2910626 to help look for mismatched data between AA and GL that should be corrected before closing the GL year.  

Why wouldn't the data match between AA and GL tables?

There could be many reasons why your AA data doesn't match the GL data.  ALL transactions from other modules also update the AA tables, whether or not the GL accounts are linked to AA or whether or not you put AA codes on the transactions.  All transactions need to be present in the AA tables if you are doing your financial reporting from AA tables.   Discrepancies can occur if there are any posting interruptions, data is being imported, AA is not installed on all machines, GL was closed on a machine in the past where AA was not installed, users are disabling AA if any posting interruptions with AA messages, multi-currency issues, and many more reasons.  Therefore, you should be continually using the scripts in KB 2910626 to monitor if there are any ongoing issues in your environment to ensure the data between AA and GL stays in synch if you are doing any financial reporting from AA tables.

When should the Year End Close for Analytical Accounting be done?

Since there is no separate process to close AA, we recommend that you run through the following KB articles before closing the GL year:

• Run through the steps in KB 960356 - The Year End Close procedures for Analytical Accounting in Microsoft Dynamics GP. 

• If you are using Management Reporter (MR) for your reporting, you should also run through KB 2910626 -Financial Reports from Management Reporter do not match the General Ledger Trial Balance Reports in Microsoft Dynamics GP.     

Note:  If you have any of the scripts saved locally in the past from these KB articles, be sure to re-download the scripts again so you have the most up to date versions of these scripts.  

What does the GL year end close process do and/or affect in Analytical Accounting?

The GL Year End close process will affect the following in the AA tables:

• Moves AA data from open tables (AAG30000-AAG30003) to the history tables (AAG40000-AAG40003)
• Creates Balance Brought Forward (BBF) entries in the AAG30000 series tables
• Consolidates balances and ties AA codes to the BBF entries for the AA dimensions that were marked to be included in the year-end close

What steps should I take to have AA included in the GL Year-end close and BBF entries created in AA?

In order to have AA codes tied to your beginning balances created by the GL year-end close, you must first verify that the following options are selected:

1. In the Analytical Accounting Options window (Click Tools under Microsoft Dynamics GP |Setup | Company | Analytical Accounting | Options), mark the checkbox for ‘Include dimensions in the year end close’ and click OK.

2. In the Transaction Dimension Maintenance window (Click Cards | Financial | Analytical Accounting | Transaction Dimension), select the AA dimension code you want a balance carried forward for, and mark the checkbox for ‘Consolidate balances during Year End close’ and click Save.  Do this for each Transaction Dimension you wish to have linked to the beginning balance entries create by the GL year end close process.

Do I need to run the 'Move to History' utility every year for Analytical Accounting?

If this is the first time you are closing GL on a version of GP 10.0 SP2 or higher (with AA activated), you will be prompted to move AA data to history before the system will allow you to close the GL year.  The system will verify that the AA data is in the corresponding open/historical series of AA tables, as the GL data sits in the open/historical tables in GL.  If you run into this, you will receive a message stating You must consolidate transactions and transfer detail to history utility to close the year" during the GL Year End close, and then you can refer to the steps in KB 960356 on how to resolve this.  You should not need to run the Move to History Utility for AA more than the initial first time.  The Move to History utility was meant to be a one-time process to get the customer 'caught up' with getting historical AA tables populated, and then data should automatically close along with the GL year-end close process going forward.  

Is there any new functionality in Microsoft Dynamics GP 2013 or Microsoft Dynamics GP 2015 for the AA YEC process?

There are no new features for AA in these versions.  However, the GL Year-End Closing window now includes a Reverse Historical Year button to reopen a GL year yourself.  If the beginning balances are incorrect in AA, or you find data discrepancies with data from your historical years with the scripts in KB 2910626, you can use this new feature in GL to reopen the year, fix the AA data, and then reclose the year again to have the BBF entries recalculated correctly in the AA tables.

Key points to remember:

•Follow the steps in KB 960356 titled “The Year-End close procedures for Analytical Accounting in Microsoft Dynamics GP”.  This KB includes steps and SQL scripts to make sure the AA data matches GL data.  It also has steps to verify that the AA dimensions that you wish to be consolidated during the year-end close process are properly marked to create BBF entries, and steps on how to move data to history.  You should determine if your reporting tool uses AA tables or not.  Data Mart with Management Reporter now reads from AA tables, so it is more important than ever to make sure your AA data matches GL data.

•New to Microsoft Dynamics GP 2015, the user can determine the data that is available to the Microsoft Dynamics Management Reporter Data Mart to help improve the performance and give the user control over the data selected.  Note that the latest release of Data Mart (CU10) does have the option to report with or without AA data. 

•Make sure the GL year-end close is performed at a workstation that has AA installed and activated, and that users know not to disable AA if they receive any messages.  Restore to the backup immediately, and make a screenprint of the AA error message if assistance is needed with the GL year-end close process.    

Where can I ask questions or get more assistance for Analytical Accounting Year End Close?

• Microsoft Dynamics GP Blog - https://community.dynamics.com/product/gp/gptechnical/b/dynamicsgp/default.aspx

• Microsoft Dynamics Community - https://community.dynamics.com/default.aspx

• Microsoft Dynamics Support - https://mbs.microsoft.com/support/newstart.aspx

Assistance with year-end close issues directly related to Analytical Accounting should be logged under the categories below to ensure you reach the correct Support team:  (Please include a detailed description of the issue and a screenprint of any error messages received.)

   --Support Topic Selection:   Financial – Analytical Accounting

   ---Sub-topic Selection:         Other

Resources:

• The year-end close procedures for Analytical Accounting in Microsoft Dynamics GP can be found in KB 960356.

• The scripts to use to verify that your AA data matches GL data before you close the GL year can be found in KB 2910626.

• Here is a link to the 'standard' Year-End Close Procedures (ppt) that generally do not change from year to year.

Be sure to check back to the 2015 Year-End Blog Schedule page to review current and upcoming blog posts and other helpful resource links related to Year-End Closing for Dynamics GP.

I hope this information is helpful to you and gives you enough time to plan.  Ensuring your AA data is consistent with GL prior to closing the year will help ensure correct financial reporting going forward!  Have a great year-end!

Cheryl Waswick | Microsoft Dynamics GP | Sr. Support Engineer

Quick reminder, there is NO year-end update for Microsoft Dynamics GP 2010, if you need the changes in this update, please upgrade to Microsoft Dynamics GP 2013 or Microsoft Dynamics GP 2015.

Click HERE for U.S. Payroll specific documentation and install steps.
Click HEREfor all you ever wanted to or needed to know about ACA (Affordable Care Act)

Below is a list of changes in this update by product version. 

Microsoft Dynamics GP 2015 (version 14.00.0898) (Includes GP 2015 R2 and all prior patches)

MicrosoftDynamicsGP14-KB3102158-ENU.msp

U.S. Payroll
There are many changes in this update for Affordable Care Act, click HERE for a list of detailed ACA changes.

Added to W3 Kind of Payer option (not required for reporting in 2015 year)

Employee Self Service added option to make W-2's available to employees.

Advanced Human Resource
You may see a beneficiary save at 100% with an incorrect sequence number. 

Project Time and Expense
-You may receive the following error “account index errors exist for PTE” when posting accounts are sourced to “None” for Employee Expense and Timesheet transactions.
-Approve Timesheet, Approve Expense Reports, and Status tiles were not available on the Home Page for users other than Poweruser role.
-Blank batches may be created when submitting Timesheets or Employee Expenses thru Project Time and Expense.
-A line may be created with zero quantity when hours do not exist while utilizing Project Time and Expense Timesheet Templates.
-Employee Expense Report Tile on the Home Page is displaying all expenses for all users.
-Payment Method for Employee Expense Entry was defaulting incorrectly.

Payables - click HERE

Encumbrance

Encumbrance options for Requisitions are not available for Limited or Self Service Users types.

Fixed Assets -Luxury Auto Depreciation changes

Web Client
Ability to add domain accounts to Workflow Managers and Workflow Approvers in separate domain/forest.
Employee timecard information viewing of detail may be cut off with web client.

***If you are using Web Client, remember to patch it as well, click HERE.

Microsoft Dynamics GP 2013 (version 12.00.2038)  -  MicrosoftDynamicsGP12-KB3102154-ENU.msp

U.S. Payroll
There are many changes in this update for Affordable Care Act, click HERE for a list of detailed ACA changes.

Added to W3 Kind of Payer option (not required for reporting in 2015 year).

Advanced Human Resource

You may see a beneficiary save at 100% with an incorrect sequence number. 

Payables - click HERE

Fixed Assets -Luxury Auto Depreciation changes

***If you are using Web Client, remember to patch it as well, click HERE.

Download links:

Microsoft Dynamics GP 2015  Customersource                Partnersource

Microsoft Dynamics GP 2013  Customersource                Partnersource

It's that time again!!! The end of the year is fast approaching, and I'd like to provide you with information you'll need ensure that your Payroll Year End goes smoothly.

The 2015 Year-End Update for GP 2013 was released on 11/20/2015 and GP 2015 was released today to ensure you have plenty of time to install prior to year-end. In Support, we are often asked if it is OK to install the 2015 Year End Update even though 2015 payrolls are not completely processed. The answer to that is YES YOU CAN! We release the update early so you have plenty of time to install it.

This update is all inclusive of prior updates for Microsoft Dynamics GP 2013 and GP 2015.

The 2016 Round 1 Tax Update (tax table update only) is targeted to be available the week of December 21, 2015. *Do not install this until ALL pay runs for the 2015 year are completed.

The 2016 Round 2 Tax Update will be available mid-January 2016.

Please review all documentation in detail so you are well prepared for the year-end close, specifically around what has changed for this year. Click HEREto download the U.S. 2015 Year End Update manual.

Please Note: The 2015 Year-End Update and 2016 Tax Updates will not be available for Microsoft Dynamics GP 2010 and prior versions. Click HERE for more information.

When should the Year End Close be done?

The Payroll Year End Close should be processed after all pay runs have been completed in the current year, and before processing any pay runs in the new year.

Are there any changes I should know about related to the Year End Update for Payroll?

 Microsoft Dynamics GP 2013 (version 12.00.2023) and Microsoft Dynamics GP 2015 (14.00.0898):

• There are NO W2 form changes

• Added W3 'Kind of Payer' option in the 'Print W-2 Forms' window - Please note: this is not required for reporting in 2015 year:

• EFW2 change (Electronic Filing)

• The submitter information - Attn/Suite/Room# field is no longer required for electronic filing.
• Users can continue to populate this field if desired, and should not run into a problem submitting electronically if it's included in the file.
• As always, use Accuwage for Electronic File Verification prior to submitting electronically! 

• Affordable Care Act, click HERE for a list of changes

• Product Quality Fixes, click HERE to see what's been fixed

What does the Year End Close process do?

Creates the 'Year End Wage' file with annual wage information used to generate W2s, W3s, 1099's, EFW2's (aka Magnetic Media), 1095-Cs, and 1094-Cs for the year being closed.

What steps should I take to close the year? (See KB Article 850663 for detailed instructions on each step listed below):

**First and foremost make a restorable backup of the company database so you can restore should you run into a problem.**

1.  Complete all pay runs for the current year. 

2.  Complete all month-end, period-end, or quarter-end procedures for the current year. 

3.  Make a backup of the original file.

4.  Install the Year-End Update. 

5.  Create the Year-End file. 

6.  Make a backup of the new file. 

7.  Verify W-2 and 1099-R statement information. 

8.  Print the W-2 statements and the W-3 Transmittal form. 

9. Print the 1099-R forms and the 1096 Transmittal form. 

10. (Optional:) Create the W-2 Electronic file. 

11. (Optional:) Archive inactive employee Human Resources information. 

12. Set up fiscal periods for 2016. 

13. (Optional:) Close fiscal periods for the payroll series for 2015. 

14. Install the payroll tax update for 2016. 

To recap, prior to processing a pay run in 2016 the following is:

Required:

All 2015 pay runs completed.

Year End Wage File created.

Backup of company database made.

Payroll Tax Update for 2016 (2016 Tax Update Round 1) installed.

Optional:

Print W-2s.

Create W-2 Electronic File.

Why may Microsoft Dynamics GP 2010 users want to upgrade?

Microsoft Dynamics GP 2010 DOES NOT contain Affordable Care Act Changes, the 2015 Year End Update, and will not receive Tax Updates (table and/or code) going forward. If you need changes included in the 2015 Year End Update, you'll need to upgrade to Microsoft Dynamics GP 2013 or Microsoft Dynamics GP 2015. Click HERE for more information about upgrading!!

What cool feature should I be aware of in association with US Payroll this year?

With the release of Microsoft Dynamics GP 2015 R2 (14.00.0725), Self-Service users can view and print their own W2s!! Click HERE to read more about this new feature in US Payroll.

With the release of the 2015 Year End Update for GP 2015 (14.00.0898), users can control 'when' employee self-service users are able to access W2 information!! To enable this new feature, the 'Publish to Employee Self Service' field was added to the Print W-2 Forms window (Microsoft Dynamics GP >> Tools >> Routines >> Payroll >> Print W-2s):

Questions about ACA?

Never fear! Click HERE to view Terry's latest and greatest BLOG (link to be inserted as soon as it's available).

Assistance for Payroll Year End Close

Microsoft Dynamics GP Blog - https://community.dynamics.com/product/gp/gptechnical/b/dynamicsgp/default.aspx

Microsoft Dynamics Community - https://community.dynamics.com/default.aspx

Microsoft Dynamics Support - https://mbs.microsoft.com/support/newstart.aspx

If you are creating a case with the Technical Support Team for assistance with Year End close for Payroll, please refer to the category selections below to ensure you are routed to the correct Support team for assistance:

     --Support Topic Selection:    Payroll

          --Sub-topic Selection:      Year End Procedures 

Resources:

Year-end closing procedures for the Payroll module in Microsoft Dynamics GP are found in KB 850663:  http://support.microsoft.com/kb/850663

Click HERE to view standard Year-End Close Procedures that generally do not change from year to year!!!

Be sure to check back to the 2015 Year End Blog Schedule post for current posted blogs and upcoming blog posts related to Year-End Closing for Dynamics GP.

Here are the 2013 Year-End Update pages which will provide you with documentation and installation instructions you’ll need for a successful year-end:

2013 U.S. Payroll Year End Update for Microsoft Dynamics GP 2013 (version 12.00.2023) Download Pages:

Customers click HERE 
Partners click HERE 

2015 U.S. Payroll Year End Update for Microsoft Dynamics GP 2015 (version 14.00.0898) Download Pages:

Customers click HERE
Partners click HERE

Here are the pages on which you can access the latest (and previous) Tax Updates:

Latest U.S. Payroll Tax Update for Microsoft Dynamics GP2013:

Customers click HERE 
Partners click HERE 

Latest U.S. Payroll Tax Update for Microsoft Dynamics GP2015:

Customers click HERE 
Partners click HERE

I hope you find this information helpful!  Here's to a seamless Year End and a Happy New Year!

Andrea Melroe| Microsoft Dynamics GP  | Technical Advisor

Hi Everyone,

We are winding down to the last bit of information to help the Year End Close process go smoothly for you!

Does the Year-End Update include any changes specifically for the Inventory Control Year-end close?

No, there are no changes included for the Inventory Control year-end close process. 

When should the Inventory Control Year-end close be done?

The Inventory module should be closed at the end of your fiscal year, before any new transactions that would affect inventory quantities are posted.

What does the year end close process do and/or affect?

1. Transfers all of your summarized current-year quantities, costs and sales amounts to last-year, for the items which you are maintaining summarized sales history for.

2. Updates each item’s Beginning Quantity, from the Quantity on Hand, at each site.

3. Zeros the Quantity Sold field in the Item Quantities Maintenance (Cards | Inventory | Quantities/Sites) for each site.

4. Gives you the options to:

a. Remove discontinued items
b. Remove sold purchase receipts
c. Remove sole lot attributes
d. Update items standard cost

What steps should you take to close the year?

Enter and post all Purchase Order Processing, Invoicing/Sales Order Processing, and Inventory transactions for the current year and then continue with the steps outlined in KB 872713

titled “Inventory year-end closing procedures in Inventory Control in Microsoft Dynamics GP”

Key points to remember:

1. Make restorable backups when it is recommended in KB 872713

2. If you are using Sales Order Processing and/or Purchase Order Processing, be sure to reconcile each of these modules along with the Inventory module prior to closing.

3. The order in which to reconcile these modules is: SOP, POP and then Inventory.

Assistance for the Inventory Control Year End Close

Microsoft Dynamics GP Blog - https://community.dynamics.com/product/gp/gptechnical/b/dynamicsgp/default.aspx

Microsoft Dynamics Community - https://community.dynamics.com/product/GP/default.aspx

Microsoft Dynamics Support - https://mbs.microsoft.com/support/newstart.aspx

Note:  If you are creating a case with the Technical Support Team for assistance with Inventory Control Year End close, use the following category selections to log the support incident: (Be sure in enter a detailed description of the issue and include screenprints of any error messages or specific issues.)

- Support Topic Selection: Distributions - Inventory

-- Sub-topic Selection: Inventory - Other

Resources:
• To see the Year End Closing Procedures in Inventory Control Management for Microsoft Dynamics GP, click on KB 872713.

• To see Information about the order in which the reconcile procedures should be run in Microsoft Dynamics GP, click on KB 864622.

• For Information about Inventory accidentally closed twice, click on KB 855316.

• For information about The Inventory Year End Close Routine does not remove Discontinued Items in Microsoft Dynamics GP, click on KB 872172.

• Here is a link to the 'standard' Year-End Close Procedures that generally do not change from year to year.

Be sure to check back to the 2015 Year-End Blog Schedule page to review current and upcoming blog posts and other helpful resource links related to Year-End Closing for Dynamics GP.

Good luck and have a great Year-End!

Cheryl Waswick | Sr. Technical Support Engineer | Microsoft Dynamics GP Support