How to use a Righthand with Harvest

Quick answer

Use Righthand to prepare a Harvest uninvoiced-work review that keeps time, expenses, and invoice status distinct. The reviewer decides what can be billed.

Start with a reviewable deliverable, keeping Harvest 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

Harvest documents time, expense, project, and uninvoiced-report APIs. See the official Harvest reference. Provider capabilities and Righthand's available tools are separate checks.

Request the approved project time and expense packet with entry IDs, client mapping, period, and owner-defined billing rules. 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: client, project, entry ID, date, duration or expense amount, currency, billable state, invoice link. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Uninvoiced does not mean billable or overdue. Financial classification and invoice issuance belong to the billing owner.

Illustrative first-run brief

Use the owner-provided Harvest snapshot or approved read-only view. Review the supplied uninvoiced report for one client. Separate time and expenses, flag unclear billable status, and prepare a review packet without creating invoices. 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 billing lead 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 expense lacking approval remains a question even when it appears in the report. No proposed amount becomes a final charge.

Match sample entries to their project and reconcile each currency separately. 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

Mixed currencies or changed project rates can invalidate a combined amount. Ask for the accepted rate and currency basis before totaling.

When a time entry's project association is ambiguous, ask the project owner to reconcile it before attributing the hours to a client.

FAQ

What should the reviewer verify first?

Verify entry, project, and client IDs, date boundaries, approval status, and billable designation. Logged time, invoice preparation, and received payment are separate states.

How should a repeat run be scoped?

Retain project mapping and cutoff dates between reviews. Reopen corrected entries and keep historical totals tied to the version the reviewer accepted.

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