EMPLOYEE PAYROLL MANAGEMENT SYSTEM

PROJECT REPORT

Submitted to

UNIVERSITY OF MADRAS - CHENNAI 600 005

In partial fulfillment of the requirement for the award of the degree of

BACHELOR OF COMPUTER APPLICATIONS

Submitted by

1. Ms.B.ARTHI (Reg.No.212003178)

2. Ms.SUSMITHA SHAI (Reg.No.212003180)

3. Ms.G.SUMITHRA (Reg.No.212003328)

UNDER THE GUIDANCE OF

Ms.M.MARIAMMAL GLAXINA M.C.A., M.Phil.,

Assistant Professor, BCA Department

VEL TECH RANGA SANKU ARTS COLLEGE

(Affiliated to University Of Madras)
Avadi, Chennai – 600062.

APRIL 2023
 BONAFIDE CERTIFICATE

Certified that this report titled “ Employee Payroll Management System ” is a bonafide

record of the project work done by Sri / Kum ________________________________

under our supervision and guidance, towards partial fulfillment of the requirement for

award of the Degree of BCA of Veltech Ranga Sanku Arts College.

HEAD OF THE DEPARTMENT PROJECT GUIDE

The Viva-Voce Examination held on ____________________________ at

Veltech Ranga Sanku Arts College, Chennai – 600062.

INTERNAL EXAMINER EXTERNAL EXAMINER

 ABSTRACT

“Employee Database And Payroll Management System” is designed to make the

existing manual system automatic with the help of computerised equipment and full-

edged computer software, fulfilling their requirements, so that their valuable data

and information can be stored for a longer period with easy access and manipulation

of the same. The required software is easily available and easy to work with. This web

application can maintain and view computerised records without getting redundant

entries. The project describes how to manageuser data for good performance and

provide better services for the client.

 
 ACKNOWLEDGEMENT

I am privileged to spell my thanks to our beloved Chairman

Col.Prof. Rangrajan., Founder & Chancellor, Veltech Ranga Sanku Arts, College,

Avadi, Chennai for his constant support towards me. I am privileged to spell my thanks to

Mrs. K. Vijayakumari, ., Secretary, Veltech Ranga Sanku Arts College, Avadi,

Chennai for her interest in my growth and constant encouragement to do this project.

I wish to extend my gratitude to Prof. Dr. T. JEYACHANDRAN, Principal,

VELTECH RANGA SANKU ARTS COLLEGE, Avadi, Chennai for providing an

opportunity to do this project with constant encouragement.

I express my sincere thanks to Head of the Department

Ms.M.Mariammal Glaxina, Project Coordinator and Project Guide Ms.

Ms.M.Mariammal Glaxina , Asst.Professor, Department of Computer

Applications ,Veltech Ranga Sanku Arts College, Avadi Chennai for her constant support.

I also thank all the B.C.A Faculty members for their consultant help towards the

completion of the project. I take this opportunity to convey my profound thanks to all

those, who gave me assistance; it has been possible for me to complete this work.
 TABLE OF CONTENTS

Page No

LIST OF TABLES…………………………………………………….…..……....

LIST OF FIGURES….…………………………….……………………..……….

LIST OF SYMBOLS, ABBREVIATIONS…………..……………...…..……….

CHAPTERS

1. INTRODUCTION 1

1.1 System Overview….………….…………………………………..…................... 2

1.2 Objective………....……….………………………………………….….............. 4

1.3 Existing System….………………………………………………………….….... 5

1.4 Proposed System….…………………………………………………….…….…. 5

2. SYSTEM REQUIREMENT SPECIFICATION 15

2.1 Hardware Requirements……….…………...……………………..…................... 16

2.2 Software Requirements..…………...……………………..…............................... 19

2.3 Other Tools Requirements………….…………...……………………..…............ 20

3. SYSTEM DESIGN 22

3.1 System Architecture………………………...……………………..….................. 23

3.2 Data Flow Diagram………………………...……………………..…................... 30

4. IMPLEMENTATION

4.1 Program List……….………………………...……………………..….................. 35

4.2 Files or Tables…...….……………………...……………………..…................... 40

5. CONCLUSION AND FUTURE ENHANCEMENT 50

APPENDIX 52

Sample Code……………………………………………………………… 53

Screen Layouts…………………………………………………………… 54

Reports ………………………….………………………………………. 75

REFERENCES 80
 LIST OF TABLES

S. No Table No. Table Name Page No.

5
LIST OF FIGURES

S. No Figure No. Figure Name Page No.

5
 LIST OF SYMBOLS, ACRONYMS AND DEFINITIONS

SYMBOLS

Process

Flow of Data

State

Start

Stop

ABBREVIATIONS
10

CHAPTER 1
INTRODUCTION
11

1.INTRODUCTION

The proposed project “Employee Database and Payroll Management System” has been
developed to overcome the problems faced in the practicing of manual system. This software is
built to eliminate and in some cases reduce the hardships faced by the existing system. Moreover
this system is designed for particular need of the company to carry out its operations in a smooth
and effective manner. This web application is reduced as much as possible to avoid errors while
entering data. It also provides error message while entering invalid data. It is user-friendly as no
formal knowledge is required to use the system. Human resource challenges are faced by every
organization which has to be overcome by the organization. Every organization has different
employee and payroll management needs. Therefore I have design exclusive Employee and
payroll Management System that are adapted to the organization’s Managerial Requirements.

The main concept we cover in our system is manage employee detail, manage leave, Generate
monthly salary, Extra Allowance and Deduction. Admin is a responsible for operate whole
system. Admin has rights to Add new Employee, Each employee has a unique username and
password to login in to system. After login in to system all employee can apply for a leave with
valid reason. The admin can check leave and he can approve and reject employee leave.
According to approve leave the leave deduction will be deducted from salary.

At the time of generate salary we can manually set Travel Allowance, Medical
Allowance, Washing Allowance and Calculate HR and DA. Admin can generate and
view Employee Report, Leave Report, month wise salary report, year wise salary
report, Employee wise salary report. We have use crystal report for generate salary slip
of employee.

The Payroll Management System is a web application made in C# using

ASP.NET framework with the database. The main aim of the project is to pay the
employees perfectly without any delays.

Ø There are five modules and they are as follows,

• Employee Management
12

• Leave Module

• Allowance and Deduction

• Salary Module

• User Account
 Admin can add new class, add new employee and manage employee detail.
Each employee has unique username and password to operate the system.

 Employee can apply for leave after logging in to the system. Admin can
respond to the leave by approving or rejecting. Employee can check his leave
status if it is approved or rejected.

 At the time of salary generation Admin can set manually HR, DA, Travel,
Medical, and Washing Allowance for each employee. Leave will be deducted
from salary.

 Admin can generate month wise salary for each employee one by one and
generate salary pay slip.

Create new admin account with username and password for operate system
13

1.1SYSTEM OVERVIEW
The payroll management system has been developed for the organisation, keeping in view the
requirements of employees to prepare salary.The objective of the project was to computerize the
payroll system which was earlier being handled manually every precaution has been taken at
each process involved in the complex task of salary preparation.By computerization , it implies
that all process handling is entirely being done by computer.All the records necessary for the
processes involved in the salary calculation are stored in a computer based record keeping
system using a back-end tool.All the processes handling is done at the front-end by using a front-
end tool.The most important of the features are payslip generation and printing which provides
the user with the hard copies of the data also.

FEATURES
1. Preparation of salary.
2. Printing of windows based user-friendly software.
3. Maintenance of rich electronic records of employees.
4. Payslips.
5. Attendance record.
6. Standard report generation.
14

1.2OBJECTIVE
To overcome the limitations in “payroll management system” , we proposed a new system that is
a computerized system of “payroll management system”.The proposed system would store all
the information captured in different registers that will be linked with each other and will provide
direct and immediate access.Using a computerized system, we will do storing of data. All the
addition, deletion, modification, printing will be done through the computer for faster accessing.
This proposed system would set free from all the burdens mentioned in the limitations of the
existing system.

1. Fast and Efficient: As compared to the existing manual system, in the proposed system,
the user can get the information fast, easily and efficiently from the computer since
information is a single click away from the user.
2. Reliable and Accurate: As in the proposed system the information is stored and
processed in computers so that data will be more reliable and accurate.
3. Centralized Data: In the existing system most of the data records are kept in registers
and some data are maintained in Microsoft Excel due to this system the placement of the
data is not at one particular place. But in the proposed system, each and every record is
maintained on a computer, which leads to the centralization of data and every user which
have the access to the system can retrieve the data at ease.
4. Low Operation and Maintenance Cost: The proposed system is not very costly as it
doesn’t include any costs and overhead expenses like file management, stationary charges
etc.
5. Non-Redundant Information: As in proposed system data maintained on the computers
so inconsistency doesn’t occur whichever leads to a problem like duplication of data. As
in our project, most of the inventory codes are Auto Generated hence There is no chance
of duplication of the master records.

6. User-Friendly: the Proposed system is very user-friendly. We have applied many check
and balances (i.e. validation rules) in the proposed system so that a less knowledgeable
person can also enter the data error-free and at an ease.
7. Easy to Access: As compared to an existing system, in the proposed system the user can
easily and efficiently access the information from the computer only if the user is given
the right of the same. In the proposed system we have used the concept of level of access.
We have created the users to access the database. So depending upon the type of
hierarchy we can assign different rights for the user.
8. No Documentation: As everything is stored on the computer so there is any need for
documentation or maintaining the files or registers.
15

1.3EXISTING SYSTEM

This Organization is maintaining most of their day-to-day transactions data in the registers (i.e.
manually). The employees of the organization are doing the whole work manually.All the work
is done manually (i.e. maintained in registers) so different employees are appointed for the
maintenance of registers containing all the information related to the organization.It is very time
consuming and is also not error-free in some situations. In existing manual system databases
calculations are difficult to perform so report generation as very much difficult.

Drawbacks of Existing System

Generally, whenever we implement a new system it is developed to eliminate the shortcomings

of an existing system. The computerized system has more edge over the manual system. It is
because of accuracy, high speed, quick result, diligence etc. The existing system is totally based
on the manual system. The existing system has many drawbacks in comparison with the
computerized system.

1. Time Consuming: High time consumption is the main weakness of the existing

system. A lot of time is wasted in searching records from different files, which
resulted in the loss of time, and moreover, workload also increases. Also, a lot of
time is wasted in duplicating the same entries in different registers. The overall
checking of the records and modifications if necessary has to be made at several
places which is time-consuming and error-prone.
2. Service and Working Conditions: With the unusual delay due to various reasons
(such as non-availability of record or absence of an employee etc) the customer
suffers a lot. Without any firm reason, he has to wait which disfigures the working
conditions.
3. Difficulties in Retrieving Information: Sometimes, to get any of any type of
instant information more than one document needs to be searched. This requires
the opening of both files and then combining the information to get the required
information. Further, the files may not be indexed according to the need, which
causes difficulty in retrieving information.
4. Difficult for the Top Management to analyze data: Top management faces lots
of problems to know about the details of the Current Transactions, Current
Bookings, Current Cancellation, and Employee as all is maintained at the lower
level. Except for the media and their reliable resources they have nobody to ask
about the current outputs and the overall results to be generated along with the
reports at the end of the year.
5. Not Easy to understandable by new user: To understand the manual system the
user has to get more practice and have a grape all fields that help by other
employee and have to be in contact with that person. If the person was in leaving
the user can get the information from him.
16

6. Need more space to store: Here by using the paperwork system the user needs to
maintain all the documents in a proper way to avoid the difficulty in action and
need more space to store these documents because they can’t destroy the old
documents
7. Very Expensive: The existing manual system is a very expensive method as a lot
of paperwork has to be done and a lot of wastage of manpower, which increases
the expenses of the existing system.
8. Data sharing: The different user in the different department cannot share data
simultaneously.
9. The security feature is not prominent in the existing system.
17

1.4 PROPOSED SYSTEM

This consists of a Payroll System. All these transactions need to be carefully understood and
taken into consideration. The system also contains a lot of data redundancy at various stages.
One of the objectives of the new system would be to stores data in an efficient and non-
redundant form and hence increase the overall efficiency of the system.The new system should
ensure simple and easy data entry procedures through the suggestive looking form. There are
quite a number of lengthy calculations being done on the acquired data. These calculations
should be thoroughly understood. The new system should be able to perform all these
calculations automatically and efficiently.Numerous kinds of queries are done on large amounts
of accumulated data, to find out the desired data. The new system should provide efficient,
simple, fast and smarter procedures for retrieval of exhaustive types of data from the
database.Finally, there are quite a number of reports that are generated during the normal
working of the system. Each of these required reports should be understood very carefully and
the new system shall provide easy and efficient methods for generation of these reports.

Working

The working of the project is based on a payroll system for performing it’s working it use Visual
Basic.NET as a front-end and SQL as a back-end. In which user perform all its functions in the
Visual Basic.NET environment and all database stored in the database . This proposed system
reserve the ticket on request of the user and also refund the unconfirmed orders after lasing the
commission them. All the calculations are automatically and efficiently performed.The new
computerized system has an edge over the manual system. The beneficial features of the new
computerized system are the following:

1. Improves Services and Working Conditions: The proposed system improves the

existing working conditions in each step of inventory control system Customer services
are improved to a greater extent. The whole process is very easy and efficient.
2. User-Friendly: The new system is using windows as its runtime environment and is
developed using Visual Basic.NET which is a very user-friendly rapid application
development tool. The new system is totally graphical and the user just has to select his
desired option and the next step will be taken immediately and automatically by the
system.
3. Less Time Consumption: Another aspect of the system, which will reduce the time
consumption, is its speed. The speed of the system is measured in terms of response time
i.e. the time it takes to respond to user’s request. The computer is an electronic device
which can manipulate, modifies, retrieve and store information very speedily so it will be
able to report within a fraction of time.
18
19

CHAPTER 2

SYSTEM REQUIREMENT SPECIFICATION

20

2.1 HARDWARE REQUIREMENTS

Processor : Intel Pentium or more

Motherboard : Intel chipset motherboard

Ram. : 128MB or more

Cache. : 512kb

Harddisk. : 16 GB harddisk

Disk drive. : 1.44 Floppy disk drive

Monitor. : 1024*720 Display

21

2.2 SOFTWARE REQUIREMENTS

 Visual Studio 2017,

 SQL server management studio.

2.3 OTHER TOOLS REQUIRED

 ASP.NET,
 HTML,
 CSS,
 SQL sever(XAMPP).
1. HTML , CSS , Javascript , PHP , MySQL , XAMPP server had been used.
2. Javascript has been used for front end development since many years . Php has
been the popular language for connecting the front-end with the back-end.
3. MYSQL database is one of the most common database software used . Wamp
server is used to locally host the web-application in the machine for testing
purposes.
22

CHAPTER 3

SYSTEM DESIGN
23

3.SYSTEM DESIGN
Payroll Management System is an important activity in any organization. Payroll software has
been specially designed for automating payroll system. The Payroll Management System deals
with the financial aspects of employee’s salary, allowances, deductions and gross pay, net pay
etc. The outstanding benefit of Payroll Main aim of developing Employee Payroll and
Attendance Management System is to provide an easy way not only to automate all
functionalities involved. Biometrics identification systems are becoming common nowadays, but
to get there was not an easy task. Aside from offering competitive price for all its fingerprint.
Payroll system automates your company payroll, with keeping record of your employees and
their financial activities.

Fig1.1
24

3.1SYSTEM ARCHITECTURE

fig 1.2
25

3.2 DATA FLOW DIAGRAMS

The design involves the production of technical and visual prototypes. This stage has some non-
technical aspects such as gathering of content. For the server side programming and other
technical aspects of the design emphasis will be laid on such design concepts and principles as
effective modularity (high cohesion and low coupling), information hiding and stepwise
elaboration. The goal is to make the system easier to adapt, enhance, test and use.

Level-0 fig 1.3Level-1 fig 1.4

26

LEVEL 2 fig1.5
27

CHAPTER 4
IMPLEMENTATION
28

4 . IMPLEMENTATION
1. Open XAMPP panel path thispc/windows c/XAMPP (fig 1.6)

2. Start MYSQL and Click on the admin button the Php myadmin will open in the
internet browser.Import the source code from the thispc/windows
c/XAMPP/htdocs/payroll/DATABASE FILE.(fig1.7)
29

3.Enter localhost/payroll in the another page in the internet browser.the module for login site
opens.(fig1.8)

4.The admin site or the employee site can be opened by entering the login details.fig(1.9)
30

4.1 PROGRAM LIST

31

4.2 FILES OR TABLES

The Employee Payroll Management System Database consists of 11 tables. It has
the Department, Position, Allowances, Deductions, Attendance, Employee, Employee
Allowances, Employee Deductions, Payroll, Payroll Items/Payslip, and Users Tables.

1.The Department Table stores all the list of departments in the company. This table is connected
to both the Position and Employee tables. The data stored in this table helps to identify the
certain departments of the employees. (tab1.1)

FIELD NAME DESCRIPTION TYPE LENGTH

emp_id Department ID int 11

name Department Name TEXT  

2.The Position Table stores all the Employees' Positions in the company. Each of the positions is
connected to the department which means the position is only available for a certain Department.
(tab 1.2)

FIELD NAME DESCRIPTION TYPE LENGTH

emp_id Position ID int 11

department Department ID int 11

32

3.The Allowances Table stores all the allowances available for the company's

eemployees(tab1.3)

FIELD NAME DESCRIPTION TYPE LENGTH

emp_id Allowance ID int 11

allowance Allowance Name Text  

description Allowance's Description Text  

4.The Deductions Table stores all the allowances available for the company's employees.(tab
1.4)

FIELD NAME DESCRIPTION TYPE LENGTH

id (PK) Deduction ID int 11

deduction Deduction Name Text  

33

FIELD NAME DESCRIPTION TYPE LENGTH

description Deduction's Description Text  

5.The Employee Table stores the list of the employees of the company. This contains fields
about the basic personal information and employee's details to the company.(tab1.5)

FIELD NAME DESCRIPTION TYPE LENGTH

emp_id Employee ID int 11

employee_code Employee's Company ID Code varchar 100

firstname Employee's First Name varchar 250

middlename Employee's Middle Name varchar 250

lastname Employee's Last Name varchar 250

34

FIELD NAME DESCRIPTION TYPE LENGTH

department Department ID int 11

position Position ID int 11

salary Employee's Monthly Salary double  

6.The Employee Allowances Table store the list of allowances of each employee. Employees'

Allowances might be different to others and others might not have. This table contains a field
that helps the system to identify when (Monthly, Semi-Monthly) the system will add the other
earnings of the employee.(tab1.6)

FIELD NAME DESCRIPTION TYPE LENGTH

id _no Employee Allowance ID int 11

emp_id Employee ID int 11

35

FIELD NAME DESCRIPTION TYPE LENGTH

allowance Allowance ID int 11

type Payroll Type to Add the Allowance (Monthly) tinyint 1

amount Allowance Amount double  

7.The Employee Deductions Table store the list of deductions of each employee. Like the
Allowance Table, Employees Deduction might be different from others and others might not
have. This table contains a field that helps the system to identify if when (Monthly, Semi-
Monthly, or once) the system will deduct the amount to the certain employee.(tab1.7)
36

FIELD NAME DESCRIPTION TYPE LENGTH

id _no Employee Allowance ID int 11

emp_id Employee ID int 11

deduction Deduction ID int 11

type Payroll Type to deduct the Deduction (Monthly) tinyint 1

amount Deduction Amount double  

8.The Attendance Table stores all the attendances of the employees. Each employee will have 4
data per day in this table. This data could be the employees for Time-in, Lunch-out, After Lunch-
37

in, and Time-out. This also contains a DateTime log that will be used in calculating the rendered
working hours of the employees each working day.(tab1.8)

FIELD NAME DESCRIPTION TYPE LENGTH

id _no Attendance ID int 11

emp_id Employee ID int 11

Login&Logout Attendance Log Type (1 = Time IN, 2 = Time Out) tinyint 1

datetime Log's Date and Time Date  

38

9.The Payroll Table stores the payroll cut-offs of the company. The system relies on this table on
how to compute the employees' payslips. The system will also fetch the employees' attendances
between the cut-off's date range.(tab1.9)

FIELD NAME DESCRIPTION TYPE LENGTH

id _no Payroll ID int 11

date_from Payroll Cut-off start date Date  

date_to Payroll Cut-off end date Date  

date_created Date/Time when the data has been inserted DateTime  

10.The Payroll Item/Payslip Table stores the payslip details of each employee for a certain
payroll. This table contains the number of presents, absences, late of the employee.
The Allowances and Deductions JSON Data of employees is also stored in this table.(tab1.10)

FIELD NAME DESCRIPTION TYPE LENGTH

id _no Payslip ID int 11

emp_id Employee ID int 11

39

FIELD NAME DESCRIPTION TYPE LENGTH

present Employee's days of present tinyint 3

absent Employee's days of absences tinyint 3

salary Base Salary Amount of the Employee for the double  

certain Cut-off

allowance_amount Total Amount of the Employee's Allowance double  

allowances Employee's Allowances TEXT  

deduction_amount Total Amount of the Employee's Deduction double  

deductions Employee's deductions TEXT  

net Employee's NET Income double  

40

FIELD NAME DESCRIPTION TYPE LENGTH

date_created Date/Time when the data has been inserted DateTime  

11.Lastly, the Users Table. This table doesn't have any relation with the other tables above. This
table only stores the system users' credentials.(tab1.11)

FIELD NAME DESCRIPTION TYPE LENGTH

Id_no User ID int 11

name User Name TEXT  

username Username TEXT  

password User Password TEXT  

type User Type (1 = Admin, 2 = Staff) tinyint 1

41

CHAPTER 5
CONCLUSION AND FUTURE ENHANCEMENT
42

5.1 CONCLUSION

It is built for use in small scale organisation where the number of employees is
limited.According to the requested requirement the admin can add, manipulate, update or delete
all employee data in his organisation.The admin can add new departments and delete them.The
admin can also predefined paygrades for the employees.The required records can be easily
viewed by the admin anytime he wants in an instant.The payment of the employee is based on
monthly basis.The main objective of this project is to save time , make the system cost effective
and management records efficiently.
43

5.2 . FUTURE ENHANCEMENT

As a future work , some additional information could be implemented and integrated into the
application code making it much more reliable and flexible , especially what concerns a pay-roll
management module.Apparently , the role of such system is basic and essential within the
company that wants to keep a really good control and record concerning its personnel data ,
functionality and performance on all levels in its structure.Every organization , now a days has
the necessity of managing its staff on a really good level as the staff definetly the greatest merit
of building up a company as such as it is.The well managed employee means giving the
appropriate financial award-ness and all other kind of benefits as such they have been
deserved .That’s why the development of such systems is not just a programming business – a lot
of people are ordinarily involved in such projects and one of the basic requirements is the
reliability of the system , especially what concerns the storage of data and all of the operations
that will be performed upon it.
44

APPENDIX
45

SAMPLE CODE
-- phpMyAdmin SQL Dump

-- version 4.6.5.2

-- https://www.phpmyadmin.net/

--

-- Host: 127.0.0.1

-- Generation Time: Apr 14, 2021 at 06:35 PM

-- Server version: 5.6.21

-- PHP Version: 5.6.3

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

SET time_zone = "+00:00";

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;

/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;

/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;

/*!40101 SET NAMES utf8mb4 */;

--

-- Database: `payroll_mdb`

--

-- --------------------------------------------------------

--

-- Table structure for table `wy_admin`

--

CREATE TABLE `wy_admin` (

`admin_id` int(11) NOT NULL,

`admin_code` varchar(255) NOT NULL,

`admin_name` varchar(255) NOT NULL,

`admin_email` varchar(255) NOT NULL,

`admin_password` varchar(255) NOT NULL,

`admin_time` datetime NOT NULL

46

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--

-- Dumping data for table `wy_admin`

--

INSERT INTO `wy_admin` (`admin_id`, `admin_code`, `admin_name`, `admin_email`, `admin_password`, `admin_time`) VALUES

(1, 'WY00', 'Arthi', 'arthidevakar@gmail.com', '7c4a8d09ca3762af61e59520943dc26494f8941b', '2019-04-18 02:22:37');

-- --------------------------------------------------------

--

-- Table structure for table `wy_attendance`

--

CREATE TABLE `wy_attendance` (

`attendance_id` int(11) NOT NULL,

`emp_code` varchar(255) NOT NULL,

`attendance_date` date NOT NULL,

`action_name` enum('punchin','punchout') NOT NULL,

`action_time` time NOT NULL,

`emp_desc` varchar(255) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--

-- Dumping data for table `wy_attendance`

--

INSERT INTO `wy_attendance` (`attendance_id`, `emp_code`, `attendance_date`, `action_name`, `action_time`, `emp_desc`) VALUES

(2, 'WY01', '2021-04-13', 'punchin', '10:41:27', '21'),

(3, 'WY01', '2021-04-13', 'punchout', '17:37:36', '220'),

(4, 'WY02', '2021-04-14', 'punchin', '15:05:42', 'D114'),

(5, 'WY02', '2021-04-14', 'punchout', '22:19:14', 'out-144'),

(6, 'WY03', '2021-04-14', 'punchin', '10:30:30', 'IN'),

(7, 'WY03', '2021-04-14', 'punchout', '17:30:52', 'OUT'),

(8, 'WY04', '2021-04-14', 'punchin', '10:00:59', 'IS1'),

(9, 'WY04', '2021-04-14', 'punchout', '14:31:27', 'IS1'),

(10, 'WY05', '2021-04-14', 'punchin', '19:11:29', 'In'),

(11, 'WY05', '2021-04-14', 'punchout', '19:13:02', 'Outt');

47

-- --------------------------------------------------------

--

-- Table structure for table `wy_employees`

--

CREATE TABLE `wy_employees` (

`emp_id` int(11) NOT NULL,

`emp_code` varchar(255) NOT NULL,

`emp_password` varchar(255) NOT NULL,

`first_name` varchar(255) NOT NULL,

`last_name` varchar(255) NOT NULL,

`dob` varchar(255) NOT NULL,

`gender` enum('male','female') NOT NULL DEFAULT 'male',

`merital_status` varchar(255) NOT NULL,

`nationality` varchar(255) NOT NULL,

`address` longtext NOT NULL,

`city` varchar(255) NOT NULL,

`state` varchar(255) NOT NULL,

`country` varchar(255) NOT NULL,

`email` varchar(255) NOT NULL,

`mobile` varchar(255) NOT NULL,

`telephone` varchar(255) NOT NULL,

`identity_doc` varchar(255) NOT NULL,

`identity_no` varchar(255) NOT NULL,

`emp_type` varchar(255) NOT NULL,

`joining_date` varchar(255) NOT NULL,

`blood_group` varchar(255) NOT NULL,

`designation` varchar(255) NOT NULL,

`department` varchar(255) NOT NULL,

`pan_no` varchar(255) NOT NULL,

`bank_name` varchar(255) NOT NULL,

`account_no` varchar(255) NOT NULL,

`ifsc_code` varchar(255) NOT NULL,

`pf_account` varchar(255) NOT NULL,

`created` datetime NOT NULL

) ENGINE=MyISAM DEFAULT CHARSET=latin1;

48

--

-- Dumping data for table `wy_employees`

--

INSERT INTO `wy_employees` (`emp_id`, `emp_code`, `emp_password`, `first_name`, `last_name`, `dob`, `gender`, `merital_status`, `nationality`, `address`, `city`, `state`, `country`, `email`,
`mobile`, `telephone`, `identity_doc`, `identity_no`, `emp_type`, `joining_date`, `blood_group`, `designation`, `department`, `pan_no`, `bank_name`, `account_no`, `ifsc_code`, `pf_account`,
`created`) VALUES

(01, 'WY01', '5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8', 'Arthi', 'Divakar', '07/10/2002', 'female', 'Single', 'Indian', 'Phuzal', 'Chennai', 'Tamilnadu', 'India', 'Arthidevakar@gmail.com',
'2457878540', '014577854', 'Passport', '012345678', 'Permanent position', '01/29/2019', 'B+', 'Developer', 'WEB', '14785424', 'Demo Bank', '012457854512', '12458', '11452', '2021-04-12
13:54:49'),

(02, 'WY02', '7c4a8d09ca3762af61e59520943dc26494f8941b', 'Susmithra', 'G', '04/01/2002', 'female', 'Registered partnership', 'Indian', 'Chennai', 'Chennai', 'Tamilnadu', 'India',
'susmithra888@gmail.com', '2450157695', '1245785540', 'Passport', '914575421', 'Permanent position', '04/01/2020', 'AB+', 'Chief Marketing Officer', 'Marketing', '2014578540', 'Grand Summit
Bank Inc.', '69529712540', 'GRSB0069961', 'GB LAD 054110 000 000542', '2021-04-14 13:18:32'),

(03, 'WY03', '5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8', 'Susmitha', 'Shai', '04/20/2003', 'female', 'Single', 'Indian', 'Chennai', 'Chennai', 'Tamilnadu', 'India', 'shaisusmitha@gmail.com',
'4578545555', '4547854520', 'Passport', '100035420', 'Part-time employee', '04/01/2021', 'A+', 'Executive Assistant', 'General', '1450578569', 'Crest Bank', '87529722555', 'CBSB0096960', 'CB
LAD 094169 000 000111', '2021-04-14 14:23:30'),

(04, 'WY04', '5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8', 'Manoj', 'Naidu', '01/20/2003', 'male', 'Registered partnership', 'Indian', 'Madurai', 'Madurai', 'Tamilnadu', 'India',
'manojnaidu566@gmail.com', '3457856970', '1045786310', 'Passport', '321457852', 'Intern', '04/14/2021', 'A-', 'Internship Period', 'IT', '2222060446', 'Federal Bank', '273794443158',
'FBSB00139980', 'FB LAD 033385 000 000135', '2021-04-14 15:49:34'),

(05, 'WY05', '5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8', 'pooja', 'Divakar', '07/29/2004', 'female', 'Single', 'Indian', 'Chennai', 'Chennai', 'Tamilnadu', 'India', 'pooja88d@gmail.com',
'3247548880', '2457778540', 'Passport', '245785000', 'Permanent position', '10/15/2020', 'B+', 'Chief Technology Officer', 'IT', '425569690', 'Centreville Bank', '4201483626', 'CVCB0011377', 'CB
LAD 032425 000 000753', '2021-04-14 19:22:17'),

(06, 'WY06', '5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8', 'Pushpa', 'B', '06/01/1982', 'female', 'Married', 'Indian', 'Phuzal', 'Chennai', 'Tamilnadu', 'India', 'Pushpa223@gmail.com',
'2457878540', '014577854', 'Passport', '012345678', 'Permanent position', '01/29/2019', 'B+', 'Developer', 'WEB', '14785424', 'Demo Bank', '012457854512', '12458', '11452', '2021-04-12
13:54:49'),

(07, 'WY07', '7c4a8d09ca3762af61e59520943dc26494f8941b', 'Radhika', 'D', '04/01/1985', 'female', 'Registered partnership', 'Indian', 'Chennai', 'Chennai', 'Tamilnadu', 'India',
'radhika888@gmail.com', '2450157695', '1245785540', 'Passport', '914575421', 'Permanent position', '04/01/2020', 'AB+', 'Chief Marketing Officer', 'Marketing', '2014578540', 'Grand Summit
Bank Inc.', '69529712540', 'GRSB0069961', 'GB LAD 054110 000 000542', '2021-04-14 13:18:32'),

(08, 'WY08', '5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8', 'Lahari', 'D', '04/20/2005', 'female', 'Single', 'Indian', 'Chennai', 'Chennai', 'Tamilnadu', 'India', 'laharinaidu@gmail.com',
'4578545555', '4547854520', 'Passport', '100035420', 'Part-time employee', '04/01/2021', 'A+', 'Executive Assistant', 'General', '1450578569', 'Crest Bank', '87529722555', 'CBSB0096960', 'CB
LAD 094169 000 000111', '2021-04-14 14:23:30'),

(09, 'WY09', '5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8', 'Sai', 'Prasad', '01/20/2006', 'male', 'Registered partnership', 'Indian', 'Madurai', 'Madurai', 'Tamilnadu', 'India',
'prasad566@gmail.com', '3457856970', '1045786310', 'Passport', '321457852', 'Intern', '04/14/2021', 'A-', 'Internship Period', 'IT', '2222060446', 'Federal Bank', '273794443158', 'FBSB00139980',
'FB LAD 033385 000 000135', '2021-04-14 15:49:34'),

(10, 'WY10', '5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8', 'Nikitha', 'Naidu', '07/29/2005', 'female', 'Single', 'Indian', 'Chennai', 'Chennai', 'Tamilnadu', 'India', 'nikitha888d@gmail.com',
'3247548880', '2457778540', 'Passport', '245785000', 'Permanent position', '10/15/2020', 'B+', 'Chief Technology Officer', 'IT', '425569690', 'Centreville Bank', '4201483626', 'CVCB0011377', 'CB
LAD 032425 000 000753', '2021-04-14 19:22:17');

-- --------------------------------------------------------

--

-- Table structure for table `wy_holidays`

--

CREATE TABLE `wy_holidays` (

`holiday_id` int(11) NOT NULL,

`holiday_title` varchar(255) NOT NULL,

`holiday_desc` varchar(255) NOT NULL,

`holiday_date` varchar(50) NOT NULL,

`holiday_type` enum('compulsory','restricted') NOT NULL DEFAULT 'compulsory'

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

49

--

-- Dumping data for table `wy_holidays`

--

INSERT INTO `wy_holidays` (`holiday_id`, `holiday_title`, `holiday_desc`, `holiday_date`, `holiday_type`) VALUES

(7, 'Holka Dahana', 'Holi', '03/07/2023', 'compulsory'),

(8, 'Holi', 'Holi', '03/08/2023', 'restricted'),

(21, 'March Equinix', 'Equinix', '03/21/2023', 'compulsory'),

(22, 'Ugadi', 'Ugadi', '03/22/2023', 'restricted'),

(30, 'Rama Navami', 'Navami', '03/30/2023', 'compulsory');

-- --------------------------------------------------------

--

-- Table structure for table `wy_leaves`

--

CREATE TABLE `wy_leaves` (

`leave_id` int(11) NOT NULL,

`emp_code` varchar(255) NOT NULL,

`leave_subject` varchar(255) NOT NULL,

`leave_dates` varchar(255) NOT NULL,

`leave_message` longtext NOT NULL,

`leave_type` varchar(255) NOT NULL,

`leave_status` enum('pending','approve','reject') NOT NULL DEFAULT 'pending',

`apply_date` datetime NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--

-- Dumping data for table `wy_leaves`

--

INSERT INTO `wy_leaves` (`leave_id`, `emp_code`, `leave_subject`, `leave_dates`, `leave_message`, `leave_type`, `leave_status`, `apply_date`) VALUES

(1, 'WY01', 'Requesting for leave days', '02/13/2023', 'this is a demo leave message', 'Sick Leave', 'approve', '2023-02-13 10:09:02'),

(3, 'WY03', 'Leave for 2 days', '02/15/2023,02/17/2023', 'Dear admin, i\'d like to apply leave for 2 days as i\'ve been a regular employee since my first day at office. And now, i finally got to rest
and spend some time with my family too!', 'Casual Leave', 'reject', '2023-02-14 15:47:06'),

(5, 'WY05', 'Leave for a week', '02/15/2023,02/23/2023', 'i wont be able to join office as i\'ve been suffering from a rough common cold and fever. so, i\'d like to request a leave for week', 'Sick
Leave', 'approve', '2023-02-14 19:15:11');
50

-- --------------------------------------------------------

--

-- Table structure for table `wy_payheads`

--

CREATE TABLE `wy_payheads` (

`payhead_id` int(11) NOT NULL,

`payhead_name` varchar(255) NOT NULL,

`payhead_desc` varchar(255) NOT NULL,

`payhead_type` enum('earnings','deductions') NOT NULL DEFAULT 'earnings'

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--

-- Dumping data for table `wy_payheads`

--

INSERT INTO `wy_payheads` (`payhead_id`, `payhead_name`, `payhead_desc`, `payhead_type`) VALUES

(1, 'Basic Salary', 'Basic Salary', 'earnings'),

(2, 'Dearness Allowance', 'Dearness Allowance', 'deductions'),

(3, 'House Rent Allowance', 'House Rent Allowance', 'deductions'),

(4, 'Conveyance Allowance', 'Conveyance Allowance', 'deductions'),

(5, 'Medical Allowance', 'Medical Allowance', 'deductions'),

(7, 'Overtime', 'Overtime', 'earnings'),

(8, 'Traveling Expenses', 'Traveling Expenses', 'earnings'),

(9, 'Loans & Advance', 'Loans & Advance', 'earnings'),

(10, 'Other Allowance', 'Other Allowance', 'earnings'),

(11, 'Professional Tax', 'Professional Tax', 'deductions'),

(12, 'Income Tax', 'Income Tax', 'deductions'),

(13, 'Employee Provident Fund', 'Employee Provident Fund', 'deductions'),

(14, 'Loans & Advance', 'Loans & Advance', 'deductions');

-- --------------------------------------------------------

--

-- Table structure for table `wy_pay_structure`

--
51

CREATE TABLE `wy_pay_structure` (

`salary_id` int(11) NOT NULL,

`emp_code` varchar(255) NOT NULL,

`payhead_id` int(11) NOT NULL,

`default_salary` float(11,2) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--

-- Dumping data for table `wy_pay_structure`

--

INSERT INTO `wy_pay_structure` (`salary_id`, `emp_code`, `payhead_id`, `default_salary`) VALUES

(129, 'WY01', 1, 56000.00),

(130, 'WY01', 2, 600.00),

(131, 'WY01', 3, 2400.00),

(132, 'WY01', 4, 500.00),

(133, 'WY01', 5, 800.00),

(136, 'WY01', 8, 1200.00),

(137, 'WY01', 9, 750.00),

(138, 'WY01', 10, 600.00),

(139, 'WY01', 11, 3500.00),

(140, 'WY01', 12, 1740.00),

(141, 'WY01', 13, 350.00),

(142, 'WY01', 14, 1750.00),

(143, 'WY02', 1, 44000.00),

(144, 'WY02', 2, 550.00),

(145, 'WY02', 3, 1500.00),

(146, 'WY02', 4, 600.00),

(147, 'WY02', 5, 1000.00),

(150, 'WY02', 8, 1250.00),

(151, 'WY02', 9, 800.00),

(152, 'WY02', 10, 500.00),

(153, 'WY02', 11, 2700.00),

(155, 'WY02', 12, 1400.00),

(156, 'WY02', 13, 400.00),

(158, 'WY03', 1, 42500.00),

(159, 'WY03', 2, 600.00),

(160, 'WY03', 3, 1800.00),

(161, 'WY03', 4, 500.00),

52

(162, 'WY03', 5, 650.00),

(165, 'WY03', 8, 1200.00),

(166, 'WY03', 9, 650.00),

(167, 'WY03', 10, 500.00),

(168, 'WY03', 11, 2200.00),

(169, 'WY03', 12, 1250.00),

(170, 'WY03', 13, 560.00),

(172, 'WY04', 1, 40000.00),

(173, 'WY04', 2, 500.00),

(174, 'WY04', 3, 1600.00),

(175, 'WY04', 4, 500.00),

(176, 'WY04', 5, 850.00),

(179, 'WY04', 8, 1400.00),

(180, 'WY04', 9, 950.00),

(181, 'WY04', 10, 650.00),

(182, 'WY04', 11, 2100.00),

(183, 'WY04', 12, 1150.00),

(184, 'WY04', 13, 450.00),

(186, 'WY06', 1, 42000.00),

(187, 'WY06', 2, 450.00),

(188, 'WY06', 3, 1550.00),

(189, 'WY06', 4, 500.00),

(190, 'WY06', 5, 6700.00),

(193, 'WY06', 8, 1350.00),

(194, 'WY06', 9, 780.00),

(195, 'WY06', 10, 620.00),

(196, 'WY06', 11, 2100.00),

(197, 'WY06', 12, 1250.00),

(198, 'WY06', 13, 750.00),

(200, 'WY07', 1, 38000.00),

(201, 'WY07', 2, 550.00),

(202, 'WY07', 3, 1500.00),

(203, 'WY07', 4, 500.00),

(204, 'WY07', 5, 850.00),

(207, 'WY07', 8, 1500.00),

(208, 'WY07', 9, 700.00),

(209, 'WY07', 10, 500.00),

(210, 'WY07', 11, 1950.00),

(211, 'WY07', 12, 1100.00),

53

(212, 'WY07', 13, 550.00),

(214, 'WY08', 1, 38000.00),

(215, 'WY08', 2, 550.00),

(216, 'WY08', 3, 1500.00),

(217, 'WY08', 4, 500.00),

(218, 'WY08', 5, 850.00),

(221, 'WY08', 8, 1500.00),

(222, 'WY08', 9, 700.00),

(223, 'WY08', 10, 500.00),

(224, 'WY08', 11, 1950.00),

(225, 'WY08', 12, 1100.00),

(226, 'WY08', 13, 550.00),

(228, 'WY09', 1, 36000.00),

(229, 'WY09', 2, 500.00),

(230, 'WY09', 3, 1400.00),

(231, 'WY09', 4, 450.00),

(232, 'WY09', 5, 800.00),

(235, 'WY09', 8, 1400.00),

(236, 'WY09', 9, 650.00),

(237, 'WY09', 10, 500.00),

(238, 'WY09', 11, 1900.00),

(239, 'WY09', 12, 1050.00),

(240, 'WY09', 13, 500.00),

(242, 'WY10', 1, 36000.00),

(243, 'WY10', 2, 500.00),

(244, 'WY10', 3, 1400.00),

(245, 'WY10', 4, 450.00),

(246, 'WY10', 5, 800.00),

(249, 'WY10', 8, 1400.00),

(250, 'WY10', 9, 650.00),

(251, 'WY10', 10, 500.00),

(252, 'WY10', 11, 1900.00),

(253, 'WY10', 12, 1050.00),

(254, 'WY10', 13, 500.00),

(256, 'WY05', 1, 32000.00),

(257, 'WY05', 2, 400.00),

(258, 'WY05', 3, 1200.00),

(259, 'WY05', 4, 400.00),

(260, 'WY05', 5, 700.00),

54

(263, 'WY05', 8, 1200.00),

(264, 'WY05', 9, 550.00),

(265, 'WY05', 10, 450.00),

(266, 'WY05', 11, 1750.00),

(269, 'WY05', 12, 950.00),

(270, 'WY05', 13, 400.00);

-- --------------------------------------------------------

--

-- Table structure for table `wy_salaries`

--

CREATE TABLE `wy_salaries` (

`salary_id` int(11) NOT NULL,

`emp_code` varchar(255) NOT NULL,

`payhead_name` varchar(255) NOT NULL,

`pay_amount` float(11,2) NOT NULL,

`earning_total` float(11,2) NOT NULL,

`deduction_total` float(11,2) NOT NULL,

`net_salary` float(11,2) NOT NULL,

`pay_type` enum('earnings','deductions') NOT NULL,

`pay_month` varchar(255) NOT NULL,

`generate_date` datetime NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--

-- Dumping data for table `wy_salaries`

--

INSERT INTO `wy_salaries` (`salary_id`, `emp_code`, `payhead_name`, `pay_amount`, `earning_total`, `deduction_total`, `net_salary`, `pay_type`, `pay_month`, `generate_date`) VALUES

(244, 'WY01', 'Basic Salary', 45000.00, 45000.00, 0.00, 45000.00, 'earnings', 'January, 2023', '2023-02-01 13:48:19'),

(245, 'WY03', 'Overtime', 5500.00, 39500.00, 0.00, 39500.00, 'earnings', 'January, 2023', '2023-02-01 16:09:02'),

(246, 'WY03', 'Basic Salary', 34000.00, 39500.00, 0.00, 39500.00, 'earnings', 'January, 2023', '2023-03-01 16:09:02'),

(247, 'WY02', 'Basic Salary', 51500.00, 58000.00, 5510.00, 52490.00, 'earnings', 'Febraury, 2023', '2023-03-01 19:17:13'),

(248, 'WY05', 'Overtime', 6500.00, 58000.00, 5510.00, 52490.00, 'earnings', 'Febraury, 2023', '2021-03-01 19:17:13'),
55

(249, 'WY05', 'Income Tax', 5510.00, 58000.00, 5510.00, 52490.00, 'deductions', 'Febraury, 2023', '2023-03-01 19:17:14'),

(250, 'WY04', 'Basic Salary', 39000.00, 44600.00, 4250.00, 40350.00, 'earnings', 'February, 2023', '2023-03-01 19:22:25'),

(251, 'WY04', 'Overtime', 5600.00, 44600.00, 4250.00, 40350.00, 'earnings', 'February, 2023', '2023-03-01 19:22:25'),

(252, 'WY04', 'Income Tax', 4250.00, 44600.00, 4250.00, 40350.00, 'deductions', 'February, 2023', '2023-03-01 19:22:25');

--

-- Indexes for dumped tables

--

--

-- Indexes for table `wy_admin`

--

ALTER TABLE `wy_admin`

ADD PRIMARY KEY (`admin_id`),

ADD UNIQUE KEY `admin_email` (`admin_email`),

ADD UNIQUE KEY `admin_code` (`admin_code`);

--

-- Indexes for table `wy_attendance`

--

ALTER TABLE `wy_attendance`

ADD PRIMARY KEY (`attendance_id`),

ADD KEY `emp_code` (`emp_code`);

--

-- Indexes for table `wy_employees`

--

ALTER TABLE `wy_employees`

ADD PRIMARY KEY (`emp_id`),

ADD UNIQUE KEY `emp_code` (`emp_code`);

--

-- Indexes for table `wy_holidays`

--

ALTER TABLE `wy_holidays`

ADD PRIMARY KEY (`holiday_id`);

--

-- Indexes for table `wy_leaves`

56

--

ALTER TABLE `wy_leaves`

ADD PRIMARY KEY (`leave_id`);

--

-- Indexes for table `wy_payheads`

--

ALTER TABLE `wy_payheads`

ADD PRIMARY KEY (`payhead_id`);

--

-- Indexes for table `wy_pay_structure`

--

ALTER TABLE `wy_pay_structure`

ADD PRIMARY KEY (`salary_id`),

ADD KEY `emp_code` (`emp_code`),

ADD KEY `payhead_id` (`payhead_id`);

--

-- Indexes for table `wy_salaries`

--

ALTER TABLE `wy_salaries`

ADD PRIMARY KEY (`salary_id`),

ADD KEY `emp_code` (`emp_code`);

--

-- AUTO_INCREMENT for dumped tables

--

--

-- AUTO_INCREMENT for table `wy_admin`

--

ALTER TABLE `wy_admin`

MODIFY `admin_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;

--

-- AUTO_INCREMENT for table `wy_attendance`

--

ALTER TABLE `wy_attendance`

MODIFY `attendance_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=12;

57

--

-- AUTO_INCREMENT for table `wy_employees`

--

ALTER TABLE `wy_employees`

MODIFY `emp_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=11;

--

-- AUTO_INCREMENT for table `wy_holidays`

--

ALTER TABLE `wy_holidays`

MODIFY `holiday_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=22;

--

-- AUTO_INCREMENT for table `wy_leaves`

--

ALTER TABLE `wy_leaves`

MODIFY `leave_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;

--

-- AUTO_INCREMENT for table `wy_payheads`

--

ALTER TABLE `wy_payheads`

MODIFY `payhead_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=16;

--

-- AUTO_INCREMENT for table `wy_pay_structure`

--

ALTER TABLE `wy_pay_structure`

MODIFY `salary_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=141;

--

-- AUTO_INCREMENT for table `wy_salaries`

--

ALTER TABLE `wy_salaries`

MODIFY `salary_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=253;

/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;

/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

SCREEN LAYOUTS
58

ADMIN’S SITE: Attendance :fig 1.10

Employee session: fig 1.11

59

Salaries:fig 1.12

Leave management:fig 1.13

60

Pay heads : fig 1.14

Holidays:fig 1.15
61

Salary slip : fig 1.16

Leave :fig 1.17

62

Holidays :fig 1.18

63

REFERENCES
1. www.researchgate.net/publication/49619781_A_System_for_Payroll_Management
2. www.tutorialspoint.com/csharp
3. Retrieved from Payroll Management Definition:
http://www.entrepreneur.com/encyclopedia/term/82350.html
4. Retrieved from Orange Technolab Website:
http://www.payrollsoftware.co.in/payrollsoftware.htm
5. Retrieved from Makerere University Research Repository:
http://dspace.mak.ac.ug/bitstream/123456789/635/3/kanobe-fredrick-cit-masters-
report.pd
6. Michael Halvorson, Microsoft Visual Basic 2012.
7. https://en.m.wikipedia.org/wiki/Payroll
8. https://en.m.wikipedia.org/wiki/Absence_management
9. https://youtube.com/@CodeAstro