This manual has been written to describe the operation of payrollBash - free
software to process UK payrolls within a gnu/linux operating environment .
It is not an instructional manual on payroll procedures and Inland Revenue
legislation and requirements. For a knowledge base on those issues then I can thoroughly recommend
visiting Inland Revenue and down-loading material freely available
in either PDF or HTML format.
The structure of your payroll will be determined by your operational requirements and
not , I trust , my pre-conceived assumptions. Nonetheless, before you implement your payroll it is
advisable to go through this manual and establish how you can leverage its capabilities - and
circumvent its weaknesses - to achieve your goals . Once you have gone through this manual and
created your own payroll I hope that you will only need to reference it in exceptional circumstances such as
a Director starting or resigning .
The manual has not been written in the same order as the "Main Menu"................
_____________________________________________________________________________
Soap plc : Payroll
"1" "Prepare input:Overtime/Payments/Deductions"
"2" "Process Monthly/Weekly Payroll"
"3" "View Error Log"
"4" "View Payslips"
"5" "View Nominal Analysis"
"6" "View Remittance Lists"
"7" "View P11Dtax schedules"
"8" "View P11Dni schedules"
"9" "Period-end run down"
"A" "Year-end run down"
"B" "Edit Organisation database"
"C" "Edit/Create payroll database"
"D" "Edit/Create payment/deduction profiles"
"E" "Run Health Check"
"F" "Back-up to floppy"
"G" "Manual"
"q" "Quit
Enter your choice : ->
_____________________________________________________________________________
but rather in the chronological order that the processes occur when you are creating and operating a payroll.
A training database has been supplied for you to experiment on . Feel free to subject it to as
much grief as you desire . This hopefully will give you confidence in the software and make
the process of learning the systems more fruitful . Furthermore you may uncover faults in my programming which will help in the "development" process.
If you "break" the programme please make a note of how you inflicted the
mortal blow/s and email me a damage report .
Indeed, If you have any comments and/or suggestions I'd be grateful for an email .