The average cost of an item is calculated with a periodic weighted average, based on the average cost period that is set up in Dynamics NAV.
The valuation date is set automatically.
The following table describes the two fields in the Inventory Setup window that must be filled to enable average cost calculation.
| Field | Description |
|---|---|
| Average Cost Period | Specifies which period the average cost is calculated in. The following options exist: - Day - Week - Month - Accounting Period All inventory decreases that are posted in the average cost period receive the average cost calculated for that period. |
| Average Cost Calc. Type | Specifies how the average cost is calculated. The following options exist: - Item - Item, Variant, and Location With this option, the average cost is calculated for each item, for each location, and for each variant of the item. This means that the average cost of this item depends on where it is stored and which variant of the item that you have selected, such as color. |
You can only use one average cost period and one average cost calculation type in a fiscal year.
The Accounting Periods window shows which average cost period and which average cost calculation type is in effect during that period, for each accounting period.
When you post a transaction for an item that uses the Average costing method, an entry is created in the Avg. Cost Adjmt. Entry Point table. This entry contains the transaction’s item number, variant code, and location code. The entry also contains the Valuation Date field, which specifies the last date of the average cost period in which the transaction was posted.
This field should not be confused with the Valuation Date field in the Value Entry table, which shows the date when the value takes effect and is used to determine the average cost period in which the value entry belongs.
The average cost of a transaction is calculated when the item’s cost is adjusted. For more information, see Design Details: Cost Adjustment. A cost adjustment uses the entries in the Avg. Cost Adjmt. Entry Point table to identify which items (or items, locations, and variants) to calculate average costs for. For each entry with a cost that has not been adjusted, the cost adjustment uses the following to determine the average cost:
Divides by the total inventory quantity for the end of the average cost period, excluding inventory decreases that are being valued.
The calculated average cost is then applied to the inventory decreases for the item (or item, location, and variant) with posting dates in the average cost period. If any inventory increases exist that were fixed applied to inventory decreases in the average cost period, then the calculated average cost is forwarded from the increase to the decrease.
The following example shows the effect of calculating the average cost based on an average cost period of one day. The Average Cost Calc. Type field in the Inventory Setup window is set to Item.
The following table shows item ledger entries for the sample average-cost item, ITEM1, before the Adjust Cost - Item Entries batch job has been run.
| Posting Date | Item Ledger Entry Type | Quantity | Cost Amount (Actual) | Entry No. |
|---|---|---|---|---|
| 01-01-20 | Purchase | 1 | 20.00 | 1 |
| 01-01-20 | Purchase | 1 | 40.00 | 2 |
| 01-01-20 | Sale | -1 | -20.00 | 3 |
| 02-01-20 | Sale | -1 | -40.00 | 4 |
| 02-02-20 | Purchase | 1 | 100.00 | 5 |
| 02-03-20 | Sale | -1 | -100.00 | 6 |
Because cost adjustment has not yet occurred, the values in the Cost Amount (Actual) field of the inventory decreases corresponding to the inventory increases that they are applied to.
The following table shows the entries in the Avg. Cost Adjmt. Entry Point table that apply to value entries resulting from the item ledger entries in the preceding table.
| Item No. | Variant Code | Location Code | Valuation Date | Cost is Adjusted |
|---|---|---|---|---|
| ITEM1 | BLUE | 01-01-20 | No | |
| ITEM1 | BLUE | 02-01-20 | No | |
| ITEM1 | BLUE | 02-02-20 | No | |
| ITEM1 | BLUE | 02-03-20 | No |
The following table shows the same item ledger entries after the Adjust Cost - Item Entries batch job has been run. The average cost per day is calculated and applied to the inventory decreases.
| Posting Date | Item Ledger Entry Type | Quantity | Cost Amount (Actual) | Entry No. |
|---|---|---|---|---|
| 01-01-20 | Purchase | 1 | 20.00 | 1 |
| 01-01-20 | Purchase | 1 | 40.00 | 2 |
| 01-01-20 | Sale | -1 | -30.00 | 3 |
| 02-01-20 | Sale | -1 | -30.00 | 4 |
| 02-02-20 | Purchase | 1 | 100.00 | 5 |
| 02-03-20 | Sale | -1 | -100.00 | 6 |
The following example shows the effect of calculating the average cost based on an average cost period of one month. The Average Cost Calc. Type field in the Inventory Setup window is set to Item.
If the average cost period is one month, then only one entry is created for each combination of item number, variant code, location code, and valuation date.
The following table shows item ledger entries for the sample average-cost item, ITEM1, before the Adjust Cost - Item Entries batch job has been run.
| Posting Date | Item Ledger Entry Type | Quantity | Cost Amount (Actual) | Entry No. |
|---|---|---|---|---|
| 01-01-20 | Purchase | 1 | 20.00 | 1 |
| 01-01-20 | Purchase | 1 | 40.00 | 2 |
| 01-01-20 | Sale | -1 | -20.00 | 3 |
| 02-01-20 | Sale | -1 | -40.00 | 4 |
| 02-02-20 | Purchase | 1 | 100.00 | 5 |
| 02-03-20 | Sale | -1 | -100.00 | 6 |
Because cost adjustment has not occurred yet, the values in the Cost Amount (Actual) field of the inventory decreases corresponding to the inventory increases that they are applied to.
The following table shows the entries in the Avg. Cost Adjmt. Entry Point table that apply to value entries resulting from the item ledger entries in the preceding table.
| Item No. | Variant Code | Location Code | Valuation Date | Cost is Adjusted |
|---|---|---|---|---|
| ITEM1 | BLUE | 01-31-20 | No | |
| ITEM1 | BLUE | 02-28-20 | No |
The valuation date is set to the last day in the average cost period, which in this case is the last day of the month.
The following table shows the same item ledger entries after the Adjust Cost - Item Entries batch job has been run. The average cost per month is calculated and applied to the inventory decreases.
| Posting Date | Item Ledger Entry Type | Quantity | Cost Amount (Actual) | Entry No. |
|---|---|---|---|---|
| 01-01-20 | Purchase | 1 | 20.00 | 1 |
| 01-01-20 | Purchase | 1 | 40.00 | 2 |
| 01-01-20 | Sale | -1 | -30.00 | 3 |
| 02-01-20 | Sale | -1 | -65.00 | 4 |
| 02-02-20 | Purchase | 1 | 100.00 | 5 |
| 02-03-20 | Sale | -1 | -65.00 | 6 |
The average cost of entry number 3 is calculated in the average cost period for January, and the average cost for entries 4 and 6 is calculated in the average cost period for February.
To get the average cost for February, the average cost of the piece received in inventory (100.00) is added to the average cost at the beginning of the period (30.00). The sum of the two (130.00) is then divided by the total quantity in inventory (2).This gives the resulting average cost of the item in the February period (65.00). The average cost is assigned to the inventory decreases in the period (entries 4 and 6).
The Valuation Date field in the Value Entry table is used to determine in which average cost period an inventory decrease entry belongs. This also applies to work in process (WIP) inventory.
The following table shows the criteria that are used to set the valuation date.
| Scenario | Posting Date | Valued Quantity | Revaluation | Valuation Date |
|---|---|---|---|---|
| 1 | Positive | No | Posting date of item ledger entry | |
| 2 | Later than the latest valuation date of applied value entries | Negative | No | Posting date of item ledger entry |
| 3 | Earlier than the latest valuation date of applied value entries | Positive | No | Latest valuation date of the applied value entries |
| 4 | Negative | Yes | Posting date of the revaluation value entry |
The following table of value entries illustrates the different scenarios.
| Scenario | Posting Date | Item Ledger Entry Type | Valuation Date | Valued Quantity | Cost Amount (Actual) | Item Ledger Entry No. | Entry No. |
|---|---|---|---|---|---|---|---|
| 1 | 01-01-20 | Purchase | 01-01-20 | 2 | 20.00 | 1 | 1 |
| 2 | 01-15-20 | (Item Charge) | 01-01-20 | 2 | 8.00 | 1 | 2 |
| 3 | 02-01-20 | Sale | 02-01-20 | -1 | -14.00 | 2 | 3 |
| 4 | 03-01-20 | (Revaluation) | 03-01-20 | 1 | -.4.00 | 1 | 4 |
| 5 | 02-01-20 | Sale | 03-01-20 | -1 | -10.00 | 3 | 5 |
In entry number 5 in the preceding table, the user has entered a sales order with a posting date (02-01-20) that comes before the latest valuation date of applied value entries (03-01-20). If the corresponding value in the Cost Amount (Actual) field for this date (02-01-20) were used for this entry, then it would be 14.00. This would give a situation where the quantity on inventory is zero, but the inventory value is –4.00.
To avoid such a quantity-value mismatch, the valuation date is set to equal the latest valuation date of the applied value entries (03-01-20). The value in the Cost Amount (Actual) field becomes 10.00 (after revaluation), which means that the quantity on inventory is zero, and the inventory value is also zero.
Because the Inventory Valuation report is based on posting date, the report will reflect any quantity-value mismatches in scenarios as in the above example. For more information, see Design Details: Inventory Valuation.
If the quantity on inventory is less than zero after posting the inventory decrease, then the valuation date is first set to the posting date of the inventory decrease. This date may be changed later, according to the rules described in the note earlier in this section, when the inventory increase is applied.
Valuing inventory decreases as a weighted average would be straightforward if purchases were always invoiced before sales are invoiced, postings were never backdated, and you never made mistakes. However, the reality is somewhat different from this ideal.
As illustrated in the examples in this topic, the valuation date is defined as the date from which the value entry is included in the average cost calculation. This gives you the flexibility to do the following for items using the Average costing method:
Another reason for this flexibility is fixed application. For more information about fixed application, see Design Details: Item Application.
Because of this flexibility, you may have to recalculate the average cost after the related posting has occurred. For example, if you post an inventory increase or decrease with a valuation date that comes before one or more inventory decreases. The recalculation of the average cost will occur automatically when you run the Adjust Cost - Item Entries batch job, manually or automatically.
It is possible to change the inventory valuation base within an accounting period by changing the Average Cost Period field and the Average Cost Calc. Type field. However, this should be done with care and in agreement with an auditor.
The following example illustrates how the average cost is recalculated when a late posting is introduced on a date that comes before one or more inventory decreases. The example is based on an average cost period of Day.
The following table shows the value entries that exist for the item before the posting is introduced.
| Valuation Date | Quantity | Cost Amount (Actual) | Entry No. |
|---|---|---|---|
| 01-01-20 | 1 | 10.00 | 1 |
| 01-02-20 | 1 | 20.00 | 2 |
| 02-15-20 | -1 | -15.00 | 3 |
| 02-16-20 | -1 | -15.00 | 4 |
The user posts an inventory increase (entry number 5) with a valuation date (01-03-20) that comes before one or more inventory decreases. To balance the inventory, the average cost must be recalculated and adjusted to 17.00.
The following table shows the value entries that exist for the item after entry number 5 is introduced.
| Valuation Date | Quantity | Cost Amount (Actual) | Entry No. |
|---|---|---|---|
| 01-01-20 | 1 | 10.00 | 1 |
| 01-02-20 | 1 | 20.00 | 2 |
| 01-03-20 | 1 | 21.00 | 5 |
| 02-15-20 | -1 | -17.00 | 3 |
| 02-16-20 | -1 | -17.00 | 4 |
Design Details: Inventory Costing
Design Details: Costing Methods
Design Details: Cost Adjustment
Design Details: Item Application
Managing Inventory Costs
Finance
Working with Dynamics NAV
© 2017 Microsoft. All rights reserved.