Wages calculated on-platform, paid through your systems.
Hirebase computes employee wages at the shift level and routes exceptions through chained approval queues. Resolve time, job, and missed punch adjustments before syncing verified payroll data directly to your payment systems.
chained approval queues
time, job & missed punch
to approve
a typed reason to reject
calculation accuracy
wages calculated per shift, location, and role
Shift-Level Wage Calculation & Pay Boundaries
Hirebase calculates every employee's wages from verified time and job records. Getting that pay onto a check, and keeping it compliant with regional payroll law, is handed to systems built for exactly that: a direct paycheck integration, or a submission to ADP, QuickBooks or another payroll provider your team already trusts.
Wages are captured at the individual-employee level, so every calculation traces back to a specific worker's verified time.
Union Dispatching & Labor Rules Mapping.
Multiple labor unions can be mapped in the system, delivered the same way payroll and ERP connections are: engineered per client deployment, not a generic toggle every tenant sees.
We configure union rules alongside your other integrations when we set up your deployment.
Three-Stage Approval Workflow & Queue Audit Trails
Every exception lands in one of three queues before it affects a paycheck.
Time Adjustment
Corrected punches
Job Adjustment
Reassigned or corrected jobs
Missed Punch
Unresolved punch gaps
Approving any of the three queues is a single click. The default path stays fast for the common case, where the record is correct.
A supervisor can also open a time adjustment directly against a specific punch from the punch report, attaching an adjustment note as it moves into review.
Rejecting requires a typed reason. The asymmetry is intentional: approval needs no explanation, but every rejection leaves a record of why.
A missed punch can be filed by an admin or supervisor on an employee's behalf, through a form that requires a reason before it can even be submitted.
Review Discipline for Shift Adjustments
A time adjustment, a job adjustment and a missed punch are not interchangeable labels on the same form. Each one corrects a different part of the record.
Time Adjustment
Corrects a punch's original in and out time against the time being requested instead, break changes included. Employee-initiated by default, and a supervisor can open the same kind of request directly against a punch on the reporting side, without waiting for the employee to raise it.
Captured on every request: Employee, date, job, original and requested punch times, break changes, adjustment reason, requested by, status, review note, reviewed by.
Job Adjustment
Moves which job or site code a shift is charged against, not the hours themselves. The punch stays exactly as recorded; only the job it counts toward changes, from an original job to a requested one, which matters for job costing and client billing as much as for payroll.
Captured on every request: Employee, date, original job, requested job, adjustment reason, requested by, status, review note, reviewed by.
Missed Punch
Fills a gap where no punch exists at all, rather than leaving the hours blank or editing a total by hand. An admin or supervisor can file one on an employee's behalf, and it enters the same review queue as any other request rather than skipping the approval step.
Captured on every request: Employee, job code and name, punch-in and punch-out date-time, breaks, reason, requested by, status, review note, reviewed by.
Leave Management & Accrual Balance Verification
Requesting time off follows the same request-then-review shape as the three adjustment queues, on its own dashboard. An employee opens a leave type, sees a live balance detail for it, sets a date range, adds an optional note, and submits; a manager works the result as a queue, not an inbox.
Each tile is filterable by date range. The list beneath carries employee, dates, duration, reason and status on every row.
The same asymmetry applies here. Approving a leave request is a single confirmation; rejecting one requires a typed reason, on the record against the reviewer's name.
On the employee's own mobile app, a rejected request shows that reason inline. Accountability extends to self-service, not just the admin console.
Onboarding
Activation
Field Execution
Monitoring
Completion
Exit
Approvals and wage calculation are what turn a verified shift into a closed, payable record at Completion.
Wages calculated here.
Paid through your systems.
We will map Hirebase to your compliance framework,
your ERP and your region.
© 2026 Hirebase. All rights reserved.