Answer the question about money already paid, pin the statement it rests on, and log the clock that the employee message may itself have started, for a named payroll officer to release.
A pay query arrives, and the wage statement it concerns is pinned to the reply before it is sent.
02
A records request is spoken, not written, and Cal. Lab. Code 226(c) still runs twenty-one days.
Reason
03
A deduction is queried, and the reply gives the ledger line, not that anybody authorised it.
04
A departure is mentioned, and 29 CFR 2590.606-4(b)(2) puts forty-four days on a named person.
05
A leaver asks for a W-2, and 26 U.S.C. 6051(a) runs thirty days from that written request.
Decide
06
A 1095-C is asked for, and Pub. L. 118-167 makes the asking itself the start of the clock.
07
A disability claim comes up, and 29 CFR 2560.503-1(l)(2)(i) wants strict adherence, so it is handed on.
Out
08
A figure cannot be tied to a record, and the gap is reported as the finding, not smoothed away.
09
Write back to payroll records only inside the approval boundaries agreed at implementation.
→Product statement
Reading, matching and holding belong to the agent. The answer that binds belongs to a named payroll officer, who releases it and owns the clock it started.
Example workflow
One pay query, arrival to release
AgentHuman
1Query receivedA message about a payslip, a deduction, a benefit election or a form already due
2Characterised and datedWhether the message is a statutory demand, which clock it starts and the day it arrived
3Records pulled and matchedThe wage statement, the deduction backup, the plan record and what could not be found
4Controls appliedClock checks, retention checks, jurisdiction checks and match confidence
No human action required
Stages 1 to 4 run unaided, and nothing is confirmed to an employee at any of them — the agent is assembling, and the officer lane opens at the release gate.
5DecisionSplits at the release gate
Reply matches the record
Goes to the named payroll officer to release.
Anything unmatched
Adds a benefits officer read first.
Officer review
The reply is held with the statement it cites, the clock it started and the records it could not find.
Release · Attach record · Send to officer review
Released — by the named payroll officer▼
6Case and payroll records updatedOnly where write access and records policy allow it
7Outcome evaluatedClock capture, record currency, officer corrections and what review found
Corrections
Each officer correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Confirming to an employee that a figure is correct.
Signing the wage-statement compliance attestation.
Deciding a deduction was lawfully authorised.
Furnishing a COBRA election notice.
Automation boundaryAgent acts unaided
✓Log the day the request arrived, and its clock.
✓Report what the payroll record holds, and no more.
✓Characterise each incoming request a statute might treat as a demand.
✓Report the deduction, the code beside it and any authorisation held.
Nothing is confirmed to an employee except by a named officer, inside the agreed boundaries.
Judging whether a request is a statutory demand.
Telling an employee a claim will be paid.
Choosing which jurisdiction rule governs a case.
Changes to pay, plan enrolment or a statement.
Example output
One pay query, annotated
This serves a payroll team that may have to defend the wording of a statement under Cal. Lab. Code 226(e) years after the pay itself was settled; below is one reply exactly as the agent leaves it.
Pay query · single statementIllustrative example
Reply
Recorded as
Statement
Evidence of record
Confidence
Held for
Deduction query, March statement
Matched to the ledger line
Statement, itemised
Payroll register, 3 August 2026
Held unreleased
The named payroll officer
As receivedDrawn from the payroll register and the plan record for that period, and it claims nothing beyond them.
What the record holdsPayroll registerDeduction backupPlan record
Why no confirmation hereConfirming a figure is a judgement the named payroll officer makes.
ActionReleaseAttach recordSend to officer review
What the score decidesBelow the configured threshold a reply gets a benefits read before the officer sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Each replyFrom the record that carries it
03Evidence
Where the evidence is used
The agent does not vouch for a payroll system, only for what it recorded and when; under Naranjo, No. S279397 (Cal., 6 May 2024), the belief that counts is the employer's.
01Approved path
Correct is not the same as said
Under 29 U.S.C. 259 the only assurance with effect is a written ruling of the Wage and Hour Administrator, and an answer from a system is not one.
02Human review
What was checked, and not found
No independent payroll error rate exists, and the percentages in circulation trace to vendor marketing, so none is published here. What was checked instead was currency: NY Lab. L. 198(1-a) was narrowed on 16 May 2025, and 29 CFR 516.5 has not moved since 1987.
04Build an evidence trail
The query, the statement it concerns and the officer who answered it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Payroll system of recordHRIS · payroll engine · registers Pay runs and wage statements
Benefits administrationPlan administration · carriers Elections and cover dates
Time and absence recordsTimekeeping · absences · accruals Hours worked and applicable rates
Agent
Payroll and benefits support
Reads the records Assembles the reply Holds for the officer
Tax and statement archiveTax-form archive · statement store W-2, 1095-C and prior statements
A team-level correction figure can read clean while multi-state wage-statement queries carry most of the corrections. Nestack reports the correction rate by query class, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Multi-state wage statements
13.1%
3.7×
Review
Benefit and COBRA queries
9.3%
2.6×
Review
Deduction and authorisation queries
5.8%
1.6×
Watch
Routine payslip queries
2.6%
0.7×
Normal
Bar: correction-rate lift vs. routine-payslip baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What an unlogged request costs
A loop closes when the request that started a clock nobody logged is a standing case. That suite is what the next queue worked is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on multi-state wage-statement queries.
02Diagnose
The records request that was answered helpfully, closed as resolved and never logged is worked backwards until one cause is left standing.
03Improve
Number the reply; the statements that support it are filed beneath it.
04Verify
A single unlogged request case stops the whole queue closing.
05Learn
One case joins the suite, and one line joins the reply rules.
Learn → DetectThe return edge. The next reply is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, records, reply assembly, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Wage-statement and automation-boundary scoping work.
02Payroll, plan and archive sources.
03Request-to-clock and statement-coverage mapping work.
04Payroll record ingestion.
05Statement, record and period binding.
06Match scoring and review routing.
07Officer release workflow.
08Payroll-system integration.
09Statement and request cases.
10Guardrails and reply controls.
11Request-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne pay group, one cycleProductionProduction support workflowAdvancedMultiple pay groups / states
Introduced at Pilot
Reply assembly to your records✓✓✓
Named officer release✓✓✓
Pay-record baseline✓✓✓
Introduced at Production
Reporting by query class—✓✓
Officer review workflow in your systems—✓✓
Approved write-back—✓✓
Ledger-and-benefits integration—✓✓
Introduced at Advanced
Multi-state statement rules——✓
Cross-jurisdiction reply packs——✓
Large query volumes——✓
Multi-state statement controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, query volume, release controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your live pay groups and the statement each is issued under→Statement capture and clock versioningWeek 1
02Representative payroll, plan and archive records→Record binding, reply logic and the pay-record baselineWeek 2
03Your pay calendar and the officers it names→Statement mapping, clock capture and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Payroll, plan and archive assessment, then integration setupWeek 2
05Replies you would not want itemised→Statement cases and the failure roundWeek 4
06What no reply may confirm→Match scoring, review routing, guardrails and release controlsWeek 3
07A named payroll officer who releases the reply→Release to the named officer, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
These bands are counted and never evened for looks; the fifth week holds two because the two coincide.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Statement discovery, clock versioning and the automation boundaryW2Record integration and the pay-record baselineW3Reply assembly, match logic and release controlsW4Evaluation suite, statement cases and failure-mode testingW5Payroll-system integration, pilot replies and targeted correctionsW6One pay cycle run under the payroll officer, then Agent Care handover
Reading the bandNo bar runs past the weeks its own work is named for, and week five is shared by design.
At the end of W6When the request record validates, Agent Care picks the agent up.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · HR AI agent
Build a payroll and benefits support agent around the clock your last reply never logged.
Show us one week of pay queries and the replies that went back. In Magadia, No. 19-16184 (9th Cir., 28 May 2021), the pay was never in dispute and the statement carried the case anyway. If a request was answered with no clock logged, correct is not the same as said.
