Wa0001
Wa0001
MAHARASHTRA
2023-24
2
SHRI. GOPINATH MAHADEV VEDAK PRATISHTHAN’S
CERTIFICATE
Place: Tala
Project Guide
Mrs. Manasvi Wadhawal
3
PayRoll Management System
ACKNOWLEDGEMENT
“Success is to be measured not so much by the position that one has reached in life, but
as by the obstacle which he has had to overcome while trying to succeed.”
I would like to extend our heartiest thanks with a deep sense of gratitude and respect to
all those who provides me immense help and guidance during my study period.
I would like to thank our Head of Department as well as my Project Guide Prof.
Manasvi Wadhawal for providing a vision about the system and gave me an opportunity to
undertake such a great challenging and innovative work.
I have been greatly benefited from their regular critical reviews and inspiration
throughout my work.
4
PayRoll Management System
DECLARATION
The project is done in partial fulfillment of the requirements for the award of degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) to be submitted as final
semester project as part of our curriculum.
5
PayRoll Management System
SYNOPSIS
Payroll is very simple, flexible and user-friendly Management software. That takes
care of all your requirements relating to accounting and management of employees Payroll.
Payroll stores complete records of the employees, Bonus, Advance, generates Pay-slips and
Register Attendance, Computes all allowances and deductions and generates all statutory
reports.
Payroll is only salary processing software with good and wide-industry range of
clients. It offers very high flexibility in defining various allowances, deductions: leave rules
etc. for the employees and all formula for P.F etc. are definable and changeable at User's end.
Payroll Application has been designed for the purpose of maintaining details of
various allowances and deductions that needs to be given to the employees of the organization.
Also, it generates the salary sheet of the employees of the organization that assists the accounts
department in many ways. Main Objectives:
There are multiple objectives behind the designing and implementation of the Module:
• To prepare the detailed salary record of all the employees in an organization
• To maintain Allowances, Deductions, Savings and Arrears details for the employees
• To generate various important reports that provides valuable information to the top-level
management
6
PayRoll Management System
CONTENT
Chapter Name.
1. System Study
1.1 Existing System
1.2 Drawbacks Of Existing System
1.3 Need for a New System
3. Proposed system.
3.1 Working
3.2 Objective/Advantages of New System
4. System Analysis
4.1 Analysis
4.2 Problem Understanding
5. Requirement Analysis
5.1 Requirements Specification
5.2 Constraints
6. System Design 7.
Platform Used
7.1 Hardware Requirement
7.2 Software Requirement
7.3 Front End Tool: C#.NET
7.4 Languages Used
18. Reference
8
PayRoll Management System
Chapter 1
SYSTEM STUDY
In system study we study the existing system and new proposed system. In system
study we study that what are the drawbacks, and limitations exist. What are the needs of the
existing system? And also study what is the new proposed system, and how new proposed
system removes the limitations and drawbacks of the existing system. In this Section we study
the advantages of the new proposed system.
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.
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
9
PayRoll Management System
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 have
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 leave the user can get the information from
him.
6. Need more space to store: Here by using the paper work system the user need to maintain
all the documents in 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 very expensive method as lot of paper work
has to be done and lot of wastage of manpower, which increase the expanses of existing
system
8. Data sharing: The different user in the different department cannot share data
simultaneously.
3. User friendly: To make the system user friendly this system using window as its run time
environment and is developed using Visual Studio 2008, which is very user-friendly rapid
application developed tool. Because in the existing system register work was very difficult
to handled by each user and was boring job.
4. Data Security: The proposed will also prevent unauthorized access to the system. At the
very beginning, the user name and password is to be entered by the user and if it is correct
only then the permission to use the software is given to user. There are different users
according to different roles and one user can't use the resources given to another user.
5. Data Redundancy: The data is stored only once which can be accessed by any one at any
time and at any place. So it can be minimized but cannot be removed completely
1
0
PayRoll Management System
6. Easy to Access: In this database project, data can be easily access through computer
networking.
8. Time & Efforts Reduction: It requires fewer amounts of time and efforts.
10
PayRoll Management System
Chapter 2
Introduction to Payroll Management System
A user friendly GUI (Graphical User Interface) based software "Payroll Management
System" has been developed for organization, 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. The project provides
sample facilities to its users. The most important of the facilities are the report generation and
printing which provides user with the hard copies of the data also.
2.1 Features:
Preparation of salary.
Printing of Windows Based user friendly software.
Maintenance of rich electronic records of employees available at station.
Bonus
Advance
Pay slips.
Attendance record.
Standard report generation
11
PayRoll Management System
Chapter 3
PROPOSED SYSTEM
This consists of 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 he to stores data in an efficient and
nonredundant form and hence increase overall efficiency of the system.
The new system should ensure of simple and easy data entry procedures through
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.
3.1 Working
The working of the project is based on payroll system for performing its working it use Visual
Basic.NET as a front-end and SQL as a back-end. In which user perform all its functions in
Visual Basic.NET environment and all database stores in the database oracle. 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
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 very user friendly rapid application development
tool. The new system is totally graphical and 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 system, which will reduce the time
consumption, I its speed. The speed of system is measured in terms of response time i.e. the
time it takes to respond to user's request. Computer is an electronic device which can
12
PayRoll Management System
manipulate, modifies, retrieve and store information very speedily so it will be able to report
within a fraction of time
2. Reliable and Accurate: As in 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 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 proposed system each and every record is maintained on computer,
which leads to the centralization of data and every user which have the access to system can
retrieve the data at ease.
4. Low Operation and Maintenance Cost: The proposed system is not very costly as it doesn't
includes many costs and overhead expenses like file management, stationary charges etc.
6. User Friendly: 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 existing system, in 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.
13
PayRoll Management System
Chapter 4
SYSTEM ANALYSIS
4.1 Analysis
Analysis is a detailed study of the various operations performed by a system and their
relationship within and outside of the system. A key question is: What must be done to solve
the problem? One aspect of analysis is defining the boundaries of the system and determining
whether or not a candidate system should consider other related systems. During analysis
data are collected on the available files, decision points and transactions handled by the
present system. Some logical system models and tools are used in analysis are data flow
diagrams, interviews, on-sight observations and questionnaires etc. The interview is a
commonly used tool in analysis. It requires special skills and sensitivity to the subjects being
interviewed. Bias in data collection and interpretation can be a problem. Training, experience
and common sense are required for collection of the information needed to do the analysis.
Once analysis is completed, the analyst has a firm understanding of what is to be done. The
next step is to decide how the problem might be solved. Thus, in system design, we move
from the logical to the physical aspect of the life cycle.
14
PayRoll Management System
Chapter 5
REQUIREMENT ANALYSIS
5.2 Constrain
The company functions manually. This system has a lot of problems as the work done is very
time consuming and sometimes errors also creep in, so there was an urgent need to develop
a system, which is simple .error free and suits the working of the institution. The software
"Payroll Management System" is such software, which will serve to these purposes.
Constraints are validations, which are used to check that the software is working properly. The
software also has some constraints, which make it a successful application
15
PayRoll Management System
Chapters 6
SYSTEM DESIGN
The development of the Transaction Control Software consisted of studying of the
existing manual system and developing an efficient computerized system that emphasizes on
easy storage and retrieval of data in the database.
The new system should ensure of simple and easy data entry procedures through
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.
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. Moreover,
the new system should provide a very easy to use interface, so that user should feel at home
throughout the working of the system.
16
PayRoll Management System
Chapter 7
PLATFORM USED
Software Specification
Visual Studio .NET 2015
C# Language
SQL
17
PayRoll Management System
integrated debugger, and many other tools to make it easier to develop applications based on
the C# language and the .NET Framework.
C#: C# syntax is highly expressive, yet it is also simple and easy to learn. The curlybrace
syntax of C# will be instantly recognizable to anyone familiar with C, C++ or Java.
Developers who know any of these languages are typically able to begin to work
productively in C# within a very short time. C# syntax simplifies many of the
complexities of C++ and provides powerful features such as nullable value types,
enumerations, delegates, lambda expressions and direct memory access, which are not
found in Java. C# supports generic methods and types, which provide increased type
safety and performance, and iterators, which enable implementers of collection classes to
define custom iteration behaviors that are simple to use by client code.
LanguageIntegrated Query (LINQ) expressions make the strongly-typed query a
firstclass language construct.
18
PayRoll Management System
DETAIL LIFECYCLE
OF
THE PROJECT
19
PayRoll Management System
Chapter 8
DATA FLOW Diagram
A Data Flow Diagram (DFD) is a diagram that describes the flow of data and the processes
that change or transform data throughout a system. It's a structured analysis and design tool
that can be used for flowcharting in place of, or in association with, information oriented and
process oriented system flowcharts. When analysts prepare the Data Flow Diagram, they
specify the user needs at a level of detail that virtually determines the information flow into
and out of the system and the required data resources. This network is constructed by using
a set of symbols that do not imply a physical implementation. The Data Flow Diagram
reviews the current physical system, prepares input and output specification, specifies the
implementation plan etc. Four basic symbols are used to construct data flow diagrams. They
are symbols that represent data source, data flows, and data transformations and data storage.
The points at which data are transformed are represented by enclosed figures, usually circles,
which are called nodes.
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 modulated. It’s designed to be an at-a-glance view of Task,
Pay Receipt and Department showing the system as a single high-level process, with its
relationship to external entities of Employee, Admin . It should be easily understood by a wide
audience, including Employee, Admin In zero level DFD of Payroll Management System, we
have described the high level flow of the Payroll system.
20
PayRoll Management System
First Level DFD (1st Level) 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 of the functionality of the Payroll
Management System as a whole. It also identifies internal data stores of Department, Pay-Slip,
Salary, Employee, Bonus and Advance, Attendance that must be present in order for the Payroll
system to do its job, and shows the flow of data between the various parts of Employee, Pay-
Slip, Department, Attendance, Bonus and Advance 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.
21
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,
PaySlip, Bonus and Advance, Salary, Attendance and Employee
22
PayRoll Management System
Chapter no 9
E-R (entity- relationship ) Diagram
While able to describe just about any system, ER diagrams are most often associated with
complex databases that are used in software engineering and IT networks. In particular, ER
diagrams are frequently used during the design stage of a development process in order to
identify different system elements and their relationships with each other
23
PayRoll Management System
Chapter no.10
USE-CASE Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements
of Payroll Management System. It represents the methodology used in system analysis to
identify, clarify, and organize system requirements of Payroll Management System. The main
actors of Payroll Management System in this Use Case Diagram are: Super Admin, System
User,
Accountant, Employee, who perform the different type of use cases such as Login, Add New
Employee, Add new Bonus and Advance Salary, Manage Attendance, Manage Employee
Salary Details, Manage Department, Manage Salary Issue, Generate Payroll, Logout and Full
Payroll Management System Operations. Major elements of the UML use case diagram of
Payroll Management System are shown on the picture below.
24
PayRoll Management System
Chapter no.11
ACTIVITY Diagram
This is the Activity UML diagram of Payroll Management System which shows the
flows between the activity of Salary, Payments, Employee. The main activity involved in this
UML Activity Diagram of Payroll Management System are as follows:
• Salary Activity
• Bonus and Advance Activity
• Employee Activity
• Attendance Activity
• Total Paid Amount
• Pay-Slip Activity
25
PayRoll Management System
Chapter no.12
CLASS Diagram
A class diagram in the Unified Modeling 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.
The class diagram is the main building block of object-oriented modeling. It is used both for
general conceptual modeling of the systematic of the application, and for detailed modeling
translating the models into programming code. Class diagrams can also be used for data
modeling. The classes in a class diagram represent both the main elements, interactions in the
application, and the classes to be programmed.
In the diagram, classes are represented with boxes that contain three compartments:
• The top compartment contains the name of the class. It is printed in bold and centered, and
In the design of a system, a number of classes are identified and grouped together in a class
diagram that helps to determine the static relations between them. With detailed modelling,
the classes of the conceptual design are often split into a number of subclasses.
In order to further describe the behavior of systems, these class diagrams can be complemented
by a state diagram or UML state machine.
26
PayRoll Management System
27
PayRoll Management System
Chapter no.13
SEQUENCE Diagram
This sequence diagram shows object interactions arranged in time sequence. It depicts the
objects and classes involved in the scenario and the sequence of messages exchanged between
the objects needed to carry out the functionality of the scenario. Sequence diagrams are
typically associated with use case realizations in the Logical View of the system under
development.
28
PayRoll Management System
Chapter no.14
DATABASE TABLES
• Employees Table
• Bonus Table
29
PayRoll Management System
• Advance Table
• Attendance Table
30
PayRoll Management System
31
PayRoll Management System
CHAPTER 15
SNAPSHOTS
*Login Page
*Coding
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
namespace Payroll_Management_System
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}
{
Dashboard ds = new Dashboard();
ds.Show();
this.Hide();
}
else
{
MessageBox.Show("Wrong Admin or Password");
}
}
33
PayRoll Management System
*Home Page
*Coding
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data; using
System.Drawing; using
System.Linq; using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms; using
System.Data.SqlClient; namespace
PayRoll_Management
{
public partial class Form1 : Form
{
SqlConnection con = new SqlConnection("Data Source=DESKTOP-
NPHCRPV;Initial Catalog=PayRollManagement;Integrated
Security=True"); public
Form1()
{
InitializeComponent();
CountEmployee();
CountManagers();
SumSalary();
SumBonus(); }
public void CountEmployee()
{ con.Open();
SqlDataAdapter sda = new SqlDataAdapter("Select Count(*) from
34
PayRoll Management System
EmployeeTb1", con);
DataTable dt = new DataTable(); sda.Fill(dt);
EmpLb.Text = dt.Rows[0][0].ToString(); con.Close();
}
public void CountManagers()
{
String Pos = "Manager";
con.Open();
SqlDataAdapter sda = new SqlDataAdapter("Select Count(*) from
EmployeeTb1 where EmpPosition='"+Pos+"'", con);
DataTable dt = new DataTable(); sda.Fill(dt);
ManaLb.Text = dt.Rows[0][0].ToString(); con.Close();
}
public void SumSalary()
{
con.Open();
SqlDataAdapter sda = new SqlDataAdapter("Select Sum(EmpSBalance)
from SalaryTb", con);
DataTable dt = new DataTable();
sda.Fill(dt);
SalaryLb.Text ="Rs" +dt.Rows[0][0].ToString(); con.Close();
}
public void SumBonus()
{
con.Open();
SqlDataAdapter sda = new SqlDataAdapter("Select Sum(EmpSBonusAm)
from SalaryTb", con);
DataTable dt = new DataTable();
sda.Fill(dt);
BonusLb.Text ="Rs" +dt.Rows[0][0].ToString(); con.Close();
36
PayRoll Management System
*Employees Page
*Coding
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using System.Data.SqlClient;
namespace Payroll_Management_System
{
public partial class Employees : Form
{
SqlConnection con = new SqlConnection("Data Source=SURAJSAKPAL\\SQLEXPRESS;Initial
Catalog=PayrollManagment;Integrated Security = True");
public Employees()
{
InitializeComponent();
ShowEmployee();
}
private void ShowEmployee()
{
con.Open();
String Query = "Select * from EmployeeTb1";
SqlDataAdapter sda = new SqlDataAdapter(Query, con);
SqlCommandBuilder Builder = new SqlCommandBuilder(sda);
var ds = new DataSet();
sda.Fill(ds);
EmpDGV.DataSource = ds.Tables[0];
con.Close();
}
}
private void label14_Click(object sender, EventArgs e)
{
Dashboard Obj = new Dashboard();
Obj.Show();
}
38
PayRoll Management System
}
catch //(Exception Ex)
{
//MessageBox.Show(Ex.Message);
}*/
}
}
int key = 0;
private void EmpDVG_CellContentClick(object sender, DataGridViewCellEventArgs e)
{
EmpName.Text =EmpDGV.SelectedRows[0].Cells[1].Value.ToString();
EmpGender.SelectedItem =EmpDGV.SelectedRows[0].Cells[2].Value.ToString();
EmpDOB.Text =EmpDGV.SelectedRows[0].Cells[3].Value.ToString();
EmpNumber.Text =EmpDGV.SelectedRows[0].Cells[4].Value.ToString();
EmpAddress.Text =EmpDGV.SelectedRows[0].Cells[5].Value.ToString();
EmpPosition.SelectedItem =EmpDGV.SelectedRows[0].Cells[6].Value.ToString();
EmpJoinDate.Text =EmpDGV.SelectedRows[0].Cells[7].Value.ToString();
EmpQuali.SelectedItem =EmpDGV.SelectedRows[0].Cells[8].Value.ToString();
EmpSalary.Text =EmpDGV.SelectedRows[0].Cells[9].Value.ToString();
if (EmpName.Text == "")
{
key = 0;
}
else
{
key =Convert.ToInt32(EmpDGV.SelectedRows[0].Cells[0].Value.ToString());
}
}
private void btnEdit_Click(object sender, EventArgs e)
39
PayRoll Management System
{
if (EmpName.Text == "" || EmpNumber.Text == "" ||EmpGender.SelectedIndex == -1 ||EmpAddress.Text
== "" ||EmpSalary.Text == "" || EmpQuali.SelectedIndex == -1
||EmpPosition.SelectedIndex == -1)
{
MessageBox.Show("Missing Information");
}
else
{
try
{
con.Open();
SqlCommand cmd = new SqlCommand("Update EmployeeTb1 Set EmpName = @EN,
EmpGender = @EG, EmpDOB = @ED,EmpPhoneNumber = @EP, EmpAdd = @EA, EmpPosition = @EPos, EmpJoinDate
= @EJD,EmpQuali = @EQ, EmpBaseSalary = @EBS where EmpId = @EmpKey" , con);
cmd.Parameters.AddWithValue("@EN",EmpName.Text);
cmd.Parameters.AddWithValue("@EG",EmpGender.SelectedItem.ToString());
cmd.Parameters.AddWithValue("@ED",EmpDOB.Value.Date);
cmd.Parameters.AddWithValue("@EP",EmpNumber.Text);
cmd.Parameters.AddWithValue("@EA", EmpAddress.Text);
cmd.Parameters.AddWithValue("@EPos",EmpPosition.SelectedItem.ToString());
cmd.Parameters.AddWithValue("@EJD",EmpJoinDate.Value.Date);
cmd.Parameters.AddWithValue("@EQ",EmpQuali.SelectedItem.ToString());
cmd.Parameters.AddWithValue("@EBS",EmpSalary.Text);
cmd.Parameters.AddWithValue("@EmpKey", key);
cmd.ExecuteNonQuery();
MessageBox.Show("Employee Updated");
con.Close();
ShowEmployee();
Clear();
}
catch (Exception Ex)
{
MessageBox.Show(Ex.Message);
}
}
}
cmd.Parameters.AddWithValue("@EmpKey", key);
cmd.ExecuteNonQuery();
MessageBox.Show("Employee Deleted");
con.Close();
ShowEmployee();
}
catch (Exception Ex)
{
MessageBox.Show(Ex.Message);
}
31
0
PayRoll Management System
*Bonus Page
*Coding
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
using System.Data.SqlClient;
namespace Payroll_Management_System
{
public partial class bonus : Form
{
SqlConnection con = new SqlConnection("Data Source=SURAJSAKPAL\\SQLEXPRESS;Initial
Catalog=PayrollManagment;Integrated Security = True");
public bonus()
{
InitializeComponent();
ShowBonus();
}
private void Clear()
{
BNameTb.Text = "";
BAmountTb.Text = "";
Key = 0;
}
private void ShowBonus()
{
31
1
PayRoll Management System
con.Open();
String Query = "Select * from Bonus";
SqlDataAdapter sda = new SqlDataAdapter(Query, con);
SqlCommandBuilder Builder = new SqlCommandBuilder(sda);
var ds = new DataSet(); sda.Fill(ds);
BonusDGV.DataSource = ds.Tables[0]; con.Close();
}
private void label17_Click(object sender, EventArgs e)
{
Dashboard obj = new Dashboard();
obj.Show();
}
31
2
PayRoll Management System
{
MessageBox.Show(Ex.Message);
}
}
}
40
PayRoll Management System
Obj.Show();
}
private void label8_Click(object sender, EventArgs e)
{
Employees Obj = new Employees();
Obj.Show();
}
int Key = 0;
private void BonusDGV_CellContentClick_1(object sender, DataGridViewCellEventArgs e)
{
BNameTb.Text = BonusDGV.SelectedRows[0].Cells[1].Value.ToString();
BAmountTb.Text = BonusDGV.SelectedRows[0].Cells[2].Value.ToString();
if (BNameTb.Text == "")
{
Key = 0;
}
else
{
Key = Convert.ToInt32(BonusDGV.SelectedRows[0].Cells[0].Value.ToString());
}
}
}
}
41
PayRoll Management System
*Advance Page
*Coding
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
using System.Data.SqlClient;
namespace Payroll_Management_System
{
public partial class Advancs : Form
{
SqlConnection con = new SqlConnection("Data Source=SURAJSAKPAL\\SQLEXPRESS;Initial
Catalog=PayrollManagment;Integrated Security = True");
public Advancs()
{
InitializeComponent();
ShowAdvance();
}
42
PayRoll Management System
Key = 0;
}
private void ShowAdvance()
{
con.Open();
String Query = "Select * from AdvanceTb2";
SqlDataAdapter sda = new SqlDataAdapter(Query, con);
SqlCommandBuilder Builder = new SqlCommandBuilder(sda);
var ds = new DataSet(); sda.Fill(ds);
ADGV.DataSource = ds.Tables[0]; con.Close();
}
private void label17_Click(object sender, EventArgs e)
{
Dashboard obj = new Dashboard();
obj.Show();
}
43
PayRoll Management System
}
else
{
try
{
con.Open();
SqlCommand cmd = new SqlCommand("insert into AdvanceTb2(AdName,
AdAmount)values(@BN, @BA)", con);
cmd.Parameters.AddWithValue("@BN", ANameTb.Text);
cmd.Parameters.AddWithValue("@BA", AAmountTb.Text);
cmd.ExecuteNonQuery();
MessageBox.Show("Advance Saved");
con.Close(); ShowAdvance();
Clear();
}
catch (Exception Ex)
{
MessageBox.Show(Ex.Message);
}
}
}
private void btnDelete_Click(object sender, EventArgs e)
{
if (Key == 0)
{
MessageBox.Show("Select The I Advance");
}
else
{
try
{
con.Open();
SqlCommand cmd = new SqlCommand("Delete from AdvanceTb2 Where AID = @AKey",
con);
cmd.Parameters.AddWithValue("@AKey", Key);
cmd.ExecuteNonQuery();
MessageBox.Show("Advance Deleted");
con.Close(); ShowAdvance();
}
catch (Exception Ex)
{
MessageBox.Show(Ex.Message);
}
}
}
int Key = 0;
private void ADGV_CellContentClick_1(object sender, DataGridViewCellEventArgs e)
{
ANameTb.Text = ADGV.SelectedRows[0].Cells[1].Value.ToString();
AAmountTb.Text = ADGV.SelectedRows[0].Cells[2].Value.ToString();
if (ANameTb.Text == "")
{
Key = 0;
}
else
{
Key = Convert.ToInt32(ADGV.SelectedRows[0].Cells[0].Value.ToString());
}
}
44
PayRoll Management System
{
if (ANameTb.Text == "" || ANameTb.Text == "")
{
MessageBox.Show("Missing Information");
}
else
{
try
{
con.Open();
SqlCommand cmd = new SqlCommand("Update AdvanceTb2 Set AdName = @BN, AdAmount
= @BA Where AID = @AKey", con);
cmd.Parameters.AddWithValue("@BN", ANameTb.Text);
cmd.Parameters.AddWithValue("@BA", AAmountTb.Text);
cmd.Parameters.AddWithValue("@AKey", Key);
cmd.ExecuteNonQuery();
MessageBox.Show("Advance Updated");
con.Close(); ShowAdvance();
Clear();
}
catch (Exception Ex)
{
MessageBox.Show(Ex.Message);
}
}
}
}
}
45
PayRoll Management System
*Attendance Page
*Coding
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
using System.Data.SqlClient;
namespace Payroll_Management_System
{
public Attendance()
{
InitializeComponent();
ShowAttendance();
GetEmployees();
}
private void Clear()
{
46
PayRoll Management System
AtNameTb.Text = "";
AtAbsentTb.Text = "";
AtPresentTb.Text = "";
AtExcusedTb.Text = "";
Key = 0;
}
private void ShowAttendance()
{
con.Open();
String Query = "Select * from AttendanceTb1";
SqlDataAdapter sda = new SqlDataAdapter(Query, con);
SqlCommandBuilder Builder = new SqlCommandBuilder(sda);
var ds = new DataSet(); sda.Fill(ds);
AtDGV.DataSource = ds.Tables[0]; con.Close();
}
private void GetEmployees()
{
con.Open();
SqlCommand cmd = new SqlCommand("Select * from EmployeeTb1", con);
SqlDataReader Rdr;
Rdr = cmd.ExecuteReader(); DataTable
dt = new DataTable();
dt.Columns.Add("EmpId", typeof(int));
dt.Load(Rdr);
AtEmpIdTb.ValueMember = "EmpId";
AtEmpIdTb.DataSource = dt; con.Close();
}
private void GetEmployeeName()
{
con.Open();
String Query = " Select * from EmployeeTb1 where EmpId=" +
AtEmpIdTb.SelectedValue.ToString() + "";
SqlCommand Cmd = new SqlCommand(Query, con);
DataTable dt = new DataTable();
SqlDataAdapter sda = new SqlDataAdapter(Cmd); sda.Fill(dt);
foreach (DataRow dr in dt.Rows)
{
AtNameTb.Text = dr["EmpName"].ToString();
}
con.Close();
}
private void label17_Click(object sender, EventArgs e)
{
Dashboard obj = new Dashboard();
obj.Show();
}
47
PayRoll Management System
obj.Show();
}
}
else
{
try
{
con.Open();
SqlCommand cmd = new SqlCommand("insert into AttendanceTb1(AtId, AtName,
AtPresent, AtAbsent, AtExcused,AtPeriod)values(@AtI, @AtN, @AtP, @AtA, @AtE, @AtPe)", con);
cmd.Parameters.AddWithValue("@AtN", AtNameTb.Text);
cmd.Parameters.AddWithValue("@AtI", AtEmpIdTb.Text);
cmd.Parameters.AddWithValue("@AtP", AtPresentTb.Text);
cmd.Parameters.AddWithValue("@AtA", AtAbsentTb.Text);
cmd.Parameters.AddWithValue("@AtE", AtExcusedTb.Text);
cmd.Parameters.AddWithValue("@AtPe", AtPeriodTb.Value.Date);
cmd.ExecuteNonQuery();
MessageBox.Show("Attendance Saved");
con.Close(); ShowAttendance();
Clear();
}
catch (Exception Ex)
{
MessageBox.Show(Ex.Message);
}
}
}
private void btnEdit_Click(object sender, EventArgs e)
{
if (AtNameTb.Text == "" || AtPresentTb.Text == "" || AtEmpIdTb.SelectedIndex == -1 ||
AtAbsentTb.Text == "" ||AtExcusedTb.Text == "")
{
48
PayRoll Management System
MessageBox.Show("Missing Information");
}
else
{
con.Open();
SqlCommand cmd = new SqlCommand("Update AttendanceTb1 Set AtId = @ATI,AtName =
@AtN, AtPresent = @AtP, AtAbsent = @AtA, AtExcused = @AtE,AtPeriod = @AtPe where AtNum = @AtKey",
con);
cmd.Parameters.AddWithValue("@AtN", AtNameTb.Text);
cmd.Parameters.AddWithValue("@AtI", AtEmpIdTb.Text);
cmd.Parameters.AddWithValue("@AtP", AtPresentTb.Text);
cmd.Parameters.AddWithValue("@AtA", AtAbsentTb.Text);
cmd.Parameters.AddWithValue("@AtE", AtExcusedTb.Text);
cmd.Parameters.AddWithValue("@AtPe", AtPeriodTb.Value.Date);
cmd.Parameters.AddWithValue("@AtKey", Key);
cmd.ExecuteNonQuery();
MessageBox.Show("Attendance Updated");
con.Close(); ShowAttendance();
Clear();
/* try
{
}
catch (Exception Ex)
{
MessageBox.Show(Ex.Message);
}*/
}
}
}
int Key = 0;
private void AtDGV_CellContentClick_1(object sender, DataGridViewCellEventArgs e)
{
AtEmpIdTb.SelectedItem = AtDGV.SelectedRows[0].Cells[1].Value.ToString();
AtNameTb.Text = AtDGV.SelectedRows[0].Cells[2].Value.ToString();
49
PayRoll Management System
AtPresentTb.Text = AtDGV.SelectedRows[0].Cells[3].Value.ToString();
AtAbsentTb.Text = AtDGV.SelectedRows[0].Cells[4].Value.ToString();
AtExcusedTb.Text = AtDGV.SelectedRows[0].Cells[5].Value.ToString();
AtPeriodTb.Text = AtDGV.SelectedRows[0].Cells[6].Value.ToString();
if (AtNameTb.Text == "")
{
Key = 0;
}
else
{
Key =
Convert.ToInt32(AtDGV.SelectedRows[0].Cells[0].Value.ToString());
}
50
PayRoll Management System
*Coding :
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
using System.Data.SqlClient;
namespace Payroll_Management_System
51
PayRoll Management System
public salary()
InitializeComponent();
GetEmployees();
GetAttendance();
GetBonus();
ShowSalary();
SName.Text = "";
salalry.Text = "";
SAbsence.Text = "";
SExcused.Text = "";
//Key = 0;
con.Open();
52
PayRoll Management System
con.Open();
SqlDataReader Rdr;
dt = new DataTable();
dt.Columns.Add("EmpId", typeof(int));
dt.Load(Rdr);
SId.ValueMember = "EmpId";
con.Open();
SqlDataReader Rdr;
= new DataTable();
dt.Columns.Add("Bname", typeof(String));
dt.Load(Rdr);
SBonus.ValueMember = "BName";
con.Open();
SqlDataReader Rdr;
53
PayRoll Management System
Rdr = cmd.ExecuteReader();
SAtte.ValueMember = "AtNum";
SAtte.DataSource = dt;
con.Close();
con.Open();
String Query = " Select * from EmployeeTb1 where EmpId =" + SId.SelectedValue.ToString() + "";
sda.Fill(dt);
SName.Text = dr["EmpName"].ToString();
salalry.Text = dr["EmpBaseSalary"].ToString();
con.Close();
con.Open();
String Query = " Select * from AttendanceTb1 where AtNum = " + SAtte.SelectedValue.ToString() + "";
54
PayRoll Management System
SPresence.Text = dr["AtPresent"].ToString();
SAbsence.Text = dr["AtAbsent"].ToString();
SExcused.Text = dr["AtExcused"].ToString();
con.Close();
con.Open();
String Query = " Select * from Bonus where BName='" + SBonus.SelectedValue.ToString() + "'";
sda.Fill(dt);
bonuss.Text = dr["BAmount"].ToString();
bonuss.Text = dr["BAmount"].ToString();
con.Close();
Obj.Show();
55
PayRoll Management System
Obj.Show();
Application.Exit();
obj.Show();
obj.Show();
obj.Show();
56
PayRoll Management System
else
Pres = Convert.ToInt32(SPresence.Text);
Abs = Convert.ToInt32(SAbsence.Text);
Exc = Convert.ToInt32(SExcused.Text);
MessageBox.Show("Missing Information");
else
57
PayRoll Management System
cmd.Parameters.AddWithValue("@SId", SId.SelectedValue.ToString());
cmd.Parameters.AddWithValue("@SN", SName.Text);
cmd.Parameters.AddWithValue("@SBS", salalry.Text);
cmd.Parameters.AddWithValue("@SB", SBonus.Text);
cmd.Parameters.AddWithValue("@SA", SAdvance.Text);
cmd.Parameters.AddWithValue("@SBA", bonuss.Text);
cmd.Parameters.AddWithValue("@SBal", GrdTot);
cmd.Parameters.AddWithValue("@SPe", Period);
cmd.ExecuteNonQuery();
MessageBox.Show("Salary Saved");
con.Close(); ShowSalary();
Clear();
try
MessageBox.Show(Ex.Message);
GetBAmount();
58
PayRoll Management System
GetAttendanceDate();
MessageBox.Show("Missing Information");
else
try
SId.SelectedValue.ToString()); cmd.Parameters.AddWithValue("@SN",
cmd.Parameters.AddWithValue("@SB", SBonus.Text);
cmd.Parameters.AddWithValue("@SA", SAdvance.Text);
cmd.Parameters.AddWithValue("@SBA", bonuss.Text);
cmd.Parameters.AddWithValue("@SBal", GrdTot);
cmd.Parameters.AddWithValue("@SPe", Period);
cmd.Parameters.AddWithValue("@SalKey", key);
cmd.ExecuteNonQuery();
MessageBox.Show("Salary Updated");
59
PayRoll Management System
con.Close(); ShowSalary();
Clear();
MessageBox.Show(Ex.Message);
fm.Show();
int key = 0;
SId.SelectedValue = SDGV.SelectedRows[0].Cells[1].Value.ToString();
SName.Text = SDGV.SelectedRows[0].Cells[2].Value.ToString();
salalry.Text = SDGV.SelectedRows[0].Cells[3].Value.ToString();
SBonus.Text = SDGV.SelectedRows[0].Cells[4].Value.ToString();
SAdvance.Text = SDGV.SelectedRows[0].Cells[5].Value.ToString();
SBonus.Text = SDGV.SelectedRows[0].Cells[6].Value.ToString();
SBalancy.Text = SDGV.SelectedRows[0].Cells[7].Value.ToString();
if (SName.Text == "")
key = 0;
60
PayRoll Management System
else
key = Convert.ToInt32(SDGV.SelectedRows[0].Cells[0].Value.ToString());
if (key == 0)
MessageBox.Show("Missing Information");
else
try
con.Open();
SqlCommand cmd = new SqlCommand("Delete from SalaryTb Where SalNum = @EmpKey", con);
cmd.Parameters.AddWithValue("@EmpKey", key);
cmd.ExecuteNonQuery();
MessageBox.Show("Salary Deleted");
con.Close(); ShowSalary();
MessageBox.Show(Ex.Message);
61
PayRoll Management System
GetEmployeeName();
GetAttendance();
Application.Exit();
62
PayRoll Management System
Chapter no.17
Accurate and correct payroll is very important to your employees and important
to you as a business owner. Payroll is more than just sending out paychecks every two
weeks. You need to comply with and make sure you pay all of the federal, state and local
taxes that are tied to having employees. A payroll service will handle the details and keep
you out of trouble with the taxman: however, such a service does have some drawbacks.
17.1.1 Advantages:
The decision to use a payroll service could be a personal choice dictated by how
much control you want to have over the different aspects of you company. If you keep
payroll in house, it is easy to make changes and answer questions concerning the pay
information of your employees. The decision to use a payroll service means giving up
some control of that portion of your business. However, payroll is primarily a repetitive
operation, so letting someone else handle the details can free up time for more productive
tasks.
17.1.1.2 Costs:
A payroll services adds another cost to your budget. If you are a small business
with few employees on a tight budget, paying for the service may not fit into the budget.
The cost of a payroll service for a small business will be proportionately larger than for a
bigger business. You need to compare the cost of the service to the time required to
complete the payroll in house and what that time would be worth doing other work.
63
PayRoll Management System
Using a payroll service means your employee pay data will be on some other company's
computer system. This may be an issue if you need to make a change or if an employee
has a problem with her paycheck. How much the fact that pay information is not kept in
your business depends on how much access the service provides. You may want to compare
services with this need in mind as wells comparing costs.
17.1.1.4 Compliance
Possibly the biggest benefit of using a payroll service is that the service will keep
your business compliant with payroll tax laws and changes. While you are an expert at
your business, unless your business is a CPA firm, you probably dont have the time to
become a payroll tax expert. The payroll service can determine what taxes need to be
withheld from employees, what you need to pay and send in the money to the correct
agencies.
17.1.2 Disadvantages:
17.1.2.1 Manual:
erroneous tax withholding, reporting and payment occur. This can result in penalties from
federal and state tax agencies
64
PayRoll Management System
17.1.2.2 Outsourced/External:
The employer uses the outsourced or external payroll system when it hires a
payroll service provider. The latter has a payroll staff that, for a flat fee, processes its
client's amp risqué; payroll. Services vary by provider, but most payroll service providers
perform paycheck and direct deposit processing. Many also offer payroll tax and benefits
administration. Because the employer is entrusting its payroll tasks to an off-site
company, it can suffer from not having immediate help when needed. If the payroll service
provider has many clients, the employer may have to wait in line to get any problems
resolved. Depending on the urgency of the situation, this can be frustrating to the
employer. Furthermore, according to the Internal Revenue Service, if the payroll service
provider makes a tax error, the employer alone incurs the penalty. With the payroll being
processed off-site, if there amp; rsquos a problem with it, the employer may not know
about it until payday.
17.1.3 Scope:
17.1.4 Limitations:
On the other hand, this study limits only to the proposed enhancement Computerized
Payroll System of the Q Works. A proposed system which can only be access by
authorized person. It does not support network topology implementation, online program
or online transaction.
65
PayRoll Management System
REFERENCE
BOOKS
WEBSITES
https://www.google.com
https://www.wikipedia.org
www.employeesalarysoftware.com
www.payrollsoftware.co.in/
https://www.c-sharpcorner.com
66