Analytical Accounting (AA) has been around for quite some time and many of you know it like the back of your hand. But just in case there are any questions at year-end time, I hope the information below will help you out. Remember that AA closes along with GL and is done behind the scenes, so be sure to give yourself plenty of time to read through this blog and understand it before you close the GL year. With the suggestions below, you can make sure your AA tables match GL so you don’t run into issues with your Financial reporting later on. GP Year-End Analytical Accounting Update for 2022.
Does the 2022 Year-End Update include changes that will affect year-end processing for Analytical Accounting (AA)?
There are no changes included in the 2022 Year-End Update that affect year-end processing for Analytical Accounting.
Is there a separate Year-End close process to run for Analytical Accounting?
No, the year-end close process for Analytical Accounting is automatically integrated with the year-end close process for General Ledger. Therefore, 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 you generate your Financial reports from AA tables (such as Management Reporter Data Mart), it is highly recommended to run through the scripts Financial Reports from Management Reporter don’t match the General Ledger Trial Balance Reports in Microsoft Dynamics GP (Original KB 2910626) before you close the General Ledger year. The scripts in the article will compare AA data to GL data and return any discrepancies with the AA data, so you can fix the data prior to closing the year.
Finding these data discrepancies can also help you to monitor your if there are any ongoing issues in your environment. The scripts in this KB article can be run throughout the year as well. This will ensure the data between AA and General Ledger stays in sync if you are doing any financial reporting from AA tables.
What is the impact if the AA data does not match GL data?
If the data in the AA tables does not match General Ledger data, and financial reports are pulled from AA tables, then your Financial reports may include inaccurate totals 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. (You can determine this for Management Reporter under Microsoft Dynamics GP | Tools | Setup | Company | Company | Options in the MR section at the bottom to see if GL or AA is enabled.) If you do use AA tables and/or Management Reporter, it is highly recommended to run through KB 2910626 to help look for data discrepancies 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 including:
- Posting interruptions, network connection issues, power fluctuations, etc while posting can cause damaged data
- Data is imported
- AA is not installed on all machines
- General Ledger was closed on a machine in the past where AA was not installed
- Users disable AA when AA error messages crop up
- Multi-currency is not registered
Remember that when AA is active, ‘ALL’ transactions are updated to the AA tables, regardless if the GL account used is linked to AA or not, and regardless of whether an AA dimension code is on the transaction or not. All transactions need to be present and accurate in the AA tables so you can generate Financial reporting from AA tables.
When should the Year End Close for Analytical Accounting be done?
Before closing the General Ledger year, we highly recommend to run through the steps/scripts in these KB articles:
- 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. (Original KB 2910626)
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.
Note: You can download all the scripts in KB 2910626 and run them in text (Control – T) before executing them. If any results are in the open years (i.e. AAG30000 series tables or GL20000) then you can just fix the data before closing the GL year. However if any of the results are in historical years (i.e. AAG40000 series tables or GL30000), then you most likely will need to reopen the GL year back to that year, fix the data, and then re-close the year again, so the BBF in the AA tables can be recalculated with this change. So that is why it is important to run through this KB every year, so you can keep the historical data in the AA tables clean and correct. After any changes are made to the AA tables, you will need to rebuild the Datamart for Management Reporter (which is outlined in the last step in KB 2910626). For assistance with fixing any AA data, you can open a Support Incident per your support plan
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:
- 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 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:
- In the Analytical Accounting Options window (Microsoft Dynamics GP >> Tools >> Setup >> Company >> Analytical Accounting >> Options), mark the checkbox for ‘Include dimensions in the year end close’ and click OK.
- In the Transaction Dimension Maintenance window (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 General Ledger year-end close process.
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 General Ledger 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 General Ledger data.
- With the release of 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 Data Mart CU10 and up does have the option to report with or without AA data.
- Make sure the General Ledger 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 screen print of the AA error message if assistance is needed with the General Ledger year-end close process.
By CAL Business Solutions, Connecticut Microsoft Dynamics GP & Acumatica Partner, www.calszone.com
Read the original post at: https://community.dynamics.com/blogs/post/?postid=733bff42-8442-4831-b66f-14d9f8d89ffe