This post was originally published on this site
Sometimes we encounter complex customer requirements that involve a little more creativity to problem-solve. Recently, a client requested that they needed actual employee historical data for budget calculations while using point in time data for calculating employee incentive outcomes, and they wanted to utilise standard functionality available in the Compensation module for multiple lumpsum components. With a stand-alone variable pay solution, a requirement like this this presents a bit of a challenge. Point in time calculations (where all data is derived on a single date) is possible. Date driven time slice calculations using standard employee history data over a period of time is possible. But having some data as at a point in time and some data over a time period, that’s complicated. And to further compound that complication, my customer wanted to utilise the standard lumpsum fields and functionality in the Compensation module to assign guidelines and rules.
Such a requirement usually results in an Employee Central (EC) solution with complex rules and custom fields. It’s a difficult sell for the compensation team who need to convince internal stakeholders to amend/build/tweak existing working EC configuration.
The Total Compensation template was our solution.
A typical use case for a Total Compensation template is
