Project Report

on

“Employee Payment Management System”

SRI BALAJI UNIVERSITY PUNE

SCHOOL OF COMPUTER
STUDIES

Program: Master of Computer Application

2023-25 Batc h (Semester-3)

SUBMITTED BY: -
SUBHAM TIWARI (MCA2302074)
 Sri Balaji University Pune

School of Computer Application

MCA- 2023 Semester-2

As part of Mini Project (MCA109)

CERTIFICATE

Certified that the Project Report entitled “EMPLOYEE PAYMENT

MANAGEMENT SYSTEM”, submitted by Subham Tiwari of MCA
A, is his own work and has been carried out under my supervision. It is
recommended that the candidates may now be evaluated for their work
by the University

Name : SUBHAM TIWARI

Roll no.: MCA2302074
Date: 01/06/2024

Remark:
Prof: DEBIDUTTA SHARMA Richa Purohit
(Project Guide) (Vice-Principal)
 ACKNOWLEDGEMENT

We feel immense pleasure to introduce “Employee Payment

Management System” as our major project. I express my sincere thanks
to our instructor Prof:Debidutta Sharma who guided us to the
successful completion of this project report. We take this opportunity
to express our deep sense of gratitude for their individual guidance,
constant encouragement and immense motivation which have sustained
our efforts at all stages of this project report. We are grateful and
appreciate all the staff members of the School of Computer Application
for their cooperation and support. I extend my sincere thanks to our
principal Dr.G.Y.Shitole for his support and for all the facilities
provided for the preparation of this project report. Also, we wish to
thank our parents & friends who helped us a lot in collecting data,
pictures and continuous help and support. Finally, we would wish to
thank everyone involved in this project time.
SR NO. TABLE OF CONTENT PAGE NO

ABSTRACT 6

SYNOPSIS OF PROJECT 7-15

*Introduction
*Problem Statement
1
*Objective*Available Model
*Scope
*System Analysis

SOFTWARE REQUIREMENTSPECIFICATION 16-28

AND FEASIBILITY STUDY
*Introduction
*Purpose and scope
*Advantage
A)SRS
B)Use
2 C)Purpose
D)Functional Requirement
E)Non-Function Requirement
F)Software Tools
G)Deployment
*FEASIBLITY STUDY

DESIGN AND DIAGRAM 29-44

*DFD(Data Flow Diagram)
*Deployment Diagram
3 *ER Diagram*Class Diagram
*Object Diagram
*Use Case Diagram
*Activity Diagram
*Sequence Diagram
SR N0 TABLE OF CONTENT PAGE
NO

4 CODING AND 45-52

IMPLEMENTATION

5 CONCLUSION AND 53-54

RECOMMENDATION
6 FUTURE SCOPE

7 BIBLIOGRAPHY AND
REFERENCES
 ABSTRACT

It is an “Employee payment management system” GUI application. It is

used to calculate the employee salary with overtime bonus in weekly
wages and generate the employee payment slip with all details about that
employee.
Some of the employees are doing overtime work in this application and
calculation of overtime payment is based on how many hours he/she
works greater than the daily hours. By condition employees who works
40 hours and above will be considered for the overtime work. It will be
beneficial for the employees because he/she can earn some extra money
added with whatever is the weekly salary.
It is used for weekly wages and overtime employee salary management
system. After giving hours per worked and wages per hour clicking the
weekly wages button then automatically shows tax, gross payable
overtime bonus and net payable .it is main advantage of this application.
1.SYNOPSIS OF PROJECT
Introduction

As a result of the impact that innovation has had across all industries,
management in those industries has vastly improved, as has the
administration of systems in general. The payroll management system is
an essential component of every organization.
It calculates salaries according to the rules established by the company for
each employee of the administration in a variety of different ways. It
reduces the amount of manual labour required to handle the desk job
and increases the reliability of the system.
The payroll process and management system in Dubai has all the
necessary components to handle employees’ monetary compensation,
making it one of the most advanced in the world. It automates the entire
salary management process, which was previously done manually.
By reducing the time spent on activities that would otherwise require
more time to complete physically, it is a more reliable and effective
system for the company to rely on.
The Principal Modules of the System
•Administration
•Employee
•Divisions
•Salary
Now, to accurately understand the functioning of the system, we need to
understand what each module is responsible for doing. This will make it
much easier to combine the modules, which in turn will simplify the
functioning of the complete system.
*Problem statement
Our task is the creation of a new payroll system. The old system is outdated
and no longer adequately manages the payroll process and the entry of
employee timecard information. Therefore, manual intervention is required to
process the payroll. In addition to the preexisting category of salaried
employee, which the current payroll process does support, our organization
now accommodates two new types of employees: those employees working
on commission, and those employees working on an hourly basis. The current
payroll process doesn't support these two new employee types, which are
described in detail later in this problem statement. In addition to
accommodating all employee types, as well as ensuring that our system can
accommodate newly created categories of employees in the future, the
system must also allow each of these employees to enter his or her time
information via a corporate intranet using a standard Web browser. Because
employees can manage only their individual timecard information, a user ID
and password is required of each employee prior to gaining access to this
section of the corporate intranet. The payroll process can process only
"signed" timecards, which are those timecards that the employee has
identified as accurate. Overall, the system will store information about the
approximately 2,000 company employees. This data will be stored in the
Oracle payroll database. The payroll process must run on the fifteenth and
last day of each month at 12:00 a.m. All pay checks must be accurately
calculated and deposited into one or more bank accounts of the employees'
choosing. Employees also should be able to change personal information,
such as names, addresses, and passwords. Eventually, the system must enable
employees to maintain their direct deposit information via the system as
well. However, this feature is beyond the scope of the initial release.
A human resources representative must be able to initiate the payroll
process on demand based on a selected list of employees. When doing so,
the system should cycle through the list of selected employees, running
payroll only for those employees. This process typically will be done by a
human resources representative during normal business hours. As stated
earlier, our system must be able to track information and calculate salaries
for the following three types of employees:
1. Salaried: These employees are paid a flat salary. However, they're still
required to submit timecards that include the dates worked and the
number of hours worked on those dates.
2. Hourly: These employees are paid based on their hourly rate. Employees
working more than a standard 40-hour work week are paid 1.5 times
their hourly rate.
3. Commission: These employees are paid a commission based on their total
sales. The commission rates for commissioned employees are 10, 20, or
25 percent. In addition to the percentage rate, these employees also
may receive a base salary.
Available Models
Three different models of global payment have developed over the years.
Understanding the key differences can help us choose a payroll provider that
meets our organization’s needs now and into the future

Model 1: Local Payroll Vendors

A company following the local vendor model of global payroll has multiple
contracts with individual local providers, typically one for every country in
which they need payroll.

Model 2: Payroll Aggregators

The aggregator model of global payroll is a payroll provider which has either
acquired or partnered with local providers in other countries to process all
payrolls for a company under a single contract.

Model 3: Unified Payroll Solution

The newest model for global payroll aims to address that risk by processing all
payrolls in all countries on a single, unified platform. Taking a holistic approach
to payroll, the unified cloud solution model is based on managing every element
involved in payroll processing within the same, centralized, connected system.
Objective and Scope of Payroll Management System

Makes Payroll Systems More Organised

Maintaining logbooks for ten employees can be hard enough; maintaining so
many records for hundreds of employees is an arduous task. Using the latest
tech in payroll management systems ensures that everything is a lot more
organized.

Ensures Data is Safe

Employee data is just as necessary as customer data; the best payroll
management system providers know this and ensure security systems are put in
place to keep company and employee data safe.

Ensure Data is Easy to Access

While safety is a primary concern, having a smart payroll management system
also means that you can access all the data you need with just a few clicks. This
could be employee information, overall budget estimates, or payroll
expenditure reports.

Easy to Pass on Information and Updates

Payroll systems have to be updated often, whether internal compliance or
regional and national laws and regulations; these are vital. Payroll
management systems can do this with ease. They can also pass on important
information between departments directly to employees and vendors if
required.

Easy to Manage Multiple Locations

Only large companies had to worry about multiple locations, different tax
laws, and various labour laws in the past. With more companies hiring across
geographic boundaries, this has changed. Payroll management systems ensure
that every location is managed with ease, the data and parameters have to be
entered once, and the system will take care of the rest.
Streamlines Payroll Process
Payroll management systems of the past relied heavily on humans in the past,
and this has changed. Systems no longer require mountains of paperwork and
meticulous tasks to be executed by HR executives. Intelligent systems and AI
take care of all these mundane tasks with ease.

Increased Accuracy
While payroll management systems don’t remove the need for human
intervention entirely, they are a lot less prone to error. Once the system has
been put in place, it ensures that it executes all its functions without error.

Makes Compliance Easier

Labour laws can be complicated and are often updated without much notice.
A reliable payroll management system ensures that your organization always
stays within the boundaries of legal compliance and ensures your company’s
policies are adhered to.

Reminders for Essential Tasks

HR departments are usually sent into chaos towards the end of the month,
tying up every loose end while doing their best to ensure everything is done
right. This can lead to people missing out on essential tasks. A sound payroll
management system helps HR departments stay on top of all their tasks with
automated reminders.

Budget Forecast
Knowing what finances your HR department needs every month doesn’t sound
very complicated; however, disbursing funds can be. HR departments have to
take every single factor that affects employees, such as schedule adherence,
overtime bonuses, the list goes on and on. Even if the changes are minor,
knowing precisely what your expenditure is in advance makes life a lot easier
for HR departments and organizations in general.
 Improves Employee Morale
. Timely payments are essential in any organization. They make sure that
employees don’t feel cheated or forgotten. Payroll management systems
don’t just make sure that payments are made on time; they also ensure
that every calculation is done and that your employee deserves is given to
them
System Analysis

User interfaces
The software provides good graphical interface for the front end which is
self-explanatory.

Hardware interfaces
Memory minimum of 4GB RAM
Hard disk of 450 GB
Monitor: 1980x1080 resolution
Mouse: Compatible
Keyboard: Compatible

Software Requirements Specification

Printer
Operating System :Windows XP.
Front End Microsoft :SQL
Backend: Python
Communication interfaces: Windows 11
2.SOFTWARE REQUIREMENT SPECIFICATION
AND FEASIBILITY STUDY
Introduction.

This document outlines the Software Requirement Specification (SRS) and

feasibility study for an Employee Payment Management System (EPMS), a
web-based application designed to streamline the process of calculating,
generating, and distributing employee salaries within an organization,
ensuring accuracy, efficiency, and compliance with payroll regulations.
Purpose: To clearly define the functional and non-functional requirements of
the EPMS, serving as a blueprint for the software development process. To
evaluate the technical, operational, economic, and schedule feasibility of
implementing such a system within the organization's constraints.

System Overview:

The EPMS will automate the entire payroll cycle, including:

Employee data management:
Capture and maintain employee details like personal information,
employment type, salary structure, tax deductions, and bank account
information.
Time and attendance tracking:
Integration with timekeeping systems to record employee work hours,
overtime, and leaves.
Salary calculation:
Accurate calculation of basic salary, allowances, deductions (taxes,
insurance, etc.) based on predefined rules and regulations.
Payslip generation:
Electronic generation of detailed payslips with itemized breakdowns for
each employee.
Payment processing:
Interface with bank systems for direct deposit or check generation.
Reporting and analytics:
Generate various payroll reports (e.g., salary summaries, tax reports,
employee pay history) for management oversight and compliance purposes.
Purpose and scope

This part of the study discusses about the importance of creating

computerized Payroll System.
It provides sample discussed how to run a computerized Payroll System
and here are some examples of how it run.
Many employers use a timekeeping system, such as clock time, to track
work hours employees can separate this system regular hours from
overtime hours worked.
The scope of the study covers the individual information of the OLAMPC
employees. It includes the generation report in the backup files such as
employee and salary record.
The study focuses on processing of payroll system of the employees. Its
concern is the computation of employee's salary and produce report
needed by the accountant especially on each employee's payroll.
It secured also with log-in and log- out from our proposed system and
which can be access only authorized person. It has maintenance for record
of employee and salary which can be maintained by adding, deleting,
updating all the needed transaction in the system and may the employee
can see his/her own standing of their performance anytime and it will
compute the proponent's system the payment such as their deduction and
bonuses.
The study does not cover any other not employee of the OLAMPC This is
not a group pay slip. This system is not cover by any deduction that may
not belong to the pay slip. And the other income that not belong in
OLAMPC.
ADVANTAGE

SRS
Definitions, Acronyms, Abbreviations
Visual Basic .NET (VB.NET) is an object-oriented computer programming
language that can be viewed as an evolution of the classic Visual Basic (VB)
which is implemented on the .NET Framework.
Microsoft SQL Server is a relational model database server produced by
Microsoft.
SRS - Software Requirements Specification.
EPMS - Employee Payment Management System

Project Overview and its Use

The following subsections provide the complete overview of the software
specifications requirements documentation for the product EMPS.
The entire SRS is documented in view of User and the following sub sections are
arranged to give a complete look of the software, its perspective, features,
system requirements and users know how it is.
Overall description, product perspective.
This software is developed specifically to cater the company employees leave
management is totally self-contained and works efficiently. It provides simple
database rather than complex ones for high requirements and it provides good
and easy graphical user interface to both new as well as experienced user of
the computer.
Product functions Master module
Designation
Department Employee module
Employee details Search module and Attendance module
Leave
Attendance
Managing Leave and Salary module
Allowance
Deduction
Pay Slip and Report module
Purpose

Main aim of developing Employee Payment Management System is to

provide an easy way not only to automate all functionalities involved
managing leaves and Payment for the employees of Company, but also to
provide full functional reports to management of Company with the details
about usage of leave facility.
It is committed to bring the best way of management in the various forms of
EPMS.
AS we understand that EPM in not a product to be sold, it is a tool to
manage the inner operation of Company related to employee leave and
Payment
*Functional requirements

Payroll Compliance
It is essential to stay current on tax rules and regulations in order to stay
out of legal problems. This procedure may be streamlined and automated
tax filing and withholding made easier with the help of the payroll
automation system. Provident Fund calculations are also essential, and this
system allows organizations to carry out these calculations automatically. It
is crucial to maintain a record of insurance-related calculations. Software
enables you to conveniently incorporate insurance-related computations
and adjustments based on your organization’s insurance plans.

Compensation Management
Payroll software is crucial in ensuring that employees receive proper
compensation. It simplifies the management of incentives, deductions, and
insurance, and handles payment details from start to finish, including any
modifications made during employment. This includes adjustments to the
minimum salary, bonuses, and other forms of compensation. The software
guarantees accurate tax estimates and makes compensation planning

Expense Management
You can automate your employee expense claims, reimbursements, and
expenses such as official traveling, medical, food, etc. In addition, some
systems visualizations provide insight into a company’s processes. It can
help businesses to make tailor-made policies over time and observe the
effectiveness of these policy changes.

Loans and Advances Management

A payroll administration system can make things easier for the entire
company, including the HR and Finance departments. This approach can
simplify and expedite the entire procedure. The payroll software helps
design eligibility and loan policy criteria and modify Equated Monthly
Instalments (EMI) deductions. The payroll software simplifies EMI
management by automating loan disbursement and monthly instalment
recovery.
Federal income tax
Social security and Medicare tax
State income tax
Local income tax
Additional state-based withholding tax

Pay Equity
Pay equity, the practice of equal and fair pay between employees
despite race, gender, and other demographics, is a heated topic
and should be closely monitored by the human resources
department. When you manage payroll, make sure that you are
complying with the Equal Pay Act, which rules that women and men
should all be given equal pay for equal work in the same
workplace. If you have pay equity issues, consider taking these steps
to improve your workplace situation:
Increase visibility on the employee population
Conduct pays equity assessments
Implement transparent compensation practices
Provide training for upper management
Continuously monitor pay equity

Pay Transparency
If you have taken the steps mentioned above but are still finding yourself
struggling with pay equity issues, you should consider implementing pay
transparency at your workplace. Pay transparency refers to an open and
communicative approach when it comes to discussing salaries within the
company. It is still a relatively new trend within the HR world but has been
proven to be useful to prevent pay discrimination and pay gaps. Other
benefits associated with pay transparency include increased trust in the
company, better physiological safety, and improved employee
performance.
wage levy, a document meant to recover unpaid federal taxes.
Dashboard and Reporting
A reliable payroll solution can simplify your administrative tasks by
automating report generation and facilitating data extraction in various
formats. With advanced business intelligence capabilities, HR departments
can analyse patterns, draw conclusions, and make informed decisions. By
accessing data, HR specialists can predict future outcomes and guide
strategic planning beyond simple pattern recognition

Mobile Integration
By integrating mobile applications, managers can monitor payroll
processes and make informed decisions from any location. Field workers
can log their hours and check in and out of designated places using the
app’s geo-fencing feature. Cloud-based software provides flexibility and
allows access to payroll systems from several mobile platforms, especially
for remote workers.

Platform Checklist
Employees may monitor their attendance, submit requests, and access pay
slips, leave balances, and attendance records through an employee self-
service portal, which is very useful.

Data Security
Protecting the personal financial information of employees is imperative
to avoid fraud and legal action against the company. Therefore, it is
essential to prioritize security aspects while selecting payroll software.
Evaluating security measures such as password protection, user access
restrictions, and data backup strategies ensures complete defence against
intrusions, safeguarding critical data and corporate activities.
Non-Functional Requirement

Costs
The costs of creating and maintaining a new system are common
nonfunctional issues that have an impact on the creation and
development of a payroll program. Most firms have budgets, and
project costs must be within the budgeting constraints. This means that
some of the functional requirements may be too expensive to become
reality, while others may be delayed in implementation. Costs of
upgrading and maintaining a program must be reasonable, or
alternatives must be sought to meet the needs -- such as buying a ready-
made system that is 80 percent done, while only 20 percent may need to
be customized.
Network Bandwidth
You can have the best payroll program, but unless you have proper
bandwidth, the system will not work well. Depending on how many
people access the system at the same time and on functions the program
offers, it can become a burden to the existing network, slowing down
processes to a halt. Bandwidth is different from storage -- you may
have enough storage in your hard drive, yet the communications
between the server and payroll users may not be sufficient. Ensure you
document your existing bandwidth and verify if you need to add to it,
which could be costly. Note that documentation is a nonfunctional
requirement.
Flexibility
A payroll system must be nimble enough to allow for easy changes. Flexibility is an important
nonfunctional requirement of a payroll program. As laws and regulations change, the system
must be updated as well. For example, tax withholdings may change from one calendar year to the
next, and these items should be modified in the system quickly. Firms may institute new benefits
or modify existing ones; the payroll system must allow for these updates to be made without
much fuss. Without a high level of flexibility, the payroll program will become obsolete, and a new
one will need to be purchased or created, which is usually not in the plans.
Reliability
Users expect the payroll system to be reliable, a common nonfunctional requirement for most
systems. Information entered yesterday in the system should be there today. Accuracy is part of
the sense of reliability -- payroll checks and reports must be mathematically correct, including
calculations involving cents. Another issue related to reliability is security. Users assume that the
system will be secured, and the information will be kept safe. A tricky part of security for payroll
systems is the process of backup, which should be done often and be extremely secure, not
allowing nonauthorized personnel access to the data. You don't want individuals changing data in
payroll, creating havoc.
Software and tools deployment

Hardware interfaces
Memory minimum of 4GB RAM
Hard disk of 450 GB
Monitor: 1980x1080 resolution
Mouse: Compatible
Keyboard: Compatible

Software Requirements Specification

Printer
Operating System :Windows XP.
Front End Microsoft :SQL
Backend: Python
Communication interfaces: Windows 11
Feasibility Study

Types of feasibility study

Operational Feasibility
Technical Feasibility
Economic Feasibility
Motivational Feasibility
Scheduled Feasibility

Every project is feasible for given unlimited resources and infinitive

time. Feasibility study is an evaluation of the proposed system
regarding its workability, impact on the organization, ability to meet the
user needs and effective use of resources. Thus, when a new
application is proposed it normally goes through a feasibility study
before it is approved for development. Feasibility and risk analysis and
related in many ways. If a project risk is great and feasibility of
producing software is reduced. During the feasibility analysis in this
project has been discussed below in the above-mentioned topics.

Operational Feasibility:
Feasibility of the working of the system after the installation in the
organization as mentioned in the feasibility analysis.

Technical Feasibility:
Technical feasibility is frequently the most difficult area to ensure at
this stage. It is essential that the process of analysis and definition to
be conducted parallel to an assessment of the technical feasibility. The
consideration that is normally associated with technical feasibility
includes the resources availability of the organization where the
project is to be developed and implemented.
Economic Feasibility:
An evaluation of development cost is weighted against the ultimate income
or benefits derived from the developed system. There was no need of extra
hardware and software for development of this project. Hence this project
has economically justified for development in this organization.

Motivational Feasibility:
An evaluation of the probability that the organization is sufficient
motivation to support the development and implementation of the
application with necessary user participation, resources, training etc.
The interest and support shown by the organization during the
system study do not seem that the new system developed to have
efficient support from the organization.

Schedule Feasibility:
An evaluation of the time needed for the development of this project.
The time schedule required for the development of this project is
very important, since more development time effects machine time,
costs and delays in the development of the other systems. So, the
project should be complete within affixed schedule time as far as the
organization is concerned
3.DESIGN AND DIAGRAM
DESIGN AND DIAGRAM

DFD(Data Flow Diagram)

Payroll Management System Data flow diagram is often used as a
preliminary step to create an overview of the Payroll without going into
detail which can later be elaborated. it normally consists of overall
application dataflow and processes of the Payroll process. It contains all of
the user flow and their entities such all the flow of Employee, Attendance,
Leave, Salary, Task, Pay-Slip, Department. All the below diagrams has
been used for the visualization of data processing and structured design of
the Payroll process and working flow.

Zero Level Data Flow Diagram(0 Level DFD) of Employee Payment

Management System:
This is the Zero Level DFD of Payroll Management System, where we have
elaborated the high-level process of Payroll. It's a basic overview of the
whole Payroll Management System or process being analysed or
modelled. It's designed to be an at-a-glance view of Task, Pay-Slip and
Department showing the system as a single high-level process, with its
relationship to external entities of Employee, Attendance and Leave. It
should be easily understood by a wide audience, including Employee,
Leave and Task In zero level DFD of Payroll Management System, we have
described the high-level flow of the Payroll system.

High Level Entities and process flow of Payroll Management System:

Managing all the Employee
Managing all the Attendance
Managing all the Leave
Managing all the Salary
Managing all the Task
Managing all the Pay-Slip
Managing all the Department
First Level Data Flow Diagram(1st Level DFD) Of Payroll Management
System:
shows how the system is divided into sub-systems (processes), each of which
deals with one or more of the data flows to or from an external agent, and
which together provide all the functionality of the Payroll Management
system . It also identifies internal data stores of Department, Pay-Slip, Task,
Salary, Leave that must be present for the Payroll system to do its job, and
shows the flow of data between the various parts of Employee, Leave, Pay-
Slip, Department, Task of the system.
DFD Level 1 provides a more detailed breakout of pieces of the 1st level
DFD. You will highlight the main functionalities of Payroll.

Main entities and output of First Level DFD (1st Level DFD):
Processing Employee records and generate report of all Employee
Processing Attendance records and generate report of all Attendance
Processing Leave records and generate report of all Leave
Processing Salary records and generate report of all Salary
Processing Task records and generate report of all Task
Processing Pay-Slip records and generate report of all Pay-Slip
Processing Department records and generate report of all Department First
Level DFD Payroll Management System
Second Level Data Flow Diagram(2nd Level DFD) Of Payroll
Management System:
DFD Level 2 then goes one step deeper into parts of Level 1 of Payroll. It
may require more functionalities of Payroll to reach the necessary level of
detail about the Payroll functioning.
First Level DFD (1st Level) of Payroll Management System shows how the
system is divided into sub-systems (processes). The 2nd Level DFD contains
more details of Department, Pay-Slip, Task, Salary, Leave, Attendance,
Employee.

Low level functionalities of Payroll Management

System Admin logins to the system and manage all the functionalities of
Payroll Management System.
Admin can add, edit, delete and view the records of Employee, Leave, Task,
Department
Admin can manage all the details of Attendance, Salary, Pay-Slip
Admin can also generate reports of Employee, Attendance, Leave, Salary,
Task, Pay-Slip
Admin can search the details of Attendance, Task, Pay-Slip
Admin can apply different level of filters on report of Employee, Salary,
Task
Admin can track the detailed information of Attendance, Leave, Salary,
Task
AIM:
To model the “Employee Payment Management System" using the software
Rational Rose with various UML (Unified Modelling Language) diagrams.

UML DIAGRAMS
System Design

This section describes the system's design by categorizing the main factors
and specifications of the system into modules. The system modules are
classified into nine categories, as shown in Fig. 1.
Design Constraints
Data security
Payroll information is private and sensitive, so it's important to take data
security seriously. You can protect data with encryption, strict access
controls, regular updates, employee training, and backup and recovery
plans. You can also consider outsourcing payroll to a trusted provider
with strong security measures.

Employee database
A clean, error-free, and deduplicated employee database is essential
for payroll processing. This database should include up-to-date tax
information, performance information, and direct deposit details for
each employee.

Automation
Automation can reduce the need for manual data entry, which can lead
to errors, delays, and inconsistencies. Payroll software can streamline
and simplify payroll processes like time tracking, payroll calculations,
and payroll taxes.

Cost
The cost of purchasing, implementing, and maintaining a payroll system
can be challenging for small businesses and startups. There may also be
ongoing expenses for training, maintenance, hardware upgrades, and
integrations.
Deployment Diagram

The deployment diagram for employee management system is used to

represent the system’s physical architecture showing the included nodes and
their associations. UML deployment diagram nodes are composed of
hardware and software components that serve as primary requirements to
carry out the employee management.
ER Diagram

This template is a database ER diagram of a personnel salary and salary

management system, and the enterprise can easily manage the
distribution of personnel through the management system. As the name
suggests, an ER diagram depicts the relationship between two or more
entities. This could be real-world entities, or entity sets of a database. The
model helps us build a logical structure of the database or the overall
connectivity in software development. The specific content is available for
reference
Class Diagram:

In software engineering, a class diagram in the Unified Modelling

Language (UML) is a type of static structure diagram that describes the
structure of a system by showing the system's classes, their attributes,
operations (or methods), and the relationships among objects.
Object Diagram

The results of an empirical study comparing user comprehension of object

oriented (OO) and process oriented (PO) models. The fundamental
difference is that while OO models tend to focus on structure, PO models
tend to emphasize behaviour or processes. Proponents of the OO modelling
approach argue that it lends itself naturally to the way
Use Case Diagram:

A use case diagram shows various use cases and different types of users
the system has and will often be accompanied by other types of diagrams
as well. The use cases are represented by either circles or ellipses. The
actors are often shown as stick figures.
COLLABORATION DIAGRAM:

A collaboration diagram, also known as a communication diagram, is

an illustration of the relationships and interactions among software
objects in the Unified Modelling Language (UML). Developers can use
these diagrams to portray the dynamic behaviour of a particular use
case and define the role of each object.
Activity Diagram

The activity diagram used to describe flow of activity through a series of

actions. In this employee payroll system, we have two active user Admin and
Employee. An activity diagram shows the overall flow of control.
SEQUENCE DIAGRAM
In software engineering, a sequence diagram is a visual representation
of how objects interact with each other in a system over time.
Sequence diagrams are used to show the order in which messages are
passed between objects and can also show the control structures
between them.
4.CODING AND TESTING
IMPLEMENTATION: CODING AND TESTING
Technologies used - Python 3.6
Python Tkinter GUI
Language Used:Python
CODE OF PROJECT
import time import datetime
from tkinter import * import
tkinter.messagebox

root=Tk()
root.title("Employee payroll system")
root.geometry('1350x650+0+0')
root.configure(background="powder blue")

Tops=Frame(root,width=1350,height=50,bd=8,bg="powder blue")
Tops.pack(side=TOP)

f1=Frame(root,width=600,height=600,bd=8,bg="powder blue")
f1.pack(side=LEFT)
f2=Frame(root,width=300,height=700,bd=8,bg="powder blue")
f2.pack(side=RIGHT)

fla=Frame(f1,width=600,height=200,bd=8,bg="powder blue")
fla.pack(side=TOP)
flb=Frame(f1,width=300,height=600,bd=8,bg="powder blue")
flb.pack(side=TOP)
lblinfo=Label(Tops,font=('arial',45,'bold'),text="Employee Employee
management system”,bd=10,fg="green")
lblinfo.grid(row=0,column=0)

def exit():
exit=tkinter.messagebox.askyesno("Employee system","Do you want to exit
the system") if exit>0:
root.destroy() return
def reset(): Name.set("")
Address.set("")
HoursWorked.set("")
wageshour.set("")
Payable.set("")
Taxable.set("")
NetPayable.set("")
GrossPayable.set("")
OverTimeBonus.set("")
Employer.set("")
NINumber.set("")
txtpayslip.delete("1.0",END) def
enterinfo():
txtpayslip.delete("1.0",END)
txtpayslip.insert(END,"\t\tPay Slip\n\n")
txtpayslip.insert(END,"Name :\t\t"+Name.get()+"\n\n")
txtpayslip.insert(END,"Address :\t\t"+Address.get()+"\n\n")
txtpayslip.insert(END,"Employer :\t\t"+Employer.get()+"\n\n")
txtpayslip.insert(END,"NI Number :\t\t"+NINumber.get()+"\n\n")
txtpayslip.insert(END,"Hours Worked :\t\t"+HoursWorked.get()+"\n\n")
txtpayslip.insert(END,"Net Payable :\t\t"+NetPayable.get()+"\n\n")
txtpayslip.insert(END,"Wages per hour :\t\t"+wageshour.get()+"\n\n")
txtpayslip.insert(END,"Tax Paid :\t\t"+Taxable.get()+"\n\n")
txtpayslip.insert(END,"Payable :\t\t"+Payable.get()+"\n\n")
def weeklywages():
txtpayslip.delete("1.0",END)
hoursworkedperweek=float(HoursWorked.get())
wagesperhours=float(wageshour.get())

paydue=wagesperhours*hoursworkedperweek
paymentdue="INR",str('%.2f'%(paydue))
Payable.set(paymentdue)

tax=paydue*0.2 taxable="INR",str('%.2f'%(tax))
Taxable.set(taxable)

netpay=paydue-tax
netpays="INR",str('%.2f'%(netpay))
NetPayable.set(netpays)
 overtimehours=(hoursworkedperweek-40)+wagesperhours*1.5
overtime="INR",str('%.2f'%(overtimehour
s)) OverTimeBonus.set(overtime)
elif hoursworkedperweek<=40:
overtimepay=(hoursworkedperweek-
40)+wagesperhours*1.5
overtimehrs="INR",str('%.2f'%(overtimepay))
OverTimeBonus.set(overtimehrs)
return

#========================Variables============================#
Name=StringVar()
Address=StringVar()
HoursWorked=StringVar()
wageshour=StringVar()
Payable=StringVar()
Taxable=StringVar()
NetPayable=StringVar()
GrossPayable=StringVar()
OverTimeBonus=StringVar()
Employer=StringVar()
NINumber=StringVar()
TimeOfOrder=StringVar()
DateOfOrder=StringVar()
DateOfOrder.set(time.strftime("%d/%m/%Y"))
#====================== Label Widget======================#
lblName=Label(fla,text="Name",font=('arial',16,'bold'),bd=20,fg="red",
bg="powder blue").grid(row=0,column=0)
lblAddress=Label(fla,text="Address",font=('arial',16,'bold'),bd=20,fg="r
ed",bg="powder blue").grid(row=0,column=2)
lblEmployer=Label(fla,text="Employer",font=('arial',16,'bold'),bd=20,fg
="red",bg="powder blue").grid(row=1,column=0)
lblNINumber=Label(fla,text="NINumber",font=('arial',16,'bold'),bd=20,fg="
red",bg="powder blue").grid(row=1,column=2)
lblHoursWorked=Label(fla,text="HoursWorked",font=('arial',16,'bold'),bd=
20,fg="red",bg="powder blue").grid(row=2,column=0)
lblHourlyRate=Label(fla,text="HourlyRate",font=('arial',16,'bold'),bd=20,fg
="red",bg="powder blue").grid(row=2,column=2)
lblTax=Label(fla,text="Tax",font=('arial',16,'bold'),bd=20,anchor='w',fg="re
d",bg="powder blue").grid(row=3,column=0)
lblOverTime=Label(fla,text="OverTime",font=('arial',16,'bold'),bd=20,fg="r
ed",bg="powder blue").grid(row=3,column=2)
lblGrossPay=Label(fla,text="GrossPay",font=('arial',16,'bold'),bd=20,fg="re
d",bg="powder blue").grid(row=4,column=0)
lblNetPay=Label(fla,text="NetPay",font=('arial',16,'bold'),bd=20,fg="red",b
g="powder blue").grid(row=4,column=2)
#====================== Entry Widget======================#

etxname=Entry(fla,textvariable=Name,font=('arial',16,'bold'),bd=16
,width=22,justify='left') etxname.grid(row=0,column=1)

etxaddress=Entry(fla,textvariable=Address,font=('arial',16,'bold'),b
d=16,width=22,justify='left') etxaddress.grid(row=0,column=3)
etxemployer=Entry(fla,textvariable=Employer,font=('arial',16,'bold'),bd
=16,width=22,justify='lef t')etxemployer.grid(row=1,column=1)

etxhoursworked=Entry(fla,textvariable=HoursWorked,font=('arial',16,'
bold'),bd=16,width=22,justify='left')etxhoursworked.grid(row=2,colum
n=1)

etxwagesperhours=Entry(fla,textvariable=wageshour,font=('arial',16,'b
old'),bd=16,width=22,justify='left')etxwagesperhours.grid(row=2,colu
mn=3)

etxnin=Entry(fla,textvariable=NINumber,font=('arial',16,'bold'),bd=1
6,width=22,justify='left') etxnin.grid(row=1,column=3)

etxgrosspay=Entry(fla,textvariable=Payable,font=('arial',16,'bold'),bd=
16,width=22,justify='left') etxgrosspay.grid(row=4,column=1)

etxnetpay=Entry(fla,textvariable=NetPayable,font=('arial',16,'bold'),bd
=16,width=22,justify='lef t')etxnetpay.grid(row=4,column=3)
etxtax=Entry(fla,textvariable=Taxable,font=('arial',16,'bold'),bd=16,width=2
2,justify='left') etxtax.grid(row=3,column=1)

etxovertime=Entry(fla,textvariable=OverTimeBonus,font=('arial',16,'bold'),
bd=16,width=22,justi fy='left')etxovertime.grid(row=3,column=3)
#============================ Text widget============================#

payslip=Label(f2,textvariable=DateOfOrder,font=('arial',21,'bold'),fg="red
",bg="powder blue").grid(row=0,column=0)
txtpayslip=Text(f2,height=22,width=34,bd=16,font=('arial',13,'bold'),fg="
green",bg="powder blue")
txtpayslip.grid(row=1,column=0)

#========================== ===Buttons ==============================#

btnsalary=Button(flb,text='WeeklySalary',padx=16,pady=16,bd=8,fo
nt=('arial',16,'bold'),width=14,fg="red",bg="powderblue",command
=weeklywages).grid(row=0,column=0)

btnreset=Button(flb,text='Reset',padx=16,pady=16,bd=8,font=('arial',16,'b
old'),width=14,comm and=reset,fg="red",bg="powder
blue").grid(row=0,column=1)

btnpayslip=Button(flb,text='ViewPayslip',padx=16,pady=16,bd=8,font=('ari
al',16,'bold'),width=14,command=enterinfo,fg="red",bg="powderblue").gri
d(row=0,column=2)btnexit=Button(flb,text='Exit
System',padx=16,pady=16,bd=8,font=('arial',16,'bold'),width=14,command
=exit,fg="red",bg="p owder blue").grid(row=0,column=3)
root.mainloop()
5.CONCLUSION AND RECOMMENDATION
CONCLUSION & RECOMMENDATION
Keeping track of each cost for the business manually every
month presents several issues for the current manual process.
The process of calculating always kept safe the company's
monthly costs and employee remuneration is very time-
consuming from the standpoint of the parties concerned.
The Company Budgeting and Payroll System can benefit allemp
loyees. If you’re budgeting and payroll procedures are currently
based on paper forms, you should consider switching to a
system solution. By moving to a system, you will save time,
prevent misplaced papers, and have better access to your
employees' data. Based on the findings of the analysis, it is
reasonable to infer that the presence of a Company Budgeting
and Payroll System will bring benefits since monthly budgeting
and payroll can be done from anywhere without having to come
to the office, saving money and time. A system for Company
Budgeting and Payroll of a web-based company can be
designed and used in the budgeting and payroll process in the
future. Based on the findings, the following recommendations
were developed: The Company Budgeting and Payroll System
must be kept safe at all times. We assured our personnel
that privacy was one of the essential necessities. In conclusion,
having strong security in our system is excellent for keeping our
employees' personal information private. Second, the Graphical
User Interface (GUI) must be enhanced, and the design must be
user-friendly.
FUTURE SCOPE

The future of employee payment management systems (PMS)

looks promising, with many advancements expected in the
areas of technology, integration, and employee benefits:
•Technology
•AI and machine learning (ML) will automate routine tasks like
data entry, tax calculations, and compliance management. This
will reduce errors and free up time for HR and payroll
professionals.
•Integration
•Payroll systems will integrate with other HR and business
management tools to provide real-time data and analytics. This
will help businesses make better decisions and adapt to market
changes.
•Employee benefits
•Businesses will offer financial planning tools and resources to
help employees set and track financial goals. These tools could
include budgeting apps, retirement calculators, and investment
platforms.
•Agile processing
•Payroll companies will use faster payments and automation to
speed up their processes and reduce errors.
•Cloud-based software
•Cloud-based payroll systems will allow for seamless
accessibility and collaboration across different locations.
When choosing a PMS, businesses should consider things like
scalability, user-friendliness, data security, customer support,
and cost.
 PAYROLL BIBLIOGRAPHY AND REFRENCES

Aiken, T. E. 1957. Processing our payroll on the Univac. N.A.C.A.

Bulletin (May): 1167-1178.
Allen, L. H. 1914. Payroll distribution on construction
work. Journal of Accountancy (July): 38-46.
American Payroll Association. 2005. Federal Payroll Tax Laws
and Regulations. American Payroll Association.
Asher, L. I. 1952. The payroll method-manual, machine or
mixed? N.A.C.A. Bulletin (March): 864-869.
Beaudry, D. P. Jr. 1949. An economical payroll system featuring
centralized processing of employee deductions by machine
methods. N.A.C.A. Bulletin (September): 43-58.
Brown, C. F. 1927. Labor classification and payroll
analysis. N.A.C.A. Bulletin (May 1): 789-802.
Bruce, R. 1942. Design and installation of payroll savings plans
for the purchase of war bonds; Introduction. N.A.C.A.
Bulletin (October 15): 169-192.
Burckhardt, G. H. 1959. Control of cash payroll and unclaimed
wages. N.A.A. Bulletin (April): 58-59.