Skip to main content

Attendance Service Responsibilities

Summary​

This boundary map distinguishes Attendance-owned responsibilities from adjacent domains.

Audience​

Developers, architects, QA engineers, support engineers, and product owners.

Owned responsibilities​

Attendance Service owns daily attendance records, punch observations, work-hour normalization, attendance status and paid-unit outcomes, overtime and shortfall quantities, submission/approval/rejection/reopen behavior, shifts, weekly-off rules, attendance policies and rules, employee shift assignments, local employee attendance profiles, payroll attendance snapshots, audit/timeline entries for supported changes, domain-event production, outbox persistence and relay, and the Payroll lock check used by reopen approval.

Explicit boundaries​

It does not own employee master data, identity lifecycle, platform tenant lifecycle, Leave approval, holiday ownership, Payroll calculation, enterprise workflow orchestration, or device/biometric ingestion. The local employee profile is a supporting projection, not an employee system of record. Payroll snapshots preserve attendance inputs, not salary results. No direct Leave client or reusable Workflow-engine integration is present.

Compatibility presentation and gateway routing allow the monolith to remain authoritative for selected surfaces during cutover. Those adapters do not transfer ownership of Employee, Leave, Payroll, Identity, or Platform responsibilities into Attendance.

Source References​

  • microservices/src/attendance-service/Program.cs
  • microservices/src/attendance-service/Domain/Attendance/AttendanceRecord.cs
  • microservices/src/attendance-service/Domain/Attendance/AttendancePunchRecord.cs
  • microservices/src/attendance-service/Application/Services/ReopenRequestWorkflow.cs
  • microservices/src/attendance-service/Application/Services/PayrollSnapshotService.cs

See Also​

Keywords​

  • Attendance Service
  • Attendance Service Responsibilities

Revision Information​

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