• Home
  • About
  • Contact
  • German

Dynamics 365FO/AX Finance & Controlling

Dynamics 365FO/AX Finance & Controlling

Tag Archives: Cost accounting module

Cost accounting (11)

01 Sunday Oct 2017

Posted by Ludwig Reinhard in Cost accounting

≈ Comments Off on Cost accounting (11)

Tags

Controlling, Cost accounting module, Cost center accounting, Hierarchy allocation base, Hierarchy based allocations, Management Accounting

Similar to what has been shown in the previous posts on cost allocations, also this post will shown an allocation technique that makes use of a dimension hierarchy that includes additional summary nodes. The allocation technique shown below will once again be based on the financial data that have been used in prior posts.

However, this time a hierarchy allocation base is setup for making the cost allocations.

The hierarchy allocation base that is setup and illustrated in the previous screenprint defines that the previously used formula – which calculates the total direct costs – will be used as the allocation base for those cost centers that belong to the ‘DIRECT CC’ node of the cost object dimension hierarchy.

This cost allocation base is then used in the cost allocation policy shown next and defines that all cost centers that belong to the ‘INDIRECT CC’ node will be allocated to the operative (‘direct’) cost centers based on the total costs that have been recorded on the operative cost centers.

 Different from what has been shown in part 7 of this series on the cost accounting module, the cost allocations ignore the cost relationships within the group of the indirect cost centers because the hierarchy allocation base specified refers to the ‘DIRECT CC’ node only.

As before, the next screenprints summarize the allocation results.

 Please note that the total costs on the direct or operating cost centers no. 210-250 are identical to what has been shown in part 7 of this series. Yet, a detailed investigation of the allocations made reveals that the allocations within the group of the indirect cost centers are skipped.

In the next part, we will extend the hierarchy allocation base allocation technique and investigate how it can be applied to costing scenarios that make use of fixed and variable costs. Till then.

Cost accounting (10)

19 Tuesday Sep 2017

Posted by Ludwig Reinhard in Cost accounting

≈ 5 Comments

Tags

Controlling, Cost accounting module, Cost center accounting, Hierarchy based allocations, Management Accounting

This post continues the previous one in a way that allocations are made once again by referring to summary nodes in a dimension hierarchy. However, this time multiple allocation bases – shown in the next overview graphic – are used for making the allocations.

To realize the multiple base hierarchical allocation approach, a new cost object dimension has been setup that includes three additional summary nodes (‚110 INDIRECT’, ‘120 INDIRECT’ and ‘130 INDIRECT’). In the example used, each of those summary nodes holds a single cost center only.

In practice, each summary node typically holds multiple cost objects that are allocated to other ones by making use of the same allocation base.

 

With the new cost object dimension hierarchy in place, one can then refer to the different indirect summary hierarchy nodes when setting up cost allocation policies. This is exemplified in the next screenprint that shows how the different indirect cost object nodes are linked to allocation bases for cost allocation purposes.

In the example illustrated in the previous screenprint, all cost centers (respectively their costs) that belong to the ‘110 INDIRECT’ hierarchy node are allocated to the operative or ‘direct’ cost centers based on the number of employees working there.

The cost center costs of the ‘120 INDIRECT’ group are allocated based on the number of company cars and the cost center costs of the ‘130 INDIRECT’ group are allocated based on the total direct costs of the other ‘direct’ or operative cost centers.

 This example illustrates once again that previously used statistical measures and formulas can be re-used multiple times in the new D365 cost accounting module. This ability can be very beneficial for example if one wants to run simulations or tests based on previously used allocation bases.

 

As in all prior posts on cost allocations, the next screenprints document the obtained allocations and are summarized in an Excel document at the very end of this post.

In the next post, we will investigate how one can make use of hierarchy allocation bases. Till then.

Cost accounting (9)

09 Saturday Sep 2017

Posted by Ludwig Reinhard in Cost accounting

≈ 1 Comment

Tags

Controlling, Cost accounting module, Cost center accounting, Hierarchy based allocations, Management Accounting

Within this post, we will once again use the financial data that have been used in all prior post on cost allocations.

However, this time all costs that have been accumulated on the indirect cost centers no. 110-130 will be allocated to the ‘direct’ or operative cost centers no. 210-250 by making use of a specific cost object hierarchy setup that is illustrated in the next screenprint.

The major difference to the cost object hierarchies that have been used in the previous posts is that two additional summary nodes (‘INDIRECT CC’ and ‘DIRECT CC’) have been introduced. As those additional nodes summarize the cost centers below, they can be used for cost allocation purposes in the cost allocation policy form, which is shown below.

The cost allocation policy form shown above specifies that the cost of all cost centers that are associated with the ‘INDIRECT CC’ node will be allocated to the other direct cost centers based on the number of employees working for those cost centers.

Please note that the employee data that will be used for making the allocations are the same that have been used in the prior post. Making use of them does not require to import another Excel file with the statistical measure data or something alike. The only thing required is that a link between the statistical measure(s) and the cost accounting ledger is established. As this establishment and the related processing steps are identical to what has been shown in the previous post, those steps are skipped for reasons of brevity. The next screenprints document the allocations that result from the cost allocation policy shown above.

As in the prior posts, the following Excel screenprint summarizes the allocations made together with the basis values that were used for making those allocations.

The next post extends this one and shows how multiple cost object summary nodes can be used for making cost allocations. Till then.

← Older posts
Newer posts →

Communities4Future

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 Bank reconciliation Budgeting Controlling Cost accounting Cost accounting module Cost center accounting customer D365 D365FO Dynamics AX Dynamics AX 2012 Electronic reporting Email Environment Fixed asset statement General Ledger journal Global Warming indirect costs intercompany Inventory Inventory reconciliation invoice invoice recording IOT Management Accounting Management Reporter Modern Finance MS Flow MT940 PowerApps PowerAutomate PowerPlatform Project Project module Purchase Order 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

  • 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 569 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...