Attendance Review Events

Summary

Submission, approval, and rejection each produce a distinct lifecycle event when the daily Attendance aggregate is mutated and saved.

Audience

• Attendance and Payroll developers, QA engineers, managers, and integration owners

Review sequence

Approval recalculates the stored outcome before raising Approved. Save paths with approval permission can raise Approved directly rather than Submitted. Audit rows and event outbox rows participate in the same save when both are added before commit.

Payroll subscribes to Submitted and Approved. Integration Service subscribes to Submitted, Approved, and Rejected. Notification Service has no direct Attendance resolver, so a notification side effect is not confirmed even though routed orchestration may target a notification-labelled downstream.

There is no separate “review started,” “recalculated,” or “audit created” integration event.

Source References

• microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
• microservices/src/attendance-service/Domain/Attendance/AttendanceRecord.cs
• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
• microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
• microservices/src/integration-service/Domain/IntegrationEntities.cs

Related Articles

• Attendance events
• Attendance technical documentation
• Attendance database documentation

See Also

• Attendance API documentation
• Attendance business documentation

Keywords

• Attendance events
• Integration contracts
• Eventual consistency

Revision Information

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