Skip to main content

Attendance Payroll Lock Integration

Summary

Attendance consults the current Payroll lock authority before approving a reopen request for a payroll period.

Audience

Backend developers, payroll integrators, support engineers, architects, and QA engineers.

Integration behavior

IPayrollLockClient is an application port implemented by a typed HTTP client. Reopen approval supplies employee and period context; a locked result returns a forbidden application outcome before attendance is changed. The adapter forwards authenticated tenant and correlation context and logs unsuccessful dependency responses or transport failures without exposing sensitive request data.

The current authority is transitional and may be the monolith while routing evolves. Source confirms non-blocking availability behavior when the dependency cannot provide a lock result; exact security-sensitive failure posture is intentionally not expanded in public documentation and requires internal review. Ordinary attendance save, approval, and rejection do not show the same explicit lock check.

This is an availability and consistency dependency, not a distributed transaction. Timeout, retry, circuit-breaker, cache, service-level objective, and post-failure reconciliation policy are not confirmed. Tests should cover locked, unlocked, unavailable, unauthorized, malformed, and cancelled calls in an approved internal environment.

Source References

  • microservices/src/attendance-service/Application/IPayrollLockClient.cs
  • microservices/src/attendance-service/Infrastructure/PayrollLockClient.cs
  • microservices/src/attendance-service/Application/Services/ReopenRequestWorkflow.cs
  • microservices/src/attendance-service/Program.cs

See Also

Keywords

  • Attendance Service
  • Attendance Payroll Lock Integration

Revision Information

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