Feature guides
Timesheet and Time Adjustment Approvals
Route attendance and time corrections through chained review queues, preserving a clear handoff before approved time reaches wage calculation.
Explore 40 questionsThe short answer
What matters for your decision
Hirebase supports three chained review queues for time, job, and missed-punch adjustments before payroll readiness. The organization defines its process and Hirebase is configured for that implementation; the practical fit is strongest when teams need a connected workflow across hourly or distributed operations.
Separate captured time from requested changes
Keep a captured punch distinct from a requested correction. That separation helps reviewers see what happened and what a worker or manager is asking to change. Require a reason and relevant shift context so a reviewer can compare the request with the original attendance record.
Route each request to its owner
Hirebase describes three chained queues: time adjustment, job adjustment, and missed-punch adjustment. Define who owns each decision and what context a request must include. A request should arrive with enough information for its assigned reviewer to approve, reject, or return it without guessing why the change is needed.
Keep a traceable decision record
A job adjustment moves the charge to a different job or site code without changing the underlying hours. Preserve the reason so payroll and job-cost reviewers can understand the change. Keep that distinction visible because correcting cost allocation should not rewrite the punch record itself.
Close the loop before payroll handoff
Only move approved records toward wage calculation and payroll handoff. Test approve, reject, return, and unresolved cases with payroll owners. Confirm what happens to an item that remains open at cutoff, and who can communicate the delay to the worker and downstream payroll team.
Keep three adjustment types distinct
The payroll page describes chained review queues for time adjustments, job adjustments, and missed punches. Time adjustments change requested punch times; job adjustments change the job or site charged; missed-punch requests address an absent punch. Separate queues make the decision under review clearer.
Preserve a reason when work is rejected
The product page describes one-click approvals and a typed reason for rejection. A supervisor can also file a missed punch on a worker's behalf through the same review queue. Confirm who may submit, approve, return, and close each request before payroll cutoff.
Hirebase for your operation
Make the workflow fit your business.
Connect workforce workflows with organization-wide licensing, configurable operating rules and customer-controlled Azure deployment. Bring your site requirements, worker journey and integration needs to an implementation conversation.
Evaluate HirebaseYour buying questions
Questions, answered
40 of 40 questions
What does this workflow cover for timesheet and time adjustment approvals?
The Timesheet and Time Adjustment Approvals workflow in Hirebase connects three chained review queues for time, job, and missed-punch adjustments before payroll readiness in a shared operational record. The exact steps depend on the client implementation.
Link to this answerWho typically owns this process for timesheet and time adjustment approvals?
Operations leaders usually define the process, with supervisors, HR/payroll, and IT contributing where their work or controls are affected.
Link to this answerWhat information should be ready before rollout for timesheet and time adjustment approvals?
Map the current roles, records, exception paths, approval owners, and downstream systems first. This gives the implementation team a concrete process to configure and validate.
Link to this answerHow does the workflow start for timesheet and time adjustment approvals?
The process starts with the operational event—such as a worker being assigned, a shift being completed, or a record needing review—and uses three chained review queues for time, job, and missed-punch adjustments before payroll readiness as its context.
Link to this answerWhat happens when an exception occurs for timesheet and time adjustment approvals?
The team should define an owner and a review path for exceptions. Hirebase records operational activity and configurable approvals; it does not remove the need for a responsible reviewer.
Link to this answerCan managers review and correct records for timesheet and time adjustment approvals?
Yes. The relevant manager review and correction steps can be configured for the client's workflow. Preserve the original event and make the adjustment reason clear to reviewers.
Link to this answerHow does this connect with scheduling for timesheet and time adjustment approvals?
Scheduling can use three chained review queues for time, job, and missed-punch adjustments before payroll readiness where the configured workflow requires it, helping operations connect planned work with what happened in the field.
Link to this answerHow does this connect with attendance for timesheet and time adjustment approvals?
Attendance records provide the actual event details that can be reconciled with three chained review queues for time, job, and missed-punch adjustments before payroll readiness; each deployment determines which verification steps apply.
Link to this answerHow does this connect with payroll for timesheet and time adjustment approvals?
Hirebase calculates wages from attendance and approved time data, then hands the result to the payroll provider the organization uses. Payroll disbursement remains with that provider.
Link to this answerCan requirements differ by client or site for timesheet and time adjustment approvals?
Yes. Hirebase is configured around client workflows, so roles, thresholds, and steps can vary where the implementation defines those differences.
Link to this answerDoes Hirebase replace our existing payroll processor for timesheet and time adjustment approvals?
No. Hirebase calculates pay; the existing payroll provider remains responsible for processing and disbursing it. Statutory filing is not performed by Hirebase.
Link to this answerCan teams exchange data with other systems for timesheet and time adjustment approvals?
Hirebase supports REST APIs, webhooks, and CSV/XLSX exchange. Named enterprise ERP integrations may require client-specific engineering; confirm the exact system and data contract during scoping.
Link to this answerWhat should operations measure for timesheet and time adjustment approvals?
Choose measures tied to the purpose: completeness, turnaround time, exceptions, approval aging, and whether the downstream handoff reconciles. Set definitions with the process owner.
Link to this answerHow can supervisors use the records for timesheet and time adjustment approvals?
Supervisors can use the operational record to see status, spot open exceptions, and route work to the next owner. Access should follow the client's role design.
Link to this answerWhat should workers be told for timesheet and time adjustment approvals?
Explain which information is collected, when it is collected, who reviews it, and how workers can raise a correction or question. Follow the organization's policies and applicable law.
Link to this answerCan the process support multiple locations for timesheet and time adjustment approvals?
The platform supports distributed operations. Site structures, permissions, and local process differences should be agreed as part of the deployment design.
Link to this answerWhich approval queues are described for time review?
The platform describes three chained queues covering time adjustments, job adjustments, and missed-punch adjustments.
Link to this answerCan a worker request a missed-punch correction?
Yes. A missed-punch adjustment can be submitted with context and routed through the configured review chain.
Link to this answerDoes a job adjustment change the recorded punch time?
A job adjustment changes which job or site code receives the shift; it does not rewrite the original punch hours.
Link to this answerWho approves a time adjustment?
The client implementation defines the manager hierarchy and which roles review each adjustment type.
Link to this answerCan a request be returned or rejected?
Approval steps should define how reviewers approve, reject, or return a request and how the submitter learns what remains to be done.
Link to this answerDo approved adjustments flow into wage calculation?
Approved time data can feed Hirebase wage calculation. Confirm the specific review and export sequence in the implementation.
Link to this answerCan teams review the reason for an adjustment?
The workflow can retain the request context and reviewer decision. Agree on required notes and evidence for each adjustment type.
Link to this answerDoes an approval guarantee legal payroll compliance?
No. The approval workflow supports review and recordkeeping; the employer remains responsible for payroll rules and compliance decisions.
Link to this answerCan time and job changes follow different review paths?
Yes. Hirebase describes separate chained queues for time adjustments and job adjustments, with the client defining the responsible reviewers.
Link to this answerCan a missed punch be submitted for review?
Yes. Missed-punch adjustments have a dedicated queue and can be reviewed with the worker's shift context.
Link to this answerDoes changing a job code alter the employee's hours?
No. A job adjustment changes the job or site code charged; it leaves the recorded hours unchanged.
Link to this answerWhat information should accompany an adjustment request?
Require the shift, requested change, reason, and any evidence the reviewer needs to make a decision. Client owners define the fields and approval policy.
Link to this answerCan a reviewer see who approved a correction?
The chained queue provides an approval workflow; confirm the audit details available to each role and the retention expectations during implementation.
Link to this answerWhat happens to a rejected request?
The client should configure the return or rejection route, explain the reason to the submitter, and retain the original punch alongside the decision.
Link to this answerCan approvals happen before the payroll cutoff?
Teams can route adjustments through the configured queues before payroll preparation. Set a cutoff and owner for requests still open at that time.
Link to this answerAre time approval rules the same for every worker?
The client defines applicable approval roles and variations by site, job, or worker group during implementation.
Link to this answerWhat are the three documented approval queues?
Time adjustment, job adjustment, and missed-punch adjustment are the three chained queues described on the payroll page.
Link to this answerCan a supervisor file a missed punch for a worker?
Yes. The platform page says an administrator or supervisor can submit a missed punch on an employee's behalf, with a required reason, through the review queue.
Link to this answerDoes a job adjustment alter the hours worked?
No. It changes the job or site code assigned to the shift; it does not rewrite the punch hours.
Link to this answerIs a reason required when a reviewer rejects a request?
The product page documents a typed reason for rejection, leaving context for the submitter and later review.
Link to this answerCan a time adjustment include break changes?
The page describes time adjustments as correcting original in and out times, including break changes. Confirm the fields used in the selected workflow.
Link to this answerCan a manager start an adjustment from a punch report?
Yes. A supervisor can open a time adjustment against a specific punch from the punch reporting view and attach a note.
Link to this answerDo these queues decide whether a payroll rule is lawful?
No. They support operational review and record correction. Employer payroll owners remain responsible for applying applicable rules.
Link to this answerHow should teams test approval routing?
Submit one item of each adjustment type, approve one, reject another with a reason, and check how an open request is handled at the payroll cutoff.
Link to this answer