Payroll Known Limitations Reference
Summary
This page records confirmed payroll known limitations reference behavior and marks incomplete boundaries explicitly.
Audience
Payroll users, developers, QA and support engineers, architects, and implementation reviewers.
Reference Content
Consolidated limitations
| Category | Confirmed limitation | Classification / operational effect |
|---|---|---|
| Payment | No payment execution, remittance acknowledgement, or reconciliation | Not implemented; a frozen run or bank file is not payment |
| Accounting | No accounting or ledger posting | Not implemented; downstream posting must not be inferred |
| Finalization | Freeze is reversible; no irreversible finalization state | Not implemented; use Frozen only as a Payroll lock |
| Approval | No Payroll workflow approval integration | Not implemented; UI review is not approval |
| Projections | Workforce, required Attendance, optional Leave, and optional Expense inputs depend on event freshness | Foundation; stale inputs can affect calculation availability/results |
| Compatibility | Native and compatibility lifecycle and error behavior differs | Transitional; record route family during diagnosis |
| Outbox | Relay execution, retry ceiling, dead-letter behavior, replay workflow, retention, and ownership are not established | Requires confirmation; durable intent is not delivery |
| Health | Health is shallow and does not prove database, broker, projection, or downstream readiness | Foundation only |
| Metrics | No Payroll-specific meter, counter, histogram, or metrics endpoint | Not implemented |
| Caching | No Payroll cache registration or invalidation behavior | Not implemented |
| Testing | Smoke/parity/scenario assets exist, but no formal Payroll backend or UI test project is confirmed | Foundation / Requires confirmation for external suites and release gates |
| Authorization | UI checks are confirmed; complete API/gateway enforcement and compatibility equivalence are not | Requires confirmation |
| Documents | PDF rendering exists without durable external payslip storage/history | Not implemented as a document repository |
| Notifications | Document/Notification consumers cover selected events; no PayrollUnfrozen consumer is confirmed | Transitional; do not expect universal downstream handling |
| Event context | Outbound tenant/user/correlation/causation propagation is incomplete for selected publishers | Transitional; limits tracing and consumer context |
| Database integrity | No database foreign keys or concurrency tokens are confirmed | Foundation; application rules carry more integrity responsibility |
| UI operations | No dedicated bank export, outbox, projection administration, cutover, or migration screen | Not implemented as UI surfaces |
These are implementation findings, not disclosures of credentials, topology, exploitable details, or planned functionality.
Source References
microservices/src/payroll-service/Program.csUI/salary-ui/apps/client-hrms-portal/src/App.tsxUI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsxUI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsxmicroservices/src/payroll-service/Application/PayrollCalculationService.csmicroservices/src/payroll-service/Application/PayrollCompatService.csmicroservices/src/payroll-service/Application/PayrollOutputsService.csmicroservices/src/payroll-service/Messaging/PayrollReadModelConsumer.csmicroservices/src/payroll-service/Infrastructure/Persistence.csmicroservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
Related Articles
See Also
Keywords
- Payroll reference
- Payroll Known Limitations Reference
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly