Harvest

The Operations Lead

Web, desktop and mobile apps with a one-click timer, offline tracking that syncs once the connection returns, GPS and geofenced check-in for field crews, and timesheet submissions with approval — workable for my office and field staff. But we found no public information on any shared kiosk, terminal or badge for workshop and shift crews without their own device, no bulk-correction workflow, and the geofencing claims come without the vendor stating its limits. 1 2 5 6

Report an error

The Payroll Officer

One-click timers run from browser, desktop and mobile, the offline app holds entries locally and syncs when the connection returns, and timesheets travel through submission and approval rather than an admin edit — that much is real. What the pages never show is a shared capture point for site and shift crews: no terminal, kiosk or badge reader, and no bulk-correction trail; GPS and geofencing are claimed without the vendor stating their limits. It fits desk workers far better than the people I actually run payroll for. 1 2 5 6

Report an error

The Works Council Advocate

Capture is broad for office work — one-click timers from browser, desktop and mobile, offline tracking that syncs when the connection returns, and timesheet submissions with approval — but we found no public information on any kiosk or terminal for shift and deskless crews, or on bulk corrections with an attributable change history. GPS tracking and geofencing are marketed to "verify employee locations" with no stated limits on what is stored, who may read a person's day, or how it can be switched off; under my co-determination that omission costs it. 1 5 6 9

Report an error

The Agency Owner

Timer, daily and weekly timesheets and calendar logging all run on web, desktop and mobile, with offline tracking that syncs back and conflict resolution on reconnect — my desk staff are well covered. We found no public information on any shared terminal, kiosk or badge reader for site crews, the geofencing claims come without stated limits, and corrections run through timesheet submission and approval rather than bulk edit. Solid capture for an office workforce, a step below the full multi-path setups. 1 2 5 6

Report an error

The Field Supervisor

Timers run from browser, desktop and mobile with one click, and the offline story is real — locally stored time syncs back to the cloud once a connection returns, with GPS tracking and geofencing mentioned though without the vendor stating its limits. We found no public information on a kiosk, terminal or badge reader as a shared capture point, nor on bulk corrections with a trail of who changed what; approvals exist as timesheet submissions. Good for crews who each carry a phone, but the gate at 6am has no terminal. 1 2 5 6

Report an error

The Skeptic

Web, desktop and mobile timers are documented, offline tracking with sync-back and conflict resolution is stated on the offline-timesheet page, and timesheets can be submitted for approval — though "Timesheet approvals" appears only in the Enterprise feature list. I found no public information on a shared capture point such as a kiosk, terminal or badge reader, on bulk correction with attribution, and the GPS and geofencing claims come without the vendor stating their limits. Desk and phone capture is solid; the shared-terminal side of the picture is unevidenced. 1 2 5 6

Report an error

The Operations Lead

The compliance story is written for the United States — record keeping is framed around the Fair Labor Standards Act — and we found no public information on break rules, the 8/10-hour daily maximum, the 11-hour rest period or retention of the working-time record itself; the retention figures published cover backups and logs, not employee time records. Since the BAG ruling that record is the whole job in my operation, and nothing here evidences the German duty. 2 4 10

Report an error

The Payroll Officer

The compliance story is written for the Fair Labor Standards Act — detailed records kept for that law — and I found no public information on break rules, daily maximum hours, rest periods, time accounts or statutory retention of the working-time record; the only retention figures are operational, up to a year of activity logs. Timesheet approvals and an activity log exist on higher tiers, but nothing maps to the German recording duty. Sent as-is, this record would not pass an inspection unaided. 2 4 10

Report an error

The Works Council Advocate

Every compliance claim on these pages points at the US Fair Labor Standards Act; we found no public information on the German recording duty, break rules, warnings on the 8/10-hour daily maximum or the 11-hour rest period. The published retention figures — backups up to 180 days, application logs up to 90 days, activity logs up to 1 year — concern system operation, not the working-time record an inspector would demand. Submissions and approval before export give it more structure than a raw hour sum, but on the German rules the captured pages are silent. 1 4 9 10

Report an error

The Agency Owner

Every compliance statement captured points at the Fair Labor Standards Act, and we found no public information on break rules, rest periods, daily maximums or anything addressing the German recording duty. The retention figures that are published cover database backups and logs rather than a statutory employee time record, so an inspection would rest on timesheet approvals and an activity log alone. 2 4 10

Report an error

The Field Supervisor

Everything captured about regulation is American — detailed records kept to meet the FLSA — and we found no public information on break handling, the daily maximum hours, the 11-hour rest period, or retention of the working-time record itself; the published retention periods cover backups, application logs and activity logs. Nothing here evidences a record built to survive a German inspection. 4 10

Report an error

The Skeptic

Every compliance reference on the captured pages is American — the Fair Labor Standards Act — and I found no public information on break rules, daily maximum hours, the eleven-hour rest period, statutory retention of the working-time record, or any mapping to the German recording duty. The only retention figures are operational ones (database backups up to 180 days, activity logs up to 1 year). Structured, approved timesheets are more than raw hour sums, so this sits just above the bottom. 2 4 10

Report an error

The Operations Lead

There is a separate scheduling product, Harvest Forecast, for scheduling a team across projects — capacity planning, not a shift or duty roster with rest checks or qualification coverage. We found no public information on vacation entitlement or carry-over, sickness recording, holiday calendars or swap workflows, which is the half of attendance that makes the time data mean anything for 200 people. 1 2

Report an error

The Payroll Officer

Vacation, sickness, entitlement and carry-over appear nowhere in the captured pages; the only planning product is Forecast, which schedules people across projects rather than running a shift roster or an absence calendar. Every vacation day and sick note would reach the payroll run by some other route, and I found no public information on holiday calendars or substitution workflows. 1 2

Report an error

The Works Council Advocate

Harvest Forecast schedules teams across projects, but we found no public information on vacation requests or entitlement, carry-over, sickness recording, an absence calendar, or any duty roster with rest-period checks. Vacation would have to live in another system, which is precisely the split that makes recorded hours useless for staffing decisions. 1 2

Report an error

The Agency Owner

Forecast schedules my people across projects, which is capacity planning for the resourcing I actually do. But we found no public information on vacation requests, entitlement or carry-over, sickness recording, an absence calendar, or a duty roster with availability — so the attendance half of this criterion leaves nothing to evaluate. 1 2

Report an error

The Field Supervisor

We found no public information on vacation requests, entitlement and carry-over, sickness recording, holiday calendars or substitution workflows anywhere in the captured pages. The separate Forecast product schedules a team across projects, which is resource allocation, not a duty roster that checks rest periods before publication. 1 2

Report an error

The Skeptic

I found no public information on vacation requests, entitlement calculation, carry-over, sickness recording or per-location holiday calendars. Harvest Forecast is presented as its own product for scheduling teams across projects — capacity planning, not a shift roster with availability or rest checks — and no substitution or swap workflow is evidenced. The absence half of this criterion is not on the pages at all. 1 2

Report an error

The Operations Lead

This is the vendor's home ground: client-project-task structure, rates by person, project or task type picked automatically, billable and non-billable flags, budget alerts before overrun, recurring hour banks, invoices created in-product with payments collected via card, ACH or wire, and timesheet approval before export. Cost centres are not named as such and I found no statement on rate rules surviving a mid-project rate change, but the chain from tracked hour to paid invoice is well evidenced. 1 2 5 7

Report an error

The Payroll Officer

Time turns into revenue in one place: clients, projects and tasks, rates by person, project or task type chosen automatically, budgets with alerts, hour banks, and invoices raised, sent and paid inside the tool, with timesheets approved before export. That earns a high mark. I stop short of the top because the captured pages say nothing about rate rules surviving a mid-project rate change, and the handoff into accounting rests on generically named accounting and payment integrations. 1 2 7 9

Report an error

The Works Council Advocate

This is the product's centre of gravity: projects and tasks with billable and non-billable flags, rates by person, project or task type selected automatically, budget alerts, recurring hour banks with real-time consumption, approval before timesheets leave the system, and invoices through to client payment. We found no public information on cost centres or on how a rate change mid-project is treated. One caution from my side of the table: "profitability and utilization metrics" with breakdowns by team is exactly the evaluation of individuals that a works agreement must govern before rollout. 1 2 7 9 10

Report an error

The Agency Owner

This is why I would buy it: rates by person, project or task type picked automatically, budget alerts before a project runs away, hour banks and estimates consumed in real time, both Time & Materials and Fixed Fee projects, breakdowns by team, project and client, and invoicing with logo, tax rates and online payment built in. Timesheet approval gates the export, so approved time becomes the invoice without re-entry. We found no public information on a cost-centre dimension or on how a rate change treats hours already booked on a live project, which is the gap that would bite me mid-engagement. 1 2 7

Report an error

The Field Supervisor

Billable and non-billable hours, rates by person, project or task type selected automatically, budget alerts before a project runs over, and invoices created and paid inside the tool — time reaches revenue without re-entry, reported by team, project and client. We found no public information on cost centres or on how rates behave when a rate changes mid-project, which is what holds it below the top of the range. 1 2 7 10

Report an error

The Skeptic

This is the vendor's home turf: rates by person, project or task type chosen automatically, budget alerts, profitability and utilization reporting by team, project and client, recurring hour banks with real-time consumption, billable and non-billable entry, and invoices clients can pay directly. Approval before export and a named QuickBooks handoff are also evidenced. I found no public information on a cost-centre dimension, role-based rate cards, or rate rules that survive a mid-project rate change, which is what separates this from the top. 1 2 5 7

Report an error

The Operations Lead

The export path is a real process: timesheets must be submitted and approved for the period, batch export to CSV with field mapping to payroll categories, payroll-period date ranges, and a mark-as-exported step that prevents duplicate transmission; QuickBooks is named for payroll integration. But we found no public information on DATEV or any German payroll system, and night, Sunday and holiday surcharges, time accounts and absences are not evidenced anywhere on the captured pages. 5 9 10

Report an error

The Payroll Officer

The month leaves through a structured door — timesheets must be submitted and approved first, exports scope to individual, group or all with a predefined payroll period, fields map to payroll categories, and a mark-as-exported flag keeps batches from going out twice — and QuickBooks is the one named payroll system. But the surcharges I answer for — night, Sunday, holiday — surface only as "customizable pay rules", and I found no public information on time accounts, mid-month changes, retro corrections after the close, or any German payroll system. The format of record is still CSV, which tells me the handoff was built for retyping. 1 5 9 10

Report an error

The Works Council Advocate

The export path is genuinely structured — approval before export, payroll-period date ranges, field mapping to payroll categories, batch export, and a step that marks timesheets as exported to prevent re-export — and QuickBooks is named as an integration. We found no public information on night, Sunday or holiday surcharges, time accounts, mid-month changes, or any German payroll system, and we found no public information on absence handling that could travel with the hours. That leaves our tax adviser re-keying the German parts. 1 5 9 10

Report an error

The Agency Owner

The export path is disciplined — timesheets must be submitted and approved first, scoped to individual, group or all with a payroll-period date range, mapped to payroll categories, and marked as exported to prevent duplicates — and QuickBooks is named. But what is captured is generic CSV, and we found no public information on night, Sunday or holiday surcharges, overtime handling, time accounts, or any German payroll system, so my tax adviser would still be retyping the complicated parts. 1 5 9 10

Report an error

The Field Supervisor

The export path is structured: individual, group or all timesheets, predefined payroll periods, approval required before export, field mapping to payroll categories and a mark-as-exported step against duplicates, with QuickBooks the one named payroll system. We found no public information on night, Sunday or holiday surcharges, time accounts, retro corrections after the close, or a German provider such as DATEV — and with absence recording itself unevidenced, absences cannot ride along to payroll. 1 5 9 10

Report an error

The Skeptic

The export workflow is genuinely documented — individual, group or all timesheets, predefined payroll periods, approval required before export, mark-as-exported to prevent duplicates, and field mapping to payroll categories — with QuickBooks named as a direct payroll integration and API or CSV/Excel as paths. I found no public information on night, Sunday or holiday surcharges, time accounts, mid-month changes, a lock step before transmission, or any German payroll system; "customizable pay rules" is the only sentence standing in for all of it. 5 9 10

Report an error

The Operations Lead

Hosting runs on Google Cloud with the server region not stated, and the captured pages give different answers on who I would be contracting with: the vendor provenance is Harvest Inc. of New York while the privacy policy names Bending Spoons S.p.A. of Milan as controller. A subprocessor list is published and EEA transfers rely on standard contractual clauses, which lifts this above nothing — but as a German employer I cannot tell from public pages where my employees' data sits. 3 4

Report an error

The Payroll Officer

The controller of record is Bending Spoons S.p.A. of Milan, a sub-processor list is published, and transfers into the EEA, Switzerland and the UK rest on standard contractual clauses, adequacy decisions or binding corporate rules — but the Google Cloud hosting region is never stated, and the chain includes US providers such as Google and the payment processors. Sovereignty is asserted at the entity level and left dark at the data-centre level. 3 4

Report an error

The Works Council Advocate

The vendor is a US company, hosting sits on Google Cloud with no region stated, and the privacy policy itself names Google Analytics and US payment providers in the chain. An Italian controller, published standard contractual clauses and a referenced sub-processor list are worth something, but contracting entity, ownership and data residency are unconfirmed, and the same policy states that personal data may be shared with advertising partners and that aggregated or de-identified data may be used to train AI models. For a system that measures working time, this would not clear our data-protection committee. 3 4

Report an error

The Agency Owner

The privacy policy names Bending Spoons S.p.A. of Milan as controller, points to a published sub-processor list, and cites Standard Contractual Clauses, adequacy decisions and binding corporate rules for international transfers. But hosting runs on Google Cloud with no region stated, the provenance is a New York company, and the same pages show advertising partners and AI model training on aggregated or de-identified data — for client-confidential hours I could not tell a German client where their data sits. 3 4

Report an error

The Field Supervisor

The privacy policy names an Italian controller, Bending Spoons S.p.A. of Milan, beside a New York vendor, hosting sits on Google Cloud with the server region not stated, and the sub-processor chain includes US payment providers and Google Analytics. Standard contractual clauses are the safeguard named for transfers; we found no public information on a data-centre location or an EU hosting option, which is the whole question for a German site office. 3 4

Report an error

The Skeptic

The provenance gives Harvest Inc. of New York as the vendor while the privacy policy names Bending Spoons S.p.A. of Milan as controller — the captured pages give different answers for the contracting entity. I found no public information on the Google Cloud hosting region, the subprocessor exposure is flagged for the US CLOUD Act with Stripe and Braintree named for payments and Google Analytics for analytics, and the sub-processor list is only pointed to, not shown. Standard Contractual Clauses exist as a safeguard, but a transfer mechanism is not a data location. 3 4

Report an error

The Operations Lead

Per-seat prices are public for every tier with both monthly and annual figures — Teams at $9 seat/month and $108 per seat billed annually, Enterprise at $14 seat/month and $168 per seat billed annually — and the currency is stated as all prices in USD, so the base seat maths for 200 people is doable. But the plan states that additional invoices, projects, clients and tasks are billed based on what you use without publishing those usage rates, and we found no public information on VAT treatment or minimum contract term, so the real annual invoice stays an estimate. 2

Report an error

The Payroll Officer

Per-seat prices are public — Free, Teams at $9 seat/month ($108 per seat, billed annually) and Enterprise starting from $14 seat/month — with the billing period, the annual 20% off and USD currency stated. But the usage-based charges for additional invoices, projects, clients and tasks carry no unit prices, and I found no public information on VAT treatment or minimum term, so the true annual invoice cannot be computed from the public pages. 2

Report an error

The Works Council Advocate

Headline per-seat prices are public with the billing period — a free single-seat tier, Teams "starting from $9 seat/month", Enterprise "starting from $14 seat/month", all in USD with a stated annual 20% discount — but the Enterprise Plus tier carries no number, and usage-based billing for additional invoices, projects, clients and tasks has no public unit rates, so the true annual invoice cannot be computed. We found no public information on VAT treatment or a minimum term. 2

Report an error

The Agency Owner

Per-seat maths is public and clean: Teams at "$9 seat/month" or "$108 per seat, billed annually", Enterprise at "$14 seat/month" or "$168 per seat, billed annually", plus "Annual 20% off", "All prices in USD", a defined free tier and a no-credit-card trial. But the base rate is metered beyond it — additional invoices, projects, clients and tasks "are billed based on what you use" with no unit prices captured — the Enterprise Plus tier lists features without a number, and we found no public information on VAT treatment or a minimum term. I can price forty seats; I cannot price my real annual invoice. 2

Report an error

The Field Supervisor

Headline per-seat prices are public with the annual maths shown — "$9 seat/month", "$108 per seat, billed annually" on Teams, "$14 seat/month" and "$168 per seat, billed annually" on Enterprise, all in USD with a 30-day trial. The real invoice stops being computable beyond that: additional invoices, projects, clients and tasks are billed on usage with no unit prices published, the Enterprise Plus tier carries no number, and no VAT treatment or minimum term is stated. 2

Report an error

The Skeptic

Per-seat prices are public with billing period and currency — "$9 seat/month" or "$108 per seat, billed annually" for Teams, "$14 seat/month" or "$168 per seat, billed annually" for Enterprise, annual 20% off, all prices in USD. But the same pricing bills additional invoices, projects, clients and tasks "based on what you use" beyond the base rate with no unit prices published, so the real annual invoice is not computable; Enterprise Plus carries no public price, and I found no VAT treatment or minimum term. 2

Report an error