Payroll Unfreeze Events
Summary
This page documents confirmed payroll unfreeze 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
PayrollUnfrozen communicates the completed native unfreeze of a Payroll run.
Publisher
PayrollCalculationService.
Consumer
No confirmed subscriber was found.
When raised
After unfreeze validation and while run/detail state, recovery reversals, audit, and timeline evidence are staged.
When mapped
The contract is mapped into the outbox before SaveChanges.
Delivery model
Transactional outbox intent; downstream delivery currently has no confirmed consumer.
Transactional boundary
Unfreeze state, reversal records, evidence, and outbox intent share one local save.
Version
Schema version 1.
Known limitations
No consumer is confirmed, and tenant/user/causation fields are unpopulated by the publisher.
Requires confirmation
- Intended downstream consumers and required compensation behavior.
- Tenant-context propagation and relay execution.
Source References
microservices/src/contracts/Events/PayrollCalculatedEvent.csmicroservices/src/payroll-service/Application/PayrollCalculationService.csmicroservices/src/document-service/Messaging/DocumentReadModelConsumer.csmicroservices/src/notification-service/Application/EventNotificationResolver.csmicroservices/src/notification-service/Messaging/NotificationEventConsumer.csmicroservices/src/platform-service/Messaging/PlatformEventConsumer.csmicroservices/src/integration-service/Domain/IntegrationEntities.cs
Related Articles
See Also
Keywords
- Payroll events
- Payroll Unfreeze Events
- Integration contracts
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly