Skip to main content

Leave Carry Forward

Summary

Carry forward has a source-backed domain and persistence foundation, but no confirmed end-to-end execution workflow.

Audience

Leave/HR/Payroll administrators, product owners, analysts, QA, and implementation partners.

Concepts

The foundation records employee/user, Leave type, source year, target year, moved units, processor, and processing time. Leave type declares eligibility; policy declares a maximum; balance can retain carried-forward units.

Not implemented: no confirmed application command, exposed capability, UI, scheduler, approval, expiry process, idempotent annual execution, or correction workflow uses this foundation. Limits and annual processing rules must not be assumed.

Source References

  • microservices/src/leave-service/Domain/Leave/LeaveExtras.cs
  • microservices/src/leave-service/Domain/Leave/LeaveBalance.cs
  • microservices/src/leave-service/Domain/Leave/LeaveConfig.cs

See Also

Keywords

  • Leave
  • Leave Carry Forward
  • Workforce management

Revision Information

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