Pattern Anomaly Agent
Reads each employee’s tip-to-sales pattern over time. Flags shifts that don’t fit the employee’s own history — not just the population statistic. Catches drift the alarms miss.
Intelligent Alarms catch what the rules can predict. AI Forensic Validation Agents catch what they can’t. Claude-powered agents read every closed day looking for pattern anomalies, FLSA edge cases, override patterns, and the kind of slow drift that becomes a wage-and-hour problem six months later.
Every closed day on PayDay Portal passes through the deterministic 10 Intelligent Alarms first. After that, six AI Forensic Validation Agents read the day’s data with a different kind of attention — probabilistic, pattern-aware, narrative-capable.
The agents run on every closed day, generate findings, and surface them through the same Insights and Alarms surfaces you already use — not as a separate tool to learn.
All 10 Intelligent Alarms have already fired. Triple Ledger has reconciled. The day is technically clean — or flagged.
Each agent ingests the closed-day record with relevant historical context: pool config, employee history, prior-period patterns, override log.
Findings carry confidence levels and reasoning. Each finding cites the rows that drove it — never just “the AI said so.”
High-confidence findings appear in Intelligent Alarms. Lower-confidence patterns appear in the Insights view. Narratives are added to the Compliance Archive entry for the day.
Fat-finger detection, duplicate distribution, compliance violation, rounding discrepancy, threshold breach — the rules everyone agrees on, run on every shift, in real time.
Best for: known failure modes, guaranteed coverage, immediate response.
Patterns the rules can’t enumerate — same employee’s tip ratio drifting, same manager always overriding the same way, FLSA edge cases that span multiple shifts. Run on every closed day.
Best for: unknown failure modes, slow drift, audit narrative.
The two layers are designed to work together. Alarms catch what we can predict; agents catch what we can’t. A clean day passes both.
Probabilistic systems must have explicit limits. Here are the locked ones.
An agent can flag a day for review. It cannot stop the payout. A human always decides.
Every finding cites the rows that drove it. No black-box outputs. If the citation isn’t there, the finding doesn’t ship.
Agents surface patterns; you decide whether they matter. The audit trail captures both the agent’s finding and your decision.
No separate tool, no new login. Findings surface in the screens your team already uses.
The 10 deterministic alarms run first; agents complement them, not replace them.
Lower-confidence patterns appear in the Insights view next to the day’s headline numbers.
Agents read the closed-day Triple Ledger record, including manager overrides and adjustments.
Agent narratives are stored alongside the rule-versioned day record. When auditors arrive, the story is there.
Slow drift surfaces before the quarter closes. Override patterns and outlier shifts arrive flagged with reasoning, not buried in a spreadsheet.
FLSA edge cases get attention before they become wage-and-hour claims. The Audit Narrative Agent writes the story your team would have to write by hand.
Override patterns — same manager always going one direction — surface as a coaching opportunity rather than a year-end surprise.







































































































