Skip to main content

Payroll Integration and Projection Reference

Summary

This page records confirmed payroll integration and projection reference behavior and marks incomplete boundaries explicitly.

Audience

Payroll users, developers, QA and support engineers, architects, and implementation reviewers.

Reference Content

Inbound projections

ProjectionConfirmed upstream event familiesNative calculation requirement
EmployeePayrollProfileEmployee lifecycleWorkforce source; eligible profiles required
AttendancePayrollSnapshotAttendance submitted/approvedRequired per calculated employee/period
LeavePayrollSnapshotLeave approved/rejected/cancelledOptional input
ApprovedExpenseSnapshotExpense approved/rejected/paidOptional input

Outbound contracts

PayrollCalculated, PayrollFrozen, PayrollUnfrozen, and PayslipGenerated are schema-version-1 shared contracts staged through outbox mapping. Confirmed consumers and delivery limits are maintained in Events documentation.

Other boundaries

Notification and Document processing occur downstream. Expense also uses a synchronous frozen-period guard outside the event projection path. Gateway owns route transitions; no distributed transaction spans these boundaries.

Source References

  • microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
  • microservices/src/contracts/Events/PayrollCalculatedEvent.cs
  • microservices/src/contracts/Events/PayslipGeneratedEvent.cs
  • microservices/src/payroll-service/Infrastructure/PayrollDbContext.cs

See Also

Keywords

  • Payroll reference
  • Payroll Integration and Projection Reference

Revision Information

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