Reference · built on requestOperator by FibricWorkforce & scheduling

Timesheet Signoff

Lists unapproved timecards and open exceptions before the pay-period lock and proposes each manager's approval batch.

Request accessPricing ↗

About

Timesheet Signoff is an operator job for the days before a pay period locks. It reads timecards from your time and attendance system, the pay-period calendar from payroll, and the exceptions those systems already flag: a missing clock-out, a punch an employee has not reviewed, a timesheet failing a validation rule. It sorts what is still unapproved by the manager responsible for it.

Each manager receives one batch in Slack or Microsoft Teams: the timecards, the hours, and the exceptions to clear first. The manager approves the batch or strikes lines from it. Only then are the approvals written to the time system, once, with a receipt of who approved what and when.

This is a reference listing. It documents what Fibric would read from Timesheet Signoff and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Timecards and their approval state: Deputy timesheets with TimeApproved and PayRuleApproved, 7shifts punches with all_punches_approved, QuickBooks Time users with submitted_to and approved_to
  • Exceptions the time system flags: a Deputy ValidationFlag, a Homebase timecard with no clock_out, a 7shifts punch an employee has left pending
  • The pay-period calendar and its lock: 7shifts payroll periods with closed and finalized states, Paylocity open pay periods, Gusto pay periods
  • Close and approval events: the 7shifts payroll_period.closed webhook, Connecteam user_timesheet_approved and admin_day_locked events, Deputy timesheet webhooks at time and pay approval
  • Which manager approves for which team: ADP Workforce Now team time cards keyed by the manager's associate OID, Deputy areas, 7shifts locations
  • Approve and strike decisions on the batches it posted, returned by Slack block_actions payloads or Microsoft Teams Adaptive Card actions

Proposed actions

  • Target capability: propose one approval batch per manager, listing each timecard with hours, the period, and open exceptions, posted to Slack or Microsoft Teams
  • Target capability: propose approving the lines a manager accepts, through Deputy /api/v1/supervise/timesheet/approve or a QuickBooks Time approved_to update
  • Target capability: propose a correction for each flagged timecard, such as a clock-out time or an ADP time-entries.modify, for the manager to confirm
  • Target capability: propose a reminder to employees whose time is unsubmitted before the lock, using QuickBooks Time submitted_to or 7shifts employee punch approvals
  • Target capability: propose handing signed-off hours to payroll as a Gusto time sheet by shift or a Paylocity pay entry batch

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Clear Deputy validation flags before pay approval

    Timesheets with a ValidationFlag set are grouped by area and sent to that area's manager in Slack. On approval, each update or approval goes through the supervise/timesheet endpoints and the receipt names the timesheet ids.

    With Deputy, Slack

  • Finalize a 7shifts period location by location

    payroll_period.closed fires per location. Where all_punches_approved is false, the operator lists the pending punches for that location's manager in Microsoft Teams and proposes each correction before the period is finalized.

    With 7shifts, Microsoft Teams

  • Move QuickBooks Time approvals into Gusto

    Users whose submitted_to trails the period end get a reminder proposal. Once a manager signs off, the operator proposes the approved_to update, then a Gusto time sheet with hours classified by shift.

    With QuickBooks Time, Gusto

  • Sign off ADP team time cards

    Team time cards are read per manager. Cards with missing entries become a batch with a time-entries.modify correction attached to each, ready to send when the manager approves.

    With ADP Workforce Now, Slack

Requirements

  • A time and attendance connector that exposes timecards and approval state: Deputy, 7shifts, QuickBooks Time, ADP Workforce Now, Connecteam, or Homebase
  • A pay-period source so the lock date is known: the same system's payroll periods, or Gusto or Paylocity
  • Slack or Microsoft Teams, where each manager receives the batch and answers it
  • A manager-to-team mapping, taken from the time system where it holds one or supplied per site
Authentication
Holds no credentials of its own. Each read and write goes through a connector you bound to it, with the scopes that connector was granted.

Limits

  • Where the time system's API is read-only, as with a Homebase public key, the batch is a list and a person approves inside the product
  • A batch nobody answers stays unapproved. Silence is reported at the lock, never treated as approval
  • It does not compute pay. Overtime, penalties, and pay rules stay with the time and payroll systems that own them
  • A period a manager reopens after export is re-read on the next pass; the operator does not reverse an export

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Timesheet Signoff ↗

Questions and answers

What does a manager approve?
A batch: every unapproved timecard for their team in the period, with hours and any exception shown on the line. The manager approves the batch, or strikes lines and approves what remains. Nothing is written to the time system until that answer arrives.
What record is left?
For each batch: who received it and when, which lines were approved or struck, the write that followed with the system's response, and how to reverse it. The record stays with the pay period.
Does it ever approve a timecard on its own?
No. It lists, proposes, and waits. It also does not edit hours; a correction is proposed as a specific change the manager confirms, and a struck line stays as it was.
Ask about Timesheet Signoff

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy