Payroll Software for Agriculture 2026

Why farm payroll is its own category

Agriculture sits in a separate payroll universe from every other industry. The rules are different. The workforce is different. The tax thresholds are different. And the pay structures would break most software that small businesses rely on.

Consider what a strawberry farm in California might run in a single week: permanent year-round employees paid bi-weekly on salary, H-2A visa workers paid weekly per the terms of their job order, and piecework day laborers who need to be settled daily based on flats picked. That is three concurrent pay cycles, two different wage floors, and a unit-based compensation calculation that must be reconciled against minimum wage law before anyone gets a check. Generic payroll software is not built for any of this.

The IRS even publishes a separate circular just for agriculture. Publication 51 (Circular A) governs agricultural employers and establishes completely different thresholds for FUTA and FICA. You only owe FUTA if you paid $20,000 or more in wages in any calendar quarter, or if you employed 10 or more workers for at least 20 weeks in the year. Standard payroll tools apply FUTA from dollar one to every employee because that is what the rules say for everyone else. If your payroll software does not know the difference, you are making incorrect tax deposits and may face penalties on audit.

Then there is the labor law patchwork. California requires overtime after 8 hours in a day for agricultural workers. Washington mandates overtime for H-2A workers specifically. Florida and Texas have minimal ag-specific protections and lean on FLSA defaults. A software platform that applies one state's overtime rules across all your locations, or that applies standard FLSA without the agricultural sector exemptions, will systematically miscalculate overtime every single pay period.

This is before you touch the piece-rate problem, which we will get to in detail. The short version: no major payroll platform handles it correctly, and farms are running parallel spreadsheet systems to stay compliant. That tells you everything about where the software market stands in 2026.

The piece-rate problem no software has solved

Piece-rate pay is the defining payroll challenge in agriculture, and it remains largely unsolved by mainstream software. If you pay workers per bin, per bushel, or per row, here is what federal law requires: take the worker's total earnings for the pay period (units times piece rate), divide by hours worked, and compare to the applicable minimum wage. If the piece-rate average falls short of minimum wage for any hour worked, you owe the difference. That makeup pay must be issued within the same pay period.

This sounds straightforward until you have 80 workers picking at different speeds across a 10-hour day with variable piece rates depending on the crop section. You need to track units per worker per day, hours worked per worker per day, apply the correct minimum wage (federal, state, or local, whichever is highest), and generate a makeup pay line item for anyone who comes in short. Then you have to do it again tomorrow.

Gusto cannot do this. ADP Run cannot do this. QuickBooks Payroll cannot do this natively. They all have custom pay type fields where you can enter piece-rate earnings as a lump sum, but none of them has a module that ingests unit counts, calculates hours-adjusted earnings, and automatically generates the reconciliation. Farms doing this correctly are running a spreadsheet alongside their payroll software, calculating the true-up manually, and then entering the makeup pay as a manual adjustment. That is a compliance liability and an administrative burden on top of already thin margins.

FarmBooks and AgriSoft, the two niche agricultural payroll systems, understand piece-rate natively. They were built specifically for this workflow. The tradeoff is that both have dated interfaces, poor mobile support, and limited direct-deposit integrations. Your field supervisor cannot approve payroll from a phone. Your workers may face delays getting paid because direct deposit options are narrow. These platforms tend to be used by agricultural accountants who process payroll on behalf of farm clients, not by farm operators directly.

Until a mainstream platform builds a real piece-rate reconciliation engine, farms have three options: use a niche ag-specific tool and accept the UX limitations, use a modern platform and maintain a parallel spreadsheet for piece-rate compliance, or hire an agricultural payroll specialist to manage the gap. None of these is ideal. For 2026, the honest recommendation is to know which choice fits your operation before you sign any contract.

H-2A compliance: what your software must handle

H-2A is the federal temporary agricultural worker visa program, and it imposes wage requirements that go beyond standard minimum wage. The Adverse Effect Wage Rate (AEWR) is a state-specific federal wage floor that the Department of Labor publishes annually each January. It varies by state and typically runs higher than both federal and state minimum wages. For 2025, AEWR rates ranged from roughly $14 to over $20 per hour depending on the state. Your H-2A workers must be paid at least the AEWR, and that rate updates every year.

Standard payroll software uses a single hourly rate field. It has no concept of a worker classification that carries a mandatory federal wage floor separate from the rate you enter. If you set an H-2A worker's rate at the AEWR when you hire them in January, and the DOL publishes a new higher AEWR mid-contract (which can happen in some years due to revised surveys), your software will not alert you. You will keep paying the old rate until a DOL audit catches it.

H-2A employers who provide housing and meals face an additional layer. You are permitted to deduct the fair market value of housing and meals from wages, but net pay after deductions can never fall below the AEWR. That requires a benefit-offset calculation that no standard payroll platform performs. Most farms handle this by either not deducting housing (accepting it as a business cost) or doing the calculation manually each pay period and entering the result as an adjustment.

The weekly pay requirement adds another constraint. H-2A job orders specify weekly pay, while your permanent staff may be on bi-weekly cycles. Gusto's architecture supports only one pay schedule per company. That is a hard blocker for any operation with both H-2A and permanent employees. Paylocity, Paycom, and ADP TotalSource all support multiple pay groups within the same account, which is the architecture you need.

If you use H-2A workers and your current payroll software does not have: (1) a worker classification field that enforces the AEWR as a wage floor, (2) annual rate-update alerts tied to DOL publication dates, and (3) support for multiple pay frequencies within the same company, you have compliance exposure right now. The DOL has increased agricultural labor enforcement activity, and back-wage assessments for AEWR violations can cover the entire contract period.

Tool-by-Tool breakdown: what each platform actually offers

ADP TotalSource is the most capable option for large multi-state farm operations. It supports multiple pay groups, can be configured for ag-specific tax thresholds, and has the implementation depth to handle custom pay types that approximate piece-rate workflows. The catch: setup requires a dedicated implementation team and typically takes 60-90 days. Pricing runs roughly $150-200 per employee per month for PEO services, which is how TotalSource is structured. That makes it unsuitable for seasonal headcount spikes. If you have 300 harvest workers for 8 weeks, the math does not work. TotalSource makes sense for large, vertically integrated operations with 100 or more year-round employees and a dedicated HR staff member who can manage the implementation.

Gusto is the best modern payroll UI on the market, and it is wrong for most farm operations. The one-pay-schedule-per-company limitation alone disqualifies it for H-2A employers. Beyond that, it has no AEWR enforcement, no piece-rate module, and its per-employee pricing ($6-12 per employee per month on top of the base fee) becomes expensive during harvest spikes. Use Gusto only if you have a small farm with under 20 permanent hourly or salaried workers, no H-2A visa employees, and no piece-rate compensation. Many small vegetable and flower farms fit this profile and find Gusto perfectly adequate.

QuickBooks Payroll earns its place in agriculture through integration with QuickBooks accounting software, which a large share of farms already use for their general ledger and farm income tracking. It handles standard hourly and salaried payroll well, and custom pay types can be used to enter piece-rate earnings as a lump sum. What it cannot do is calculate the reconciliation for you. It also applies standard FUTA rules and will not track the agricultural FUTA thresholds separately. Pricing starts around $45 per month plus $6 per employee. Best for small farms under 20 workers with no H-2A, paying hourly only, who want tight integration with their farm accounting.

Paylocity and Paycom occupy the same tier: enterprise-grade platforms that can be configured for multiple pay groups, custom piece-rate pay types, and state-specific overtime rules. Paylocity has a slightly stronger mobile experience for field supervisors. Paycom has a more unified data model that reduces duplicate entry. Both price around $25-40 per employee per month, which makes seasonal spikes of 100+ workers for 8 weeks genuinely expensive. A farm bringing on 150 harvest workers for 8 weeks at $35 PEPM is looking at roughly $42,000 in payroll software costs for the season alone. That number is real and needs to be factored into the analysis. For operations where H-2A compliance, multiple pay groups, and sophisticated reporting are non-negotiable, Paylocity is the strongest mid-market choice available today.

FarmBooks and AgriSoft are the only platforms that understand piece-rate and AEWR natively. Both were built specifically for agricultural operations and contain the compliance logic that no mainstream platform has bothered to build. FarmBooks in particular has been used by agricultural accountants and farm bureaus for decades. The limitations are significant: interfaces that feel like they were designed around 2008, weak mobile support, limited direct-deposit banking integrations, and minimal self-service for workers who want to check their pay stubs. If you have a farm accountant who manages payroll on your behalf and is already familiar with one of these platforms, staying with it may be the right call. If you are trying to manage payroll in-house with a small admin team and field supervisors who need mobile access, these tools will frustrate you.

Hourly.io deserves a mention for smaller operations focused on hourly time tracking. Its GPS-based time tracking is genuinely useful for farms with multiple field locations, and it supports multiple pay rates per employee, which can be used to approximate piece-rate entry by logging different rate codes for different crops or tasks. Direct piece-rate reconciliation is still manual, and there are no H-2A compliance features. Pricing is lower than the enterprise platforms. Best for small farms with hourly workers across multiple locations who need accurate time capture more than compliance automation.

Red flags: signs your current software is getting it wrong

FUTA on every employee from day one. If your payroll software is calculating and depositing FUTA for every agricultural worker you pay, regardless of whether you have met the $20,000 quarterly wage test or the 10-worker-in-20-weeks test, you are over-depositing on taxes and potentially filing incorrect 940s. Pull your last four quarters of 940 filings and check the agricultural exemption lines. If they are blank and you employ seasonal workers, something is off.

A single pay schedule for everyone. If your H-2A workers are on the same bi-weekly cycle as your permanent staff, check your H-2A job order. Most require weekly payment. Running H-2A workers bi-weekly violates the terms of the visa program and creates DOL exposure independent of the wage rate issues.

No AEWR rate in your system at all. If you search your payroll software for AEWR, Adverse Effect Wage Rate, or H-2A wage floor and find nothing, your software is not enforcing it. You are relying on your own memory to update H-2A worker rates when DOL publishes new figures each January. This is a compliance gap.

Piece-rate entered as a lump sum with no reconciliation step. If your payroll administrator enters piece-rate earnings as a flat dollar amount each period without a documented calculation showing total units times piece rate, hours worked, and the minimum wage comparison, you do not have a defensible compliance record. If DOL audits a particular worker's pay for a specific week, you need to be able to show the calculation, not just the check amount.

California, Washington, or Florida operations using FLSA defaults for overtime. These three states represent the largest concentrations of agricultural labor in the country and all have rules that differ materially from federal FLSA in ways that affect farm workers specifically. If your software is set to federal overtime defaults and you have workers in any of these states, verify the overtime configuration before the next harvest season.

Recommendations by farm size and operation type

Small farms, under 20 workers, hourly pay only, no H-2A: QuickBooks Payroll if you already use QuickBooks for accounting, Gusto if you are starting fresh and want the cleanest onboarding experience. Neither handles piece-rate automatically, so if you pay any piece-rate workers, budget time each pay period for a manual reconciliation spreadsheet. Confirm your software is applying agricultural FUTA thresholds correctly or work with a farm accountant to verify your 940 filings annually.

Mid-size farms, 20-100 workers, H-2A visa program, multiple pay schedules: Paylocity is the strongest choice available in 2026. Work with an implementation partner who has agricultural clients. Insist that AEWR rate tracking, multiple pay groups, and custom piece-rate pay types are configured before go-live, not promised as future additions. Budget $25-35 per employee per month for your year-round headcount, and negotiate a seasonal worker rate for harvest periods. Some Paylocity partners offer volume discounts for seasonal spikes.

Large operations, 100+ workers, multi-state, complex compliance: ADP TotalSource is worth the implementation investment if you have dedicated HR staff to manage it. The PEO structure gives you co-employment benefits including consolidated benefits administration and workers comp management alongside payroll. For farms with significant operations in California, the state-specific configuration capabilities in TotalSource are better developed than in most alternatives. Expect a 90-day implementation timeline and allocate internal resources accordingly.

Any farm with significant piece-rate operations and a dedicated accountant: Evaluate FarmBooks or AgriSoft before committing to a mainstream platform. The compliance logic built into these niche tools may outweigh the UX limitations if your accountant is the primary payroll administrator. Many farm bureaus and agricultural CPAs are already familiar with one of these systems, which reduces the learning curve significantly.

The broader truth about agricultural payroll in 2026 is that the market has not caught up to the industry's actual needs. The piece-rate reconciliation gap, the AEWR enforcement gap, and the multi-pay-cycle limitation are not edge cases. They affect the majority of commercial fruit, vegetable, and labor-intensive crop operations in the United States. Until a mainstream platform builds agricultural payroll as a real product category rather than a configuration exercise, farms will continue to run hybrid systems. Know which gaps your chosen software leaves open, document your manual processes, and work with a payroll professional who understands agricultural tax law. The exposure from getting this wrong is real.

Frequently asked questions

What is the AEWR and why does it matter for payroll software? The Adverse Effect Wage Rate is a state-specific federal wage floor for H-2A visa workers, published annually by the Department of Labor each year. For 2025, AEWR rates ranged from roughly $14 to over $20 per hour depending on the state. Payroll software must apply the correct current-year rate per state and flag when a new AEWR publication requires a mid-contract wage increase, which most generic tools do not do automatically [U.S. Department of Labor, Fact Sheet #26F].

Are agricultural workers exempt from overtime under federal law? Yes, in most cases. Employees working in agriculture are generally exempt from FLSA overtime requirements and do not have to be paid 1.5x for hours over 40 in a week. Small farms that used no more than 500 "man-days" of agricultural labor in any calendar quarter of the prior year are also exempt from federal minimum wage and overtime requirements entirely. State law can override this: California requires overtime after 8 hours in a day for agricultural workers, and Washington mandates overtime specifically for H-2A workers.

How does piece-rate pay interact with minimum wage compliance? Whether a worker is paid hourly or by piece rate (per bin, per bushel, per row), growers must ensure total earnings divided by hours worked meets or exceeds the applicable minimum wage for every hour. If piece-rate earnings fall short in any pay period, the employer owes makeup pay issued within that same pay period. No mainstream payroll platform (Gusto, ADP Run, QuickBooks Payroll) automates this reconciliation natively as of 2026; it typically requires a parallel spreadsheet or a niche ag-specific tool like FarmBooks or AgriSoft.

Can H-2A workers and permanent staff be paid on the same pay schedule? Not always. H-2A job orders typically specify weekly pay, while permanent staff are often on bi-weekly cycles. Platforms that support only one pay schedule per company, which includes Gusto, cannot accommodate both groups correctly. Paylocity, Paycom, and ADP TotalSource support multiple pay groups within a single account, which is the architecture needed for mixed H-2A and permanent payrolls.

Do FUTA and FICA rules differ for agricultural employers? Yes. IRS Publication 51 (Circular A) sets separate thresholds for agricultural employers: FUTA is owed only if the employer paid $20,000 or more in wages in any calendar quarter, or employed 10 or more workers for at least 20 weeks in the year. Payroll software built for general industry applies FUTA from the first dollar for every employee, which causes agricultural employers to over-deposit taxes and file inaccurate Form 940s if the software is not configured for the agricultural exemption.

What happened with H-2A rule enforcement in 2025? On June 20, 2025, the Wage and Hour Division suspended enforcement of provisions introduced in the 2024 H-2A Final Rule, including some piece-rate requirements, amid ongoing litigation. Employers should confirm current enforcement status with DOL guidance before assuming a specific rule is or is not in effect for the current season, since this area has been in flux [Federal Register, 2025].