Attendance Data Consistency and Reconciliation
Summary
Coexistence can create divergence between legacy and Attendance-owned models; investigation must compare source-supported business identities without direct edits.
Audience
- Support engineers, migration owners, database owners, QA, Payroll owners, and architects
Safe reconciliation
Identify the tenant and date/period with non-sensitive references; determine current gateway owner; compare API-visible records and sanitized counts; inspect Attendance audit/timeline, outbox state and consumer evidence; run approved parity tools for supported Time Office scope; identify whether divergence concerns daily Attendance, Shift/weekly-off/assignment, employee projection, or Payroll snapshot.
Legacy numeric compatibility identifiers support Time Office matching. Employee profile synchronization remains Transitional and current source confirms explicit upsert rather than a complete Attendance consumer. Payroll snapshot and Payroll read-model consistency are eventual and separately owned.
Duplicate daily records, partial multi-save workflows, application-only overlap/pending rules, stale projections and mid-cutover writes are risks. Resolve through the owning service workflow or approved migration process—never direct database editing. Escalate unexplained divergence to Attendance, Gateway, database and affected domain owners.
Source References
microservices/src/attendance-service/Backfill/ShiftPolicyBackfillValidator.csmicroservices/src/attendance-service/Domain/Attendance/EmployeeProfile.csmicroservices/src/attendance-service/Domain/Attendance/PayrollApprovedSnapshot.csmicroservices/scripts/compare-attendance-shift-parity.ps1
Related Articles
See Also
Keywords
- Attendance operations
- Support
- Reliability
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly