Attendance Capture Events

Summary

Every new punch raises a punch event. A punch that derives daily Attendance can additionally raise a submitted or approved event in the same save.

Audience

• Attendance developers, QA engineers, integration engineers, and support engineers

Punch sequence

Punches on weekly offs remain allowed and follow the same event behavior. Manual Attendance save does not raise a special “manual” contract: it raises Submitted or Approved according to saved review state. Recalculation during punch approval raises Approved only if a matching daily record exists. Punch rejection can raise Rejected only when it clears a matching non-approved daily record.

No dedicated duplicate-punch, missing-punch, correction, weekly-off, or recalculation event exists. Ordering beyond event occurrence and relay polling is not guaranteed.

Source References

• microservices/src/attendance-service/Application/Services/PunchWorkflow.cs
• microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
• microservices/src/attendance-service/Domain/Attendance/AttendancePunchRecord.cs
• microservices/src/attendance-service/Domain/Attendance/AttendanceRecord.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