The Fixed Receipt price field in the item model group in D365FO (or AX)

The Fixed Receipt price field in the item model group in D365FO (or AX)

If you work with inventory in D365FO (and older AX versions), the item model group is one of the most important parts to configure when it comes to inventory valuation. But why is there a ‘fixed receipt price’ field in the item model group?

No alt text provided for this image

To understand the meaning of this field, we need to go back to the older versions of AX. Have a look at the print screen that I made today in the inventory models available in Axapta 3 (the version where I start working with in 2006...):

No alt text provided for this image

I only have the Dutch language available in Axapta 3 (indeed, it is not that easy as in D365FO to change language), but in this list you see FIFO, LIFO, LIFO date, weighted average and weighted average date. No Standard costing here!

In Axapta 3 on the item model group there is a field called ‘standard cost price’ that you can select:?

No alt text provided for this image

So working with standard cost principle in Axapta 3 meant that organizations selected the ‘standard cost’ field on the item model group. Selecting this field made it possible to use a fixed receipt price (standard cost price) by purchasing goods of these items, even if the valuation method was FIFO:

No alt text provided for this image

Differences between the fixed receipt price and the purchasing price where posted on the profit and loss account for it, so basically standard costing was used and not the FIFO method. Other standard costing postings like revaluation the inventory value after changing the cost price had do be done manually with adjustments.

So to get the full standard costing principles Microsoft added a new standard cost inventory model in AX 2009. From that moment you could select the standard cost valuation method in the item model group, like you can do now in D365FO:

No alt text provided for this image

But the field for the old standard costing method still exist in the item model group and is renamed in… Fixed receipt price. If you look at the Control Name of the field, you still see the history of the standard costing method:

No alt text provided for this image

So basically there are still two options for working with a standard cost valuation in D365FO.

What are the differences between the fixed receipt price and standard cost inventory model?

1.??????The settings of the main accounts for purchasing price differences must be entered on different places. By fixed receipt price you enter it in the ‘Purchase order’ section of the posting profile, by standard cost you enter it by the ‘standard cost’ area.

No alt text provided for this image

2.??????The fixed price receipt field will only post purchase price differences automatically. The standard cost inventory model will do the necessary automatic postings for the total standard costing process. That's why in the 'Standard cost variance' section you can also enter the main accounts for other posting types, like for revaluate the inventory value by changing cost prices.

The conversion tool

Creating the new standard cost method in AX 2009 also ended up in a conversion tool to change items from the old standard cost functionality to the new standard cost functionality, even if there were posted transactions on the items. Also this tool is still available in D365FO:

No alt text provided for this image

This option can still be useful by changes in accounting policies, I have used it by example for a customer that changed their valuation method from FIFO to standard cost.

What about using the fixed receipt price field itself?

To be honest, I think there is no much reason any more to use the fixed receipt price field. If you really want the standard costing principle, I think you will always use the standard cost inventory model and not the field fixed receipt price.

But of course, if you know cases where this field is still useful and helpful, please let me know ??!

Carlos B.

Solution Architect | D365FO Lead en CrossPoint365

8 个月

Hi Hylke, I've come across this old post because I have a scenario where the fixed cost parameter could be interesting instead of the standard cost method. We have a company interested in standard cost but they don't want to reevaluate the cost of the existing on hand when they activate a new standard price. With the fixed parameter we achieve that but with the standard cost method we would need to use some product dimension to differentiate the material but we don't like this option because it means to mix a financial concept with the real stock. Have you ever faced a similar problem?

Zuhair Haider

Microsoft D365 F&O Functional Consultant | AI ERP | Finance and Supply Chain Analyst | Digital Transformation & Process Automation |

1 年

Thanks for sharing this!

Vijay Kumar

D365 Consultant at Microsoft | Ex-Capgemini

2 年

Thankyou so much..

Sherif Abolsaud

D365 F&O Solution Architect at G42/Core42. My main goal is to automate and streamline the organization processes and save costs wherever is possible.

2 年

You are doing really great work and posting nice stuff! Keep it up mate!

Hadhemi Hayder

Consultante Dynamics 365 Finance chez Dynagile Consulting | MB-310: Microsoft Dynamics 365 Finance Functional Consultant

2 年

Thank you for sharing this!

要查看或添加评论,请登录

Hylke Britstra的更多文章

社区洞察

其他会员也浏览了