-
Notifications
You must be signed in to change notification settings - Fork 10.1k
[ADD] Payroll: Time Off To Report #14501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,77 @@ | ||
================== | ||
Time off to report | ||
================== | ||
|
||
Payroll is often processed a few days before the end of a pay period, so that employees can be paid | ||
in a timely manner. When work schedules are predictable, this method often works. However, sometimes | ||
employees take time off unexpectedly, especially sick time. When this occurs, there can be | ||
discrepancies in payroll that must be addressed. | ||
|
||
.. example:: | ||
The payroll department for a medium-sized company processes paychecks every two weeks, on | ||
Wednesdays. Each employee is paid on the Friday after. | ||
|
||
One employee is sick on the last Thursday and Friday of the two-week pay period. Since they have | ||
automatically generated work entries based on their working schedule, and payroll is processed on | ||
Wednesdays, the paycheck they receive incorrectly states that they were paid for a regular work | ||
day for all ten days of the two-week pay period. | ||
|
||
Instead of cancelling the paycheck and reissuing it, causing delays for the employee and more | ||
work for the payroll department, Odoo allows for the deferral of the time off taken, to the | ||
following pay period. | ||
|
||
This ensures all time off balances are correct, and the employee is properly compensated for | ||
their time. | ||
|
||
.. _payroll/time-off-dashboard: | ||
|
||
Time off dashboard | ||
================== | ||
|
||
When time off requests are submitted for a time period that was already processed on a payslip, the | ||
time off requests appear in the *Time Off* page of the **Payroll** app. To access this, navigate to | ||
:menuselection:`Payroll app --> Work Entries --> Time Off to Report`. | ||
|
||
The :guilabel:`Time Off` page default filter is :guilabel:`To Defer`, and displays all requests with | ||
a :guilabel:`Payslip State` of :guilabel:`To defer to next payslip`. This is because the employee | ||
was *already paid* for that time as worked time, and it was logged as regular time spent at work. | ||
|
||
.. image:: time_off_to_report/time-off-to-report.png | ||
:alt: A list of all time off requests that were not approved before payslips were generated. | ||
|
||
Defer multiple time off entries | ||
=============================== | ||
|
||
In order to keep the employee's time off balances correct, the time off request **must** be applied | ||
larm-odoo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
to the following pay period. This not only ensures time off request balances are current, it also | ||
eliminates the need to redo work entries, cancel paychecks, and reissue paychecks. | ||
|
||
To select the work entries to defer, tick the box to the left of the work entry line on the | ||
:ref:`Time Off page <payroll/time-off-dashboard>`. To select all work entries in the list, tick the | ||
box to the left of the :guilabel:`Employee` column title, at the top of the list. | ||
|
||
Once any work entry is selected, two buttons appear at the top of the report: a :guilabel:`(#) | ||
selected` button, and an :icon:`fa-gear` :guilabel:`Actions` button. The :guilabel:`(#) selected` | ||
button indicates how many entries are currently selected. | ||
|
||
When all the desired work entries are selected, click the :icon:`fa-gear` :guilabel:`Actions` | ||
button, and a menu appears with several choices. Click :guilabel:`Defer to Next Month` in the list, | ||
and all selected entries are deferred to the following month. | ||
|
||
Defer individual time off entries | ||
================================= | ||
|
||
Time off requests appearing on the :ref:`Time Off page <payroll/time-off-dashboard>` can be deferred | ||
individually. Click on an individual time off request, and the details for that request load. | ||
|
||
The specific details for the time off request appear on the left-hand side, and all of the | ||
employee's submitted time off requests appear on the right-hand side (including the request in the | ||
details on the left-hand side). | ||
|
||
To defer the time off request to the next payslip, click the :guilabel:`Report to Next Month` button | ||
in the upper-left corner. Once processed, the :guilabel:`Report to Next Month` button disappears, | ||
and the :guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` to | ||
:guilabel:`Computed in Current Payslip`. | ||
|
||
.. image:: time_off_to_report/single-defer.png | ||
:alt: The time off details for an individual request that needs to be deferred. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+23.4 KB
content/applications/hr/payroll/time_off_to_report/time-off-to-report.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
Binary file modified
BIN
+42 KB
(400%)
content/applications/hr/payroll/work_entries/regenerate-details.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Lara! More lengthy of a comment here (:
Since this is a shorter doc, I'm wondering if you'd like to experiment with our new action-focused document type and rewrite this in a new style. Currently, the doc is clear in explaining the dashboard, context, and examples, but if this document is meant to be read for only one reason (resolve payroll discrepancies), we can shift this doc to be more about what the user needs to do and why.
So instead of titling this "Tiome off to report", for instance, we can title it something like "Resolve time off conflicts".
In addition, I have some questions for you to consider to help reframe this doc in a more action-oriented way:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To give you a sense of the vibe I'm going for, itl'l be something like this:
Defer multiple time off entries
When employees request time off after payroll has already been processed, those entries must be deferred to the next pay period.
Payroll app --> Work Entries --> Time Off to Report
.Employee
column.Actions --> Defer to Next Month
.Deferring multiple time off entries ensures time off balances remain accurate and eliminates the need to reissue paychecks.