Skip to main content

Payroll Readiness Storage

Audience​

Developers, QA and support engineers, data reviewers, implementation partners, solution architects, privacy reviewers and security reviewers.

Reference Content​

Summary​

Payroll Service keeps a local EmployeePayrollProfile projection and integration-delivery ledgers. This is an employee reference model, not a complete onboarding readiness checklist.

Projection path​

Selected objects​

  • EmployeePayrollProfile: payroll-local employee identity/status and payroll configuration reference data.
  • ProcessedIntegrationEvent: idempotency evidence for consumed events.
  • OutboxMessage: local publication intent.

The broader Payroll context contains payroll runs, calculations and components outside this lifecycle selection.

Readiness meaning​

Profile presence or status synchronization does not prove bank validation, statutory setup, compensation approval or inclusion in a payroll run. No dedicated persisted onboarding-readiness decision was found.

Consistency​

Delivery is eventually consistent. Unique event processing constraints reduce duplicate handling, but lag, poison events and reconciliation ownership require operational definition.

Requires confirmation​

Unless explicitly confirmed above, production migration governance, rollback, reconciliation, retention, privacy, performance, concurrency and operational ownership require confirmation.

Source References​

  • microservices/src/payroll-service/Infrastructure/PayrollDbContext.cs
  • microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

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