Farm Payroll Software: Check Agricultural Worker and Tax Routes

A farm can pay a harvest crew, a year-round maintenance team and a shop employee through the same bank account while needing different payroll treatment for each. A provider's agricultural industry page does not establish that its service can handle that combination. Start with the workers, the work and the required reporting, then ask a shortlisted provider to show the complete route.
Farm payroll software should support the farm's approved wage calculations, tax treatment and filings, including the exceptions it actually encounters. Form 943 support is an essential question for many agricultural employers, but it does not settle mixed farm and nonfarm reporting, H-2A treatment, piece-rate inputs or state requirements.
This guide helps U.S. farm owners and payroll administrators turn those questions into a purchase specification. The Agricultural Payroll Scope Checklist below separates the facts your advisers must resolve from the capabilities a provider must confirm. It also gives you a way to compare an all-in service with software that leaves some work to the farm or its accountant.

Comparing payroll support for your farm?
SelectSoftware Reviews offers free one-to-one help from a payroll software advisor. Describe your agricultural populations and required filings, and confirm whether the matching service can address that scope before requesting provider recommendations.
Contents
One farm can require more than one payroll route
Write a short inventory of the business before collecting quotes. Include each employing legal entity, its EIN, work locations, crops or livestock activities, related processing or retail operations, and the people paid through each arrangement. List direct employees separately from crews supplied through another organization and from genuine outside businesses invoicing for services.
Describe actual work rather than relying on job titles. A person called a farmhand may harvest one day and help another operation the next. A packing operation may handle only the farm's own produce or also buy and process produce from elsewhere. Those differences can matter to the legal analysis even when everyone wears the same uniform.
Ask the farm's tax and employment advisers to document uncertain cases. The payroll salesperson should receive an approved requirement, such as support for a particular return and wage treatment, rather than decide the employment or exemption question during onboarding. Keep the determination's date, facts and reviewer so that a later change in activities can trigger a new review.
Crew arrangements deserve a separate line. Paying a labor contractor's invoice does not, by itself, establish that the farm has no employment responsibilities. Obtain advice on the actual relationship, request the relevant records and agree who supplies hours, approves wages and answers worker questions. Do not create contractor records merely because the preferred payroll product cannot accommodate the workers.
The result should be a small number of described populations. For example: directly employed field workers, workers performing approved nonfarm duties, qualifying H-2A employees, and an externally supplied crew whose responsibilities have been separately reviewed. A population can contain many workers, but it should not hide materially different instructions behind one tax checkbox.
Ask three separate questions about agricultural work
The first question is the employment-tax reporting route. The IRS Form 943 instructions distinguish farm wages from other nonfarm wages reported on Form 941 or Form 944. They also describe a special option for household employees, so a domestic worker should not automatically be treated like every other nonfarm employee. Ask the tax adviser which returns and wage allocations apply to the actual arrangement.
The second question is wage-and-hour treatment. DOL's agricultural FLSA guidance explains primary and secondary agriculture and assesses agricultural exemption status by workweek. Its examples include packing commodities produced on a different farm as a potential problem. State protections may also apply. A federal agricultural overtime exemption is not a universal instruction to turn overtime off for everyone on the account.
California illustrates why the location question matters. Its agricultural overtime phase-in reached eight hours per day and forty per week for employers with 25 or fewer employees on January 1, 2025; larger employers reached that stage earlier. The state also describes double time after twelve hours and continuing seventh-day protections. Have the reviewer apply the relevant coverage and exceptions, then require the system to demonstrate the resulting instruction rather than a federal-only default.
The third question, where relevant, is the H-2A job order and employment program. That creates a set of contractual and recordkeeping requirements in addition to the tax and wage-and-hour analysis. DOL explains that covered U.S. workers in corresponding employment can also have H-2A protections. Their treatment should not be inferred solely from the presence or absence of a visa field.
Keep these answers in separate fields. An H-2A designation does not automatically resolve every FLSA workweek question, and a federal tax filing assignment does not establish a state overtime exemption. Ask the provider whether its system can preserve the approved distinctions without repeatedly overwriting the employee's history.
For a changing job assignment, specify what supervisors must record and when payroll receives it. If the adviser needs the source of produce handled, the site, the activity and the workweek, a time feed containing only employee name and total hours is insufficient. The missing facts must be collected upstream or the proposed operating arrangement needs to change.

Use separate determinations for tax reporting, wage rules and H-2A obligations. One agricultural label does not answer all three.
Decide which filings the service must handle
IRS Topic 760 explains the general agricultural cash-wage tests: $150 paid to an individual farmworker during the year or $2,500 in total cash and noncash farm wages, with exceptions for certain hand-harvest workers. Determine applicability before selecting a setup option. Family employment, noncash compensation and unusual employment arrangements need their own review rather than a blanket small-farm assumption.
Form 943 is an annual return, but required tax deposits can occur throughout the year. Ask for the applicable deposit schedule, its setup evidence, who monitors liability changes and where the farm receives confirmations. A sales answer about annual filing does not answer a question about timely deposits.
Build a filing list by entity and population. Include the applicable federal employment returns, unemployment reporting, state and local accounts, annual employee statements and any required special schedules. Identify whether the provider files, supplies a report for someone else to file, or excludes the task. A printable form and an accepted electronic return are different deliverables.
Federal unemployment tax also has its own farmworker tests. The 2026 IRS Publication 15 describes a $20,000 quarterly cash-wage test or 10 or more farmworkers in at least 20 different weeks in the current or preceding year. H-2A wages and workers count when determining those tests, although the qualifying H-2A wages themselves are not subject to FUTA. Have the adviser confirm the result and state treatment; do not copy the Social Security setting into the unemployment field.
For mixed farm and nonfarm payroll, get a written answer about the exact combination under the same business. Ask whether one account supports both reporting routes, whether an external preparer must take over a return, and how shared employee wage history remains reconciled. A proposed workaround involving duplicate employees or a second account requires a documented design. Opening another account does not create another employer or eliminate a reporting requirement.
Set responsibility for notices and amendments at the same time. If a prior agricultural return needs correction, identify the person who can prepare the relevant Form 943-X and obtain the supporting history. Do not assume a vendor's promise to fix its own processing error covers an old return prepared elsewhere.
Read agricultural support at the product level
The following examples come from providers' public documentation reviewed on October 30, 2026. They establish useful purchase questions, not a ranking or a claim that we tested a platform. Confirm the quoted product, service tier, jurisdiction and current written scope before committing.
OnPay: Its Company Basics help page includes a Form 943 agricultural-employees setup choice and says selecting it enables OnPay to file that form. That supports asking for an agricultural configuration. It does not establish support for every mixed 943/941 arrangement, H-2A exception or noncash wage case. Send the actual population and filing list and request an answer for each unresolved item.
Intuit QuickBooks: Its federal-forms support page states that Form 943 is supported in Intuit QuickBooks Workforce products. It describes manual Form 943 filing in Desktop Payroll Enhanced and no Form 943 support in Desktop Payroll Assisted. The same page says it cannot file both Form 943 and Form 941 or 944 for one business and excludes noncash or commodity wage reporting on Form 943. These distinctions can eliminate a proposed arrangement even when the farm already uses QuickBooks for accounting.
Gusto: Its Agricultural or farm payroll help page explicitly says agricultural payroll is not supported, including Form 943, piecework and H-2A backup withholding. Do not treat familiarity with its ordinary business payroll as evidence that the agricultural requirement is covered. If the business has a separate nonfarm operation, assess that operation's proposed service on its own facts without moving agricultural wages there to avoid the limitation.
For any other candidate, request documentation at the same level of specificity. A statement that the company serves agriculture may refer to a partner, an accounting export or only some employer types. Ask who performs the excluded work and how the two sides reconcile. If an essential task has no supported owner, remove that arrangement from the shortlist before comparing convenience features.
Describe H-2A work as a separate payroll population
For qualifying services connected with an H-2A visa, IRS guidance provides an exemption from Social Security and Medicare taxes and generally no mandatory federal income tax withholding. That does not mean the employee necessarily owes no income tax. Voluntary federal withholding requires the employer and worker to agree and the worker to provide Form W-4. Tax-residency instructions can affect the withholding calculation.
The IRS also describes a different reporting route where a worker fails to provide the required taxpayer identification number. For 2026 payments, the backup-withholding threshold is $2,000, with 24% withholding until the worker furnishes the number and Forms 1099-MISC and 945 for the affected compensation and tax instead of the ordinary W-2/943 route. Check the payment year's threshold because it is indexed after 2026. Ask the provider to demonstrate escalation and reporting for that exception. Do not use a generic contractor-payment screen as a substitute for understanding it.
Keep the approved tax instructions separate from the work contract. Under DOL's H-2A guidance, records include daily hours offered and worked, and earnings statements include relevant hours, rates, piece units and deductions. Software that records only hours paid may leave the farm without the information needed to monitor the contract's work guarantee.
Ask where the approved job order, work locations, effective wage requirements and permitted deductions are maintained. Identify the adviser or responsible specialist who updates them, the person who configures payroll and the reviewer who checks the result. Verify current applicable rules and orders at implementation; a rate copied from last season is not an approved rate for the new contract.
Request a statement showing ordinary earnings, a separately identified reimbursement and any authorized deduction. Confirm how the farm preserves the supporting instruction and how a correction reaches both the statement and reporting records. The ability to enter a negative deduction does not establish that the deduction is permissible.
Also specify worker access. Ask whether a person without reliable mobile data can receive an understandable statement, how language needs are addressed and how someone who has left the country can obtain annual documents or raise a pay question. Check access through a sample delivery method; do not assume a U.S. smartphone number will remain available all year.
Keep hours, units and job changes in the same evidence trail
Piece-rate payroll needs both production evidence and time evidence. A daily unit total cannot explain which workweek, activity, rate or employee generated the earnings unless the source records carry that information. Have the wage adviser establish the required calculations, then ask the provider to show how its supported configuration performs them.
Use a sample that resembles the farm's work: one employee changes crops or tasks, another has a rejected or corrected production ticket, and a third has hours without piece units. Include waiting, preparation or other activities that the adviser determines are compensable. The demonstration should show where these inputs are captured, who approves them and whether the wage statement remains understandable.
Keep effective dates on piece rates and hourly rates. Correcting a production quantity should change the intended event without replacing the rate that applied when earlier work occurred. Ask to see the original record, the correction, the recalculated pay and any resulting reporting change. A spreadsheet total pasted into an earnings field can be an agreed process, but its calculation and review then remain someone else's work.
Connectivity matters at the source. Have the time-system supplier explain offline capture, duplicate prevention and synchronization after a weak connection. Test the actual supported method before harvest, including a worker who transfers between crews. Retain an approved fallback that identifies the worker and work date; a supervisor's later recollection of a crew total is a poor substitute for attributable records.
Labor costing is another output. Crop, field, herd, activity and equipment codes may be useful to the farm's accounts, but changing a cost code should not silently change wage or tax treatment. Define the relationship explicitly. Ask the provider to show a corrected field allocation that leaves the approved gross wages and tax records intact where no pay change is intended.
Carry wages through to statements, taxes and farm accounts
Use distinct reconciliation totals instead of expecting every payroll number to equal gross wages. In this fictional 2026 demonstration, assume the farm's advisers have approved these three instructions for one period. The H-2A worker's annual compensation is assumed to reach the $2,000 reporting threshold, so the period's wages belong in the annual W-2 record:
Regular farm employee: $1,350 cash wages subject to Social Security and Medicare, below the applicable wage base.
H-2A employee: $1,200 qualifying visa-connected wages, valid TIN, no voluntary federal income tax withholding, and no Social Security or Medicare wages.
Nonfarm employee: $600 ordinary wages assigned to the business's separate Form 941 reporting route, also below the wage base.
Total gross wages are $3,150. The agricultural population's W-2 box 1 wage total for this example is $2,550, while its Social Security and Medicare wage totals are $1,350. The nonfarm employee's $600 belongs in the separately assigned reporting population. This is a demonstration of approved instructions, not a rule that every farm must divide its workers this way.
Ask the candidate to produce the employee statements, wage bases by filing route, liability detail, year-to-date records and accounting export. Verify that the H-2A exemption has not erased the $1,200 of reportable compensation and that the nonfarm amount has not been included in the agricultural return merely to make the report balance.
These figures do not calculate net pay, state tax, FUTA, wage-base exhaustion or a complete annual return. Add those cases separately when they affect the farm. Keep the expected answer with the demonstration so another reviewer can reproduce the comparison rather than accept a screen labeled successful.
For actual annual reporting, reconcile the applicable W-2/W-3 wage and withholding totals to their employment-return counterparts and explain valid differences. Preserve population-level detail when more than one return is involved. An all-employee gross total is useful for financial control, but it cannot replace comparisons of the correct tax bases.
For payment, distinguish the provider's funding debit from the employee's receipt and the tax deposit. Ask what evidence the farm receives for each, what happens if a bank file is rejected and who can authorize a replacement. A balanced register does not prove that the intended people or agencies received money.

In this fictional approved setup, $3,150 gross wages divide into $2,550 agricultural compensation and $600 nonfarm wages. The agricultural Social Security and Medicare wage base is $1,350.
Compare seasonal terms over the full employment year
Ask each candidate to quote the same operating year: active months, low-activity months, returning workers, annual filings and eventual corrections. Separate the recurring subscription from per-worker charges and from additional work such as prior-wage entry, registrations, special reporting and amendments. Wages, tax deposits and insurance costs should not disappear inside a single advertised service fee.
Clarify what inactive means in the contract. Does the farm retain worker and year-to-date records, can it process a late adjustment, and who prepares annual statements after the last harvest payment? Ask whether reactivation requires another implementation and whether workers can still access statements while the employer account is paused.
A fictional price comparison illustrates the point. Arrangement A charges $80 in each of six active months, $25 in each of six inactive months and $120 for the required annual filing package: $750 in service fees. Arrangement B charges $65 for all 12 months and includes that same package: $780. The first arrangement is $30 lower for the stated scope, rather than the $300 difference suggested by comparing only six active-month fees with B's annual subscription.
Neither fictional quote includes additional timekeeping modules or corrections. If one provider excludes the farm's H-2A reporting exception or mixed federal filings, first price an acceptable supported alternative and assign its work. An unsupported obligation cannot be made acceptable by a low subscription price.
Ask about support during the farm's actual payroll window. Name the cutoff, the farm's approver and backup, the escalation route and the response expected when a crew file arrives late. Do not buy an urgent-service promise without knowing the required information, funding deadline and limits on what can still change.
Agricultural Payroll Scope Checklist
Create one copy for each proposed service arrangement. Complete the population section with the farm's advisers, then ask each provider to supply evidence for the coverage section. Use a separate population row set when the approved instructions differ. Keep sensitive identity and immigration documents in the secure system rather than an ordinary comparison sheet.
The farm and its populations
1. Employing business: Record the legal employer, EIN reference, tax year and person authorized to approve the setup.
2. Actual activities: Describe the crops, livestock, processing, packing, retail or other work, including whose commodities are handled.
3. Work locations and periods: List states, sites, workweek definition and the expected season, including work outside the main season.
4. Worker arrangements: Identify direct employees, H-2A and corresponding-employment populations, family workers and reviewed crew-contractor relationships.
5. Approved wage rules: Identify the adviser, decision date and applicable hourly, piece, overtime, guarantee or other instructions, including change triggers.
6. Approved tax routes: Record required federal and state returns, wage bases and exceptions by population, with the tax review supporting them.
Do not mark the population ready while an unresolved classification or wage question is being treated as a software setting. Record what facts are missing and who will decide it.
Coverage that a provider must demonstrate
7. Product and service: Name the exact product, tier, partner and filing arrangement in the quote, including any outside preparer.
8. Reporting combination: Confirm support for the required farm and nonfarm returns for the actual business, plus H-2A and noncash exceptions where relevant.
9. Inputs and statements: Record how hours, units, job changes, rates, offered hours, reimbursements and authorized deductions reach understandable statements.
10. Deposits and payments: Name who funds, submits and verifies employee payments and tax deposits, including deadlines and failure escalation.
11. Farm accounting: Identify the crop/site/activity detail, export format and reconciliation needed without altering approved pay treatment.
12. Changes and retained records: Identify who fixes time, wages, returns and statements, with access to the original instruction and correction history.
Attach a dated answer, contract provision or demonstrated output to each item. Mark it supported, supported with a stated external owner, excluded or unanswered. An excluded task needs an acceptable alternative; unanswered required work keeps the purchase unresolved.
Commercial decision and acceptance
13. Full-year service cost: List active and inactive months, worker charges, annual work, setup, special reporting, amendments and any separately purchased module.
14. Seasonal continuity: Record pause/reactivation terms, annual reporting ownership and worker access after the season or service cancellation.
15. Conversion history: Identify prior wages, bases, returns, deposits and source records to transfer, with the old and new parties' responsibilities.
16. Demonstration result: Record the test population, expected amounts, outputs received, differences and the person accepting or rejecting the result.
17. Remaining conditions: Name each unresolved requirement, its owner and the evidence needed before purchase or before the first live run.
18. Final selection: Record the accepted arrangement, quote date, implementation owner, first-payday review and later filing-confirmation dates.
Keep the completed sheet with the service agreement. It records why the arrangement fits this farm; it is not a determination of tax liability, worker status or lawful wage rates.
Prepare the conversion before the harvest run
Choose a start date that leaves time to resolve setup questions before the first live payroll. Collect the old provider's employee-level wages, tax bases, withholding, deductions, deposit history and filed returns. Reconcile that history by the approved reporting population, rather than importing only cumulative gross pay.
Decide who owns the period spanning the transition. Record the last wages paid through the old arrangement, the first wages through the new one, the return preparer for each required filing and how year-end statements will incorporate the full history. A midyear switch can leave a provider calculating current wages while another party prepares an annual return; that split needs an explicit reconciliation and delivery date.
If previous wages, worker treatment or filings are uncertain, disclose that before implementation and obtain a separately scoped resolution. Starting a new account does not repair the old records. Ask whether the candidate accepts catch-up work, what it needs, what it costs and whether it can support future payroll while a qualified adviser addresses the earlier period.
Review the first live run against the accepted demonstration: actual hours and units, effective rates, approved tax treatment, statements, payment destination and the planned accounting output. Follow the later deposit and filing confirmations as separate tasks. IRS guidance on third-party payers explains that responsibility depends on the arrangement, so keep the farm's oversight and access to agency evidence explicit.
After the first unusual week, revisit the scope sheet. A new processing activity, a different labor supplier, a returning worker or a changed job order can reveal a requirement that did not exist at purchase. Update the underlying approved instruction and confirm support before allowing the new case to flow through the old configuration.
The strongest choice is the arrangement that can handle the farm's described populations, preserve the reasons for their treatment and deliver the required records through the whole employment year. Use a provider's clear limitation as useful buying information. Resolve the remaining work before the farm depends on that provider for harvest payday.
Browse the Decision Guides library.
Continue with Payroll Software Comparisons.
Explore Help Choosing Payroll for questions to clarify before a provider search.

About the author
Ben Scott writes and maintains payroll decision guides for founders and operators. His work focuses on execution realities and how decisions hold up under growth, complexity, and controls and documentation pressure. He works hands-on in HR and leave-management roles that intersect with payroll-adjacent workflows such as benefits coordination, cutovers, and compliance-driven process controls.




