Skip to main content

Payroll Calculation Events

Summary​

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

Audience​

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

Reference Content​

The contract characteristics below are taken directly from its shared definition, publisher, mapping, and confirmed consumer code.

Purpose​

PayrollCalculated communicates that a Payroll run calculation completed.

Publisher​

PayrollCalculationService.

Consumer​

DocumentReadModelConsumer is the only confirmed subscriber.

When raised​

After the native calculation path has assembled run details and totals and staged audit/timeline evidence.

When mapped​

The application service constructs the shared contract and immediately maps it to an outbox record before SaveChanges.

Delivery model​

Transactional outbox intent followed by asynchronous publication.

Transactional boundary​

Calculation state, evidence, and outbox intent share one SaveChanges call; downstream processing is outside it.

Version​

Schema version 1.

Known limitations​

Tenant, user, and causation envelope fields are not populated by the current Payroll publisher. Document projection application requires tenant context, so end-to-end propagation is Transitional.

Requires confirmation​

  • Runtime relay execution and tenant-context correction.
  • Whether additional consumers are planned.

Source References​

  • microservices/src/contracts/Events/PayrollCalculatedEvent.cs
  • microservices/src/payroll-service/Application/PayrollCalculationService.cs
  • microservices/src/document-service/Messaging/DocumentReadModelConsumer.cs

See Also​

Keywords​

  • Payroll events
  • Payroll Calculation Events
  • Integration contracts

Revision Information​

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