boundary
Will Payrune Calculate My Payroll?
No — never. Not gross, not tax, not net, not a helpful 'estimate'. Payrune's entire output is the reviewed exception register: what was approved, what is drafted, and where they differ. Computation and movement of money are different acts with different regulators, different failure modes, and different reversibility, and they stay outside the review by design. Missing source fields become named failures; hours and rates are never invented. Payrune never calculates pay or tax, modifies payroll, or releases payments.
Why computation is excluded, not just unreached
A review tool that also computes faces a quiet temptation: when sources conflict, produce the number anyway. Excluding calculation removes the temptation structurally — the tool has no number to defend, so honesty costs it nothing.
There is also an accountability argument. When a computed wage is wrong, someone must own the correction, the filing amendment, sometimes the back pay. That ownership belongs to the payroll professional and their systems, where obligations like tax filings actually live — not to a review layer that would split responsibility in two.
What to bring
Bring your organization's answer to one question: after the register is reviewed and accepted, which system computes and releases pay? The review is built to hand off cleanly at exactly that point.
No extra documents are needed — the boundary concerns roles, not more paperwork.
Step 1: Use the register as the run's input evidence
Attach the reviewed exception register to the run's approval record. Whoever authorizes the run can then show every difference was seen, valued, and decided — the strongest thing a review can give a payer.
Step 2: Keep computation in the payroll system of record
Gross-to-net, taxes, and filings belong where statutory obligations sit. Feeding them cleaner inputs improves them; duplicating them creates two truths about money.
Step 3: Keep release behind human authorization
Payment moves only through authorized people and systems. Payrune never releases payments — including 'just this once' at deadline; the boundary does not flex under pressure, which is what makes it reliable.
Step 4: Escalate tampering signals to people, immediately
Integrity alerts stop review and surface with audit references. They indicate possible interference with approvals — exactly the condition under which no automatic path, in any tool, should touch money.
Step 5: Hold the line when it is inconvenient
Requests to add a small calculator or a direct payout option are requests to merge review with money movement. Payrune never calculates pay or tax, modifies payroll, or releases payments — that sentence is the product's license to be trusted with sensitive records.
Verification
Two inspections prove the boundary: every result carries flags keeping calculated pay, calculated tax, and released payment false; and no artifact in the workspace contains a computed wage. Both are checkable directly on any output, without trusting anyone's word.
Limits that define this boundary
Payrune never calculates pay or tax, modifies payroll, or releases payments. It reads supplied records, compares them, and reports; the register and the payment systems leave its hands untouched.
Missing source fields become named failures; hours and rates are never invented — including when invention would be convenient before a deadline.
What Payrune is for, precisely
Payrune occupies the review layer of payroll: it turns approved time, rate records, and a draft register into a complete, typed exception list with both values preserved, and it stops there on purpose.
Everything monetary — computation, correction, filing, payment — belongs to the specialist and their system of record, now armed with a review that missed nothing and invented less.
FAQ
Questions this guide is for
Could an estimate mode be added later?
Computation is excluded by design, not deferred. The review's trustworthiness depends on having no number of its own to defend.
Then who fixes the errors it finds?
Your payroll specialist, in your payroll system. The register tells them exactly what differs and shows both values; acting on it is their role.
Is at least the net pay safe to approximate?
No approximation is offered at any layer. Approximate money in payroll is just error with decimals.
Start in the workspace
Put the review layer to work
Sign in from this page and review one pay period. Every difference surfaces with both values — and payroll itself stays exactly where it belongs.