Leave Corrections and Adjustments

Summary

Confirmed corrections are cancellation and direct balance maintenance; request editing and governed carry-forward/encashment correction are not implemented.

Audience

Employees, Leave/HR/Payroll administrators, managers, product owners, and QA.

Overview

Scenario	Confirmed behavior
Edit before approval	Not implemented; no request-update workflow is exposed.
Reject and resubmit	Rejection is implemented; resubmission is a new request and its business governance requires confirmation.
Cancel Pending	Employee self-cancellation is confirmed in compatibility behavior.
Cancel Approved	Authorized cancellation is supported and reverses prior balance usage.
Date-range correction	Cancel/new request; formal correction process Requires confirmation.
Balance correction	Administrative set/delete capability exists; approval and audit governance require confirmation.
Carry-forward correction	Not implemented end to end.
Encashment correction	Not implemented end to end.
Attendance conflict correction	Resolve the conflicting business record through its owning workflow; no bypass is supported.
Payroll-period restrictions	Requires confirmation.

Request decisions and balance changes create timeline/audit evidence in confirmed paths. Direct data manipulation is outside the supported business process.

Source References

• microservices/src/leave-service/Application/LeaveWorkflows.cs
• microservices/src/leave-service/Domain/Leave/LeaveRequest.cs
• Controllers/LeaveRequestsController.cs

Related Articles

• Leave overview
• Leave business documentation

See Also

• Attendance module
• Employee module

Keywords

• Leave
• Leave Corrections and Adjustments
• Workforce management

Revision Information

• Status: Draft
• Last reviewed: 2026-07-15
• Review cycle: Quarterly