Skip to main content

Payroll Event Publishing Flow

Summary​

This page documents confirmed payroll event publishing flow behavior and explicitly marks incomplete integration boundaries.

Audience​

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

Publishing flow​

Payroll application services construct shared integration contracts after business validation, map them to outbox records, and call SaveChanges.

Transactional boundary​

Business state, operation evidence, and outbox intent participate in the same Payroll SaveChanges call for the four native publishing paths. Broker publication and delivery acknowledgement occur later and cannot roll back the originating Payroll commit.

Mapping​

The shared serializer writes the concrete integration contract into an outbox payload and copies supported envelope metadata. No custom per-event mapper is present.

Known limitations​

Payroll host registration provides messaging and outbox services, but source does not confirm a hosted process calling the outbox processor.

Requires confirmation​

  • Deployed relay invocation and scheduling.
  • Publication monitoring and operational ownership.

Source References​

  • microservices/src/payroll-service/Application/PayrollCalculationService.cs
  • microservices/src/payroll-service/Application/PayrollOutputsService.cs
  • microservices/src/shared-kernel/Outbox/IntegrationEventJsonSerializer.cs
  • microservices/src/shared-kernel/Outbox/OutboxMessage.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
  • microservices/src/payroll-service/Infrastructure/Persistence.cs
  • microservices/src/payroll-service/Program.cs

See Also​

Keywords​

  • Payroll events
  • Payroll Event Publishing Flow
  • Integration contracts

Revision Information​

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