Carry Forward and Encashment Foundation

Summary

Carry forward and encashment have domain types, repository ports, persistence ownership, and balance hooks but no end-to-end application feature.

Audience

Backend developers, architects, QA, Payroll integrators, and product engineers.

Overview

Carry forward records user/type, source and target years, units, processor, and time; balance can accept carried-forward units. Encashment is an aggregate with user/type/year, units, optional amount, status vocabulary, requester/time, availability validation, balance effect, and a domain event.

No application service invokes these foundations. There is no confirmed API capability, scheduler, approval workflow, UI, Payroll handoff, or correction process. Encashment status constants do not establish a fully implemented transition machine. These components are Foundation, not complete features.

Source References

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

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Carry Forward and Encashment Foundation
• Technical architecture

Revision Information

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