Pieter Esterhuizen - SBFC We run dummy scenarios (dummy payrolls) by creating a copy of our current company and then run the scenarios as if you are processing a payroll.  This way you don't need to worry about losing any live data etc.

Thanks Vone, that makes sense, but what if you need to do just a single dummy payslip for an employee that wants to add a Retirement Annuity contribution to his payslip? I find myself in many cases like this, Do you need to copy the whole payroll company for that single dummy payslip as well or is there another feature?

Pieter Esterhuizen - SBFC I keep the copy company updated on a regular basis, for example I have two sets of systems.  One we use for training, testing new items, trying new methods etc. and then I have my live system.  So at the end of each month, I make a backup of my live system and restore in the copy company for dummy payslip purposes.  Alternatively, you can make a backup of your live system, do the dummy payslip and restore the backup again, which isn't ideal if you are getting these on a regular basis.

Pieter Esterhuizen - SBFC I keep the copy company updated on a regular basis, for example I have two sets of systems.  One we use for training, testing new items, trying new methods etc. and then I have my live system.  So at the end of each month, I make a backup of my live system and restore in the copy company for dummy payslip purposes.  Alternatively, you can make a backup of your live system, do the dummy payslip and restore the backup again, which isn't ideal if you are getting these on a regular basis.

Thanks Vone, I like your idea to have an updated copy company available for these purposes you mentioned, I will approach my proposals to include that as a practical tool to demonstrate the implementation of employee benefits schemes or when working with individual employees. Thanks again