• Home
  • About
  • Contact
  • German

Dynamics 365FO/AX Finance & Controlling

Dynamics 365FO/AX Finance & Controlling

Tag Archives: Inventory reconciliation

12 best practice tips to avoid problems with inventory reconciliation

10 Saturday Oct 2015

Posted by Ludwig Reinhard in General Ledger, Inventory

≈ Comments Off on 12 best practice tips to avoid problems with inventory reconciliation

Tags

best practice, Dynamics AX, Inventory reconciliation

Within this blog post I will summarize some of the most important tips and tricks that you should take into consideration when setting up Dynamics AX to avoid reconciliation problems between the finance and inventory data.


Tip 1: Inventory posting setup
Don’t setup inventory posting accounts more than once. That is, don’t use the same ledger account for more than a single line in the inventory posting form and try to avoid a setup that is valid for all combinations of items and accounts as illustrated in the following screenshot.
EN_31_0010
Please also try to avoid setting up the same ledger accounts for different inventory posting types. As an example, if you compare the inventory posting setup for sales order issue transactions in the next screenshot with the posting setup for packing slip transactions in the previous screenshot you can identify the same ledger accounts. This is something that should possibly avoided to make inventory reconciliation less complex.
EN_31_0015


Tip 2: Main account setup
Lock all ledger accounts that have been setup in the inventory posting form for manual entries as shown in the next screenshot.
EN_31_0016

Note:
Make sure that only a limited number of people – ideally those who are not involved in the operating accounting process – can activate and deactivate the manual entry parameter.
If manual inventory value adjustments are required in General Ledger, please setup and use separate sub-ledger accounts.


Tip 3: Item setup (1)
Setup items with their own item financial dimension value as this can considerably reduce the time required for identifying and analyzing differences between General Ledger and inventory.
EN_31_0020
Please note that this setup requires a small system adjustment to that was illustrated in an earlier blog post.


Tip 4: Item setup (2)
Once an item has been setup and used, do not allow anybody to make changes to…

  • the item model group setup, and …
    EN_31_0025
  • the item group setup
    EN_31_0030


Tip 5: Data Quality
Do not make compromises on the quality of your item data that you migrate to your new ERP system, hoping that those issues get fixed by themselves over time.


Tip 6: Use templates
Use item templates or other features/processes that ensure a consistent and straightforward way of setting up new items. The underlying idea here is to make sure that items are correctly setup right from the beginning to avoid later changes.


Tip 7: Special inventory team
Specify a small team of people who are allowed to

  • setup/change items,
  • setup/change item groups,
  • setup/change item model groups,
  • setup/change the inventory posting setup.

Do not allow each user – especially operating accountants – setting up new items.


Tip 8: Database log
Setup the database log to track (at a minimum) changes of the …

  • item setup
  • item group setup
  • item model group setup
  • inventory posting setup


Tip 9: Test inventory reconciliation before Go Live
Test the inventory reconciliation before Go Live. Once you are working with your new system, there won’t be much time for testing what to do if you identify problems with reconciling inventory and ledger balances. So, test it before just to be ready.


Tip 10: Inventory & warehouse processes
Setup your inventory & warehouse processes in a way that transactions are not backdated and ensure that the time lags between registering receipts and posting receipt packing slips is small. Otherwise you run the risk that Dynamics AX shows you a negative physical and/or financial inventory value.

Please note that the setup of registration and receiving requirements in the item model group window do not ensure that you will see negative physical and/or financial inventory values. That is because items can be sold as soon as they are registered in the system.
EN_31_0035


Tip 11: Service items
Put much consideration in whether and how you want to setup service items (e.g. for subcontracting or other purposes) as those items are generally excluded from the inventory value report and might thus result in reconciliation issues.

 

Tip 12: Scheduled batch transfers from subledgers
EN_31_0040
If you setup your General Ledger parameters in a way that subledger transactions are transferred in batch mode to General Ledger, ensure that the “subledger journal entries not yet transferred” form in the General Ledger does not include pending inventory related transactions as illustrated in the next screenshot. EN_31_0045
The underlying reason is that pending transactions might result in reconciliation problems, that is, differences between the ledger and inventory balances.

 

I hope that you enjoyed the last series of inventory reconciliation blog posts and look forward to seeing you in the next posts.

Alternative methods for reconciling inventory with General Ledger – Addendum

01 Thursday Oct 2015

Posted by Ludwig Reinhard in General Ledger, Inventory

≈ Comments Off on Alternative methods for reconciling inventory with General Ledger – Addendum

Tags

Dynamics AX, Inventory reconciliation

Within this addendum I would like to show you how inventory and ledger balances can be reconciled by using the first “financial dimension” reconciliation approach presented in the earlier post.

I will do this based on the following simplified production item (finished product) “L6300” that consists of another item (“L6301”) and a subcontracting service item (“L6302”). The quantities and cost prices that make up the Bill of Materials (BOM) of the finished product can be identified in the next screenshot.EN_32_0190

 

Production step 1: Inventory adjustment Item L6301
In order to produce the production item, I first need to ensure that sufficient parts of the BOM item “L6301” are on stock. I realize this by posting an inventory adjustment journal that generated the following ledger transaction (please see the next screen-print).
EN_32_0195
What you can identify from this voucher is an increase in inventory value of 40 EUR that is posted against a profit & loss account (“510504”). Please note that all transactions are recorded with the financial item transaction of the BOM item (“L6301”).


Production step 2: Production start
After ensuring that sufficient parts are on hand for production, I started the production order. While doing that, Dynamics AX generated the following voucher:
EN_32_0200
What you can see from this voucher is an increase in the WIP balance sheet account 150151 and 150153 that are highlighted in green color. The offset transactions are all posted on the inventory accounts 140103 and 140303.

Please note that the voucher for the subcontracting service item that is recorded against the inventory account 140303 could also be recorded against a profit and loss account. In addition, with a slightly different item setup, the voucher for the service item could also have been posted later; that is in later production steps.

Irrespective of the timing of the subcontracting service item posting and the ledger account used, after posting the voucher for the subcontracting item, the inventory value report shows a variance of 10 EUR, which is equal to the value of the subcontracting item “L6302”.
EN_32_0205EN_32_0206
The underlying reason for this variance is that the inventory value report does not incorporate service items.

Now, let’s have a look at the result that can be identified in the trial balance after finishing the first production step.

The following screenshot shows you, the outcome of the first production step (inventory adjustment) highlighted in yellow color and the outcome of the second production step (production start) highlighted in green color. What you can identify from this screenshot is that both financial item dimensions (“L6300” and “L6301”) are balanced and add up to a total value of 0 EUR.
EN_32_0210
The next screenshot shows the very same balances sorted by main accounts. What I would like to emphasize from this screenshot are the transactions recorded on the green highlighted WIP accounts that incorporate the total value of the finished product.
EN_32_0215

Production step 3: Report as finished
The next production step is reporting the production order as finished, which results in the following voucher:
EN_32_0220
As before, the inventory value report still shows a variance of 10 EUR.
EN_32_0225 EN_32_0226
The trial balance list page on the other hand does still show a balanced result for the financial dimensions “L6300” and “L6301”.
EN_32_0230
The WIP accounts are now cleared and show a total amount of 0 EUR (highlighted in green color). At the same time, the preliminary inventory account for the finished item (main account 140204) shows a balance of 50 EUR.
EN_32_0235

 

Production step 4: End production
The last production step ends the production order. When ending the production order, Dynamics AX reverses all previous vouchers and posts the increase in inventory for the production item. The next screenshot shows you the voucher generated for my demo item.
EN_32_0240
As before, even after finishing the production order, the inventory value report still shows a variance of 10 EUR.
EN_32_0245 EN_32_0246
The trial balance list page on the other hand shows balanced item financial dimensions.
EN_32_0250
The same holds for the ledger accounts.
EN_32_0255

 

Production step 5: Post vendor invoice for the subcontracting item with a price variance of 2 EUR
Some days after ending the production order, the subcontracting vendor sends his invoice for 12 EUR. The 2 EUR price variance is accepted. After posting the vendor invoice, the following voucher results.
EN_32_0260
If we have a look at the inventory value report we do now see a variance of 2 EUR that is equivalent to the price difference for the subcontracting item.
EN_32_0265 EN_32_0266
An analysis of the trial balance list page shows – as before – a balanced outcome for the financial item dimensions …
EN_32_0270
… as well as for the main accounts.
EN_32_0275

 

Production step 6: Inventory reconciliation
The last “production” step used in this demo is running an inventory reconciliation, which generated the following voucher:
EN_32_0280
If we have a look at the inventory value report we can now identify that inventory and ledger amounts are finally balanced.
EN_32_0285 EN_32_0286

Yet, from a financial dimension perspective this has always been the case as the following screenshots illustrate.
EN_32_0290 EN_32_0295

 

Summary
Within this blog post I highlighted you the specific problems that many production companies face with the inventory value report when they outsource a part of their production chain. Those companies might always see a variance in the inventory value report. Yet, by applying an alternative reconciliation approach – such as using an item financial Dimension – reconciling inventory and ledger balances becomes possible.

Alternative methods for reconciling inventory with General Ledger

01 Thursday Oct 2015

Posted by Ludwig Reinhard in General Ledger, Inventory

≈ Comments Off on Alternative methods for reconciling inventory with General Ledger

Tags

Dynamics AX, Inventory reconciliation

Within the previous blog post I showed you several problems of the inventory value report and the potential conflicts report that can cause you some “headache” if you try reconciling ledger and inventory balances. As I do not want to leave you on your own with those problems, I thought it might be useful to show you some alternative approaches for reconciling ledger and inventory values.

Because of the problems with the inventory value report, (as described in the previous blog post), I setup a completely new Dynamics AX demo environment and repeated the previously shown transactions for two newly created test items “L2000” and “L2100”. As before, all item transactions for the first test item “L2000” are recorded in January 2015 and all item transactions for the second test item “L2100” are recorded in February 2015. The next screenshot gives you once again an overview of the inventory transactions executed for the first test item in January 2015.
EN_32_0005
After recording those transactions, I run the inventory value report without any date restriction and got the following result.
EN_32_0010
What you can identify from this screen-print is identical to the result for the inventory transactions that I showed you in the previous blog post. Against the background of those transactions let’s now have a look at some alternative inventory reconciliation approaches.


Approach 1: Financial dimension “item”
A first alternative approach for reconciling inventory and ledger balances is setting up all items with a financial item dimension and using standard General Ledger features, such as the trial balance list page, for reconciliation purposes. Example:
EN_32_0015
What you can identify from the screen-print above (that filters on the first test item “L2000”) is
(a) the total inventory value of 14250 EUR recorded on ledger account 140200, and
(b) the financial inventory value of 14525 EUR that can be calculated by adding the green highlighted lines / values.

Prerequisites:
In order to apply this approach you have to make sure that your account structures incorporate the item financial dimension as exemplified in the following screenshot and…
EN_32_0020
… that all your items are setup with their corresponding financial dimension.
EN_32_0025

Note: To make sure that each newly setup item automatically gets linked to its item financial dimension, a minor code adjustment, as illustrated in the next screenshots, might be smart. In my example, I first generated a new method (“SetFDIT”) in the InventTable …
EN_32_0030
… and made the following adjustment to the insert method.
EN_32_0035

Note: If you setup inventory posting based on an item group level, it might be sufficient using the item group financial dimension for reconciliation purposes as illustrated in the next screenshot.
EN_32_0040
Yet, this approach has the disadvantage that it does not help you identifying errors/problems e.g. if a specific item transaction was recorded on a “wrong” ledger account. That is because using the item group financial dimension for reconciliation purposes does not allow you identifying which item caused the problem. For that reason, in an “ideal world”, it would be best working with both, an item group financial dimension and an item financial dimension as they give you the possibility to do your reconciliation at the item group level and “drill down” to the item level if you identify problems.

Advantages/Disadvantages of this reconciliation approach:
This first approach has several advantages and disadvantages. Let’s start having a look at the advantages:

  • People working in the finance & controlling department are familiar with using and analyzing financial dimension values via the trial balance list page and other forms/reports in the General Ledger. They are thus familiar with this reconciliation approach.
  • The trial balance list page provides some standard drill down functionalities that help identifying problems quickly.
  • As Dynamics AX is a fully integrated ERP system, differences between inventory and General Ledger are by definition not possible. That is because each debit transaction requires a corresponding credit transaction. Reconciling inventory and General Ledger is thus a mere question of understanding the Dynamics AX posting framework and having a look at the “right” ledger accounts. As the trial balance list page does possibly give the best and fastest view at ledger accounts, this first alternative approach seems predestined for the inventory-ledger reconciliation job.

Now let’s have a look at the disadvantages of this approach:

  • Depending on your system setup and number of items used in your company, the trial balance list page might need more time to open up and is limited to a single year. If you need to analyze data quickly for several years, the Management Reporter might be the better choice for doing the reconciliation job.
  • You “lose” at least one financial dimension for reconciliation purposes,
  • This approach works best if a code adjustment is implemented that makes sure that the financial item dimension is automatically filled once a new item is setup.

 

Approach 2: Inventory transaction inquiry forms
A second alternative approach for reconciling inventory and ledger balances is using inquiries forms that allow you analyzing inventory transactions. An example of such an inquiry form is the transactions form that can be found in the inventory management module. Please see the following screenshot.
EN_32_0045

Prerequisites:
A major disadvantage of this and other standard Dynamics AX forms is that information on ledger accounts cannot be personalized in a way that allows analyzing the transaction data quickly and easily. Please have a look at the next screenshot which illustrates that the inventory transaction form does only show the ledger information for the first record.
EN_32_0050
For the following illustrations, I thus created a new inventory transaction form denominated “LRE INVRE” that is based on the InventValueTransView that is also used for the inventory value cube. (Please note that you can use several other standard views, queries or tables for setting up this form). As you can identify from the next screenshot, this form allows you identifying the account and offset account for each inventory transaction.
EN_32_0055neu
Note: What is important in this respect is that you implement a form that allows you filtering those inventory transactions before the form is opened. Otherwise you might experience some performance issues due to the large number of transactions that need to be loaded when opening the form.

Once the form is implemented you can either analyze the inventory data directly in the form or export the results to Excel for a more detailed reconciliation analysis. Example:
EN_32_0060

Advantages/Disadvantages of this reconciliation approach:
After illustrating you the underlying principle of this second reconciliation approach, let’s have a look at the advantages and disadvantages of this approach.

Advantages:

  • As shown above, this second approach allows you analyzing the ledger account and offset account for each inventory transaction recorded (provided that the transaction is already posted on ledger accounts).
  • Different from the first approach, this second inventory reconciliation approach does also allow you analyzing inventory transactions that have not yet been posted to ledger accounts. This is a major advantage as you can e.g. quickly identify items that have been picked or registered but not packing slip updated and/or invoiced.
  • A third advantage of this approach is that it can be implemented quickly and easily with a simple system modification. Moreover, users can make use of the standard Excel export functionalities that allow a detailed analysis of the inventory transactions.
  • A final advantage of this approach is that you don’t necessarily “lose” a financial dimension for reconciliation purposes.

Disadvantages:

  • A major disadvantage of this approach is that transaction level data are analyzed. Analyzing those data can consume lots of time unless you are able to filter those transactions e.g. by date, item or other features.
  • When using this approach, users will most likely copy the data to Excel for a detailed analysis. Please remember that also Excel does have its limitations as exporting more than 1.1 mio. data at a time is generally not possible requiring incremental data exports.
  • A final disadvantage of this approach is that it is in general more difficult identifying errors, as the data are not pre-aggregated. This means that you have to “slice and dice” the data in a way to identify inconsistent / incorrectly entered transactions. This last disadvantage can be overcome by using the next alternative approach for inventory reconciliation.

 

Approach 3: Inventory value cube
The third and last alternative method to reconcile inventory and General Ledger balances that I want to present in this post is using cubes. (Please note that I do not make a differentiation between the many BI instruments available for Dynamics AX, such as SSAS cubes, the various Power BI instruments and alike and simply call this approach “cube” solution to keep things as easy as possible).

For the following illustrations, I simply used the inventory value cube that ships with the standard Dynamics AX application. The next screenshot shows the result of an analysis that I did for the demo item “L2000” by browsing the cube in the SQL server management studio.
EN_32_0065
You can, of course, do the same in MS Excel simply by establishing a connection to this cube.
EN_32_0072
Example:
EN_32_0073

Note:
If you compare the data from the inventory value cube and the trial balance list page you will notice some differences in the detailed amounts that make up the total inventory balance of 14250 EUR. In my example you can identify ledger balances on the balance sheet accounts 200100 and 200140 in the Dynamics AX General Ledger that sit on the profit and loss account 600180 in the inventory value cube.
EN_32_0080
The underlying reason for this outcome is the “design” of the inventory value cube, which currently does not allow reconciling the physical inventory amount shown in the inventory value report. For that reason, you need to make some adjustments to the standard inventory value cube if you want to use it for reconciling purposes in your Dynamics AX environment.

Advantages/Disadvantages of this reconciliation approach:
Now, let’s also have a look at the advantages and disadvantages of using this approach.

Advantages:

  • The cube solution is probably the most powerful and fastest solution for reconciling inventory and ledger balances as users can easily analyze the data they want e.g. in Excel.
  • Different from the previous approach, the cube solution can easily handle large data volumes as transactional data are pre-aggregated. At the same time, cube “drill through” features allow you taking a detailed look at the transactional data simply by doing a double click on the data.

Disadvantages:

  • A first disadvantage of this approach is that you need a cube expert for implementing cubes, as ordinary finance & controlling users regularly do not have sufficient system rights and the expertise to implement those cubes.
  • Another disadvantage is that not all the standard inventory value cube measures, calculations and KPIs can be used “out of the box” and need some modification before they can be used in a live environment.

 

Summary
Because of the many problems of the inventory value report it is prudent to make use of alternative inventory reconciliation approaches.
Within this blog post I showed you three possible alternative reconciliation approaches that can help you overcoming the weaknesses of the inventory value report.
From a finance and controlling perspective, the first approach seems to be the one that should always be implemented as it can be setup by ordinary finance & controlling users without making a system modification.
If differences between inventory and General Ledger arise, using the second and/or third approach seem to be inevitable.

Due to its importance and ease of implementation, I will show you a detailed step-by-step example on how to reconcile production vouchers by using the first “financial dimension approach” within the next post.

← Older posts

Microsoft BizApps Deutschland Podcast

Dynamics UserGroup Deutschland

Project Accounting Book – Part 2

Project accounting book

Categories

  • Accounts Payable
  • Accounts Receivable
  • Bank Management
  • Book reviews
  • Budgeting
  • Cost accounting
  • Fixed Assets
  • General Ledger
  • Inventory
  • Management Reporter
  • Miscellaneous
  • Podcast
  • Project
  • Sustainability
  • Uncategorized

Tags

Advanced bank reconciliation Allocations Artificial Intelligence Bank reconciliation Budgeting Controlling Cost accounting Cost accounting module Cost center accounting customer D365 D365FO Dynamics 365 Dynamics AX Dynamics AX 2012 Electronic reporting Email Environment Fixed asset statement General Ledger journal Global Warming intercompany Inventory Inventory reconciliation invoice invoice recording IOT Management Accounting Management Reporter Modern Finance MS Flow MT940 PowerApps PowerAutomate PowerPlatform Project Project module Resource scheduling Sensor settlement SharePoint Sustainability Sustainability Accounting Tax time recording timesheet Vendor invoice recording Vendor payments WBS workflow

Important Websites

  • Dynamics AX/365FO Links

Legal

  • Disclaimer

Subcribe

  • RSS - Posts
  • RSS - Comments

Enter your email address to follow this blog and receive notifications of new posts by email.

Archives

  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015

Blog at WordPress.com.

  • Follow Following
    • Dynamics 365FO/AX Finance & Controlling
    • Join 575 other followers
    • Already have a WordPress.com account? Log in now.
    • Dynamics 365FO/AX Finance & Controlling
    • Customize
    • Follow Following
    • Sign up
    • Log in
    • Report this content
    • View site in Reader
    • Manage subscriptions
    • Collapse this bar
 

Loading Comments...