How to Use Gusto for Payroll for a Small US-Based Agency

The Modern Agency Payroll Stack: Why Gusto Is Only Half the Solution#

Gusto is a strong primary payroll system when your agency mostly runs U.S. payroll. Once you start paying people outside the U.S., it becomes one part of a broader stack, because sending money and carrying compliance responsibility are different jobs.

Keep Gusto as the core for U.S. payroll#

Use Gusto as your core system when your needs stay in four lanes: U.S. payroll, domestic contractor administration, benefits administration, and accounting sync. Gusto states payroll is available in all 50 states, and it positions unlimited payroll runs, automated tax filing, and integrations as core functions.

For a small agency, that gives you a repeatable payroll process instead of manual monthly cleanup. Gusto also supports contractor payments and 1099 workflows, stores employee and contractor documents online, links medical, dental, and vision benefits to payroll, and integrates with QuickBooks, Xero, and FreshBooks. If your team is W-2 employees plus U.S.-based contractors, this setup can keep records centralized and make them easier to audit.

Separate domestic payroll from cross-border compliance#

Before you add any cross-border hiring, separate domestic payroll execution from international compliance work.

Do not treat payment execution as proof of compliance. The IRS states the withholding agent is personally liable for tax required to be withheld, and that liability is separate from the foreign payee's tax liability.

Add a second platform when you cross borders#

Add a second platform when your operating signals move outside domestic payroll. If you are collecting W-8BEN forms, deciding whether a foreign contractor payment should be reported on 1042-S, or hiring someone who needs local payroll, tax, and benefits handling in-country, Gusto should not stand alone.

Use one checkpoint before the first payment: confirm country, worker classification, tax document path, and reporting path. For U.S. contractors, follow your standard domestic documentation and reporting flow. For foreign payees, IRS guidance says Form W-8BEN is submitted when requested by the withholding agent or payer. It also says nonemployee compensation paid to nonresident aliens is reported on Form 1042-S. For exact Form 1042 filing triggers and treaty-documentation rules, confirm the current IRS requirements before finalizing your process.

Keep classification review separate from payroll setup. The DOL announced a new NPRM on February 26, 2026, so classification criteria are still time-sensitive. Gusto also states rules vary by location and over time, so treat software as an execution layer, not as legal or tax advice. If you want a deeper dive, read Value-Based Pricing: A Freelancer's Guide.

The Global Blind Spot: Where the Gusto Playbook Breaks Down#

Once you move outside U.S. payroll, treat it as three separate jobs: payment execution, compliance control, and legal accountability. Gusto can help you pay contractors in 120+ countries, but payment flow is not the same as proving the payee was documented, classified, and reviewed correctly.

Separate payment execution from accountability#

This matters early. If you blur these jobs together, you start treating a successful payment as proof the file was compliant, when it may only mean the transfer went through.

A payment rail moves money and supports onboarding and payment workflows. A compliance control is your pre-payment check, including tax form path, classification path, and local-law review. Legal accountability typically remains with your agency unless you use a structure that changes who employs the worker, such as an EOR for a full-time international hire.

Gusto's global contractor offer has broad reach, but it also states that you still need to manage hiring law, local labor law, and tax requirements.

Checkpoint: before any non-U.S. payout, confirm who owns tax review, who owns local-law review, and which document set supports worker status.

Tighten tax-form handling before money moves#

If you pay foreign contractors, tax-form handling needs to be tighter than simple collection. The starting document for a foreign individual contractor is often Form W-8BEN, and IRS instructions say it should be provided before income is paid or credited.

Collection alone may not be enough. Review for correct form type, completeness, signature, date, and consistency with your payee records. IRS guidance says you may rely on a properly completed W-8BEN. If documentation is missing, presumption rules apply, and a requested but missing W-8BEN can lead to 30% withholding.

Assign ownership for renewals and records. A W-8BEN is generally valid through the last day of the third succeeding calendar year unless circumstances change. IRS instructions also state that the payee must notify the payer within 30 days of a change in circumstances. Requester guidance says W-8 forms are kept in your records, not filed with the IRS.

Do not treat a platform folder, by itself, as proof the file is sufficient. Keep one evidence set: signed W-8 form, contract, invoice trail, foreign-status rationale, and a dated review note for unresolved items.

Screen for PE and classification risk before onboarding#

Review permanent establishment and classification before you create the profile, not after the first invoice arrives. The OECD baseline defines permanent establishment as a fixed place of business through which the business of an enterprise is wholly or partly carried on.

Escalate before approval if facts suggest a potential in-country fixed place of business. Do not guess jurisdiction thresholds. Mark Add current threshold after verification and get jurisdiction-specific review.

Run classification as a separate control. IRS framing uses behavioral control, financial control, and relationship-of-the-parties evidence. DOL guidance focuses on the economic realities of the full relationship. Current DOL materials also show active regulatory movement, including the March 11, 2024 rule effective date, the May 1, 2025 enforcement-guidance update, and the February 26, 2026 NPRM announcement. If the role functions like staff, reassess whether contractor setup is appropriate and whether an EOR path is safer.

Lock minimum controls before first international payout#

Before the first international payment goes out, set a minimum control set and hold to it. Use this checklist before the first international payment:

• Confirm country, worker type, and whether contractor treatment is appropriate or should move to EOR.
• Collect the required tax form before payment, review for completeness, and assign a renewal date.
• Document expected withholding and reporting path, and mark unresolved points as Add current threshold after verification.
• Store contract, invoice trail, tax form, classification note, and reviewer name in one record set.
• Hold payout if there is missing tax documentation, unclear status, or PE-related escalation signals.

Verification point: a non-finance reviewer should be able to read the file and quickly understand why this person was paid, in what capacity, and on what tax-document basis. If they cannot, tighten controls before release.

For a step-by-step walkthrough, see How to Perform a Business Valuation for a Small Agency.

Stage 1: Your Playbook for Hiring Your First Global Contractor#

For your first non-U.S. contractor, treat onboarding as a pre-payment control, not admin cleanup. If classification, tax documentation, invoice quality, or payout ownership is unclear, pause payment.

Define and collect before you pay#

Start by deciding what must be true before money moves. Four definitions should be set before the first payment is queued:

• Contractor classification: not a checkbox. Under IRS framing, assess behavioral control, financial control, and relationship evidence. If that review still leaves uncertainty, escalate and consider Form SS-8.
• Tax-document validation: confirm form-to-payee fit before payment. Form W-9 is for U.S. persons. Foreign beneficial owners generally provide a W-8 series form to the withholding agent before payment.
• Invoice compliance fields: the minimum invoice details needed for legal, tax, and approval review.
• Payment-rail responsibility: who owns fee review, FX review, timing checks, and failed-transfer follow-up.

Build one onboarding file with: signed contract, identity details, country, tax form, classification note, invoice instructions, reviewer name, and review date. Where local rules are not yet verified, use Add current requirement after verification. Keep the record trail under your retention rules.

Verification point: a reviewer should be able to show why the worker is classified as a contractor, which tax form supports payment, and who approved first payout.

Standardize invoice quality#

Invoice quality is one of the easiest places to lose control, so standardize it early. Use one base checklist, then apply country or regional checks before approval.

• UK: include unique invoice number, issue date, supplier and customer details, description, amount, and show both VAT tax point and invoice issue date.
• EU: apply EU-wide VAT invoicing baseline, then check member-state overlays.
• Australia: for tax invoices at $1,000 or more, include buyer identity or ABN.
• Canada: keep invoice evidence because it supports GST/HST recordkeeping.

Choose the payout rail deliberately#

Choose the payout method only after the file is complete. Contractor payments are handled separately from W-2 payroll, and Gusto states coverage across 120+ countries, but you still need clear rail controls.

Compare options on four checks, and prefer rails that surface hard blockers, such as submission blockers, before release:

1. Fee transparency: transfer and FX costs are visible before approval.
2. Settlement predictability: planned debit timing includes the expected_debit_date and realistic clearing expectations. Traditional international transfers may take three to five business days.
3. Exception handling: failed or delayed transfers have a named owner and response path.
4. Pre-send disclosure: transfer amount, exchange rate, and fees are confirmed before authorization.

Ready to pay#

Release the first payment only if all five are true:

1. Classification review is documented, and unresolved points are escalated.
2. The correct W-8 or W-9 is collected and reviewed before payment.
3. The invoice passes your base checklist and country checks, with open items marked Add current requirement after verification.
4. Fees, FX handling, debit timing, and exception ownership are confirmed.
5. A reviewer can open the file and explain the payment decision quickly.

Before sending a first cross-border contractor payment, collect the required tax form and check it against your onboarding controls with the W-8 Form Generator. Related: What to Do If You've Been Misclassified as an Independent Contractor.

Stage 2: How to Scale Your Global Team Without Scaling Your Anxiety#

After your first clean contractor file, scale with controls, not reminders. If you use Gusto for U.S. hires, keep global contractor operations in the same controlled model so records, approvals, and exceptions stay auditable as headcount grows.

Build one record spine#

As volume grows, file quality matters more than software branding. Keep one primary record set for every person you pay: signed contract, current tax document, payout approval trail, and audit-ready change history. A reviewer should be able to see who changed payout details, who approved first payment, who approved later changes, and when each action happened.

Gusto positions Gusto Global as a unified platform for international workers, and Gusto payroll states forms are stored and organized online. Whether you use that stack or another one, lock in a minimum record set before you scale:

• Contract and country
• Form W-8BEN (when requested by the payer or withholding agent), or other required form, signed and dated
• Payout method, currency, and approval owner
• Invoice approvals and exception notes
• Access history for finance, ops, and system permissions

Use role-based access control and least privilege. The person collecting payout details should not be the same person who can both release funds and grant admin access.

Verification point: open any contractor file and confirm quickly which tax form supports payment, whether it is current, and who approved the latest payout change.

Assign owners before you automate#

Automation only helps when ownership is clear. Scaling breaks when decisions are shared but nobody clearly owns them, so assign named roles to three approvals:

1. Legal or tax owner: approves contract fit, classification notes, and tax-document completeness. IRS common-law analysis still applies for federal tax classification, and the DOL final rule effective March 11, 2024 is part of the current U.S. backdrop.
2. Finance owner: approves payout setup, first-payment release, fee review, and exception handling.
3. IT or ops owner: provisions access after approvals and removes access at offboarding.

One risk pattern is one manager collecting W-8BEN, approving payout-detail changes, and granting system access. Keep the evidence pack simple and complete: timestamps, approver name, payout-detail change log, and access request or ticket ID.

Choose payout rails with a margin-first framework#

Payout choice affects margin, so do not choose a rail by habit. Compare options on fee transparency, FX exposure, settlement reliability, and margin impact before approval.

If you bill in USD and pay in local currency, review landed cost before large or long-running scopes. The World Bank's 6.49 percent global remittance send-cost average is not a direct agency benchmark, but it is a useful reminder not to assume transfer costs are negligible.

Run a recurring review with clear escalation#

Recurring review keeps a clean setup from drifting. Set an internal compliance-review cadence, document it, and follow it. Your dashboard should track expiring tax documents, failed or delayed payments, unresolved classification notes, and access-review items.

For Form W-8BEN, two timing rules matter. Validity generally runs through the last day of the third succeeding calendar year, and changes in circumstances must be reported within 30 days. Define escalation before issues happen: ops flags, finance pauses payment, and legal or tax clears the file before release. For repeated payment exceptions or classification concerns, use Add current threshold after verification instead of inventing a hard number.

You might also find this useful: How to Manage and Pay a Global Team of Contractors Compliantly.

Stage 3: The Modern Agency Stack - Integrating Gusto for US Hires#

Once you add a U.S. employee, use a dual-system model. U.S. employee payroll is the employer duty to withhold, deposit, report, and pay employment taxes. Global contractor compliance is a separate workflow for worker-status review, cross-border contracting, tax-document collection, and non-U.S. payee withholding or reporting decisions. Keep those lanes separate so each risk is handled in the right system.

If you use Gusto for U.S. payroll, treat it as your U.S. payroll engine, not a universal compliance layer. Keep global contractor and cross-border hiring records in your contractor or global platform, and remember worker status is based on the substance of the relationship, not the label.

Define system ownership and limits#

Use Gusto as the source of truth for U.S. employee payroll records: Form W-4 data, payroll runs, and payroll outputs that sync to your ledger. Gusto states payroll coverage across all 50 states. What this lane does not settle is worker-classification judgment or foreign-payee documentation risk.

Use your contractor or global platform as the source of truth for cross-border files: non-U.S. contractor contracts, tax forms, payout approvals, and withholding or reporting review where required. For non-U.S. contractors, Form W-8BEN is central. For full-time hires outside the U.S. without a local entity, route to an EOR model.

Route work before onboarding or payment setup#

Routing should be a required first decision, not a later fix. Use the lane below before you onboard anyone or set up payment:

Verification point: sample one active file per lane and confirm the payment-supporting document: I-9 and W-4 for U.S. employees, W-9 for U.S. contractors, W-8BEN for non-U.S. contractors.

Run one operating workflow from hire request to retention#

The operating model should be simple and repeatable: hire request, role classification, documentation checkpoint, approval handoff, payroll or payment run, ledger sync, then record retention. No profile gets activated before required documents and approvals are complete.

Keep one accounting destination even with two worker systems. Gusto states integrations with QuickBooks and Xero. QuickBooks setup includes chart-of-accounts mapping, and payroll totals can auto-post to expenses. In Xero, Gusto pay runs create a bill or manual journal after clearing-account mappings are completed in Gusto. Also note the stated limitation: Gusto integration does not work with Xero Expenses.

Success here is operational, not cosmetic: clean reconciliation, traceable records, and lower risk of classification or payroll errors. Retain the audit trail for routing decisions, approvals, payroll outputs, and ledger sync. Align retention with the applicable rule set, since IRS and DOL minimum periods differ.

For the workflow detail, see How to Use Harvest for Time Tracking and Invoicing in a Small Agency.

Conclusion: Build Your Agency on Confidence, Not Anxiety#

The core decision is often a two-track model: use Gusto for U.S. employee payroll, and run global contractor compliance in a separate contractor or global workflow. Keeping those lanes distinct can reduce payment blockers, keep records cleaner for review, and give you clearer cost visibility across your workforce.

Keep your tool boundaries explicit#

Be explicit about what each tool does and does not do. Treat Gusto as a U.S. payroll service provider, not a full compliance transfer. Gusto states it files payroll taxes when payroll runs and supports state tax registration resources in all 50 states. IRS guidance is still clear that your business owns timely, correct deposits, filings, and tax payment duties.

For cross-border contractor work, do not treat payment reach as compliance coverage. Even if you can pay contractors in 120+ countries, the control point should still be the file behind each payment: classification record, required form, and approval trail.

Use control language, not set-and-forget language#

This work is ongoing operations: routing, documentation, approvals, reconciliation, and retention. Worker classification remains fact-based under common law control and independence criteria, and required forms should be complete before payment.

Before each payroll or contractor run, do a quick pre-submit check: right worker lane, required documents present, approval captured, and payment record ready for retrieval. Keep records for at least 4 years under IRS employment-tax guidance, and preserve payroll records for at least 3 years under 29 CFR 516.5.

Run this operating confidence checklist#

• Confirm each worker is classified before onboarding or payment setup.
• Confirm required forms are on file: I-9 for U.S. employees hired to work in the United States, W-9 for U.S. contractors, and W-8BEN for non-U.S. contractors when requested by the payer or withholding agent.
• Confirm named owners for payroll operations, contractor compliance, and final approval.
• Confirm payroll totals reconcile across payroll records, Forms 941, and W-2/W-3 totals.
• Confirm records and approvals are stored so supporting files are retrievable quickly.

Your next move is practical: document tool boundaries, assign compliance ownership, and run one full payroll-cycle test before scaling headcount. If that test is clean on approvals, reconciliation, and documentation retrieval, you are operating from control, not anxiety.

This pairs well with our guide on HRIS vs Payroll, EOR, and MoR for Small Businesses in 2026. If you want to confirm which setup fits your agency across markets and compliance requirements, talk to Gruv.