Skip to main content

Employee Attendance Integration

Summary​

Employee owns workforce identity and joining context; Attendance owns attendance records, shifts, policies, punches, and local employee profile data. Automatic Employee-to-Attendance synchronization was not confirmed.

Audience​

  • Backend developers and QA engineers
  • Solution architects and product owners

Purpose​

Document the confirmed boundary without implying a consumer or direct integration that is not present.

Confirmed boundary​

  • Employee employment state includes joining date and employee status.
  • Employee source comments identify joining date as relevant to downstream attendance behavior.
  • Attendance maintains its own employee-profile concept.
  • Attendance Service does not contain a confirmed Employee lifecycle consumer.
  • Employee Service registers no Attendance client and contains no Attendance consumer.

Attendance employee-profile population is available through Attendance-owned application behavior, but the provisioning owner and production synchronization path Require confirmation.

Requires confirmation​

  • Automatic employee creation/update/status synchronization.
  • Joining-date activation and terminated/suspended employee behavior.
  • Department, designation, manager, work-location, and employment-type propagation.
  • Backfill, reconciliation, failure handling, and ownership of stale Attendance profiles.

Source References​

  • microservices/src/employee-service/Domain/Employees/Employee.cs
  • microservices/src/attendance-service/Program.cs
  • microservices/src/attendance-service/Application/
  • documentation-inventory/hr-suit-backend-source-inventory.md

See Also​

Keywords​

  • Attendance employee profile
  • Synchronization gap
  • Joining context

Revision Information​

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