Attendance Corrections

Attendance Corrections lets an employee propose a correction without directly editing the attendance record. An authorized approver reviews the request, and approval applies the accepted times to native Odoo Attendances with a retained revision history.

Technical module name: corvus_hr_attendance_correction.

Before you start

• The matching Attendance Corrections addon must already be installed with Odoo Attendances. This guide describes the Odoo 19 workflow; source differences for Odoo 18 and 20 are listed below.
• Your internal Odoo user must be linked to an employee in an allowed company. Employees normally create and submit their own requests.
• An approver must be configured for the employee or company. Policy configuration requires an Attendance administrator; deciding a request requires the assigned approver, an authorized manager or an authorized attendance reviewer.
• Check your user timezone before entering times. The draft shows Draft times (your user timezone); the submitted comparison records the snapshot timezone displayed on the request.

Verification: This guide was checked against the versioned source on 28 October 2026. No installation, employee record, request or approval was created for this guide. Menu visibility and approval rights depend on the installed version, company and assigned role.

Open Live Test for Odoo 19. Catalogue eligibility for this exact app and version was checked on 28 October 2026. Availability can change; no demo session or approval scenario was run for this guide.

Find the feature

Open Attendances; this addon does not add a separate app tile.

Task	Menu or control
Submit or follow your request	Attendances → My Attendance Corrections
Review requests assigned to you	Attendances → Attendance Correction Approvals
Review the HR request queue	Attendances → Management → Attendance Correction Requests
Configure policies	Attendances → Configuration → Correction Policies
Review detected issues	Attendances → Management → Attendance Anomalies
Analyze correction history	Attendances → Reporting → Attendance Correction Analysis

Authorized reviewers can also use Corrections on an employee or attendance record. A menu’s presence does not grant permission to decide every request.

Set up the approval policy

An Attendance administrator completes this setup in the intended company.

1. Open the Attendances settings and find Attendance Corrections. Review the Default approver, request limits, approval reminders and anomaly boundaries. Company defaults are used when no correction policy matches.
2. Open Configuration → Correction Policies and create or review the applicable policy. Set its name, company and any department, employee-tag or date scope.
3. Review Limits: request age, future tolerance, evidence requirement and schedule warnings. Set limits appropriate to your organization instead of assuming the defaults apply to every request.
4. Under Approval, choose Employee Attendance Approver, Line Manager, Specific User or Company Default. Select the user when using Specific User. Review activity and decision-comment requirements.
5. Save the policy. Confirm the employee’s approver and timezone are correct. On the next submitted request, check Policy snapshot and Assigned Approver to confirm the effective settings.

Self-approval is normally blocked. An explicit self-approval exception must be present in the submitted policy snapshot; an administrator role alone does not bypass that check.

Example: request a missed check-out

For example, you checked in yesterday at 09:00 but forgot to check out at 17:30. Use your actual date and times, within the applicable policy.

1. Open My Attendance Corrections and create a request. Confirm the employee and company, then choose Missing Check-Out.
2. Select the open record in Original Attendance. It must belong to you and have no recorded check-out.
3. Enter the correct date and time in Requested Check Out. The original check-in remains the effective start time. Check the timezone shown on the form.
4. Enter a Reason explaining what happened and why the proposed time is correct. Add an evidence attachment if the policy requires it.
5. Save and select Submit. Resolve any validation message before continuing. A successful submission changes the request to Submitted, assigns an approver and records a revision.
6. Review the before, requested and effective times and the Policy snapshot. Follow the same request for the decision; submitting does not itself change the attendance.

Approve or reject the request

1. The authorized approver opens Attendance Correction Approvals and selects the submitted request. HR reviewers may use the broader request queue where permitted.
2. Check the employee, original attendance, proposed times, timezone, reason, evidence and any schedule warning. Enter the required Decision Comment.
3. Select Approve only if the correction is accurate, or Reject with the required explanation. Approval changes native attendance, so verify the target and times before deciding.
4. After approval, confirm Approved, the final times and Audit revisions or Revisions. The missed check-out updates the selected attendance record. Authorized reviewers can inspect its Correction Audit and Corrections control.

Expected result: The existing attendance has the approved check-out. The request retains its original, requested, effective and final values, decision and revision history. A rejected request does not apply the proposed change; its owner can correct the request and submit another revision.

Choose another request type

Request type	What you provide
Missing Check-In or Add Complete Attendance	Both proposed check-in and check-out; no original attendance is selected. Approval creates a complete attendance interval.
Missing Check-Out	An open original attendance and the proposed check-out.
Correct Check-In	The original attendance and a new check-in; its existing check-out is retained.
Correct Check-Out	The original attendance and a new check-out; its existing check-in is retained.
Correct Both	The original attendance and both proposed times.

Every request must resolve to both an effective check-in and check-out, with check-out later than check-in. It must also pass the overlap, duplicate-request and policy checks.

Review history and anomalies

Use Revisions or Audit revisions on the request to inspect its recorded submissions and decisions. Print, when available, requests the Attendance Correction Request report. PDF generation depends on the Odoo server’s report renderer.

Authorized reviewers can use Attendance Correction Analysis for pivot, graph or list views, and Attendance Anomalies to review missing pairs, overlaps and outstanding correction requests. Anomaly detection does not invent punches or repair attendance automatically.

Troubleshooting

Message or situation	Next step
User must be linked to an employee	Ask an administrator to check the user-to-employee link and allowed company.
No correction approver configured	Ask an Attendance administrator to check the employee approver, line manager, policy and company fallback.
Missing check-out requires an open attendance	Check that you selected the right record. Use the appropriate correction type if it already has a check-out.
Times overlap an attendance	Review the existing records and proposed interval; correct the request instead of creating a duplicate attendance.
An open correction already exists	Find the existing submitted or stale request for that attendance event.
Too old, too far in the future or evidence required	Review the effective policy and supply the required evidence or ask HR to review the situation.
Stale	The attendance or surrounding records changed after submission. The requester or authorized attendance reviewer enters a refresh comment when required and selects Refresh to Draft. For an existing attendance, this reloads its current times: re-enter and check the intended correction, then submit again.
Approve is absent or self-approval is blocked	Confirm the request is submitted and that you are its authorized approver. Ask another authorized approver to review your own request unless an explicit policy exception applies.
Request is being processed	Allow the other operation to finish, refresh the record and inspect its state before retrying.

Submitted requests are protected from ordinary editing. Cancel applies to your own draft or rejected request; it is not an undo for an approved attendance. Retained requests are archived when allowed rather than deleted.

Versions and limitations

Odoo series	Addon version reviewed	Evidence for this guide
19.0	19.0.1.0.1	Primary workflow, models, menus, security, reports and existing test assertions reviewed. No new runtime workflow test.
18.0	18.0.1.1.0	Request and settings views compared. Visible policy path is the same; broader HR review permissions use the Attendance Manager role in this source. No runtime test.
20.0	20.0.1.0.0	Request and settings views and menus compared. Same documented request flow, with version-specific calendar warning handling. No runtime test.

The addon requires native hr_attendance and mail. Other Odoo series were not reviewed for this guide. It is a server-side addon; Odoo Online compatibility is not established here.

The feature does not calculate payroll, approve overtime, synchronize biometric devices, plan shifts or validate geofences. Schedule and calendar-closure messages are advisory when enabled. Approval applies the submitted correction; it does not establish a payroll or legal entitlement.

For help, use Corvus customer support and provide the addon/Odoo version, company, user role, request reference, displayed state and redacted reproduction details. Keep employee-sensitive attachments out of a general support message.

Guide version 1.0 · Source verification date 28 October 2026 (UTC).