Slack notification — as the team sees it
How critical findings reach the on-call payroll specialist. Routine dispositions can be done from Slack. Every button writes to ai_decision_log.
Channel: #payroll-ops · Bot: peopleops-bot · Latency: 1.2s from detection to delivery · API: Notification v46
# payroll-ops 12 members
PO
peopleops-bot APP 12:31 PM
🚨 CRITICAL anomaly detected
ClassGarnishment not applied
EmployeeEMP-48329 (Backcountry)
Pay periodPP-2026-08
Detected2 minutes ago
Evidence: Active child-support order CO-2024-77821 (25% of disposable, effective 2024-11-01) on file. Current period shows $0 deducted. Order has not expired.
AI explanation: The garnishment_orders table shows order CO-2024-77821 as active. The deductions table for PP-2026-08 shows no garnishment line item. Most likely cause: sync gap between garnishment vendor feed and HRIS deduction module. Validator: PASS.
Failure safe: If Slack delivery fails, notification is queued + retried. Daily reconciliation surfaces undelivered. Critical findings also trigger email + SMS to on-call.