Payroll Workflow Boundary
Summary
No Payroll integration with Workflow Service or a distinct Payroll approval workflow is confirmed.
Audience
Backend and frontend developers, QA and DevOps engineers, support and security engineers, and solution architects.
Overview
No Payroll integration with Workflow Service or a distinct Payroll approval workflow is confirmed.
Technical Detail
Confirmed state
Payroll lifecycle operations are invoked directly through application services. The run vocabulary has no separate PendingApproval or Approved state, and startup registers no Workflow client or consumer.
Ownership boundary
Workflow-engine internals remain outside Payroll. Business review may precede freeze, but the service does not persist an approval hierarchy or approval task in the confirmed path.
Classification
Payroll workflow integration is Not implemented. Whether freeze should later require Workflow approval, maker-checker controls, or policy-driven authorization Requires confirmation.
Source References
microservices/src/payroll-service/Program.csmicroservices/src/payroll-service/Application/PayrollCalculationService.csmicroservices/src/payroll-service/Application/PayrollCompatService.cs
Related Articles
See Also
Keywords
- Payroll Service
- Payroll Workflow Boundary
- Technical architecture
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly