Check a pay run

Every person in the latest pay run is priced from their profile and their hours, then compared with what payroll is about to pay. Only the exceptions are shown. This is the one screen that can stop an underpayment before the money moves rather than find it afterwards.

What this checks

The check reads the pay run straight from a connected payroll system. With no system connected the page says "No payroll system connected" and offers "Connect a payroll system", which goes to Integrations. If a system is connected but no pay run has come through yet, the page says "Nothing to check — no pay run has come through from yet."

It uses the same compliance engine, rules and accuracy tiers as a single payslip result. Only the timing and the source of the inputs change: the questions are answered on the person's work profile and the hours come from a system feed or an attested answer, so a run with hours reaches the Evidenced tier and may claim dollars.

Two notes can appear above the results:

"These are the latest posted pay run." — there is no draft pay run to read, so this checks pay that has already been processed. With Xero, the check reads the latest draft pay run whenever there is one, so it runs before the money moves; with no draft, it falls back to the latest posted run.
"Demo data." — the pay run was seeded to show what the gate does and didn't come from a payroll system.

The result

The run reads like a single payslip result, for the whole team at once:

A chip — "Pay run needs a look" or "Ready to run" — beside the pay run's period, how many people are in it and the payroll system.
A headline: "4 of 14 need a look before you run this." (just "need a look" when the run has already been processed), or "Everyone in this run looks right."
A sentence with the total: "If you sent it as it is, about $X would be underpaid", and how many people have been overpaid.
The areas that were checked — award rate, penalties, overtime, allowances, super, junior and apprentice steps, public holidays and overpayments. An area with a flag is highlighted.
One row per person with something to deal with: their name and role, what looks wrong in plain words, and roughly how much short. "See what to change" opens each finding with what to do about it and the clause it rests on. FairCheck can't change the pay run itself — make the change in your payroll system.
"Also worth knowing" — an overpayment, such as a casual loading paid to someone employed full-time or part-time. It is never counted as money owed, and never blocks the run.
"N people looking right", folded away, naming everyone with nothing to do.

Can this run be cleared?

The line at the bottom is the hard stop. It reads one of:

"This run can be marked as checked" (adding "once the flags above are fixed in " when there are any)
"This run can't be cleared yet: N people with no hours. Pay worked out without hours isn't a check, so supply them or record a reason for each."

with "N people checked" beside it.

Missing hours are the only thing that blocks a run. Every other flag is something you can act on or accept.

For each blocked person, their row offers three ways forward:

"Record hours" — type the hours yourself in the box (for example mon:8 tue:8, or ordinary:38). They are recorded and attributed to your email address.
"Ask their manager" — opens a request that goes to the manager on the person's record. Shown only when the person has a manager email; otherwise the link reads "Add a manager email first".
"Record and waive" — accept that this person has no hours for this run. A reason is required: "Give a reason — a waiver without one isn't a record of anything." The waiver is recorded with your name and applies to this run only.

"Ask for all N" beside the hard stop opens a hours request for every blocked person at once.

Hours we're waiting on

Once requests are open, this section lists each person with who the request is waiting on and when it moves to the next person, for example " — with you · moves 21 Aug, 09:00".

The chain has three steps: you → their manager → the person. Each step gets the interval set in Account settings under "Wait before asking the next person" (a choice of 4, 8, 12, 24, 48 or 72 hours). The last step doesn't expire — an unanswered request is still someone whose pay can't be checked, so it stays on this screen ("moves only when answered") until it is answered or waived. Requests for cycles older than 45 days stop generating emails but stay open.

Managers and employees answer through emailed links that need no login:

The manager's email is "FairCheck — confirm hours for " and opens a page headed "Confirm your team's hours", with an "Hours this period" box per person and an "I can't say — ask the employee instead" tick box that moves that request straight to the person. The email carries no names; the team list sits behind the link.
The person's email is "FairCheck — were these your hours?" and opens "Were these your hours?" showing either what their manager supplied or a suggested total from their usual week. They answer "Yes, that's right" or "No, it was different" with their own hours.

The links expire; each answer is recorded with who gave it and when. A later answer is added rather than overwriting an earlier one, so a manager's and an employee's figures can both survive. If the hours turn up in payroll before anyone answers, the request closes on its own.

Waived

Lists every waiver recorded for the runs on screen, as <person> — "<reason>" by <name>. A waived person is no longer an exception, but the waiver itself is the record and stays here.

Worth a look this cycle

Triggers that fired for a person this cycle and change the money — each with a title, detail and suggested action. Triggers that fired but don't change the money are logged, not shown.

Exceptions

An exception is a person with something to deal with: a finding, no hours, or no seat on your plan. Each is a row in the result, grouped by person, so someone with three findings appears once.