The impacts of percentage rules can be different from what you expect when you create Percentage type rules. This guide explains the origin of these differences.
Two elements are important to consider when choosing this type of rule:
The calculation mode chosen in the project: Headcount or FTE
The level at which the driver rules are entered
Calculation in headcount or FTE
When working on a project in Headcount mode, the results of the percentage impacts on the lowest level entities (i.e., at the intersection of the lowest level business, geo and orga segments) will necessarily be rounded to the nearest integer.
We advise you to switch your project to FTE mode in order to obtain more precise and accurate results. Indeed, in FTE, the results are rounded to two decimals.
Impact level of the rule
If you enter a percentage impact on a family of entities, Albert will in fact reflect this impact on all the sub-entities that make up this family. The results of each sub-entity are then rounded to the nearest integer if we are working in headcount, or to two decimals if we are working in FTEs, then aggregated to obtain the result for the family.
Thus, if family A has 100 people, and a driver rule with an impact of -2% is imputed to it, you might expect the final result to be 98. However, the 2% will in fact impact all the sub-entities of family A in the same way, namely A1, A2 and A3.
As mentioned earlier Albert rounds the impact results to the nearest integer when the project is in headcount.
Once again, we advise you to switch your project to FTE mode in order to obtain more precise and accurate results. Indeed, in FTE, the results are rounded to two decimals.