Headcount r
Hi all,
We’ve set up a UD1 member to account for headcount in our application. We have cost centers in our account dimension which we’re using in conjunction with the headcount UD1. The issue is th...
Forum Discussion
When you say you are using the UD1 to capturer Headcount, are you saying that the UD1 members are numbers like 1,2,3 that represents the number of folks or just the type of Headcount (Salary, Hourly,…). Also, how are you putting Cost Centers in the Account Dim. Is that Cost Center A as a parent with a number of children’s as accounts or you are not using the Account dim as Accounts at all. Making the Account Type = NonFinancial should keep currency from coming into play. You still want it to consolidate so you get summary numbers at the top.
Hi Clarke,
We have the parent of Headcount_Total then children Headcount_Filled and Headcount_Vacant as the UD1 members which are then populated with the headcount number by cost center (account dimension). We have CCs in the account dimension the same as accounts - they’re in the opex area of the income statement where costs are driven by CC instead of account. CC is the base member in those areas of the IS with accounts being the base members in other areas (for example, the balance sheet). The CCs then work in conjunction with the UD1s where the shared expense accounts exist (for example, salary, bonus, benefits, etc.).
We can’t make the account nonfinancial because it’s a cost center where real dollars exist.
Does that make sense? I know it’s a bit confusing so just let me know.
I assume you wouldn’t want to have a sibling cost center labeled _HC? You could use that for just headcount and make that non financial. It wouldn’t be the most elegant solution, but it would stop the translation issue. You could also create a USD entity for each of your foreign currency entities to load the headcount in. We did that for one of our clients who wanted to be able to make top-down adjustments without having to calculate the translation for foreign subsidiaries.
Hello!
Thanks for the suggestions but yes, we wouldn't want to duplicate all the cost centers just for headcounts as we have hundreds of cost center accounts. Similarly with the USD entity - that seems like too much extra master data in our case just for headcount tracking but good thinking outside the box!
