Skip to main content

Payroll Document Events

Summary​

This page documents confirmed payroll document events behavior and explicitly marks incomplete integration boundaries.

Audience​

Payroll and integration developers, QA and support engineers, solution and security architects, and implementation partners.

Confirmed subscriptions​

DocumentReadModelConsumer subscribes to PayrollCalculated, PayrollFrozen, and PayslipGenerated. It does not subscribe to PayrollUnfrozen.

The consumer updates a local Payroll snapshot, maintains a processed-event ledger, rejects older projection events by occurrence time, and records audit/timeline evidence.

Boundary​

Payroll's PayslipGenerated document reference is logical. Payroll does not publish DocumentGenerated and does not persist generated files in Document Service as part of its transaction.

Known limitations​

Document projection handling requires a usable tenant identity, while current Payroll publishers leave the shared tenant envelope field empty. Unfreeze cannot update the Document projection through a confirmed subscription.

Requires confirmation​

  • Tenant identity alignment between Payroll contracts and Document parsing.
  • Whether PayrollUnfrozen should be subscribed.
  • Ownership of durable payslip document generation/storage.

Source References​

  • microservices/src/document-service/Messaging/DocumentReadModelConsumer.cs

See Also​

Keywords​

  • Payroll events
  • Payroll Document Events
  • Integration contracts

Revision Information​

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