How to use a Righthand with Deputy

Quick answer

Use Righthand to prepare a Deputy payroll-readiness exception list without approving time or running payroll. Approval stages matter more than a filled-in hours field.

Start with a reviewable deliverable, keeping Deputy as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

Deputy documents draft, approved, and approved-for-payroll timesheet states. See the official Deputy reference. Provider capabilities and Righthand's available tools are separate checks.

Use the restricted timesheet packet for one approved period, retaining employee IDs and the documented draft, approval, and payroll states. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: timesheet ID, employee reference, period, location, hours, approval state, reviewer. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Operational review and payroll authorization are separate. Righthand should not infer wage rules or approve a disputed entry.

Illustrative first-run brief

Use the owner-provided Deputy snapshot or approved read-only view. Review the supplied weekly timesheet snapshot. Separate draft, approved, and payroll-ready entries and list missing owner reviews. Do not approve, edit, or export to payroll. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the payroll administrator to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

An approved operational timesheet may still require payroll approval. The report preserves that distinction instead of counting every entry as ready.

Compare a timesheet ID and approval state with the original source, then reconcile the selected period. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

A date cutoff can split overnight shifts. Preserve source times and ask the payroll owner to resolve period treatment.

If a submitted timesheet is awaiting approval, route the draft question to the manager rather than asking the employee to submit again.

FAQ

What should the reviewer verify first?

Verify employee and timesheet IDs, worked dates, timezone, and separate approval states. “Approved” and “payroll approved” should retain their actual meanings.

How should a repeat run be scoped?

Keep period, source zone, and approval cutoff consistent. Refresh late corrections and approval changes before readiness review; do not reuse a prior payroll conclusion.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.