Attendance Integration Events

Summary

Five shared contract records derive from IntegrationEvent; Attendance mapping publishes all five with schema version 1.

Audience

• Producers, consumers, integration engineers, QA engineers, and architects

Reference Content

Exact contract	Purpose / trigger	Confirmed consumer	Context and maturity
AttendancePunchedEvent	Punch aggregate created	None	v1; Foundation downstream adoption
AttendanceSubmittedEvent	Unapproved daily computation saved	Payroll, Integration Service	v1; Transitional
AttendanceApprovedEvent	Approved computation or recalculation saved	Payroll, Integration Service	v1; Transitional
AttendanceRejectedEvent	Daily outcome rejected/cleared	Integration Service	v1; Transitional
AttendanceReopenedEvent	Reopen approval applies recomputed result	None	v1; Foundation downstream adoption

All contracts carry the shared event envelope plus contract-specific Attendance facts. Numeric tenant context is carried by the Attendance contract; the cross-service GUID tenant/user fields are unset in current producer mapping. Correlation is derived from the daily business identity. Causation is unset.

Integration Service is a confirmed subscriber to Submitted, Approved, and Rejected and may route them to configured targets. That routed configuration does not make Notification Service a direct consumer: its current resolver does not subscribe to Attendance contracts.

Compatibility routes and direct routes converge on the same application/domain producer behavior; no separate compatibility event contract exists.

Source References

• microservices/src/contracts/Events/IntegrationEvent.cs
• microservices/src/contracts/Events/AttendanceLifecycleEvents.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