Payroll Support, Escalation, and Operational Checklist

Summary

This page records confirmed payroll support, escalation, and operational checklist behavior and marks incomplete boundaries explicitly.

Audience

Payroll users, developers, QA and support engineers, architects, and implementation reviewers.

Operational checklist

1. Confirm scope: tenant, period, operation, route ownership, and observed time without collecting sensitive values.
2. Confirm host health and relevant structured logs/traces.
3. Check projection freshness and required Attendance coverage.
4. Confirm run/lifecycle state and whether compatibility or native behavior was used.
5. Check outbox state for asynchronous downstream symptoms.
6. Reproduce only with synthetic data in an approved environment.
7. Escalate with correlation, event/run identifiers where approved, timestamps, and sanitized evidence.

Escalation

Security or tenant-isolation concerns go directly to security and service ownership. Data-correction, replay, migration, and cutover actions require approved operators; support must not perform direct database changes.

Source References

• microservices/src/payroll-service/Program.cs
• microservices/src/payroll-service/Application/PayrollCalculationService.cs
• microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
• microservices/src/payroll-service/Infrastructure/Persistence.cs
• microservices/docs/payroll-cutover-runbook.md
• microservices/scripts/compare-payroll-parity.ps1
• microservices/scripts/payroll-cutover-go-no-go.ps1
• microservices/scripts/smoke-payroll-cutover.ps1

Related Articles

• Payroll operations documentation
• Payroll technical documentation

See Also

• Payroll API documentation
• Payroll module

Keywords

• Payroll operations
• Payroll Support, Escalation, and Operational Checklist

Revision Information

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