How to Pay Contractors in 2026: What to Get Right Before You Pick a Payment Method

Key takeaways

• Classification comes first. Calling an employee a 1099 contractor is the expensive mistake here, not whichever transfer method you end up using.
• Before any money moves, three things need to exist: a signed contractor agreement or statement of work (SOW), a W-9 for US contractors (W-8BEN for everyone else), and an invoice or an approved timesheet.
• The 1099-NEC/1099-MISC reporting threshold for 2026 payments jumps from $600 to $2,000 per payee, per IRS instructions for Forms 1099-MISC and 1099-NEC implementing the One Big Beautiful Bill Act — fewer contractors will trigger a form, but income under $2,000 is still taxable to them.
• Picking ACH, wire, a payment app, or a contractor operations platform is a mechanical decision. It comes after documentation and tax setup are settled, not before.
• Paying contractors outside the US adds currency conversion, withholding treaties, and cross-border delays. It's a real problem, just a separate one from what's covered here in depth.

Who counts as a contractor, and why the answer changes everything

An independent contractor controls how and when the work gets done, uses their own tools, and isn't exclusive to one client. A W-2 employee doesn't. Get this wrong and no payment method fixes it afterward: misclassifying an employee as a 1099 contractor exposes you to back taxes, penalties, and benefits claims, regardless of whether you paid by wire or PayPal.

The test the IRS and most state agencies apply looks at behavioral control (do you dictate hours, method, and tools), financial control (who bears the risk of profit or loss, who supplies the equipment), and the type of relationship (is the work project-based or open-ended, is it core to what your business does). A contractor who logs fixed hours on your schedule, works on your laptop, and reports to a manager the same way an employee does looks like an employee on paper, whatever the contract calls them.

That test is currently in flux. The US Department of Labor put out a proposed rule in February 2026 to rescind the 2024 independent-contractor rule under the Fair Labor Standards Act and replace it with a narrower economic reality test built on two core factors: how much control the worker has over the work, and their opportunity for profit or loss based on their own initiative or investment. Three secondary factors — skill required, permanence of the relationship, and how integrated the work is into your business — still apply, but carry less weight than they did under the 2024 rule.

This matters for planning ahead, not for tomorrow's payment. It's a proposed rule, not a final one: the public comment period closed April 28, 2026, and the 2024 rule stays in effect until the DOL finalizes whatever replaces it. Don't restructure your contractor agreements around a rule that could still change before it takes effect. Keep applying the classification test you already use — control, tools, exclusivity — and revisit it once a final rule actually publishes.

The paperwork that has to exist before the first payment

Three documents need to exist before you send a single payment: a signed contractor agreement, a W-9 or W-8BEN, and an invoice or an approved statement of work. Skip any of them and you're trading a small compliance problem now for a bigger one at tax time, or at an audit.

A contractor agreement, not just a verbal deal

A Slack message saying "yes, go ahead" is not a contract. A contractor agreement, or a statement of work if you're structuring the engagement project-by-project, needs to spell out scope, deliverables, rate, payment schedule, and who owns the IP once the work is delivered. On distributed dev teams specifically, skipping this step is how you end up renegotiating scope three weeks in: the contractor built what the ticket described, the ticket didn't match what you actually needed, and now you're arguing over whether the extra work is billable. A one-page agreement signed before the first commit avoids that argument entirely.

W-9 for US contractors, W-8BEN for everyone else

A Form W-9 gives you a contractor's taxpayer identification number so you can prepare their 1099 at year-end. A Form W-8BEN does something different: it establishes that a non-US contractor is a foreign person, which determines whether US withholding applies to what you pay them.

Collect the form before the first payment, not before the first 1099. Waiting until January to chase down a contractor's TIN is how you end up filing late, or triggering backup withholding on future payments if the TIN turns out to be wrong. Make W-9 or W-8BEN collection part of onboarding, the same step as the signed agreement, not a separate task someone remembers in Q4.

An invoice or an approved statement of work

Every payment needs a record of what was delivered, for how much, and that someone on your side approved it. A compliant invoice includes the contractor's name and TIN reference, an invoice number, the billing period or deliverable it covers, the rate, and the total due. An approved timesheet against a pre-agreed rate does the same job for hourly work.

"Slack approval" doesn't hold up as that record. A thumbs-up on a message doesn't show what was actually agreed, and it's not something you can hand an auditor two years later. Whatever you use to pay a contractor, make sure it also stores the invoice or the approval, not just the transaction itself.

1099 filing in 2026: the threshold just changed

Form 1099-NEC is what a business files to report nonemployee compensation: payments made to a contractor for services, as distinct from W-2 wages paid to an employee. Whoever pays the contractor issues it, one per payee, once total payments for the year cross the reporting threshold.

That threshold moved. For payments made in 2026 and filed in early 2027, the 1099-NEC (and 1099-MISC) reporting threshold rises from $600 to $2,000 per payee, per the IRS's instructions for Forms 1099-MISC and 1099-NEC, which implement the One Big Beautiful Bill Act. Starting with the 2027 tax year, the $2,000 figure itself adjusts for inflation, so it will likely tick up a little each year instead of staying fixed at $2,000 indefinitely.

Crossing below that threshold doesn't mean the payment goes untaxed. A contractor still owes income tax on whatever you paid them, form or no form — the 1099-NEC is a paper trail for the IRS, not what creates the tax liability. Pay a contractor $1,200 for a small project in 2026 and you won't be required to file a 1099-NEC for it, but they still have to report that $1,200 on their own return. Fewer forms going out this year doesn't mean fewer contractors owe less tax.

The other IRS mechanism worth knowing here is backup withholding. If a contractor's W-9 has a missing or incorrect taxpayer ID number, the IRS requires you to withhold 24% of what you pay them and remit it to the IRS instead of the contractor — one of the more common triggers for backup withholding, and one entirely within your control. It's a real reason to verify the W-9 before the first payment goes out, not after: fixing a bad TIN once you've already sent three payments means chasing down money that's already gone to the IRS, not to your contractor.

One more threshold changed alongside 1099-NEC's, and it matters if you pay contractors through an app rather than a bank transfer. The 1099-K, issued by payment networks like PayPal, Venmo, and Cash App for Business rather than by you, reverts to its pre-2021 threshold: $20,000 in gross payments and more than 200 transactions to a single payee in a year. Below that, the app doesn't file a 1099-K for that contractor. It's a separate form issued by a separate party, and clearing one threshold doesn't excuse the other: a contractor paid $1,500 through Venmo this year needs neither form, but a contractor paid $2,500 by direct bank transfer still needs a 1099-NEC from you.

Payment methods for contractors, and where each one actually fits

Once documentation and tax setup are settled, the payment method itself is a much smaller decision than most guides make it sound. Five options cover nearly every situation: bank transfer, wire, a payment app, a paper check, or a contractor operations platform that bundles the transfer with everything around it.

Bank transfer and ACH cover most recurring domestic pay

For a US-based contractor you pay on a recurring schedule, ACH is the default for good reason. It's cheap, often a flat fee under a dollar per transaction and sometimes free depending on your bank, and it settles in one to three business days. The tradeoff is speed: ACH isn't built for "I need this contractor paid in the next hour." For anything on a predictable cadence, though, it's the cheapest rail available and the one most accounting software already expects.

A wire transfer costs more, but sometimes that's the point

Wires cost more, commonly $15 to $35 per domestic transfer depending on the bank, and that fee is the whole reason to reserve them for situations where ACH's one-to-three-day settlement isn't fast enough. A contractor finishing a rushed project who needs same-day payment, or a one-time payment large enough that you want same-day confirmation it landed, are both good reasons to pay the wire fee. Using wires for routine recurring payments is paying a premium for speed you don't need.

Payment apps: convenient, but mind the 1099-K math

Contractors often prefer these because the money is usable immediately and there's no bank account number to exchange. The cost is a per-transaction fee, typically 2-3% on the business side, plus the 1099-K exposure covered above: pay one contractor more than $20,000 and over 200 transactions through the same app in a year, and the app issues them a 1099-K on top of whatever 1099-NEC you send. Neither form replaces the other. If you're routing a contractor's pay through Venmo or PayPal alongside direct transfers, keep a running tally of both — the two totals need to reconcile at year-end, not get discovered as a mismatch after the fact.

Paper checks still work, but rarely earn their keep

Nothing in tax law requires you to modernize how you pay a contractor. A check is legal, and for a genuinely rare one-off payment it works fine. What it costs you is time and a weaker paper trail: mailing delays, a contractor cashing it whenever they get around to it, and a canceled check as your only proof of payment instead of a timestamped transfer record. For anything you'll repeat with the same contractor, that friction stops being worth it fast.

Contractor operations platforms bundle everything the four options don't

The four methods above are all just transfer rails: they move money and nothing else. A contractor operations platform is a different category. It bundles the agreement, the W-9/W-8BEN collection, the documentation trail, and the payout itself into one workflow, so a payment isn't a standalone event you have to manually tie back to a contract and an invoice afterward.

That bundling starts to matter once you're paying enough contractors, or paying the same ones often enough, that reconstructing what was agreed, what was delivered, and what was paid from three separate systems becomes its own part-time job. Whether the switch from a plain ACH setup is worth it depends on how many contractors you manage and how audit-ready your records need to be — a question worth working through deliberately, on its own criteria, rather than deciding by whichever tool shows up first in a search.

Paying contractors outside the US is a different problem

Everything above assumes a US-based contractor getting paid in US dollars. Cross the border and the mechanics change. You're converting currency, and eating whatever spread your bank or platform builds into the rate. You're checking a tax treaty to see whether you're required to withhold anything at the source, and that answer varies by country. Wire transfers routed through SWIFT correspondent banks can add days that a domestic ACH transfer never does. Documentation shifts too: a W-8BEN replaces the W-9, but that's the easy part, since some countries expect additional local forms or registrations before a payment counts as compliant on the contractor's end, not just yours, and the contractor's own tax obligation at home doesn't disappear just because the US paperwork is in order. None of that gets a full treatment here. Instead, the mechanics of contracts, tax forms, invoicing, and payment tools for cross-border contractors are covered in How to pay international contractors in 2026.

What to weigh when choosing a payment tool for contractors you pay repeatedly

Four things decide whether a payment tool works for contractors you pay on an ongoing basis, and API depth isn't one of them. A clean API doesn't tell you whether a payment actually lands on schedule, or whether the paperwork behind it survives an audit two years later.

• Contractor-operations depth: does the tool handle agreements, classification support, and the onboarding workflow, or does it just move money from your account to theirs?
• Documentation/compliance readiness: can you pull an audit-ready record of what was agreed, delivered, and paid, without reconstructing it from three separate systems?
• Payout reliability: does the tool have a track record, or a published number, for the payment actually arriving in the currencies and countries you need?
• Pricing transparency: is the cost one clear number, or a base plan plus add-ons plus per-transaction fees you have to total up yourself?

Six tools come up often enough in this context to be worth comparing directly, from bare payroll add-ons to a dedicated contractor operations platform:

Tool	Primary use case	Documentation/compliance depth	Payout reliability signal	Pricing model	Best-fit scenario	One honest limitation
4dev.com	Contractor operations for teams paying contractors on an ongoing, often multi-country basis	Audit-ready, exportable documentation bundled with the payout, across 150+ countries	No published on-time-delivery percentage; the pitch rests on the operations model, not a disclosed rail-speed stat	Service fee of 3% or less per payout, no subscription, no hidden charges, 0% on the contractor's side	A team with recurring contractor relationships that needs agreements, compliance, and payout handled as one workflow	Not the simplest choice for a single, one-off, US-domestic payment — a bare ACH transfer or QuickBooks is cheaper for that narrow case
QuickBooks Contractor Payments	US-domestic contractor payroll add-on for businesses already on QuickBooks	W-9 collection plus automatic 1099-NEC/MISC e-filing; no broader compliance layer beyond that	Next-day direct deposit through contractor self-service	$15/month for up to 20 contractors, $2/month per additional contractor	A small US business already on QuickBooks paying only domestic contractors	US-domestic only, with no support for cross-border contractors or non-QuickBooks workflows
Square Payroll for contractors	Simple per-contractor payroll for businesses that don't need employee payroll	Automatic 1099-NEC generation and e-filing; no agreement or classification tooling	Contractor self-service direct deposit; no published delivery-time figure	$6/month per contractor paid, no base fee, no contract	A solo operator or small team paying a handful of US contractors who wants the cheapest simple option	Nothing beyond the 1099 itself — no documentation layer, no international payout
Gusto	Contractor-only payroll for businesses with zero W-2 employees	1099-NEC prep/e-filing plus a contractor self-service portal	4-day direct deposit	$35/month base plus $6/month per contractor	A business that pays only contractors, never employees, and wants an onboarding portal	Add a single W-2 employee and you're locked out — the plan only works for contractor-only businesses
Wise Business	Multi-currency payment rail for batch-paying contractors internationally	None bundled: no agreements, no W-9/W-8BEN collection, no documentation trail	70% of transfers arrive in 20 seconds, 95% within 24 hours	One-off setup fee of roughly 50 EUR, then per-transfer fees at the mid-market rate with no markup	A team that already has contracts and tax forms sorted and just needs fast, low-cost international transfers	It's a transfer rail, not a compliance system — you still need something else for agreements and audit-ready records
Tipalti	High-volume mass payments across many countries and payment methods	Self-service W-9/W-8 collection, TIN matching, 1099/1042-S prep	Coverage across 200+ countries/territories and 50+ payment methods; no single published on-time-delivery percentage	Tiered pricing starting at $99/month (AP) or $249/month (Mass Payments), plus transaction fees	A business paying a high volume of payees across many countries, where per-seat pricing pays for itself at scale	The total cost is a subscription plus transaction fees, not one flat rate, so it's harder to predict upfront

None of the six publish every fee on the homepage. Before treating any number in this table as the whole cost, check the pricing page for "starting at," "plus fees," or "contact sales" — that's usually where the rest of the bill is hiding.

Mistakes that don't show up until tax time or an audit

Most contractor-payment mistakes don't cause visible damage on the day you make them. They surface eight months later, when a contractor's return doesn't match your 1099, or two years later, when someone asks for a record you never kept. Five patterns account for most of that delayed damage.

Skipping the signed agreement has a second cost beyond scope disputes. The renegotiation problem is one issue. The audit problem is different: without a dated agreement, there's no document showing how much control you exercised over the work at the point the relationship started. If a classification question comes up a year or two later, you're reconstructing that from memory and old Slack messages instead of pointing to something you signed on day one.

Treating a recurring contractor like an occasional vendor, or the other way around, blurs a distinction an auditor will draw for you if you don't. A contractor who's invoiced you monthly for a year and one you paid once for a single deliverable aren't the same relationship, and paying them through the same loose process hides that difference until it matters. Run a long-term contractor through ad hoc app transfers with no ongoing agreement update, and there's no consistent record of the relationship being treated as anything in particular, which is exactly the kind of gap that makes a borderline case look worse than it is. The reverse mistake costs less but still wastes effort: forcing a genuine one-off payment through a full onboarding workflow built for recurring work.

Picking a tool because it moves money fast, then finding out later it can't produce an audit-ready document trail, is one I've made myself. A wire transfer or a payment app confirms that a payment cleared. It doesn't store what the payment was for, who approved it, or which agreement it satisfies, and that's the exact record you need when someone asks for it two years after the transfer already went through. I picked a tool once specifically for its transfer speed and low fee, and only found out at tax prep that its "transaction history" meant a list of dates and amounts, not anything resembling a document I could hand to an accountant.

Getting locked into a vendor's proprietary record format, with no clean way out, is the mistake that costs the most to discover late. A tool that stores agreements, invoices, and payment history inside its own system is convenient right up until you want to switch tools or an auditor asks for the full record, and the export button hands you a spreadsheet of transaction amounts while the agreements and W-9s stay behind. Before committing a year of contractor records to any single platform, check what a full export actually contains. Some tools hand over everything in a portable format. Others hand over numbers and quietly keep the documents.

Not reconciling 1099-K app payments against 1099-NEC records at year-end turns two separate ledgers into one blind spot. Pay part of a contractor's total by bank transfer and part through a payment app, and those two payment paths get reported through two different forms, filed by two different parties, with nothing reconciling them automatically. Track only the bank-transfer side and you can end up filing a 1099-NEC that understates what the contractor actually earned, or missing that the app-payment total quietly crossed a reporting threshold you weren't watching. The fix isn't complicated: keep one running total per contractor, across every payment method you use, instead of a separate tally for each.

A checklist for your next contractor payment

Run through this before you send money, not after. It takes a few minutes and it's the fastest way to catch the mistakes above before they turn into a mistake.

• [ ] Signed agreement or SOW on file, covering scope, rate, and IP ownership
• [ ] W-9 collected for a US contractor, or W-8BEN for a non-US contractor, with a correct TIN
• [ ] Invoice or an approved timesheet on hand for this specific payment
• [ ] Payment method matches the relationship: ACH or a contractor operations platform for recurring work, a wire only if the fee is worth the speed
• [ ] One running total per contractor for the year, tracked across every payment method used, not per method
• [ ] For any payment-app transfers, checked against the $20,000-and-200-transaction threshold rather than assumed it doesn't apply
• [ ] Classification reconsidered if the relationship has drifted toward more hours, more control, or more use of your equipment than when it started

Nothing here replaces judgment on a genuinely unusual case, but for the ordinary contractor payment, these seven checks catch nearly everything that turns into a problem later.

FAQ

What's the best way to pay a contractor?

There's no single method that's best for every contractor; the right one depends on how often you pay them and how fast the money needs to arrive. Handle the paperwork first: a signed agreement, a W-9 or W-8BEN, and an invoice or an approved timesheet. Once that's settled, ACH covers recurring domestic work at low cost, a wire covers a one-off or urgent payment, and a contractor operations platform covers the case where you want the agreement, documentation, and payout handled as one workflow instead of tracked by hand.

How do I pay independent contractors?

Collect the required paperwork before the first payment goes out: a signed agreement or SOW, a W-9 for a US contractor or W-8BEN for a non-US contractor, and an invoice or an approved timesheet for each payment. Then pick a transfer method: bank transfer or ACH for recurring pay, wire for urgent or one-off payments, a payment app if the contractor prefers it, or a paper check for a relationship that truly won't repeat. Track what you pay each contractor across the year so you know when a 1099-NEC is required.

How are contractors usually paid?

For US-based contractors paid on a recurring basis, bank transfer or ACH is the most common method, mainly because it's the cheapest option for regular payments and settles predictably within a few business days. Wire transfers and payment apps show up more for one-off or time-sensitive payments, where the extra cost buys either same-day settlement or contractor convenience.

How do most contractors accept payments?

Contractors generally prefer direct deposit into their own bank account for anything recurring, since it's predictable and doesn't involve cashing a check or waiting on the mail. For smaller or occasional payments, many are comfortable with a payment app like PayPal or Venmo, since the funds are usable right away, even though that convenience adds a per-transaction fee on the paying business's side.

Do I need a W-9 before I pay a contractor?

Yes, and the timing matters more than the form itself. A W-9 gives you the taxpayer ID number you'll need to prepare a 1099 later, but it should be collected at onboarding, not chased down in January. Waiting until year-end risks a missing or incorrect TIN triggering backup withholding on payments already made, or a scramble to reach a contractor who's moved on.

What happens if I don't send a 1099?

Two separate things happen, and neither cancels the other out. The IRS can penalize a business for failing to file a 1099-NEC that was required, and the contractor still owes tax on the income regardless of whether a form was ever sent. Falling under the reporting threshold just means the form isn't required; it doesn't mean the payment goes untaxed.

How much can I pay a contractor before I have to file a 1099-NEC?

For payments made in 2026, the 1099-NEC reporting threshold is $2,000 per payee, up from $600, under the One Big Beautiful Bill Act. The figure starts adjusting for inflation with the 2027 tax year. Staying under $2,000 means you're not required to file the form, but the contractor still owes tax on what you paid.

Can I pay a contractor through PayPal or Venmo?

Yes, it's legal and common, but check the 1099-K math before assuming it's simpler than a bank transfer. Once a single contractor crosses $20,000 in payments and 200 transactions through the same app in a year, the app issues them a 1099-K, separate from any 1099-NEC you file for other payments to that same contractor. The two totals need to reconcile with each other, not just exist side by side.

How to pay contractors with direct deposit?

Direct deposit runs over ACH: the contractor gives you their bank routing and account number, or connects their account through whatever tool you're using, and the transfer settles within a few business days. It's the standard method for recurring domestic payments because it's cheap and predictable, though it's not built for the same-day urgency a wire handles.

What's the difference between 1099-NEC and 1099-K?

They report different payments, from different filers, at different thresholds. A 1099-NEC is filed by the business paying the contractor directly, once total payments cross $2,000 in a year. A 1099-K is filed by a payment network like PayPal or Venmo, not by the business, once a payee crosses $20,000 and 200 transactions through that network. A contractor paid through both a bank transfer and an app could end up with one form, the other, both, or neither, depending on how much moved through each channel.