Payroll Usecase
Payroll Usecase
I. Introduction
1. In-house payroll
Like the name suggests the payroll is managed in-house, meaning one/group of
employees within the company take care of processing the payroll. Be it staying updated with
tax laws, or tax filing/withholding etc. every part of payroll is taken care of from within. In
house payroll works best for small businesses.
Cost cutting
An online portal is provided through which you can manage your payroll utilising the
automation tools. From data entry to tracking employee hours, everything can be managed in
cloud. The tools and features are optimised for your payroll so you can keep track of every
data about your employee. Tax filing, reporting and other payroll related services are also
provided on cloud.
You can hire an outside payroll service agency to take care of your payroll. With a
payroll agency handling your payroll all obligations including payment of wages, deductions
etc. will be completely handled by them on your behalf. This will ensure accuracy and can
even avoid overdue payments.
Benefits of Managed payroll service:
Check if it has a time-tracking module. A time tracking module can help keep track of
all employees working in your organization, whether they are working hourly or doing
a general shift etc. This feature allows them log in and log off on the portal avoiding the
hassle of manual entries, improving efficiency and accuracy.
2. Direct Deposit
Running behind the HR to resolve your salary issues happens more often than you
think. With the direct deposit feature in the payroll system software, the employee
portal automatically generates a payslip when the salary is paid to the employees. You
can access your salary slips to get details about any cuts, tax deductions etc.
3. Expense Management
Keeping track of Reimbursements like travel and lodging expenses of employees can
become quite chaotic. With a payroll processing system software, the expenses
management can be integrated making it a simpler affair. A payroll software must be
able to automate your expense reports and payment processes. This can save time and
enhance the accuracy of reimbursements.
4. Compensation management
5. Employee Self-service
This feature poses one of the biggest advantages for not just the employees but for the
HR team as well. Employees are given access to their records and can change any
personal information at any point in time. It gives them direct access to their leave
balances, w-2 forms etc. This drastically reduces the workload of the HR giving them
time to work on other essential tasks of the organization.
6. Payroll reports
Running payroll reports is critical for every organization. The right payroll system
must be able to customize payroll reports as per the organization’s needs and generate
reports to give quick, easy insights. Payroll reports can help you create datasets for your
company’s essential metrics. These customizable reports help create tailored datasets
for your company’s critical metrics. You need to also make sure that the software gives
you complete access to all the payroll reports generated.
7. Filing of tax
Tax law are constantly changing, and keeping up with them can become difficult. A
payroll system software automatically updates all information regarding changes in tax
rates. This makes the tax filing process easier as it eliminates your need for guesswork
on deductions and streamlines the filing process and generates W-2s.
8. Payroll integration
Payroll integration allows you to seamlessly plug into your existing programs, apps,
and partners to meet the needs of your company and employees. We have one of the
best Payroll software in India that helps automate the flow of data to and from HR and
Payroll platforms with immense ease. It helps you leverage systems without the hassle
of time management or poor user experience. Your desired one-stop shop with a single
login is what we offer. Our payroll software helps you integrate technology into the
existing platforms of your organization.
2. Flow of Events
1) Basic Flow
The use case begins when the Payroll Administrator requests that the
system create an administrative report.
1. The system requests that the Payroll Administrator specify the following report
criteria:
Employee name(s)
2. Once the Payroll Administrator provides the requested information, the system
provides the Payroll Administrator with a report satisfying the report criteria.
3. The Payroll Administrator may then request that the system save the report. At
which time, the system requests the Payroll Administrator to provide the name
and location for saving the report.
4. Once the Payroll Administrator provides the requested information and confirms
the decision to save the report, the system saves the report to the specified name
and location.
5. If the Payroll Administrator did not elect to save the report, the report is discarded.
2) Alternative Flows
1. Requested Information Unavailable
If in the Basic Flow, the requested information is unavailable, the system will
display an error message. The Payroll Administrator can choose to either return to
the beginning of the Basic Flow, or cancel the operation, at which point the use
case ends.
If, in the Basic Flow, the Payroll Administrator has not specified sufficient
information to create the selected report, the system will prompt the actor for the
missing information. The Payroll Administrator can either enter the missing
information or choose to cancel the operation, at which point the use case ends.
3. Pre-Conditions
The Payroll Administrator must be logged onto the system in order for this use case to
begin.
4. Post-Conditions
The system state is unchanged by this use case.
2. Flow of Events
1) Basic Flow
This use case starts when the Employee wishes to create a “Total Hours Worked,”
“Total Hours Worked for a Project”, “Vacation/Sick Leave,” or “Total Pay Year-to-
Date” report.
1. The system requests that the Employee specify the following report criteria:
- Report Type (either “Total Hours Worked,” “Total Hours Worked for a Project”,
“Vacation/Sick Leave,” or “Total Pay Year-to-Date”)
- Begin and end dates for the report
2. If the Employee selected the “Total Hours Worked for a Project” report, the system
retrieves and displays a list of the available charge numbers from the Project
Management Database. The system then requests that the Employee select a
charge number.
3. Once the Employee provides the requested information, the system provides the
Employee with a report satisfying the report criteria.
4. The Employee may then request that the system save the report. At which time,
the system requests the Employee to provide the name and location for saving the
report.
5. Once the Employee provides the requested information and confirms the decision
to save the report, the system saves the report to the specified name and location.
6. If the Employee did not elect to save the report, the report is discarded.
2) Alternative Flows
3) Pre-Conditions
The Employee must be logged onto the system before this use case begins.
4) Post-Conditions
The system state is unchanged by this use case.
VII. Login
1. Brief Description
This use case describes how a user logs into the Payroll System.
2. Flow of Events
1) Basic Flow
This use case starts when the actor wishes to Login to the Payroll System.
The system requests that the actor enter his/her name and password
The system validates the entered name and password and logs the actor into the
system.
2) Alternative Flows
3) Invalid Name/Password
If, in the Basic Flow, the actor enters an invalid name and/or password, the
system displays an error message. The actor can choose to either return to the
beginning of the Basic Flow or cancel the login, at which point the use case ends.
3. Post Conditions
If the use case was successful, the actor is now logged into the system. If not, the
system state is unchanged.
2. Flow of Events
1) Basic Flow
This use case starts when the Payroll Administrator wishes to add, change, and/or
delete employee information from the system.
The system requests that the Payroll Administrator specify the function he/she
would like to perform (either Add an Employee, Update an Employee, or
Delete an Employee)
Once the Payroll Administrator provides the requested information, one of the
subflows is executed.
If the Payroll Administrat-or selected “Add an Employee“, the Add an
Employee subflow is executed.
If the Payroll Administrator selected “Update an Employee“, the Update an
Employee subflow is executed.
If the Payroll Administrator selected “Delete an Employee“, the Delete an
Employee subflow is executed.
o Add an Employee
1. The system requests that the Payroll Administrator enter the employee information. This
includes:
Name
mailing address
phone number
2. Once the Payroll Administrator provides the requested information, the system
generates and assigns a unique employee id number to the employee and sets the
paycheck delivery method to default of “pickup”. The employee is added to the system.
3. The system provides the Payroll Administrator with the new employee id.
o Update an Employee
1. The system requests that the Payroll Administrator enter the employee id.
2. The Payroll Administrator enters the employee id. The system retrieves and displays
the employee information.
3. The Payroll Administrator makes the desired changes to the employee information.
This includes any of the information specified in the Add an Employee sub-flow.
4. Once the Payroll Administrator updates the necessary information, the system updates
the employee record with the updated information.
o Delete an Employee
1. The system requests that the Payroll Administrator specify the employee id.
2. The Payroll Administrator enters the employee id. The system retrieves and displays
the employee information.
3. The system prompts the Payroll Administrator to confirm the deletion of the
employee.
5. The system marks the employee record for deletion. The next time the payroll is run,
the system will generate a final paycheck for the deleted employee and remove the
employee from the system.
2) Alternative Flows
o Delete Cancelled
If in the Delete An Employee sub-flow, the Payroll Administrator decides not to
delete the employee, the delete is cancelled and the Basic Flow is re-started at the
beginning.
3. Pre-Conditions
The Payroll Administrator must be logged onto the system before this use case begins.
4. Post-Conditions
If the use case was successful, the employee information is added, updated, or deleted
from the system. Otherwise, the system state is unchanged.
2. Flow of Events
1) Basic Flow
This use case starts when the Employee wishes to enter hours worked into his current
timecard.
1. The system retrieves and displays the current timecard for the Employee. If a
timecard does not exist for the Employee for the current pay period, the system
creates a new one. The start and end dates of the timecard are set by the system and
cannot be changed by the Employee.
2. The system retrieves and displays the list of available charge numbers from the
Project Management Database.
3. The Employee selects the appropriate charge numbers and enters the hours worked for
any desired date (within the date range of the timecard).
4. Once the Employee has entered the information, the system saves the timecard.
o Submit Timecard
1. At any time, the Employee may request that the system submit the timecard.
2. At that time, the system assigns the current date to the timecard as the
submitted date and changes the status of the timecard to “submitted.” No changes
are permitted to the timecard once it has been submitted.
3. The system validates the timecard by checking the number of hours worked
against each charge number. The total number of hours worked against all charge
numbers must not exceed any limit established for the Employee (for example, the
Employee may not be allowed to work overtime).
4. The system retains the number of hours worked for each charge number in the
timecard.
6. The system makes the timecard read-only, and no further changes are allowed
once the timecard is submitted.
2) Alternative Flows
3. Pre-Conditions
The Employee must be logged onto the system before this use case begins.
4. Post-Conditions
If the use case was successful, the Employee timecard information is saved to the
system. Otherwise, the system state is unchanged.
X. Run Payroll
1. Brief Description
The use case describes how the payroll is run every Friday and the last working day of
the month.
2. Flow of Events
1) Basic Flow
The use case begins when it’s time to run the payroll. The payroll is run automatically
every Friday and the last working day of the month.
1. The system retrieves all employees who should be paid on the current date.
2. The system calculates the pay using entered timecards, purchase orders, employee
information (e.g., salary, benefits, etc.) and all legal deductions.
3. If the payment delivery method is mail or pick-up, the system prints a paycheck.
4. If the payment delivery method is direct deposit, the system creates a bank transaction
and sends it to the Bank System for processing.
5. The use case ends when all employees receiving pay for the desired date have been
processed.
2) Alternative Flows
o Deleted Employees
After the payroll for an Employee has been processed, if the employee has been
marked for deletion (see the Maintain Employee use case), then the system will delete
the employee.
3. Post-Conditions
Payments for each employee eligible to be paid on the current date have been
processed.
XI. Conclusion