PAYROLL MANAGEMENT SYSTEM

A PROJECT REPORT

Submitted by

[Link] (REG. NO: 953723104111)

[Link] (REG. NO: 953723104106)

in partial fulfillment for the award of the degree of

BACHELOR OF ENGINEERING IN

COMPUTER SCIENCE AND ENGINEERING

AAA COLLEGE OF ENGINEERING AND TECHNOLOGY

SIVAKASI

ANNA UNIVERSITY:: CHENNAI 600 025

MAY 2025

i
 BONAFIDE CERTIFICATE

Certified that this project report “PAYROLL MANAGEMENT

SYSTEM” is the bonafide work of “VAISHALINI V([Link]),
SUMITHRA M(Reg. No: 953723104106)” who carried out the project work under
my supervision.

SIGNATURE SIGNATURE
Dr. J. Hemalatha, M.E., Ph.D., Ms. K. Anuradha, M.E.,

HEAD OF THE DEPARTMENT SUPERVISOR

Professor Assistant Professor
Computer Science & Engineering Computer Science & Engineering

AAA College of Engg. & Tech., AAA College of Engg. & Tech.,
Sivakasi –626 005 Sivakasi – 626 005
Virudhunagar District Virudhunagar District

Submitted for the project viva-voce examination to be held on

INTERNAL EXAMINER EXTERNAL EXAMINER

ii
 ACKNOWLEDGEMENT

First and foremost, we praise and thank “The Almighty”, the lord of all creations,
who by his abundant grace has sustained us and helped us to work on this project
successfully.

We really find unique pleasure and immense gratitude in thanking our respected
management members, who is the backbone of our college.

A deep bouquet of thanks to respected Principal Dr. M. Sekar, M.E., Ph.D.,

for having provided the facilities required for our project.

We sincerely thank our Head of the Department Dr. J. Hemalatha, M.E., Ph.D.,

Professor & Head, Department of Computer Science and Engineering, for her guidance and
support throughout the project.

We extremely thank our project coordinator Ms. K. Anuradha, M.E., Assistant

Professor, Department of Computer Science and Engineering, who inspired us and supported
us throughout the project.

We also thank our guide Ms. K. Anuradha, M.E., Assistant Professor, Department of
Computer Science and Engineering for her valuable guidance and it is great privilege to
express our gratitude to her.

We extend our heartfelt thanks and profound gratitude to all the faculty members of
Computer Science and Engineering department for their kind help during our project work.

We also thank our parents and our friends who had been providing us with constant
support during the course of the project work.

iii
 ABSTRACT

This project outlines the development of a robust Payroll Management

System (PMS) designed to streamline and automate the complex processes involved in
calculating employee wages, deductions, and taxes. The system aims to replace manual
payroll processes, which are prone to errors and inefficiencies, with a more efficient and
reliable digital solution. The core functionality of the PMS includes features for employee
data management (e.g., personal information, employment details, and benefits),
attendance tracking, leave management, and payroll calculation. The system will be
capable of handling various pay structures, including salary, hourly wages, and
commissions, and will automatically calculate and withhold taxes according to local
regulations. Furthermore, the PMS will offer reporting capabilities to generate detailed
payroll reports, including individual employee pay stubs and summaries for accounting
and tax purposes. The PMS will also feature user management, with different access levels
for administrators, HR personnel, and employees. Administrators will have full control
over the system, while HR personnel will manage employee data and attendance, and
employees will be able to view their pay stubs and other relevant information. The
project's implementation will involve a user-friendly interface, ensuring ease of use for all
stakeholders. By automating payroll processing, this PMS will reduce manual labor,
improve accuracy, and enhance efficiency in the organization's financial operations. The
system will also contribute to compliance with payroll regulations, reduce the risk of errors
and disputes, and provide valuable insights into employee compensation and payroll
costs. Ultimately, this project aims to deliver a powerful and versatile PMS that will help
organizations effectively manage their payroll operations and contribute to their overall
financial success.

iv
 TABLE OF CONTENTS

S. NO TITLE PAGE NO
ABSTRACT iv

LIST OF ABBREVIATIONS vi

LIST OF FIGURES vii

1 INTRODUCTION
1.1 Overview 1
1.2 Payroll management system 2
1.3 Application of payroll management system 3
1.4 Problem of the manual system 3
2 LITERATURE REVIEW
2.1 Existing System 4
2.2 Limitations of Existing System 5
2.3 Proposed System 6
2.4 Advantages of Proposed System 7
3 SYSTEM DESIGN
3.1 System Architecture 8
3.2 Interface 16
4 SYSTEM REQUIREMENT
4.1 Hardware Requirement 22
4.2 Software Requirement 22
5 SYSTEM IMPLEMENTATION
5.1 Testing 23
5.2 System implementation requirements 24
5.3 Maintenance 25

6 RESULT 37

7 CONCLUSION 40

8 REFERENCES 41

9 OUTCOMES 42

v
 LIST OF ABBREVIATIONS

PMS - Payroll Management System

PHP - Hypertext Processor

MySQL- My Structured Query Language

HTML - Hyper Text Markup Language

CSS - Cascading Style Sheet

DFD - Data Flow Diagram

ER - Entity Relationship

ERM - Entity Relationship Model

vi
 LIST OF FIGURES

FIG NO TITLE PAGE NO

3.1.1 Flowchart 11

3.1.2 Flowchart 12

3.1.3 Symbols in DFD 13

3.1.4 DFD for PMS 14

3.1.5 ER Diagram 15

6.1 Login page 37

6.2 Employee details page 37

6.3 Employee details page 38

6.4 Grade details page 38

6.5 Employee salary details page 39

6.6 Employee report page 39

vi
 CHAPTER 1
INTRODUCTION

1.1 OVERVIEW
Payroll management system explain itself that it’s an accounting package
that will provide a financial solutions for a particular organization or for a particular
institutional body. This payroll management helps accounts to maintain all records by
using predefined rules set by the organization working pattern.

Its admin module has been developed in such a pattern that allows to
change the working rules any time as per the business requirement. Its automatic rates and
salary are fixed which saves processing time for preparing final ledger. Admin will only
have to fill the database with only employee’s details and select their type of work and
their post and final report will be prepared by the generation module.

As codes has been developed by using the concepts of object oriented

programming so, coding reusability can easily be achieved. Even if there will be changes
to made in future, it can be performed by the technical person within few seconds just by
changing the working rules. All working departments within the organization will share
the common file to access the particular data, so there is no chance of data redundancy and
helping in maintaining data consistency.

Each working section can be done by selecting only options and its graphical
user interface will make the system unique as compared to other system .

1
1.2 PAYROLL MANAGEMENT SYSTEM

Employee payroll Management is an application that a company maintains in order to

give a modern effective management for maintenance of records.

A computerization of company Maintenance is of great significance for making the

cumbersome process of employee payroll records maintenance as simple as possible using
structured and modular design.

Due to spurting of many books the record maintenance of employee’s has grown
considerably. Though the whole work cannot be claimed to be project, the main purpose of
this work is record maintenance and pay slip generation.

This project helps to change all the manual information into computerization. In
“PAYROLL MANAGEMENT SYSTEM,” a big number of registers are supposed to
maintain. And staff will always rely on the big manual register. But if the system is
computerized then staff can easily handle the account of each and every employee working
in the company. Maintaining the records for longer period is very difficult, space and time
consuming.

Programmer should understand the working of the whole system before starting the
project. If the working is not clearly defined, then it may possible that the project produces
the result not according to the requirement of the user. So, it is important for creating a
successfully and robust project that the problem the user for which the project has to
developed should be clearly defined to the programmer. After identifying the need of the
potential system, I have developed this project and it tries to accommodate all the need of the
existing system.

Company Management receives and maintains data of employee working. It produces

payroll slips.

2
 1.3 APPLICATION OF PMS

1. Payroll Management

2. Time and Attendance Tracking

3. Employee Finance Management

4. Employee Finance Management

5. Compliance and Tax Management

6. Integration with HR Systems

7. Automation and Efficiency

1.4 PROBLEM OF THE MANUAL SYSTEM

Problems of the manual system are mentioned below:

 Preparation of employee details is very difficult and time consuming.

 Preparation of payment slips is very difficult and time consuming.

 Record keeping of employees detail for every month is very difficult

 Lot of paper work has to be done for maintaining the record files.

 Storage is also a big problem.

 Security is also a very big problem of the manual system.

3
 CHAPTER 2

LITERATURE REVIEW

2.1 EXISTING SYSTEM

Manual payroll is a traditional approach to processing payroll where all tasks are
performed without the assistance of automated software. This method typically involves
calculating each employee's pay and deductions individually, often using spreadsheets or basic
accounting software. It's a labor-intensive process that requires a thorough understanding
of payroll laws and tax regulations to ensure accuracy.

Advantages of manual payroll

 Typicallyless expensive to start compared to automated systems, requiring

minimal technological investment.

 For very small businesses with a few employees, manual payroll can be straightforward
and manageable.

Disadvantages of manual payroll

 Payroll demands meticulous accuracy, and the

likelihood of mistakes is greater in
manual processes than with automated software, where human error is more prevalent.

 Handling manual payroll requires a high degree of trust in one’s own capabilities. Errors in
tax withholding or misclassification of taxable benefits can result in costly disputes with tax
authorities.

 Doing payroll manually usually takes much longer than using the software. While software
can quickly work out payroll taxes, doing it by hand can take several hours.

4
2.2 LIMITATIONS EXISTING SYSTEM

PROBLEMS OF THE MANUAL SYSTEM

Problems of the manual system are mentioned below:

1. Preparation of employee details is very difficult and time consuming.

2. Preparation of payment slips is very difficult and time consuming.

3. Record keeping of employees detail for every month is very difficult

4. Lot of paper work has to be done for maintaining the record files.

5. Storage is also a big problem.

6. Security is also a very big problem of the manual system.

Disadvantages of manual payroll

 Payroll demands meticulous accuracy, and the likelihood of mistakes is greater in

manual processes than with automated software, where human error is more prevalent.

 Handling manual payroll requires a high degree of trust in one’s own capabilities. Errors
in tax withholding or misclassification of taxable benefits can result in costly disputes
with tax authorities.

 Doing payroll manually usually takes much longer than using the software. While
software can quickly work out payroll taxes, doing it by hand can take several hours.

5
2.3 PROPOSED SYSTEM

2.3.1 Needs
In manual payroll records keeping, there are many paper works to do. The Manager is
always engaged in proper maintenance of register. It is very tedious as well as time-
consuming work for both the employee and company. For this he/she also requires staff to
help and assists him in performing his work.
It is very important for creating a successful and robust project that the problem or need
of the user for which the project has to develop should be clearly defined to the programmer.
I, being the system analyst, had already that all this hostel needs is one computer which help
to get rid them of all junk they are currently using in the company, for systematic storage
records.

2.3.2 Performance
A computer works and thinks very much like the human brain and in a much more
precise manner. It computes data at the speed of light and can handle millions and millions of
bits of information’s in one go. If a system can be made to handle records on a computer, it
will work at a very fast and can be handle all the different queries, which might be asked by
the user. This way, the entire performance of the company can be increase as user sitting on
the computer type in queries, and get any information looking for in blind eyes. This saves
them the entire hassle of finding one of the hundred file cabinets, then opening it and
searching for the record, which they might want. A computer system can increase
performance of the company.

2.3.3 Efficiency
When a person using the computer, pressed the enter key, a signal is sent to the
processor which is then processed and an output comes. If we could enter data, find data,
modify data and a lot of other activities at that kind of speed, it can only make work done
much faster and at a very efficient as compared to the cost of the system and the cost of 100
file cabinets. Computer, if applied for the right use, are the most resourceful and proficient
machines every created by man. We can get rid of all the file works and all the data is saved
into the computer.

6
2.3.4 Security
Security is also given a great important so that no unauthorized user can tamper
the records of the company. This makes, security a big part of the new system. Record can be
changed only by the authentication of user who is sitting in front of a system and who is
dealing with all the transaction.

2.4 ADVANTAGES OF PROPOSED SYSTEM

1. By the use of computers, preparation of employee details becomes easier and

rapidly by making some small programs.

2. Payment slips generation can be done easily by computerized payroll

management system. This means that these calculations can be done
automatically.

3. Record keeping becomes very easy and time saving.

4. Management information reports are created very easily by giving some

instructions to the computer.

5. There will be no need of paper work for maintaining the record files.

6. Storage can be easily done through floppy disk & hard disk having large
capacity.

7. Important documents can be easily protected.

7
 CHAPTER 3

SYSTEM DESIGN

3.1 SYSTEM ARCHITECTURE

Logical Design

The logical flow of a system and define the boundaries of a system. It includes the following steps:

i. Reviews the current physical system – its data flows, file content, volumes, frequencies etc.

ii. Prepares output specifications – that is, determines the format, content and frequency of reports.

iii. Prepares input specifications – format, content and most of the input functions.

iv. Prepares edit, security and control specifications.

v. Specifies the implementation plan.

vi. Prepares a logical design walk through of the information flow, output, input, controls and
implementation plan.

vii. Reviews benefits, costs, target dates and system constraints .

Physical Design

Physical system produces the working systems by define the design specifications that tell the programmers
exactly what the candidate system must do. It includes the following steps

Design the physical system.

i. Specify input and output media.
ii. Design the database and specify backup procedures.
iii. Design physical information flow through the system and a physical design Walk through.
iv. Plan system implementation.
v. Prepare a conversion schedule and target date
vi. Determine training procedures, courses and timetable.
vii. Devise a test and implementation plan and specify any new hardware/software.

8
Design/Specifications Activities

i. Concept formulation.
ii. Problem understanding.
iii. High level requirements proposals.
iv. Feasibility study.
v. Requirements engineering.
vi. Architectural design.

INPUT DESIGN

Input Design deals with what data should be given as input, how the data should be arranged or
code, the dialog to guide the operating personnel in providing input, methods for preparing input
validations and steps to follow when error occur. Input Design is the process of converting a user-
oriented description of the input into a computer-based system. This design is important to avoid
errors in the data input process and show the correct direction to the management for getting correct
information from the computerized system. It is achieved by creating user friendly GUI (Graphical
User Interface). The goal of the designing is to make the interface as simple and attractive as
possible. The user can browse through the items available on the website, add or remove them to
and from the cart as required. It provides invoices also.

When the user click on the Checkout button the session checks for a valid login. If the user has
logged in it goes to the payment gateway else it redirects to the login page. After a successful login
the payment gateway launches.

OUTPUT DESIGN

A quality output is one, which meets the requirements of the end user and presents the information
clearly. The objective of output design is to convey information about past activities, current status
or projections of the future, signal important events, opportunities, problems, or warnings, trigger an
action, confirm an action etc. Efficient, intelligible output design should improve the system’s
relationship with the user and helps in decisions making. In output design the emphasis is on
displaying the contents of the website in the best possible manner. The primary consideration in
design of output is the information requirement and product descriptions for the end users. The
major formation of the output is to convey the information and so its layout and design need a
careful consideration.

9
 DESIGN METHODOLOGY

Database and database system have become essential component of everyday life in modern
society. In the courses of a day, most of us encountered several activities that involved some
interaction with the database. There are several ways of implement database. Some of them
are file handling mechanism, relational database, object relational database. In our project
we will use file-handling features provided by C++ languages. The project is developed by
in such a way to provide a very efficient user interface of the project.

In this project there are 3 classes

i. Lines class = this class contains drawing functions.

ii. Menu class = It performs function relating to different menu in the project. In this
employee, this class controls designation & salary classes as all the display functions.

iii. Employee class = It performs function relating employees.

DESIGN OVERVIEW

i. Flow Chart

ii. DFD

iii. E-R Diagram

10
Flowchart
In procedural languages program, is started with the first line and follow a predefined
path. Flowchart is used to define that predefined path and it show the flow of control
throughout the program.

FIG 3.1.1

11
FIG 3.1.2

FIG 3.1.2

12
Data Flow Diagram

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modeling its process aspects. Often they are a preliminary step used to
create an overview of the system which can later be elaborated. DFDs can also be
used for the visualization of data processing (structured design).

A DFD shows what kinds of data will be input to and output from the system, where the data will come
from and go to, and where the data will be stored. It does not show information about the timing of
processes, or information about whether processes will operate in sequence or in parallel (which is
shown on a flowchart).

Data Flow Diagram serves two purposes:

i. To provide annunciation of how data are transformed as they move through the system.
ii. To depict the functions that transforms the data flow.

DFDs are an excellent mechanism for communicating with the customer during requirement analysis
and are widely used for the representation of external and top-level internal design specification. In the
latter situations, DFDs are quite valuable for subsystem, files and data links. The DFD methodology is
quite effective, especially when the required design is unclear. In the process, many levels of DFDs are
created depending upon the level of details needed

The Level 0 DFD is also called Context Level DFD. It depicts the overview of the entire system. The
major external entities, a single process and the output stores constitute the level-0 DFD. Though this
diagram does not depict the system in detail, it represents the overall inputs, process and output of the
entire system at a very high level.

.
Symbols Used In DFD

Fig 3.1.3
13
 DATA FLOW DIAGRAM FOR PAYROLL MANAGEMENT SYSTEM

Fig 3.1.4

3.1.1 Entity Relationship Diagrams (Er-Diagrams)

An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships

between entities in a database. ER diagrams often use symbols to represent three different types of
information. Boxes are commonly used to represent entities. Diamonds are normally used to
represent relationships and ovals are used to represent attributes.

An entity-relationship model (ERM) in software engineering is an abstract and conceptual

representation of data. Entity-relationship modeling is a relational schema database modeling
method, used to produce a type of conceptual schema or semantic data model of a system, often a
relational database, and its requirements in a top-down fashion.

14
ER DIAGRAM FOR PAYROLL MANAGEMENT SYSTEM

Fig 3.1.5

15
3.2 INTERFACE

Output Definition
In output definition following screen are shown

i. Main Menu Screen.

ii. New employee Record Screen.

iii. Display employee Record Screen.

iv. List of employee Screen.

v. Salary slip screen.

vi. Edit screen.

vii. Quit screen.

Input Definition

In input definition following screen are shown

i. Main Menu Screen.

ii. New employee Record Screen.

iii. Display employee Record Screen.

iv. List of employee Screen.

v. Salary slip screen.

vi. Edit screen.

vii. Quit screen.

16
I .MAIN SCREEN

Just after run the software user will see the main screen. In the main screen, all
the options available in this project will be available. User will use the keys to move
between the choices & press enter to select a particular choice.
 Enter 1 to add new records.

Fig.3.2.1

 Enter 2 to display the records of any particular employee.

 Enter 3 to display the list of all the employee working in the company.

 Enter 4 to display the salary slip of any particular employee.

 Enter 5 to edit the record of any particular employee.

 Enter 0 to quit from the program.

17
II . NEW EMPLOYEE RECORD SCREEN

If the user input 1 for the first option in the main screen then he will see the new
employee record screen. In this screen, the required detail of the new employee is entered.
At the bottom of the screen, message is shown to guide the user.

Fig.3.2.2

18
 III .DISPLAY EMPLOYEE RECORD SCREEN.

If the user input 2 enter at the second option in the main screen then he will see
the details of the employee working in company .in this section program want from the user to
enter the ID or CODE of the employee whose record he want to see., the program will show
another screen. In that screen the entire details of that employees will be show. ‘Press any key
to continue’ and if user presses any key than the program will jump to main screen.

Fig.3.2.3
Now press Enter key to continue and user will see this screen where all the details related to the
employee will be there.

Fig.3.2.4

19
 IV. LIST OF EMPLOYEE RECORD SCREEN:

If the user input 3 for the third option in the main screen then he will see the list of all the
employees working in the company.

Fig.3.2.5

Now press Enter key to continue……………

V. SALARY SLIP SCREEN:

user get another containing all the details of employees related to their salary details

Fig.3.2.6

20
 VI. EDIT SCREEN:
If the user input 5 for the fifth option in the main screen then the user will see the edit sub screen.
This menu will have 3 option:

 Delete record

 Modify record

 Exit.



Fig.3.2.7

If user press yes to modify the record than this screen will display.
In this screen if user wants to change any of the record than he or she can changes it or if no
then simply press enter key to continue…..

VII QUIT SCREEN:

If user input 6 for the sixth option in the main menu screen then the user will quit or exit from
the software or from the program.

21
 CHAPTER 4

SYSTEM REQUIREMENT

HARDWARE AND SOFTWARE REQUIRMENT

4.1 Hardware Requirements

Hardware requirement are the basic need of the system or the package, which is been
developed and will be deployed upon the system, which should have these basic
components or fulfill these basic hardware needs of these package.
The following hardware is recommended for the user.

Processor Intel Pentium IV 2.4 GHZ or above

Clock speed 500 MHZ
RAM 32MB or above
System bus 32 bits
Monitor Color monitor
Hard disk 8 GB or above
CD Drive Any CD ROM
Input device Key board, Mouse

4.2 Software Specification

Operating System MS WINDOWS XP SP2

Front End Visual Studio 2012, [Link]
Back End SQL Server
Additional Software DOTNet framework 3.5

22
 CHAPTER 5

SYSTEM IMPLEMENTATION

5.1 TESTING

Testing is a process of executing a program with the interest of finding an error. A good test is
one that has high probability of finding the yet undiscovered error. This helps in the prevention
of errors in a system. Testing also adds value to the product by conforming to the user
requirements. Testing should systematically uncover different classes of errors in a minimum
amount of time with a minimum amount of efforts. Two classes of inputs are provided to test
the process:
i. A software configuration that includes a software requirement specification, a design
specification and source code.

ii. A software configuration that includes a test plan and procedure, any testing tool and test
cases and their expected results.

23
5.2 SYSTEM IMPLEMENTATION REQUIREMENTS

The implementation phase is less creative than system design. It is primarily concerned
with user training, site preparation, and file conversion. When the candidate system is linked to
terminals or remote sites, telecommunication network and test of the network along with the system
are also included under implementation.
During the final testing, user acceptance is tested, followed by user training. Depending on the
nature of the system, extensive user training may be required. Conversion usually takes place about
the same time the user is being trained or late.
In the extreme, the programmer is viewed as someone who ought to be isolated from other aspects of
the system development. Programming is itself design work, however. The initial parameters of the
candidate system should be modified as a result of programming efforts. Programming provides a
‘reality test’ for the assumptions made by the analyst. It is therefore a mistake to exclude programmers
from the initial system design.
The implementation phase is less creative than system design. It is primarily concerned with user
training, site preparation, and file conversion. When the candidate system is linked to terminals or
remote sites, telecommunication network and test of the network along with the system are also
included under implementation.
During the final testing, user acceptance is tested, followed by user training. Depending on the
nature of the system, extensive user training may be required. Conversion usually takes place about
the same time the user is being trained or late.
As we know, creating software is one thing and the implementation of the created software is another.
The process of implementation software is much difficult as compared to the task of creating the
project.

First we have to implement the software on a small scale for removing the bugs and other error in the
project and after removing them we can implement the software on a large scale. We have to
implement our project named “Payroll Management System” on a small scale now, to see whether it is
working fine or not without any errors, and after testing and evaluating the software we will implement
it on a large scale.

Whenever we develop software or project certain hardware and the programmer for developing the
software is using software. The hardware and software to be used by the programmer for developing
the software should be such that it would result in the development of a project, which would satisfy
all the basic needs for which the programmer has created the project. The hardware should be such that
cost constraints of the empoyee should also be taken into account without affecting the performance.

24
 5.3 MAINTENANCE

After the installation phase is completed and the user staff is adjusted to the
changes created by the candidate system, evaluation and maintenance begin. Like any system,
there is an aging process that requires periodic maintenance of hardware and software. If new
information is inconsistent with the design specification, then changes have to be made.
Hardware also required periodic maintenance to keep in tune with design specification. The
importance of maintenance is to continue to bring the new system to standers.

User priorities, changes in organization requirements, or environmental factors also call for the
system enhancements (To contrast maintenance with enhancement).

CODE
[Link]

<?php

session_start();
?>

<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<style>
body {font-family: Arial, Helvetica, sans-serif;}
/* Full-width input fields */

input[type=text],

input[type=password] {

width: 100%; padding:

12px 20px; margin: 8px

0; display: inline-block;

border: 1px solid #ccc;

25
 box-sizing: border-box;
}
/* Set a style for all buttons */

button {

background-color: #4CAF50;

color: white;

padding: 14px 20px;

margin: 8px 0; border:

none; cursor: pointer;

width: 100%;
}
button:hover {

opacity: 0.8;
}
/* Extra styles for the cancel button */
.cancelbtn { width:

auto;

padding: 10px 18px;

background-color: #f44336;
}
/* Center the image and position the close button */
.imgcontainer {
text-align: center; margin:

24px 0 12px 0; position:

relative;
}
[Link] { width:

40%;
border-radius: 50%;
}

26
.container { padding:

16px;
}
[Link] { float:

right;

padding-top: 16px;
}
/* The Modal (background) */
.modal {
display: none; /* Hidden by default */

position: fixed; /* Stay in place */

z-index: 1; /* Sit on top */ left:

0;

top: 0;
width: 100%; /* Full width */

height: 100%; /* Full height */

overflow: auto; /* Enable scroll if needed */

background-color: rgb(0,0,0); /* Fallback

color */

background-color: rgba(0,0,0,0.4); /* Black w/

opacity */ padding-top: 60px;

}

.modal-content {

background-color: #fefefe;

margin: 2% auto 10% auto; /* 5% from the top, 15% from the bottom and

centered */ border: 1px solid #888;

width: 40%; }

27
 .close {
position: absolute;

right: 25px;
top: 0;
color: #000;
font-size: 35px; font-

weight: bold;
}
.close:hover,
.close:focus { color:

red; cursor: pointer;

}
/* Add Zoom Animation */
.animate {
-webkit-animation: animatezoom 0.6s;

animation: animatezoom 0.6s

}
@-webkit-keyframes animatezoom

{ from {-webkit-transform:

scale(0)} to {-webkit-transform:

scale(1)}
}
@keyframes animatezoom {

from {transform: scale(0)}

to {transform: scale(1)}
}

@media screen and (max-width: 300px) { [Link] {

display:

block; float: none;

}

28
.cancelbtn { width:

100%;}}

.button {
background-color: #000000;

color: #FFFFFF;

padding: 10px; border-

radius: 10px;

-moz-border-radius: 10px;
-webkit-border-radius: 10px;

margin:10px
}
.small-btn { width:

50px; height: 25px;

}
.medium-btn {

width: 70px; height:

30px;
}
.big-btn { width:

180px; height: 40px;

}

</style>
<?php

include("[Link]");

include("[Link]");

extract($_POST);

if(isset($submit))
{

29
$rs=mysql_query("select * from users where username='$username' and password=

MD5('$password')"); if(mysql_num_rows($rs)<1)
{

$found="N";}
else
{

$_SESSION[login]=$username;

header("Location: [Link]");
}

?>

</head>
<body>
<center>
</br></br></br>
<h1><strong>MY EMPLOYEE MANAGER</strong></h1>
<br>
<h1><STRONG>ADMINISTRATOR &nbsp; LOGIN</STRONG></h1>

<button onclick="[Link]('id01').[Link]='block'" class="button big-btn"

style="width:10%; font-size : 20px;"><strong>Login</strong></button>
</center>
<div id="id01" class="modal">
<form class="modal-content animate" name="form1" method="post" action="">
<div class="imgcontainer">
<span onclick="[Link]('id01').[Link]='none'" class="close" title="Close
Modal">&times;</span>
<img src="[Link]" alt="Avatar" class="avatar">
</div>

<div class="container">
<label for="uname"><b>Username</b></label>
30
<input type="text" placeholder="Enter Username" name="username" id="username" required>

<label for="psw"><b>Password</b></label>
<input type="password" placeholder="Enter Password" name="password" id="password" required>

<button type="submit" name="submit" id="submit" value="Login">Login</button>

<!-- <label>
<input type="checkbox" checked="checked" name="remember"> Remember me
</label>-->
</div>

<div class="container" style="background-color:#f1f1f1">

<button type="button" onclick="[Link]('id01').[Link]='none'"
class="cancelbtn">Cancel</button>

<!-- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <button

onclick="[Link]('id02').[Link]='block'" class="button big-btn"
style="width:50%; font-size : 20px;"><strong>Forget Password</strong></button> -->

</div>
</form>
</div>

<div id="id02" class="modal">

<form class="modal-content animate" method="post" action="">
<div class="imgcontainer">
<span onclick="[Link]('id02').[Link]='none'" class="close" title="Close
Modal">&times;</span>

</div>
<div class="container">
<label for="uname"><b>Enter Your Email id</b></label>
<input type="text" placeholder="Enter Username" name="username" id="username" required>

31
 <input type="submit" name="submi" value="Submit">
</div>
</form>
</div>
<script>
// Get the modal
var modal =

[Link]('id01'); var

modal = [Link]('id02');

// When the user clicks anywhere outside of the modal, close it

[Link] = function(event) {

if ([Link] == modal) {

[Link] = "none";}}

</script>
[Link]
<?php

session_start();
include "[Link]";
?>

<!doctype html>
<html>
<head>
<style>
.button {
background-color: #000000;

color: #FFFFFF;

padding: 10px; border-

radius: 10px;

-moz-border-radius: 10px;

32
 -webkit-border-radius: 10px;

margin:10px
}
.small-btn { width:

50px; height: 25px;}

.medium-btn { width:

70px; height: 30px;

}
.big-btn {
width: 250px; height:

40px;}
</style>
<meta charset="utf-8">
<title>Untitled Document</title>
</head>
<body class="bg">
<center>

<br>
<form action="emp_master.php" align= "center">
<!--<div class="button big-btn">This is a big button</div>-->

<button type="submit" class="button big-btn" value="emp_master" name="add" ><font

size="3"><strong>Add New Employee</strong></font></button>
</form>
<br>
<form action="dep_master.php">
<button type="submit" class="button big-btn"value="" name="add"
><font size="3"><strong>Add New Department</strong></font></button>
</form>
<br>
<form action="grad_master.php">

33
<button type="submit" class="button big-btn" value="#"
name="add" ><font size="3"><strong>Add New Grade</strong></font></button>
</form>
<br>
<form action="emp_grad_detail.php">
<button type="submit" class="button big-btn" value="#" name="add" ><font
size="3"><strong>Employee Grade Details</strong></font></button>
</form>
<br>
<form action="salary_detail.php">
<button type="submit" class="button big-btn" value="#" name="add" ><font
size="3"><strong>Prepare Monthly Salary</strong></font></button>
</form>
<br>
<form action="[Link]">
<button type="submit" class="button big-btn" value="#" name="add" ><font
size="3"><strong>Generate Report</strong></font></button>
</form>

</table>
</form>

</center>
</body>
</html>
emp_master.php
<?php

session_start();
include_once "[Link]";
?>

<?php

34
include_once '[Link]';

if(isset($_POST['submit']))
{

$file = rand(1000,100000)."-".$_FILES['file']['name'];
$file_loc =
$_FILES['file']['tmp_name'];
$file_size = $_FILES['file']['size'];
//echo $file_size;
$file_type = $_FILES['file']['type'];

$folder="uploads/";

// new file size in KB

$new_size = $file_size/1024; echo

$new_size;

// new file size in KB

// make file name in lower case

$new_file_name = strtolower($file);
// make file name in lower case

$final_file=str_replace(' ','-',$new_file_name);

if(move_uploaded_file($file_loc,$folder.$final_file))
{

$sql="INSERT INTO tbl_uploads(file,type,size)

VALUES('$final_file','$file_type','$new_size')";
$_SESSION['final_file']=$final_file;

mysqli_query($connection,$sql);
?>

35
 <script>
alert('successfully uploaded');

[Link]='emp_master.php?success';

</script>
<?php
}

else
{

?>

36
 CHAPTER 6
RESULT

Login page:

Figure:6.1

Thus, the login page is created to login into the employee details.

Employee details page:

Figure :6.2
This page was created to known the existing employee details and to include the new
employee details.
37
 Figure:6.3

Now the details are recorded, and it can be retrieved when required.
Grade details page:

Figure:6.4
The details of employees are fed up, to calculate the employees grades.
38
 Employee salary details page:

Figure:6.5

This page gives the salary details of the employees.

Employee report page:

Figure:6.6
Enter the employee ID, to known about the employees history.

39
 CHAPTER 7

CONCLUSION

In conclusion, this Payroll Management System (PMS) project successfully

demonstrates the feasibility and benefits of automating payroll processing, significantly
improving efficiency, accuracy, and reducing the time and effort involved in managing
employee compensation. The system addresses key challenges in manual payroll systems, such
as potential errors, data inconsistencies, and compliance issues, offering a streamlined and
secure solution.

The PMS is designed to handle various payroll-related tasks, including employee data
management, attendance tracking, salary calculations, deduction management, and payslip
generation. By automating these processes, the system minimizes human error and ensures
data integrity, crucial for accurate and timely payroll processing.

The system's user-friendly interface and intuitive design facilitate easy navigation and
data entry for authorized personnel, ensuring a smooth and efficient workflow. The modular
architecture of the PMS allows for easy customization and integration with other HR or
accounting systems, further enhancing its adaptability and utility.

Moreover, the system's ability to generate comprehensive reports and manage tax
compliance obligations ensures a high degree of transparency and accountability, which is
essential for maintaining financial integrity. The PMS also addresses concerns about data
security, protecting sensitive employee information through secure storage and access
controls.

In essence, the PMS project serves as a valuable blueprint for organizations seeking to
modernize their payroll management practices, offering a more efficient, accurate, and
compliant solution for managing employee compensation and ensuring financial stability. It
demonstrates the power of automation in streamlining administrative tasks, freeing up valuable
time for HR and accounting personnel to focus on strategic initiatives and employee relations.

40
 REFERENCES

1. W3Schools - Web Development Tutorials [Link]

(Used for learning HTML, CSS, and JavaScript syntax and examples.)

2. MDN Web Docs (Mozilla Developer Network) [Link]

(Used for in-depth documentation and browser compatibility for web technologies.)

3. GeeksforGeeks - Web Development Section [Link]

(Referred to for tutorials on JavaScript form handling and localStorage usage.)

4. Stack Overflow [Link]

(For resolving implementation issues and debugging common coding errors.)

5. GitHub Documentation [Link]

(Optional reference if version control or project hosting was used.)

6. Bootstrap Documentation (if used) [Link]

(For responsive design components and layout ideas, if applicable.)

41
 OUTCOMES

A successful payroll management system project yields significant benefits for organizations,
including increased efficiency, reduced errors, and improved employee satisfaction. By
automating tasks and providing centralized data access, these systems streamline payroll
processing and enhance financial management. They also ensure compliance with relevant
regulations, minimize administrative burden, and facilitate data-driven decision-making.
Increased Efficiency and Reduced Errors:
 Automating manual processes like calculations and data entry saves time and reduces the risk of
errors.
 Payroll systems can process payroll faster than manual methods, ensuring timely payments.
 Centralized record-keeping eliminates data redundancy and makes it easier for HR to access
information.
Improved Employee Satisfaction and Retention:
 Accurate and timely payments build trust and loyalty among employees.
 Employee self-service portals provide easy access to pay slips, tax forms, and other payroll-
related information, enhancing convenience and control.
Enhanced Financial Management and Compliance:
 Payroll systems enable real-time reporting and analytics, allowing organizations to monitor
payroll trends and make informed decisions.
 They assist in managing deductions, benefits, and taxes, ensuring compliance with statutory
regulations.
 Automated payroll calculations and record-keeping minimize the risk of under- or over-
payment, preventing financial discrepancies.
Reduced Administrative Burden:
 Payroll systems automate tasks, freeing up HR staff to focus on strategic initiatives rather than
administrative tasks.
 Simplified access to payroll information reduces the need for manual inquiries and paperwork.
Data-Driven Decision Making:
 Payroll systems provide comprehensive data and reporting capabilities, allowing organizations
to gain insights into employee compensation, benefits, and other related metrics.
 This data can be used to make informed decisions about compensation strategies, benefits
packages, and other HR policies.
Overall, a well-implemented payroll management system project provides a significant return
on investment by improving efficiency, reducing errors, enhancing employee satisfaction, and
facilitating data-driven decision-making.

42