Skip to main content

Shift and Attendance Integration

Summary​

The extracted Attendance Service resolves an employee’s effective shift for a date and applies its working-time values during manual, punch-derived and approval recalculations.

Audience​

Employees, managers, HR/payroll administrators, QA and solution architects.

Reference Content​

Resolution precedence​

The resolver obtains the employee profile, tenant default attendance policy and effective assignment/shift. Shift values take precedence for standard hours, overtime threshold, grace and working window; policy rules and employee-profile data provide fallbacks where required.

Business outcomes​

  • Manual attendance normalization uses effective standard hours and attendance mode.
  • Punch calculation derives status, overtime, shortfall/deduction and paid units from worked hours.
  • Approval recalculation derives canonical outcomes from approved hours.
  • Weekly-off detection affects calendar/day classification.
  • Approved attendance becomes a payroll snapshot input and can block overlapping leave decisions.

Responsibilities​

HR/attendance administrators own correct shift and policy configuration. Managers own attendance review within their scope. Employees own accurate punch behavior where enabled. Payroll should use approved/frozen attendance inputs rather than shift definitions directly.

Limitations​

The policy resolver does not publish a schedule to employees. Break deductions, split shifts, multiple shifts per day and staffing coverage are not modeled. Compatibility attendance can retain older profile/fixed-shift semantics depending on routing.

Requires confirmation​

Actual device/punch sources, lateness policy, approval practice and production routing require confirmation.

Business Evidence Checklist​

  • Business purpose: Apply shift/policy values to actual attendance outcomes.
  • Actors: Employees, managers, HR/attendance and payroll administrators.
  • Business process: Resolve policy, normalize/derive attendance, approve and snapshot.
  • Status transitions: Attendance lifecycle is documented by Attendance; no schedule state is added.
  • Responsibilities: HR configures, employees record, managers approve and Payroll consumes.
  • Business rules: Effective-date precedence and nonnegative hour calculations apply.
  • Integrations: Employee profile, shift assignment, weekly offs and Payroll.
  • Limitations: No schedule publication, split shift, break or coverage comparison.
  • Requires confirmation: Punch source, policy and routed implementation require confirmation.

Source References​

  • microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
  • microservices/src/attendance-service/Domain/Attendance/EffectiveAttendancePolicy.cs
  • microservices/src/attendance-service/Domain/Attendance/AttendanceCalculator.cs
  • microservices/src/attendance-service/Application/Services/AttendanceCommands.cs

See Also​

Keywords​

  • Effective policy
  • Attendance calculation
  • Shift threshold

Revision Information​

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