Skip to main content

Payroll Known Limitations

Summary​

The confirmed service is functional but transitional across lifecycle governance, integration reliability, tenant enforcement, outputs, operations, and testing.

Audience​

Backend and frontend developers, QA and DevOps engineers, support and security engineers, and solution architects.

Reference Content​

  • No distinct Payroll approval state or hierarchy.
  • No irreversible finalization state.
  • No payment execution, bank acknowledgement, settlement, or reconciliation.
  • No accounting or general-ledger posting.
  • Native and compatibility unfreeze status behavior differs.
  • Projection correction/reconciliation and equal-time event ordering are incomplete.
  • Leave metadata can overlap Attendance-derived totals during migration.
  • Payroll Workflow integration is absent.
  • Outbox persistence exists, but automatic Payroll relay invocation requires confirmation.
  • Health checks are process-level; Payroll-specific metrics and caching are absent.
  • No formal Payroll .NET test project was found.
  • Document Service storage/version governance is absent; PDF and exports are in-process.
  • Post-payment correction is undefined because payment execution is outside the service.
  • Salary-component assignment/version/approval governance is incomplete.
  • Service-local authorization and universal tenant enforcement require confirmation.

Source References​

  • microservices/src/payroll-service/Application/PayrollCalculationService.cs
  • microservices/src/payroll-service/Application/PayrollCompatService.cs
  • microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
  • microservices/src/payroll-service/Program.cs
  • microservices/src/payroll-service/Application/PayrollOutputsService.cs
  • microservices/src/gateway-api/Program.cs

See Also​

Keywords​

  • Payroll Service
  • Payroll Known Limitations
  • Technical architecture

Revision Information​

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