> ## Documentation Index
> Fetch the complete documentation index at: https://absentify.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Approve overtime (beta)

> Review extra work, approve all or part of its duration, decline entries, and check overtime history.

Overtime entries appear alongside absence requests on **Open** in the approval area, reached through the bell icon. This requires workspace access to the overtime beta. The user's configured approvers and approval process apply; see [admin setup](https://absentify.com/docs/en/roles/hr_admins/guides/toil-overtime.md).

## Review and decide

Open **Details** on an **Overtime** entry. Check the work date, allowance, logged duration, comment, expected credit, expiry and earlier decisions.

* **Approve** recognizes the current duration. If other approvals are required, the entry stays open; credit is added only when the approval process finishes successfully.
* **Approve less** lets you recognize a shorter duration. Enter a positive amount below the currently recognized duration and give a reason. The user sees your reason. Hourly amounts use whole minutes; day-based entries use half-day or whole-day amounts. Later approvers cannot increase an earlier recognized amount.
* **Decline** requires a reason that the user can read. Whether another approver can still decide depends on the configured approval process. A finally declined entry earns no credit.

The factor is applied to the recognized duration, not the original logged duration. Approving one of two logged hours at a factor of 1.5 gives 1 hour 30 minutes of credit once approval is complete.

You can include eligible overtime entries in [bulk approval](https://absentify.com/docs/en/roles/manager/approval_requests.md#approve-several-requests-at-once). Review their details first; use **Approve less** individually for reductions.

## Permissions and notifications

Assigned approvers act when it is their turn. Administrators and authorized department managers can act on behalf of other approvers within their permissions. Users without administrator rights cannot manually decide on their own overtime entries. The record shows who acted and any decision made on behalf of another approver.

Approvers can receive email and Microsoft Teams notifications according to their notification preferences and linked account. Teams cards support approval and decline with a reason; open absentify to approve a lower duration. The approval list and bell indicator in absentify show actionable entries. Users can receive email or Teams notifications when their entry is finally approved or declined.

## History

Open **History** and choose **Overtime** to review processed entries visible to you. Administrators have workspace-wide access; managers and approvers see entries within their permitted scope. Use employee search and **Show more** to find older results. Open **Details** to review the decision trail, including reductions, reasons, withdrawals and credit validity.

Users review their own entries under [My overtime](https://absentify.com/docs/en/roles/employee/overtime.md#follow-approval-and-credit).

## When a decision is blocked

* **Not your turn:** another approver must act first, or the entry is not assigned to you. Check the current approval chain.
* **Already processed or withdrawn:** refresh the entry. Another decision may have closed it.
* **Expired credit:** fixed validity runs from the work date. Final approval cannot add credit after this validity has expired. An approver can decline the pending entry, or the user can withdraw it.
* **Work date outside the allowance range:** ask an administrator to check the user's allowance setup. Approval must still be able to credit the original work date.
* **Allowance updates in progress:** retry after the update finishes. Contact [support@absentify.com](mailto:support@absentify.com) if the problem persists.

Approving logged work and approving a later recovery absence are separate decisions. Recovery requests follow their leave type's approval policy.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.