Workforce Scheduling Business Integrations

Summary

Attendance is the central implemented integration. Employee identity/profile data supports assignments, Leave shares calendar/conflict behavior, and Payroll consumes attendance outcomes. Notification and organization-based scheduling are not implemented.

Audience

Product, HR/payroll administrators, QA, support, architects and implementation partners.

Reference Content

Domain	Classification	Verified business interaction	Limitation
Employee	Transitional	Assignments reference employee/labor identity; employee profile/fixed shift appears in compatibility UI and Attendance read model	Attendance profile sync is explicit upsert/seed; no verified Employee event consumer
Attendance	Implemented	Effective shift/policy drives hours, status, overtime, shortfall and paid units	No roster publication or schedule-vs-actual comparison
Leave	Partial	Weekly offs/holidays affect leave-day calculation; approved attendance conflicts block leave	Shift assignment is not queried for leave duration
Payroll	Implemented indirectly	Attendance snapshot provides payable categories, hours, overtime and shortfall	No direct shift premium or shift assignment input
Notification	Not implemented	No shift/assignment/schedule notification resolver or template found	No publication, change or reminder notification
Organization	Foundation only	Employee records can carry department/manager/location-related data	Scheduling commands do not use organization hierarchy
Department	Not implemented	Department is visible in employee/attendance data	No department shift assignment, calendar or coverage
Team	Not implemented	Manager/team scope exists for attendance	No team scheduling domain
Factory	Not implemented	Legacy employee/user records contain factory fields	Shift and assignment models do not use factory
Location	Not implemented	Department and requisition data may contain location	No location schedule, policy or calendar assignment
Gateway	Transitional	Compatibility shift/weekly-off routes can move between monolith and Attendance	Delete/update semantics and ownership differ

Business architecture

Requires confirmation

Live routing, synchronization ownership, external scheduling tools, factory structure and production notification practices require confirmation.

Business Evidence Checklist

• Business purpose: Define what scheduling data actually crosses business domains.
• Actors: HR, employees, managers, payroll, support and domain service owners.
• Business process: Supply identity/configuration, calculate attendance, check leave and calculate payroll.
• Status transitions: Downstream Attendance, Leave and Payroll lifecycles apply; no scheduling lifecycle is emitted.
• Responsibilities: Each domain owns its records and reconciles the documented handoff.
• Business rules: Tenant identity, effective assignment, calendar conflict and snapshot rules apply.
• Integrations: Eleven domain/boundary classifications are cataloged above.
• Limitations: Notification and organization-group scheduling are absent; employee sync/routing are transitional.
• Requires confirmation: Live topology, external systems and ownership require confirmation.

Source References

• microservices/src/attendance-service/Application/Services/EmployeeProfileService.cs
• microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs
• microservices/src/payroll-service/Application/PayrollCalculationService.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs

Related Articles

• Attendance integration
• Payroll impact

See Also

• Business limitations

Keywords

• Integration matrix
• Cross-domain boundary
• Notification gap

Revision Information

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