How does it work?
Mappings
In the Quick Pay Checker the mappings used define the scope for testing.
Mappings can be individual elements or balance values (e.g. Taxable Pay) or a mixture of both. Elements can be classified by type so that they can be grouped together when sorting, e.g. Earnings elements, Tax elements and Deduction elements. The mimimum requirement for the Quick Pay Checker is a mapping for Net Pay only.
For larger payrolls (>10000 employees) users may choose to first focus on categories of elements, e.g. Earnings elements first, then introduce Deduction elements later. For smaller payrolls a full list of individual element mappings can be used to give a more detailed comparison.
Group mapping options allow for one-to-many, many-to-one and many-to-many mapping relationships to exist in the element mappings. An Auto-group feature will automatically sort a mapping list into valid groups.
Additional mapping features also allow users to add individual tolerance settings to each mapping. Multiplication factors allow users to add factorisations to the data comparison, for instance to make a positive value match to a negative value.
Users can define dependencies, where one element is dependent on the result from another element (e.g. Tax Paid is dependent on Taxable Pay). If the primary element comparison has a difference, then the comparison will automatically associate a reason to the secondary element difference.
The Quick Pay Checker stores the element/balance mapping information and validates the data to ensure that the mappings are valid prior to any data comparison runs.
When all the initial element mappings have been completed and validated the Source Data from the old payroll system and the Target Data from the new payroll system can be added.
Print