Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
It's that time of year again! 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 ensure a successful year-end process for AA:
Does the 2019 Year-End Update include changes that will affect year-end processing for Analytical Accounting?
There are no changes included in the 2019 Year-End Update that affect year-end processing for Analytical Accounting!!!
IMPORANT TO NOTE THIS YEAR If you are on version 18.2 AND using SQL 2019:The following error will occur when you attempt to close the GL year and AA is installed:
“Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.”
This error is cropping up due to the syntax associated with the glYECCreatePLTranslationOpen stored procedure.
To Avoid the error, download this fixed glYECCreatePLTranslationOpen stored procedure, and run the script against the appropriate company database prior to closing the GL year.
If you have already attempted to close the year and recieved the error above, restore from your backup, download the fixed procedure and run the script against the appropriate company database prior to closing the GL year.
If you are on version 18.2 AND using SQL 2019, you will get the same error when you attempt print an edit list for and/or post to the most recently closed historical year. For more information on this along with how to avoid the error, see the Year-End Update blog for Analytical Accounting:
Microsoft Dynamics GP Year-End Update 2019: General Ledger blog
These problems will be fixed with the release of the February Hotfix for Microsoft Dynamics GP.
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. **However, you should always verify AA data is accurate prior to closing the year.
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 KB Article 2910626 before you close the General Ledger year.
What is the impact if the AA data does not match GL data?
If the AA data does not match General Ledger data, and financial reports are pulled from AA tables: This could skew your Financial reports (when AA tables are not consistent with General Ledger) and you won't balance to the General Ledger Trial Balance reports. Missing or duplicated data in the AA tables can skew the beginning balance entries created in the AA tables. The first step is to determine if your Financial reports use the AA tables or not. If you do use AA tables or Management Reporter, it is highly recommended to run through KB 2910626 to help look for mismatched data between AA and General Ledger that should be corrected before closing the General Ledger year.
Why wouldn't data match between AA and General Ledger tables?
There are many reasons why AA data may not match the General Ledger data. If AA is active, ALL transactions from other modules update the AA tables(whether or not the General Ledger accounts are linked to AA and whether or not you put AA codes on the transactions). All transactions need to be accurate in the AA tables if you are doing your financial reporting from AA tables.
Discrepancies can occur when:
As such, we recommend that you continually use the scripts in KB 2910626 to monitor if there are any ongoing issues in your environment (most definitely prior to closing your General Ledger year). This will ensure the data between AA and General Ledger stays in sync 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 General Ledger year:
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 General Ledger year end close process do and/or affect in Analytical Accounting?
The General Ledger Year-End close process will affect the following in the AA tables:
What steps should I take to have AA included in the General Ledger Year-end close and BBF entries created in AA?
In order to have AA codes tied to your beginning balances created by the General Ledger year-end close, you must first verify that the following options are selected:
Key points to remember:
Where can I ask questions or get more assistance for Analytical Accounting Year End Close?
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 screen print of any error messages received.)
--Support Topic Selection: Financial – Analytical Accounting
---Sub-topic Selection: Other
Year-End Close Resources:
Be sure to refer to the 2019 Year-End Blog Schedule to review current and upcoming blog posts and other helpful resource links related to Year-End Closing for Dynamics GP.
I hope this is helpful and that you have a successful Year-End!! If you have any feedback or suggestions, please let us know.
Have a wonderful Year-End!!!
Andrea Melroe | Sr. Technical Advisor | Microsoft Dynamics GP
Business Applications communities