# Payroll input validation > Payroll input validation: Changes explained (hours, starters, leavers, rates) Checked: vetoed by code. Produces approved inputs, queries. Source: https://www.sumarity.ai/library/payroll-input-validation/ HR and payroll # Payroll input validation Reads this run's payroll inputs, the last run, contracts. Produces approved inputs, queries. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person. Vetoed by codeScreening, audit and compliance Start from this workflowMore for hr and payroll What it decides ## Narrow questions, each with a check behind it. Changes explained (hours, starters, leavers, rates) Vetoed by code: variance against last run, contracts. Code can't prove the answer right, but it can prove it wrong: an amount out of range, an impossible date, a name not on the document. Many settle; the rest go to a person. | Reads | This run's payroll inputs, the last run, contracts | Produces | Approved inputs, queries | Who signs | A person on your team, with every figure traced to its document and every call on record | Process | Screening, audit and compliance | Industry | HR and payroll See it run ## Every line, decided where it's safest. An example run. Each stage lights up as a line is decided there; pick a stage to see its lines. ReadsThis run's payroll inputs, the last run, contractsCodeReads, matches, ties out and works out every figure.JudgementChanges explained (hours, starters, leavers, rates). Settles only when it clears the cutoff and no check in code rules it out.A personGets whatever stays uncertain, with the evidence. Their ruling tunes the next run.ProducesApproved inputs, queries Payroll input validation · example run Example run | Ref | Item | Value | Decided by | EMP-118 | Hours 168 → 172Overtime approved | +4 h | Code · approved | EMP-121 | New starterContract and bank details complete · 0.96 | | Engine · checked | EMP-130 | Salary +15%No change letter on file | | To a person | EMP-133 | Leaver, final payHoliday balance paid out · 0.93 | | Engine · checked | EMP-140 | UnchangedSame as last run | | Code · unchanged | Settled 4 To a person 1 Settled wrong 0 Illustrative lines. Amber rows are the Judgement Engine's calls; each settles only above its cutoff and when its check agrees. What it could save ## Your volumes in. Your hours out. In our tests, between 24% and 42% of items still went to a person after tuning. Set your own share; a pilot measures it on your data. Items per run Runs per month Minutes per item by hand Cost per hour Share of items that still need a person: 30% By hand today80 ha month With Sumarity24 ha month, for the items people decide Saved56 hCHF 53,760 a year Related ## Start from what's closest. ### Screening, audit and compliance in other work Finance ### Supplier bank-detail change verification Whether a change request is genuine Cross-checkedFinance ### Expense claim audit Whether each claim fits policy; receipt matches the claim Proven by codeBanking ### Sanctions screening alert review True match or false positive Vetoed by code ### More for hr and payroll ### Timesheets vs rota vs payroll Hours worked, paid, scheduled agree Proven by code ### Right-to-work and onboarding checks Documents valid and complete Cross-checked ### Benefits enrolment reconciliation Insurer list vs payroll deductions Proven by code Questions ## What buyers ask What happens when Sumarity isn't sure? Nothing settles below the cutoff, or when the check disagrees. The item goes to a person in the inbox with what the engine saw, its best answer and the runner-up. The person's ruling is kept and tunes the next run. How are its judgements checked? Code can't prove the answer right, but it can prove it wrong: an amount out of range, an impossible date, a name not on the document. Many settle; the rest go to a person. Can we change it to fit how we work? Yes. Start from this workflow and describe your differences in plain words. The design assistant revises it, the validator checks it, your expert reviews it on the canvas, and your admin publishes it. Does it read our files as they are? Yes: spreadsheets and CSV in any layout, PDFs, bank formats and e-mail attachments. Sumarity suggests how each column maps, proves the mapping on a sample and remembers it once a person confirms it. Where does our data go? Sumarity runs in Zurich. Your data, backups and logs are stored in Switzerland. How does it get better? Your team's rulings become an answer key. Better questions and cutoffs are proposed, tested on data they haven't seen, and published only when your admin approves. It improves itself, with permission. ## Start from this workflow. Run it on your data. A pilot runs alongside your own process for a few weeks, at our cost, and ends in a line-by-line comparison. Talk to usBack to the library