Leave Payroll Integration

Summary

Payroll consumes Leave decision events into a Payroll-owned read model while legacy Payroll still reads monolith Leave data.

Audience

Leave/Payroll developers, architects, QA, and product engineers.

Overview

The Payroll consumer handles approved, rejected, and cancelled Leave events, applies tenant/employee/time context, ignores stale events, and updates a period read model. Paid/unpaid classification currently uses a compatibility textual convention, while LeaveType has explicit paid metadata; alignment is Transitional.

Publication is eventually consistent. Leave does not own Payroll formulas, Payroll-period finality, or read-model reconciliation. A published event does not itself prove successful Payroll consumption.

Source References

• microservices/src/leave-service/Domain/Leave/LeaveDomainEvents.cs
• microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
• Services/SalaryService.cs

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Payroll Integration
• Technical architecture

Revision Information

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