Nothing is approved for payment until the right people have checked it.
Givver flags payroll issues before approval, then takes each employee through your approval levels. Approvers can send people back for changes, and nothing moves on until enough approvers have signed off.
- Checks before approval
- Approval levels
- Send back with a note
Issues raised while there is still time to fix them.
- Large changesPay that moves more than expected from last month.
- Missing dataDetails payroll needs but does not have yet.
- Zero or negative payResults that need a second look.
- High deductionsDeductions above what you would expect.
- Minimum wage concernsPay that may fall below the minimum.
- Joiners and leaversStarters and leavers in this cycle, listed together.
Per-employee approval, level by level.
Each employee moves through the approval levels you configure, such as payroll then finance. Where quorum is enabled, the run only proceeds when enough approvers have signed off.
- Configurable approval levels
- Approval quorum
- Send back or revoke with permission
Notes and documents kept with the payroll.
Payroll specialists and reviewers keep cycle notes and employee notes with linked documents, so the reasoning stays with the run.
- Cycle-level notes
- Employee-level notes
- Linked documents
Payroll approvals, answered.
What does Givver check before payroll is approved?
Large changes from last month, missing data, zero or negative pay, high deductions, possible minimum wage concerns, and joiners and leavers in the cycle.
Can we have more than one approval level?
Yes. Each employee moves through the levels you configure, such as payroll then finance. With quorum enabled, the run only proceeds when enough approvers have signed off.
Can an approver send an employee back?
Yes, with a note. Cycle notes, employee notes and linked documents stay with the payroll.
See the checks on your own payroll.
Bring an anonymised recent pay run, or talk us through how it works. We'll show you what Givver would flag.