The difference is due to the way the 2 reports are setup and run.
If you were to rerun the reports right now you would see a $113 difference.
The inventory Discrepancy Report is a true representation of the value of the stocktake at the time you ran it. This report uses the values which are stored in the database against that particular record. I.e. when you enter an inventory discrepancy (via stocktake) a record is added to the database, this record includes the details of item number, quantity and prices. This particular report will use all these values.
The stock inventory comparison report is an adhoc calculation of the value of discrepancies. This report will use the number of discrepancies and multiply that by the Purchase price of the item which is stored against the item record. The value against the item record being a weighted average price is always changing (controlled by M3). For this reason evertyime you rerun this report you could get a difference.
If you look at the attached excel doc:
- Column B is the quantity of discrepancy
- Column C is the True representation of stocktake value (same as on Inventory Discrepancy by Item report)
- Column D is the Stock Inventory Comparison which can change.
- Column E shows the difference between C and D.
- There is a total row which clearly shows C is matching, but again D is different (I reran report and my column D matched my report).
Thinking back to Y2 this is logical and by design
- While conducting a stocktake you need a report to compare scans to PC inventory to see if the value is in the right ballpark figure. In this case there is no inventory discrepancy yet created, so it needs to get a snapshot of the value, and the item price is the correct item to use.
- When validating a stocktake you then take this item price and place it against the stocktake essentially locking in the value. If you were to run both reports at the same time as validation the totals of both reports would match.
Looking at the Y2 structure:
