BEWARE: This operation initiates actions which should be considered irrevocable.
[ Nothing is irrevocable if you don't mind going through archive data files and stripping out manually but it is not recommended ].
What it does is :
- Check that there is a Monthly or Weekly Payroll
- Check that the period has been processed.
- Check that the Payroll Database has not been altered since the last "Payroll Processing" .
This and the following two checks is
to ensure that you don't inadvertently make changes to the structure of your payroll input that will not be reflected in the final payslips,
nominal analysis etc.
Payroll Database has been amended since last period processing
Re-run "Process Monthly/Weekly Payroll"
- Check that the Organisation Database has not been altered since the last "Payroll Process"
Organisation Database have been amended since last period processing
Re-run "Process Monthly/Weekly Payroll"
- Check that the Payment/Deduction Profiles have not been altered since the last "Payroll Process"
Payment/Deduction Profiles have been amended since last period processing
Re-run "Process Monthly/Weekly Payroll"
- If the payroll has passed the above checks you will see the next screen:
You are about to perform close-down for M1
Do you wish to continue (y/n)?
- Having hit "y" then the "dogs of war" are "unleashed". Reports for the period are moved to an archive .
- The file made by "Payroll/Input/Input " is processed so that those payments and deductions which have "keep"
as their "Retain" profile are stripped out and put into the next period's "in" file . The effect of this is that when you begin
"Input/Input" for the next period , these items will already be entered. The current month's "in" file is deleted.
- The period being "run down" becomes history and the next period becomes the "current" period