Humi Review
Humi is a Canadian all-in-one HR, payroll and benefits platform for SMBs, now owned by Australia's Employment Hero. Real CRA and Quebec compliance, but pricing turned quote-only and the agent story is thin.
Humi is one of the few genuinely Canadian all-in-one platforms for SMBs, pairing HR, full-service payroll, and benefits, and for a finance buyer the compliance is the draw: automated CRA remittances, T4s, ROEs filed to Service Canada within one business day, CPP, EI, and CPP2, multi-province EHT and QHSF reporting, and, via Humi by Employment Hero, full Quebec coverage with RL-1 filed to Revenu Quebec plus QPP, QPIP, and CNESST.
Every pay run posts to Xero or QuickBooks Online as a mapped journal entry or A/P bill, keeping month-end clean. The catch is the January 2025 acquisition by Australia's Employment Hero. English Canada was rebuilt onto the Employment Operating System in September 2025, HR data now lives on AWS servers in Australia and Canada while payroll stays in Canada, Quebec runs on a separate product, modular pricing became quote-only with 10-user minimums and reported increases, and engineering shifted toward the global platform amid reported culture disruption.
The Canadian unit is not yet profitable and is chasing a CA$100M target. Under roughly 200 employees Humi is still a strong, compliance-first choice, especially if you need benefits or Quebec; if you require pricing transparency or an external-agent and payroll-API path, weigh it carefully.
- ✓Multi-state or multi-jurisdiction payroll where compliance is the real exposure
- ✓Mid-market to enterprise (50 to 1,000+) needing benefits, HR, and audit-ready reporting
- ✓CFOs who want one accountable vendor to absorb tax and penalty risk
- !Cost-sensitive teams under ~25 employees with simple single-state payroll, where Gusto is cheaper
- !Buyers who need all-in pricing transparency upfront
- !Software-first teams wanting native real-time API and GL sync as a core workflow
The jobs a controller actually hires Humi for
ROEs filed to Service Canada within one business day
Humi issues Records of Employment through ROE Web, and per its help centre the ROE is filed within one business day after you select Submit. Note two manual points: stat holiday pay and ROE block 15B are not auto-populated and must be completed when they apply. Published (Humi Help Centre).
Full Quebec run: RL-1, QPP, QPIP and CNESST
Through Humi by Employment Hero, the retained Quebec product, Humi generates employee RL-1 slips and files them with Revenu Quebec once you submit (or you self-file), and handles QPP instead of CPP, QPIP, the reduced Quebec EI rate and CNESST. It is positioned as the solution of choice for Quebec. Published (Humi Help Centre).
Every pay run posts to Xero or QuickBooks Online
After each pay run Humi pushes payroll to Xero (or QuickBooks Online) automatically as either a journal entry or an accounts-payable bill, with income types, benefits and deductions mapped to specific ledger accounts to cut manual entry. No native NetSuite or general-ERP path. Published (Humi Help Centre / Xero App Store).
Agents can read HR data but cannot run payroll
There is no official Humi or Employment Hero MCP server. The Partners API (JSON:API, bearer token requested from support) is read-mostly: GET employees, time off and additional incomes, one POST to submit hours, and employee/company webhooks. An external agent can query and monitor, not execute payroll. Published (Humi API docs); MCP absence verified against registries.
Watch the same task in each tool
Forget the 40-row feature grid. Pick a finance workflow and see how ADP, Gusto, and Rippling actually do it, with our verdict on who wins for whom.
Most controls and the deepest audit trail, but the most clicks before money moves.
Fewest steps to approve and run; cleanest for a simple single-state shop.
Most automatable via native API; the workflow can run itself once configured.
Compare on what matters
What it actually costs
Here's what it really costs: published rates where a vendor lists them, aggregated quote data where they don't, plus a path to your own number.
Get your real number
Tell us your setup and we will line up a tailored ADP quote and benchmark it against what similar companies pay.
Free. We benchmark your quote; vendors pay us, never you.
What it actually takes to go live
For an SMB, standing up the all-in-one is manageable, but first payroll still depends on a CRA payroll (RP) account, prior year-to-date wages and deductions for any mid-year switch, ROE and stat pay handling, and benefits or carrier setup. Quebec adds a second remittance agency (Revenu Quebec), RL-1, QPIP and CNESST. The extra 2025 wrinkle is the platform move itself: English-Canada clients were migrated onto Employment Hero eOS, and dual-province or bilingual orgs may run across two products with separate data infrastructure.
No first-party MCP, a read-mostly API, and Australia-first payroll AI leave external agents thin in Canada
On the concrete question the brief asks first: there is no official first-party MCP server for Humi or for Employment Hero. The Humi and Employment Hero MCP entries that surface in registries (Knit, Zapier, mcpbundles at about 10 tools, viasocket) are third-party wrappers built over the public API, not vendor-run servers. Any agent story therefore rests on the Partners API and on Employment Hero's in-product AI.
The Partners API is real but narrow. It follows the JSON:API spec, authenticates with a bearer token you request from Humi support, and is read-mostly: GET endpoints for employees, time off and payroll additional-incomes, a single POST to submit employee time worked, and webhooks on employee and company create/update/terminate/delete events. That is enough to sync HR data and ingest hours, but there is no endpoint to run or approve a pay run, no payroll-run write scope, and no programmatic pull of pay stubs, T4s or RL-1s. An external agent sees HR and time data, not the payroll rails.
Employment Hero's parent-level AI is more advanced but only partly relevant to a Canadian payroll buyer. It markets Hero AI as an employment operating system with agents for recruitment, payroll and HR knowledge, yet the payroll agent is built around Australian modern awards and superannuation compliance (the ATO mandate), which does not map to CRA, Revenu Quebec, EHT or ROE. The clearest capability actually shipped for Canada is a Recruitment Agent powered by Hero AI, launched March 30, 2026, which runs first-round AI video screening with human-in-the-loop approvals. Useful for hiring, not for closing payroll.
Net for an agent-minded controller: Humi is a data source an agent can read and a place hours can be pushed, not a payroll surface an agent can operate. Running payroll, filing slips and moving money remain human tasks inside the product, and the richest AI in the family is recruitment and Australia-first payroll rather than Canadian payroll automation. That earns a 2 of 5.
The demos that matter, none of the noise
Humi, kept current
Humi FAQ
What will Humi actually cost in 2026, and is pricing still transparent?
Not the way it used to be. Legacy Humi published modular pricing in CAD (about a CA$49/mo base plus per-employee module fees, roughly CA$6/ee for HR core and another CA$6/ee for payroll, with Time Off, Performance and Time tracking at CA$3 to CA$5/ee each). Under Employment Hero the Canadian pricing page is quote-only: HR plans carry a 10-user minimum, the Payroll plan a minimum near CA$70/mo, Managed Payroll near CA$500/mo, and Team Chat CA$2/ee/mo. Third parties (Folks, late 2025) report all-in rates around CA$19 to CA$49 per employee per month, materially higher than legacy Humi. Everything is in Canadian dollars. Practically, you will need a written quote and should model it against the old modular rate to see the increase.
Is there a contract, minimums or a setup fee?
Humi historically ran month-to-month with no annual lock, did not charge for terminated employees, and kept former-employee records for free. Under Employment Hero eOS the structure adds minimums: HR plans require at least 10 users, the Payroll plan has a floor near CA$70/mo and Managed Payroll near CA$500/mo, and billing is on the greater of your contracted user count or actual active users each month. Setup or implementation fees are not disclosed on the pricing page, so ask. Group-benefit premiums are separate carrier costs, not part of the platform fee.
How hard is implementation, and what changed with the eOS migration?
For an SMB the all-in-one is manageable in days to a few weeks, but first payroll depends on a CRA payroll (RP) account, prior year-to-date data for any mid-year switch, ROE and stat pay handling, and benefits or carrier setup; Quebec adds Revenu Quebec, RL-1, QPIP and CNESST. The 2025 wrinkle is the platform itself: about nine months after the acquisition, Employment Hero rebuilt the English-Canada product as the Employment Operating System (September 2025), so existing clients absorbed a migration, HR account data now sits on AWS in Australia and Canada while payroll data stays in Canada, and Quebec customers remain on the separate Humi by Employment Hero product. Bilingual or dual-province organizations can end up running across two systems, so map that before onboarding.
Can an AI agent run Humi payroll or push data to our ledger?
Read yes, run no. There is no first-party Humi or Employment Hero MCP server; the MCP listings you will find are third-party wrappers over the public API. The Partners API (JSON:API, bearer token from support) is read-mostly: it can GET employees, time off and additional incomes, POST employee time worked, and send webhooks on employee and company events, but it has no scope to run or approve a pay run or pull T4/RL-1 detail. Employment Hero's Hero AI agents are real, but the payroll agent is tuned to Australian awards and superannuation, not CRA or Revenu Quebec; the clearest Canada-shipped AI is a March 2026 Recruitment Agent. On the ledger side the platform itself, not an external agent, posts each pay run to Xero or QuickBooks Online as a mapped journal entry or A/P bill.
Humi alternatives
See how Humi's real Canadian and Quebec payroll compliance weighs against a post-acquisition move to quote-only pricing and a thin external-agent story.
Humi Review
Humi is a Canadian all-in-one HR, payroll and benefits platform for SMBs, now owned by Australia's Employment Hero. Real CRA and Quebec compliance, but pricing turned quote-only and the agent story is thin.
Independently scored across six dimensions. Every dimension is sourced, and we say whether a claim is published, reported, or estimated.
Strong for Canadian SMBs: automated CRA remittances, T4, ROE filed within one business day, CPP/EI/CPP2, multi-province EHT and QHSF reporting, and full Quebec coverage (RL-1 filed to Revenu Quebec, QPP, QPIP, CNESST) via Humi by Employment Hero. Docked because stat holiday pay and ROE block 15B are not auto-populated, managed EHT remittance sits on the Managed Payroll tier, and it is Canada-only with weaker fit for heavily unionized workforces.
All-in-one setup is reasonable for an SMB, but going live still needs a CRA payroll account, prior year-to-date entry on mid-year switches, ROE and stat pay nuances, and benefits or carrier configuration. Existing English-Canada clients also absorbed a platform migration onto eOS, and bilingual or dual-province orgs can straddle two products with separate data infrastructure.
Sweet spot is 11 to 200 employees, workable to about 1,000, weaker for complex or unionized orgs and not built for large enterprise. Employment Hero adds a global backbone and 180+ country EOR via HeroForce as an expansion path, but for most Canadian buyers scale beyond the SMB band means the platform, not just a module, has to stretch.
Humi historically earned praise for responsive, knowledgeable support. Post-acquisition that signal is mixed: engineering and priorities were re-pointed at the global platform, established perks were removed with reported internal culture shock, and third-party alternative round-ups are fielding customers unsettled by the change. Treat legacy support reputation as in transition, not guaranteed.
No first-party MCP server for Humi or Employment Hero. The Partners API is read-mostly (GET employees, time off, additional incomes) with a single write endpoint for hours and event webhooks, so external agents cannot run payroll. Employment Hero markets Hero AI agents, but the payroll AI is tuned to Australian awards and superannuation; the clearest Canada-shipped capability is a March 2026 Recruitment Agent. Third-party MCP wrappers over the API exist but are unofficial.
A clear regression. Humi was known for published modular pricing (a monthly base plus per-employee module fees in CAD). Under Employment Hero the public pricing page is quote-only with 10-user minimums, a Payroll plan minimum near CA$70/mo and Managed Payroll near CA$500/mo, and third parties report all-in rates of roughly CA$19 to CA$49 per employee per month, materially above legacy Humi. Buyers must request a quote.
Written by the Audit Friendly research team. No vendor edits, no sponsored placement.
Humi is one of the few genuinely Canadian all-in-one platforms for SMBs, pairing HR, full-service payroll, and benefits, and for a finance buyer the compliance is the draw: automated CRA remittances, T4s, ROEs filed to Service Canada within one business day, CPP, EI, and CPP2, multi-province EHT and QHSF reporting, and, via Humi by Employment Hero, full Quebec coverage with RL-1 filed to Revenu Quebec plus QPP, QPIP, and CNESST.
Every pay run posts to Xero or QuickBooks Online as a mapped journal entry or A/P bill, keeping month-end clean. The catch is the January 2025 acquisition by Australia's Employment Hero. English Canada was rebuilt onto the Employment Operating System in September 2025, HR data now lives on AWS servers in Australia and Canada while payroll stays in Canada, Quebec runs on a separate product, modular pricing became quote-only with 10-user minimums and reported increases, and engineering shifted toward the global platform amid reported culture disruption.
The Canadian unit is not yet profitable and is chasing a CA$100M target. Under roughly 200 employees Humi is still a strong, compliance-first choice, especially if you need benefits or Quebec; if you require pricing transparency or an external-agent and payroll-API path, weigh it carefully.
- Canadian SMBs (roughly 11 to 200 employees) that want one Canadian-compliant system for HR, payroll and benefits instead of stitched-together tools
- Employers with Quebec staff or French-language needs, since Humi by Employment Hero files RL-1 to Revenu Quebec and handles QPP, QPIP and CNESST as the retained Quebec solution
- Owner-run and people-light teams on QuickBooks Online or Xero that want each pay run posted to the ledger as a mapped journal entry with benefits handled in the same platform
- Finance teams that need published, predictable pricing, since Employment Hero moved Humi from transparent modular rates to quote-only plans with 10-user minimums and reported increases
- Controllers who want to drive payroll from their own AI agent or a payroll API, because there is no first-party MCP server and the Partners API is read-mostly with no payroll-run write scope
- Large, heavily unionized, multi-country or complex-org employers, where Humi thins out above roughly 1,000 staff and international work falls back to Employment Hero's broader platform
The jobs a controller actually hires Humi for
Six jobs, each with the two-minute clip that shows it. Hover a card to preview, click to watch.
ROEs filed to Service Canada within one business day
Humi issues Records of Employment through ROE Web, and per its help centre the ROE is filed within one business day after you select Submit. Note two manual points: stat holiday pay and ROE block 15B are not auto-populated and must be completed when they apply. Published (Humi Help Centre).
Full Quebec run: RL-1, QPP, QPIP and CNESST
Through Humi by Employment Hero, the retained Quebec product, Humi generates employee RL-1 slips and files them with Revenu Quebec once you submit (or you self-file), and handles QPP instead of CPP, QPIP, the reduced Quebec EI rate and CNESST. It is positioned as the solution of choice for Quebec. Published (Humi Help Centre).
Every pay run posts to Xero or QuickBooks Online
After each pay run Humi pushes payroll to Xero (or QuickBooks Online) automatically as either a journal entry or an accounts-payable bill, with income types, benefits and deductions mapped to specific ledger accounts to cut manual entry. No native NetSuite or general-ERP path. Published (Humi Help Centre / Xero App Store).
Agents can read HR data but cannot run payroll
There is no official Humi or Employment Hero MCP server. The Partners API (JSON:API, bearer token requested from support) is read-mostly: GET employees, time off and additional incomes, one POST to submit hours, and employee/company webhooks. An external agent can query and monitor, not execute payroll. Published (Humi API docs); MCP absence verified against registries.
Watch the same task in each tool
Forget the 40-row feature grid. Pick a finance workflow and see how Workiva, BlackLine, and FloQast actually do it, with our verdict on who wins for whom.
Linked numbers, native iXBRL, and EDGAR submission in one document. Most setup up front, least tie-out work at deadline.
Governs the close and the numbers feeding the filing, but has no SEC document or XBRL layer. You still export to a printer or Workiva.
Keeps the Excel workpapers your team already built and layers checklist and review on top. Fastest to stand up, thinnest on filing.
Compare on what matters
What it actually costs
Here's what it really costs: published rates where a vendor lists them, aggregated quote data where they don't, plus a path to your own number.
Legacy Humi modular pricing, third-party reported (Avalon Accounting, Capterra): required HR core. Largely superseded by quote-only eOS plans and may reflect grandfathered accounts. Verify at quote.
Legacy add-on on top of Core: CRA remittances, T4, ROE, direct deposit, multi-province. Under eOS the standalone Payroll plan carries a minimum near CA$70/mo and is quote-only (published minimum, employmenthero.com/en-ca/pricing).
Third-party reported (Avalon): Time Off ~CA$5, Performance ~CA$3, Scheduling/Time tracking ~CA$4 per employee/mo; Recruiting ~CA$99/mo flat. Example 10-employee stack (Core + Payroll + Time Off + Performance) was about CA$249/mo.
Published as custom pricing (employmenthero.com/en-ca/pricing): Standard (onboarding, time off, docs, ATS), Premium (adds performance, expenses, LMS, scheduling), Platinum (adds OKRs, SSO, custom fields, 360s). Billed on the higher of contracted or active users.
Published bundle: HR Platinum plus Payroll, Managed Payroll, HR and employment-law advisory, Benefits+, a learning bundle and Team Chat. The full eOS package.
Published minimum (employmenthero.com/en-ca/pricing): end-to-end processing, year-end reconciliation, managed EHT remittances, CRA T4 filing and benefits audits. This tier is where remittance is handled for you.
What it actually takes to go live
Vetted Workiva partnersFind a partner →
SEC reporting manager or controller as owner, technical accounting for disclosures and tagging decisions, the SOX or internal audit lead for controls solutions, the sustainability controller for ESG scope, light IT involvement for SSO and data connectors, Workiva customer success plus its Professional Services team, and often an advisory partner (the Big 4 and firms like Riveron implement on Workiva; Deloitte has built CSRD compliance solutions on the platform).
Nine months after the acquisition, Employment Hero relaunched the English-Canada product as the Employment Operating System (September 2025). HR account data now sits on AWS servers in both Australia and Canada while payroll data stays in Canada. Confirm data-residency implications and re-test integrations and reports after any migration.
The old published modular pricing is largely gone. Employment Hero's Canadian pricing page lists HR plans at custom pricing with a 10-user minimum, a Payroll plan minimum near CA$70/mo and Managed Payroll near CA$500/mo, and bills on the greater of contracted or active users. Third parties report increases versus legacy Humi, so model the all-in cost before signing.
English Canada gets eOS; Quebec (and French-language) customers stay on Humi by Employment Hero, a distinct product with distinct data infrastructure. A company with offices in both may end up straddling two systems, so map which entity runs where before onboarding to avoid split reporting.
Stat holiday pay and ROE block 15B are not auto-populated and must be entered when they apply, and managed EHT remittance is a Managed Payroll tier feature rather than standard. The self-serve payroll tier reports EHT/QHSF per province but expects you to remit, so confirm which tier actually files what.
Governed AI is strong inside the platform; the external agent surface is real REST APIs plus an MCP gateway that is announced but not yet self serve.
On the concrete question the brief asks first: there is no official first-party MCP server for Humi or for Employment Hero. The Humi and Employment Hero MCP entries that surface in registries (Knit, Zapier, mcpbundles at about 10 tools, viasocket) are third-party wrappers built over the public API, not vendor-run servers. Any agent story therefore rests on the Partners API and on Employment Hero's in-product AI.
The Partners API is real but narrow. It follows the JSON:API spec, authenticates with a bearer token you request from Humi support, and is read-mostly: GET endpoints for employees, time off and payroll additional-incomes, a single POST to submit employee time worked, and webhooks on employee and company create/update/terminate/delete events. That is enough to sync HR data and ingest hours, but there is no endpoint to run or approve a pay run, no payroll-run write scope, and no programmatic pull of pay stubs, T4s or RL-1s. An external agent sees HR and time data, not the payroll rails.
Employment Hero's parent-level AI is more advanced but only partly relevant to a Canadian payroll buyer. It markets Hero AI as an employment operating system with agents for recruitment, payroll and HR knowledge, yet the payroll agent is built around Australian modern awards and superannuation compliance (the ATO mandate), which does not map to CRA, Revenu Quebec, EHT or ROE. The clearest capability actually shipped for Canada is a Recruitment Agent powered by Hero AI, launched March 30, 2026, which runs first-round AI video screening with human-in-the-loop approvals. Useful for hiring, not for closing payroll.
Net for an agent-minded controller: Humi is a data source an agent can read and a place hours can be pushed, not a payroll surface an agent can operate. Running payroll, filing slips and moving money remain human tasks inside the product, and the richest AI in the family is recruitment and Australia-first payroll rather than Canadian payroll automation. That earns a 2 of 5.
Humi, kept current
Employment Hero shipped a Recruitment Agent for Canadian SMBs that runs AI-led first-round video screening, reporting a 75% cut in screening time and up to 10 days off the hiring process, with human-in-the-loop approvals and customizable scoring rubrics. It is the clearest Canada-shipped Hero AI capability to date, notably in recruitment rather than payroll.
BetaKit reported that Employment Hero relaunched Humi as the Employment Operating System for English Canada in September 2025, rebuilding the product with a new LMS, mobile app, and scheduling and recruiting features, with earned wage access planned. It normalized conditions (dropping Humi's 4.5-day work week amid reported culture shock), said the Canadian unit serves 4,000+ of the parent's 350,000 customers, remains unprofitable, and is targeting a CA$100M Canadian business.
Australia's Employment Hero agreed to acquire Toronto-based Humi in its entry into Canada, a deal reported north of CA$100M (later reports range to roughly CA$155M). The stated plan was an all-in-one payroll, HR and benefits platform for Canadian businesses, combining Employment Hero's Employment Operating System with Humi's Canadian market knowledge, with Humi initially to remain Canadian-operated.
Humi FAQ
Not the way it used to be. Legacy Humi published modular pricing in CAD (about a CA$49/mo base plus per-employee module fees, roughly CA$6/ee for HR core and another CA$6/ee for payroll, with Time Off, Performance and Time tracking at CA$3 to CA$5/ee each). Under Employment Hero the Canadian pricing page is quote-only: HR plans carry a 10-user minimum, the Payroll plan a minimum near CA$70/mo, Managed Payroll near CA$500/mo, and Team Chat CA$2/ee/mo. Third parties (Folks, late 2025) report all-in rates around CA$19 to CA$49 per employee per month, materially higher than legacy Humi. Everything is in Canadian dollars. Practically, you will need a written quote and should model it against the old modular rate to see the increase.
Humi historically ran month-to-month with no annual lock, did not charge for terminated employees, and kept former-employee records for free. Under Employment Hero eOS the structure adds minimums: HR plans require at least 10 users, the Payroll plan has a floor near CA$70/mo and Managed Payroll near CA$500/mo, and billing is on the greater of your contracted user count or actual active users each month. Setup or implementation fees are not disclosed on the pricing page, so ask. Group-benefit premiums are separate carrier costs, not part of the platform fee.
For an SMB the all-in-one is manageable in days to a few weeks, but first payroll depends on a CRA payroll (RP) account, prior year-to-date data for any mid-year switch, ROE and stat pay handling, and benefits or carrier setup; Quebec adds Revenu Quebec, RL-1, QPIP and CNESST. The 2025 wrinkle is the platform itself: about nine months after the acquisition, Employment Hero rebuilt the English-Canada product as the Employment Operating System (September 2025), so existing clients absorbed a migration, HR account data now sits on AWS in Australia and Canada while payroll data stays in Canada, and Quebec customers remain on the separate Humi by Employment Hero product. Bilingual or dual-province organizations can end up running across two systems, so map that before onboarding.
Read yes, run no. There is no first-party Humi or Employment Hero MCP server; the MCP listings you will find are third-party wrappers over the public API. The Partners API (JSON:API, bearer token from support) is read-mostly: it can GET employees, time off and additional incomes, POST employee time worked, and send webhooks on employee and company events, but it has no scope to run or approve a pay run or pull T4/RL-1 detail. Employment Hero's Hero AI agents are real, but the payroll agent is tuned to Australian awards and superannuation, not CRA or Revenu Quebec; the clearest Canada-shipped AI is a March 2026 Recruitment Agent. On the ledger side the platform itself, not an external agent, posts each pay run to Xero or QuickBooks Online as a mapped journal entry or A/P bill.
Humi alternatives
Ask us anything
Answered only from our own published research on this tool, never from general internet noise. If we cannot answer it well, our research agents will dig in and publish a sourced answer.
