Why Gusto can't run Nigerian payroll — and what can in 2026

Three or four times a quarter, an African founder messages us with a variant of the same question: "We loved Gusto when we were in YC. Now we're scaling our Lagos / Nairobi / Cape Town team — can we just keep using Gusto?" The honest answer is no, and not because of pricing or product fit. Gusto is structurally a US-only payroll engine. It cannot file PAYE to the Nigeria Revenue Service, cannot remit to SSNIT in Ghana, cannot register your staff with Kenya's Social Health Authority, and cannot even let you sign up unless you already have at least one US employee on payroll.

This guide walks through the structural reason Gusto stops at the US border, what the "Gusto Global" announcements do and don't change, what the "use Gusto for Nigerian payroll" workarounds actually break, and what to use instead for compliant African SME payroll in 2026.

What Gusto is, and why founders ask

Gusto is one of the most loved US payroll products. Its 2024–2026 reviews on G2, TrustRadius, and Capterra consistently rate it highest in user satisfaction for SMB payroll. The product is excellent: clean onboarding, automated tax filing across all 50 US states, Form W-2 / 1099 generation, benefits administration, and a self-service experience that staff actually use.

For US-based startups, especially YC-incubated ones, Gusto is often the first system the founders touch — running their own founder payroll on it, then adding their first US engineers. By the time the company starts hiring across Africa, Gusto is muscle memory. Hence the question.

The structural reason it stops at the US border

Gusto is a US payroll platform built for US companies. The signup flow itself blocks non-US employers: "You need to fully onboard to Gusto and run payroll for at least one US employee before you can add non-US employees." This isn't a configuration to flip on — it's a precondition baked into the product. If you don't have a US entity, a US employer ID number (EIN), and at least one US W-2 employee, you cannot create a Gusto payroll account at all.

Even if you do have a US parent and you just want to add African staff, the supported set is narrow.

Gusto Global / EOR — 12 countries, no Africa

Gusto's international answer is Gusto Global, an embedded employer-of-record service powered by Remote. The 2024 partnership announcement on Remote's blog makes the structure explicit: Remote operates the local entity in each country, Gusto provides the front-end experience, and the US parent pays Gusto, who pays Remote.

Per the 2026 Gusto EOR review on Employ Borderless, the supported list is exactly 12 countries: "Canada, United Kingdom, Germany, Ireland, Netherlands, Portugal, Spain, India and the Philippines, Brazil and Mexico." No African country is on the list. None.

That isn't a bug or a partial roll-out. The supported countries match Remote's most established markets, and Africa is not where Remote has prioritised local-entity coverage at the scale Gusto needs to launch into.

Contractor payments — the loophole that isn't

There is a narrower path: Gusto can pay contractors in over 120 countries, routing through Wise. Some founders read this and think: "Great, I'll just classify my Nigerian engineers as contractors and pay them through Gusto." That is the workaround that breaks compliance, and it breaks it in three different places at once.

1. Misclassification. A staff member who shows up at fixed hours, takes direction from a manager, uses company equipment, and has been working with the company for more than 6 months is, in Nigerian or Kenyan law, an employee — not a contractor — regardless of what the contract says. The Nigerian Labour Act, Kenya's Employment Act 2007, and South Africa's Basic Conditions of Employment Act all use substance-over-form tests. Calling someone a contractor when they're functionally an employee creates back-pay liability for PAYE, pension, NSITF, ITF, and statutory leave from day one of the engagement.

2. PAYE non-remittance. Even if you genuinely treat them as contractors, Withholding Tax under the Nigeria Tax Act 2025 Second Schedule still applies on professional-services payments. WHT-on-vendor-payments is your obligation as the payer — not the contractor's — and Gusto has no mechanism to deduct it before payment, file the WHT return with NRS, or generate the WHT receipts your contractor needs to claim against their own personal income tax.

3. No statutory contributions. Gusto cannot remit pension, cannot file NSITF, cannot file ITF, cannot register your contractor with FMBN for NHF (whether opt-in or opted out under NTA 2025), cannot register with NHIA. These are obligations that follow the worker if substance later proves they were actually an employee.

The "use Gusto for Nigerian payroll" path looks like simplicity. It is, in practice, a back-pay timer running in the background.

"We hired through an Employer of Record — Gusto plus Deel / Remote / Oyster"

This is a different conversation. EOR routing can be entirely compliant, because the EOR is the legal employer in the local jurisdiction, files its own PAYE under its own TIN, and the worker shows up on the EOR's books, not yours. What you're paying for is exactly that: the EOR is taking the compliance load.

Two things to understand if you're going this route alongside Gusto:

Cost is the headline. EOR margins typically land at $599–$1,000+ per employee per month on top of the gross salary. For a Lagos engineer on ₦1,200,000 monthly, the EOR markup may add another ₦450,000–₦750,000/mo to the total cost. Sustainable for 1–3 strategic hires; not sustainable for a 30-person office.
The worker is not your employee. The EOR has the employment relationship. That has implications for IP assignment, non-compete enforcement, and severance — none of which are showstoppers, but all of which deserve a 30-minute conversation with employment counsel before you scale past three heads.

For an African SME running its own operating company under its own TIN, EOR is rarely the right primitive. You want a payroll system that runs PAYE and statutory remittances under your TIN, in your currency, with your country's calendar. That's a fundamentally different product category from Gusto, and the African market has its own answer.

What Gusto is very good at, kept honest

It would be unfair to spend a whole guide on Gusto's geography without acknowledging what it does superbly inside the US:

Automatic federal + state tax filing across all 50 states.
Benefits administration — health, dental, 401(k), commuter — integrated into payroll deductions.
Contractor-only plan at low cost for US 1099 contractors.
Same-day or next-day direct deposit for hourly staff.
The cleanest payroll UX in the SMB segment, which is why founders ask the question that started this guide.

If you have any US payroll exposure — a US parent, a Delaware C-corp, a US co-founder still on US payroll — Gusto is one of the best ways to run that piece. It's just the wrong tool to ask to step outside the US border.

The Pan-African alternatives in 2026

Five names cover the realistic field for an African SME doing its own employment.

AnooreHR

Profile-pack-driven HR + payroll for African SMEs. Five live country packs (Nigeria, Ghana, Kenya, Rwanda, South Africa), with Egypt and Morocco queued. Date-routed Nigerian tax acts (Finance Act 2020 → NTA 2025 transition handled automatically), self-service for NHF opt-out and Rent Relief declaration, integrated double-entry accounting. Local-currency pricing from ₦0/month for ≤3 staff.

PaidHR

Nigeria-first, single-jurisdiction depth. The 2025 PaidHR buyer's guide is a useful read of the local segment. Best for SMEs entirely inside Nigeria with no plans to expand regionally.

Workpay

Kenyan-headquartered, multi-country footprint. TechCrunch reported in August 2024 that Workpay raised $5M from Visa and others, serving over 1,000 customers across 20 African countries. Strongest credentials for East and West African operations in the same instance.

SeamlessHR

Enterprise-grade, professional services rollout. Their 2026 East Africa overview frames the regional landscape. Best for 50–500 staff on a managed implementation.

PaySpace

South-African-anchored, deep SADC coverage. The 2024 ClickUp HR South Africa roundup ranks PaySpace among the most credible SA-rooted options. Strong if your headquarters is in Johannesburg, Cape Town, or Windhoek.

Decision tree — which one to pick

If your operating entity is American and you're hiring 1–10 African staff → Stay on Gusto + EOR (Remote/Deel/Oyster).

If your operating entity is Nigerian, single country, ≤30 staff → PaidHR or AnooreHR.

If your operating entity is Kenyan, single country, ≤30 staff → Workpay or AnooreHR.

If you have employees across two or more African countries on your own TINs → AnooreHR or Workpay.

If you have 50+ staff and want a managed rollout → SeamlessHR (NG) or PaySpace (ZA).

The cleanest test is this: who is the legal employer of your African staff? If it's your African operating company, you need an Africa-native payroll engine. If it's an EOR partner, you can stay on Gusto for the US parent and let the EOR run the African seats.

Frequently dismissed workarounds

We hear all of these. None of them survive a compliance review.

"We'll just pay everyone through Wise / Payoneer / a USD bank transfer." That's a payment rail, not a payroll system. PAYE, pension, and statutory levies are still owed; the absence of payslips doesn't make the obligation go away.
"We'll have one person on Gusto in Delaware and pay everyone else through them as freelancers." That's the same misclassification trap, with the added enjoyment of a US 1099 reconciliation that doesn't match Nigerian / Kenyan tax records when audit time comes.
"Our accountant runs payroll in a spreadsheet and Gusto handles the US parent." Workable if and only if the spreadsheet runs PAYE, pension, and statutory levies correctly under the current Acts (NTA 2025 in Nigeria, the Affordable Housing Levy and SHA in Kenya, three-tier pension in Ghana, UIF/SDL in South Africa). For more than five staff, the spreadsheet becomes its own full-time job.
"Gusto Global will be in Nigeria by 2027." Maybe. But the 2024 Remote partnership and 2025–2026 expansion announcements have prioritised non-African markets. Don't plan a 2026 hiring strategy on a 2027 roadmap rumour.

What a clean cutover from Gusto-curious to Africa-native looks like

If you've been running US Gusto for the parent and patching in African staff somehow, the cleanest path is:

Keep Gusto for the US side. Don't touch what's working.
Spin up the Africa-native tool for the operating entity. Single country to start, then add country profiles as you expand.
Reconcile a parallel month — pick one recent Nigerian or Kenyan payroll, run it through the new system alongside the old (spreadsheet, accountant, EOR), and confirm the numbers match to the cent.
Cutover at a clean tax-act or fiscal-year boundary. January 2026 in Nigeria (NTA 2025 effective date) is an unusually clean window — any year-to-date figures land into the new Act framework cleanly.
Set up bidirectional reconciliation between US Gusto and your Africa-native tool for any cross-border allocations (cost-share, intercompany payroll allocations, founder time on both sides).

This is two systems, by design — but each one runs on the right tax engine for its jurisdiction, and the dual-stack scales without hidden compliance debt.

Does AnooreHR handle this?

Yes — AnooreHR is exactly the African-side primitive Gusto leaves unfilled. We run Nigerian PAYE under NTA 2025, Kenyan PAYE + SHA, Ghanaian PAYE + three-tier SSNIT, Rwandan RSSB, and South African UIF + SDL natively — under your TIN, in your local currency, with your country's deadline calendar. If you're a US-incorporated startup with growing African staff, you can keep Gusto for the US parent and add AnooreHR for the African operating company; the two co-exist cleanly.

If you're trying to figure out the right structure for your specific situation — US parent + African team, African parent only, or multi-country African operations — book a quick demo. We'll talk through the trade-offs honestly. Sometimes the answer is "stay on Gusto + EOR for now" — we'll tell you that if it's true.