# Employment Hero Payroll > Employment Hero Payroll (formerly KeyPay) is cloud payroll for Australia, New Zealand, the United Kingdom, Singapore and Malaysia. Its REST API covers businesses, employees, timesheets, leave, pay runs and reports, with an API key or OAuth 2.0. - Canonical: https://www.anchorterminal.com/tools/employment-hero - Markdown: https://www.anchorterminal.com/tools/employment-hero.md (~7,850 tokens) - Slim: https://www.anchorterminal.com/tools/employment-hero.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/employment-hero.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade D · 50.4/100 · rank #591 of 722 · #6 in Payroll infrastructure · not agent-ready · confidence medium** ## Assessment Five public Swagger 2.0 files describe 660 to 821 operations per region, and any payroll user can generate an API key without a partner review. The key carries its user's whole access, no idempotency keys or API changelog were found, and the only official client is for .NET. ## Facts | Field | Value | | --- | --- | | Vendor | Employment Hero Pty Ltd (https://employmenthero.com) | | Kind | HTTP API | | Category | Payroll infrastructure (https://www.anchorterminal.com/categories/payroll) | | Transport | HTTP | | Auth | OAuth or key · Graded on the Payroll API. A user with a payroll login generates an API key under My Account, with no partner review, and sends it as the HTTP Basic username with a blank password. The key acts with that user's access, and Change API Key invalidates the old one. OAuth 2.0 is the other route. A support request with the application's name, callback URL and logo returns a client ID and secret, and the authorisation code grant at `/oauth/authorise` and `/oauth/token` returns a 24-hour access token and a 28-day refresh token. The spec names `read` and `write` scopes, and the guide's sample token shows an empty scope. | | Pricing | Paid (Paid) · No charge for API calls was found. Access comes with an Employment Hero Payroll subscription. The Australian pricing page lists the Payroll plan at $10 with conditions, a minimum of 10 users and billing by user count, with prices stated as AUD ex. GST in the page's disclaimers. Employment Unlimited, which includes Payroll, is priced through sales. No free tier, trial or sandbox for Payroll was found on the pages read, so an agent starts only where a paying account exists (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the API guides, the five Swagger files or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under Employment Hero's General Terms. The `KeyPayV2` .NET client is MIT | | Packages | nuget: `KeyPayV2` | | Source | https://github.com/Thinkei/keypay-dotnet-v2 | | Docs | https://api.keypay.com.au/ | | llms.txt | not found | | Last release | 2026-10-08 | | GitHub stars | 6 (as of 2026-10-08) | | Surface graded | Employment Hero Payroll API (REST, JSON), formerly KeyPay. Base https://api.yourpayroll.com.au/api/v2. The separate HR API at developer.employmenthero.com is not graded here | | Regions | Australia (728 operations), New Zealand (660), United Kingdom (821), Singapore (695), Malaysia (679), one Swagger 2.0 file each | | Payroll coverage | Businesses, employees, contractors, bank accounts, super funds, pay schedules, pay runs (66 operations in the Australian spec), timesheets, rosters, leave requests, expenses, awards, reports (41), webhooks (7) and employee self-service (111) | | Pay run steps | Create, recalculate, read warnings and totals, start the approval process, finalise, unlock. Finalise options include `lodgePayRun`, `lodgePayRunInTestMode`, `publishPaySlips` and `exportJournals` | | Credentials | API key from My Account, sent as the Basic auth username with a blank password. OAuth 2.0 authorisation code grant at `/oauth/authorise` and `/oauth/token`, 24-hour access tokens, 28-day refresh tokens, and `POST /oauth/token/revoke`. The spec names `read` and `write` scopes | | Access steps | API key is self-serve for any user with a payroll login. OAuth client ID and secret come from a support request | | Rate limits | 5 requests a second per API key per IP address. Our unauthenticated test saw `x-rate-limit-limit`, `x-rate-limit-remaining` and `x-rate-limit-reset` headers, and a 429 with `retry-after: 1`. The docs don't describe these headers | | Pagination and filtering | OData v3 `$skip`, `$top` (100 by default and at most), `$orderby` and `$filter` on most GET operations. `$select` on the Employee API only. `$expand` not supported | | Errors | Some operations document 400, 404 and 409 with a `ProblemDetails` body (`type`, `title`, `status`, `detail`, `instance`). 401 and 429 answered our test as plain text | | Webhooks | Seven operations under `/api/v2/business/{businessId}/webhookregistrations`, with a test call | | SDK | `KeyPayV2` on NuGet for .NET Standard 2.0, MIT, 574 versions, latest 3.0.0.969 on 2 September 2026. Source in Thinkei/keypay-dotnet-v2, generated from the API, last build commit 3.0.0.1025 on 8 October 2026 | | Status | https://status.employmenthero.com with Login, Create Pay Run, Finalise Pay Run and Create Employee components for each of five payroll regions. No component names the Payroll API | | Data locations | Per the DPA of 15 June 2026, APAC data in Australia, United Kingdom payroll data primarily in Ireland, Canadian payroll data primarily in Canada | | Capabilities | payroll.run, payroll.employees, payroll.embedded, payroll.tax-filing, payroll.contractors, hr.time-off | | Tags | hosted, payroll, api-key, oauth, openapi, webhooks, dotnet, white-label, australia, new-zealand, uk, singapore, malaysia, status-page | | JSON | https://www.anchorterminal.com/api/v1/tools/employment-hero.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 65 | 13.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 51 | 8.3 | | Agent ergonomics | 13% | 16.2 | 53 | 8.6 | | Security & auth | 14% | 17.5 | 46 | 8.1 | | Payments & pricing | 10% | 12.5 | 10 | 1.2 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 68 | 6.0 | | Transparency & trust (editorial 49, provenance 71) | 7% | 8.8 | 60 | 5.2 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **50.4 → D** | ### Why each score - Reliability 65: Read with the hosted lines. https://status.employmenthero.com is a Statuspage with Login, Create Pay Run, Finalise Pay Run and Create Employee components for each of five payroll regions and incident history. No component names the Payroll API (20). Between 10 July and 8 October 2026 it lists two payroll incidents. On 21 July pay runs did not load employee data for businesses with a deleted leave category still referenced in a pay run, marked major and resolved in 2 hours 3 minutes. On 2 September employees could not be removed from a pay run, marked no impact, with a fix posted 5 minutes after the notice. One major that touched a subset of businesses sits between the minor and one-major lines (15 of 30). Four further incidents in the window are on HR Software, a separate product. 5 requests a second per API key per IP address (15). The usage guide says only to space calls out. Our unauthenticated test saw a 429 with `retry-after: 1` and `x-rate-limit` headers, which the docs don't describe, and no idempotency keys were found (5 of 15). No SLA found in the General Terms or the docs (0). The API is at v2 with no beta label (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 51: A Swagger 2.0 file for each of five regions, public and without a login, 728 operations and 460 definitions for Australia (25). No llms.txt or Markdown twin on the documentation site. employmenthero.com/llms.txt indexes marketing pages only (0). 713 of 728 Australian operations have a description, most of one sentence, such as noting OData support or that a pay run can't be finalised while calculations run. None say when not to use an operation (8 of 20). Every request body references a named model and 269 of 4,461 properties carry enums, but only 13 of 460 definitions list required fields and dates are plain date-time strings (9 of 15). The guides have curl and HTTP examples for both auth routes and OData. 711 of 728 operations document a 200 response, 131 a 400 and 136 a 404, with a `ProblemDetails` model, and no example bodies (5 of 15). The path carries v2. No API changelog was found, and the .NET client documents one set of breaking changes (4 of 15). - Agent ergonomics 53: `$top` caps lists at 100 and `$select` trims fields on the Employee API only. Summary endpoints exist for pay runs (15 of 25). OData `$skip`, `$top`, `$orderby` and `$filter` on most GET operations (20). Some operations return `ProblemDetails`. 401 and 429 answered our test as plain text, and the docs have no error catalogue (8 of 20). No idempotency keys. Employees and several other resources can be looked up by `externalId`, which lets a caller check before repeating a create. This is an HTTP API with no MCP annotations to read (4 of 20). One official client, for .NET. Creating a pay run needs a pay schedule, a period end and a paid date (6 of 15). - Security & auth 46: An API key generated under My Account, sent as the Basic auth username, and replaced with Change API Key. It carries its user's access. OAuth 2.0 authorisation code grant with 24-hour access tokens, 28-day refresh tokens and a revoke endpoint. The spec names `read` and `write` scopes, while the guide's sample token shows an empty scope (22 of 30). Business access can be Restricted to employee groups and locations, a user can be created as `apiOnly`, and pay runs have an approval start endpoint. Nothing holds a finalise call for confirmation (10 of 20). The API returns notes and other text written by employees and managers, with no guidance on treating it as untrusted (3 of 15). Employee audit and pay run audit reports are in the spec, and responses carry `x-correlation-id`. No per-call log for the operator was found (5 of 15). security.txt is valid until 31 December 2026 and links a Vulnerability Disclosure Policy v1.2. The trust centre is script-drawn and unread, so certifications and any bounty are unconfirmed (6 of 20). - Payments & pricing 10: Read with the hosted rubric. No x402, MPP or L402 (0). The Australian pricing page lists the Payroll plan at $10 with conditions and a minimum of 10 users, and says prices are AUD ex. GST in its plan disclaimers. That is public plan pricing with no per-call charge (10). No free tier or trial for Payroll was found on the pages read. The two-week free trial in the partner guide is for an HR organisation (0). A person signs up and generates the key in the browser (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 68: The .NET client repository, generated from the API, has a build commit on 8 October 2026, and the swagger files were last modified on 28 August 2026 (30). The repository has commits on 52 separate days since 10 July, and NuGet shows 62 package versions published in the same period (20). Closed service with no API changelog. The developer forum's front page shows spam topics and API questions from 2024 and 2025 with no replies (4 of 15). One current official client. NuGet stops at 3.0.0.969 from 2 September while the repository is at build 3.0.0.1025 (10 of 15). The client repository has no CI workflow, and its test folder holds a sample application (4 of 10). - Transparency & trust 60: Closed service. General Terms effective 15 June 2026 name Employment Hero Pty Ltd and cover access through its APIs. The .NET client is MIT (15 of 30). The privacy policy (3 June 2026) and the DPA (15 June 2026) agree on processor and controller roles, say personal data is not used to train AI models, and name storage in Australia, Ireland and Canada. Retention is 'as long as necessary' under an internal policy, with no periods (20 of 30). No deprecation policy or dated notices were found for the Payroll API (2 of 20). The DPA gives data centre locations by region and 30 days to object to a new sub-processor. The sub-processor list sits on a trust centre our reader could not read (12 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (23 items): https://www.anchorterminal.com/fixes/employment-hero.md (JSON https://www.anchorterminal.com/fixes/employment-hero.json) ### What we couldn't check - unchecked: the trust centre at trust.employmenthero.com and its sub-processor page are script-drawn and showed our reader a title only, so certifications, penetration testing, any bounty and the sub-processor list are unconfirmed - unchecked: the body of the Vulnerability Disclosure Policy v1.2 linked from security.txt, a Google document that showed our reader its title only - unchecked: the official MCP registry search answered 500, so presence of any Employment Hero server there is unconfirmed. No MCP server was found on the vendor's pages read - unchecked: open issues and replies on Thinkei/keypay-dotnet-v2, which aren't in a git clone. The GitHub API reports one open issue - Whether Employment Hero Payroll has a free trial or sandbox of its own. None was found on the pricing page or the API docs, and the free trial in the partner guide is for an HR organisation - The unit behind the Payroll plan's $10. The page shows the figure with a 10-user minimum and billing by user count, and states AUD ex. GST in plan disclaimers, but the per-user wording sits in script-drawn tooltips we did not read in full - Whether OAuth tokens can be limited to `read`. The spec names `read` and `write` scopes under an implicit flow, while the guide describes the authorisation code grant and shows an empty scope - Which API host serves each region. The docs name api.yourpayroll.com.au, the client README uses a United Kingdom host, and api.yourpayroll.co.uk, api.yourpayroll.io and api.nzpayroll.co.nz each answered 401 to our test - Whether a customer agreement includes an SLA. None is in the public General Terms - The 429 `retry-after` header and `x-rate-limit` headers were seen on unauthenticated calls and aren't in the docs, so their behaviour for authenticated calls is unconfirmed - The registrant of yourpayroll.com.au and keypay.com.au. RDAP names only the registrar - The star count is for Thinkei/keypay-dotnet-v2. The API has no public repository of its own ### Sources - documentation index and regional spec list: (seen 2026-10-08) - API home guide, base URL and forum link: (seen 2026-10-08) - API key authentication: (seen 2026-10-08) - OAuth 2.0 guide, token lifetimes and credential request: (seen 2026-10-08) - usage limits: (seen 2026-10-08) - OData filtering and paging: (seen 2026-10-08) - single sign-on guide: (seen 2026-10-08) - Swagger 2.0 file, Australia: (seen 2026-10-08) - Swagger 2.0 file, United Kingdom: (seen 2026-10-08) - Swagger 2.0 file, New Zealand: (seen 2026-10-08) - Swagger 2.0 file, Singapore: (seen 2026-10-08) - Swagger 2.0 file, Malaysia: (seen 2026-10-08) - finalise pay run reference: (seen 2026-10-08) - create pay run reference: (seen 2026-10-08) - unauthenticated call to the API (401, 429 and headers): (seen 2026-10-08) - status incidents: (seen 2026-10-08) - status components: (seen 2026-10-08) - pricing page, Australian edition: (seen 2026-10-08) - General Terms, effective 15 June 2026: (seen 2026-10-08) - privacy policy, effective 3 June 2026: (seen 2026-10-08) - Data Processing Addendum, effective 15 June 2026: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - trust centre (title only, script-drawn): (seen 2026-10-08) - .NET client versions on NuGet: (seen 2026-10-08) - .NET client repository, commits and README: (seen 2026-10-08) - developer forum front page: (seen 2026-10-08) - HR API partner guides, trial and separate API: (seen 2026-10-08) - HR API reference, separate rate limits: (seen 2026-10-08) - RDAP for employmenthero.com: (seen 2026-10-08) ## Who's behind it (provenance 71/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Employment Hero Pty Ltd | 20/20 | | Domain age | employmenthero.com, registered 2012-05-02 (14 years) | 15/15 | | Endpoint on the vendor's domain | is not on employmenthero.com | 0/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.employmenthero.com | 10/10 | | Changelog | not found | 0/10 | | security.txt | valid | 10/10 | The General Terms (effective 15 June 2026) name Employment Hero Pty Ltd and its affiliates, and define the EH Platform to include products reached through its APIs. They are the platform terms, and no separate API terms were found. The privacy policy is effective 3 June 2026 and points to a Data Processing Addendum effective 15 June 2026 at https://employmenthero.com/legals/privacy-policy/data-processing/. The API answers at api.yourpayroll.com.au and the documentation at api.keypay.com.au, both off employmenthero.com. RDAP for yourpayroll.com.au names the registrar only, so we could not confirm the registrant. https://employmenthero.com/.well-known/security.txt gives vuln@employmenthero.com, a policy link and an expiry of 31 December 2026. RDAP for employmenthero.com gives a registration date of 2012-05-02 and GoDaddy.com, LLC as registrar. No changelog for the Payroll API was found on the documentation site. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://employmenthero.com/legals/terms-conditions/), read 2026-10-08, gives no date, states 6 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "develop, support or use software, scripts, robots or any other means or processes to scrape or otherwise copy information from the EH Platform in a way that breaches another EH Platform Rule or our EH Platform Terms;" - Not found in the text. Gives the date it was last updated. - Names the governing law or courts. The law of New South Wales, with disputes in the courts of New South Wales, Australia. - Says how changes to the terms are announced. Gives 30 days of notice before a change. - Also in the text (2026-10-08). The customer is solely responsible for the outcome of any action the vendor's AI functions suggest or carry out once the customer approves it or lets it run. "You are solely responsible for the outcomes of any AI Action that you (as an Organisation or as a User) approve, confirm, initiate, or allow to execute." - Also in the text (2026-10-08). Users must not share login credentials with anyone else or let more than one individual use a single user account. "share your login credentials with any other person or allow multiple individuals to access the EH Platform using a single User Account;" - Also in the text (2026-10-08). The liability limit does not apply to liabilities arising from the customer's indemnities or from the customer's breach of the platform rules. "The exclusion of liability under clause 28 does not apply to liabilities arising out of your indemnification obligations in these General Terms or your breach of the EH Platform Rules." **Privacy policy** (https://employmenthero.com/legals/privacy-policy/), read 2026-10-08, gives no date, states 7 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "We may share certain data such as device identifiers and usage data with advertising and analytics partners in ways that may constitute ‘sharing’ under the CCPA for cross-context behavioural advertising." - Not found in the text. Gives the date it was last updated. - Says how long data is kept. For as long as needed, with no period named. - Gives a privacy contact. privacy@employmenthero.com. - Says where data is transferred or stored. Relies on standard contractual clauses. ## Live (updated 2026-10-08 21:57 UTC) - Vendor status page: none, All Systems Operational - Always current: https://www.anchorterminal.com/api/v1/live/employment-hero.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - Public Swagger 2.0 file for each of five regions, 728 operations for Australia and 821 for the United Kingdom, downloadable without a login - A payroll user generates an API key under My Account with no partner review, and Change API Key invalidates the old one - OData `$filter`, `$orderby`, `$top` and `$skip` on most GET operations, with `$top` capped at 100 - Pay run endpoints cover create, recalculate, warnings, approval start, finalise and unlock, so a run can be checked before it is finalised - The .NET client is regenerated from the API, with commits on 52 separate days between 10 July and 8 October 2026 ## Weaknesses - An API key carries the whole access of the user who generated it. No per-key scopes were found - No idempotency keys in the spec or guides, and 5 requests a second per key and IP address is the only documented limit - No changelog, versioning policy or deprecation policy was found for the Payroll API - Only 13 of 460 schema definitions in the Australian spec list required fields, and 711 of 728 operations document a 200 response and little else - The developer forum's recent topics include spam, and several API questions from 2024 and 2025 show no replies ## Before you call it (notes for agents) 1. Send the API key as the Basic auth username with a blank password, for example `curl -u {api_key}: https://api.yourpayroll.com.au/api/v2/user` 2. Pick the Swagger file for the business's region (`swagger-au.json`, `swagger-nz.json`, `swagger-uk.json`, `swagger-sg.json`, `swagger-my.json`). Paths and models differ by region 3. Stay under 5 requests a second per key and IP address. A 429 answered our test with `retry-after: 1` 4. Page lists with `$skip` and `$top` (100 at most). Filter property names are capitalised, unlike the camelCase JSON 5. Read `GET /api/v2/business/{businessId}/payrun/{payRunId}/warnings` before `POST .../finalise`. Finalise can lodge with the tax office and publish pay slips in the same call ## Connect Install: ```bash Install-Package KeyPayV2 ``` First request: ```bash curl -u {api_key}: https://api.yourpayroll.com.au/api/v2/user ``` Through letme (picks today, calling later): https://letme.dev/employment-hero. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Gusto | B | 63.3 | 314 | payroll.run, payroll.employees, payroll.embedded, payroll.tax-filing, payroll.contractors, hr.time-off | no | https://www.anchorterminal.com/tools/gusto.md | | Check | B | 67.5 | 208 | payroll.run, payroll.employees, payroll.embedded, payroll.tax-filing, payroll.contractors | no | https://www.anchorterminal.com/tools/check-payroll.md | | Everee | C | 55.1 | 519 | payroll.run, payroll.embedded, payroll.employees, payroll.contractors, payroll.tax-filing | no | https://www.anchorterminal.com/tools/everee.md | | Salsa | D | 46.1 | 651 | payroll.run, payroll.embedded, payroll.employees, payroll.tax-filing, payroll.contractors | no | https://www.anchorterminal.com/tools/salsa.md | | Zeal | E | 45.4 | 658 | payroll.run, payroll.embedded, payroll.employees, payroll.contractors, payroll.tax-filing | no | https://www.anchorterminal.com/tools/zeal.md | | Finch | BB | 71.6 | 104 | payroll.employees, payroll.contractors | no | https://www.anchorterminal.com/tools/finch.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The docs site lists a Swagger 2.0 file per region, and each downloads without a login. Operations per file, 728 Australia, 660 New Zealand, 821 United Kingdom, 695 Singapore, 679 Malaysia (source: ) - All operations are prefixed by https://api.yourpayroll.com.au/api/v2, and a white label uses its own host such as https://keypay.yourpayroll.com.au (source: ) - OAuth 2.0 client credentials are issued after a support request with the application's name, callback URL and logo. Access tokens last 24 hours and refresh tokens 28 days (source: ) - The usage guide limits the API to 5 requests per second per API key per IP address (source: ) - `POST /api/v2/business/{businessId}/payrun/{payRunId}/finalise` takes options to lodge the pay run, publish pay slips and export journals, each Manual, Immediate or Scheduled (source: ) - Brand, reseller and white label endpoints create businesses and users, and three single sign-on endpoints return a one-use URL valid for 5 minutes for embedding the payroll screens (source: ) - Employment Hero's HR platform has a separate API with its own documentation, OAuth flow and rate limits, which this listing does not grade (source: ) ## Compare - [Argyle vs Employment Hero Payroll](https://www.anchorterminal.com/compare/argyle-vs-employment-hero.md): B 63.7 vs D 50.4 - [Employment Hero Payroll vs Finch](https://www.anchorterminal.com/compare/employment-hero-vs-finch.md): D 50.4 vs BB 71.6 - [Employment Hero Payroll vs Paychex](https://www.anchorterminal.com/compare/employment-hero-vs-paychex.md): D 50.4 vs E 44.8 - [Check vs Employment Hero Payroll](https://www.anchorterminal.com/compare/check-payroll-vs-employment-hero.md): B 67.5 vs D 50.4 - [Employment Hero Payroll vs Everee](https://www.anchorterminal.com/compare/employment-hero-vs-everee.md): D 50.4 vs C 55.1 - [Employment Hero Payroll vs Gusto](https://www.anchorterminal.com/compare/employment-hero-vs-gusto.md): D 50.4 vs B 63.3 - [Employment Hero Payroll vs Salsa](https://www.anchorterminal.com/compare/employment-hero-vs-salsa.md): D 50.4 vs D 46.1 - [Employment Hero Payroll vs Zeal](https://www.anchorterminal.com/compare/employment-hero-vs-zeal.md): D 50.4 vs E 45.4 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on employmenthero.com or one of its subdomains, or the README of github.com/Thinkei/keypay-dotnet-v2. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "employment-hero", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Employment Hero Payroll on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Employment Hero Payroll on Anchor Terminal](https://www.anchorterminal.com/badges/employment-hero.svg)](https://www.anchorterminal.com/tools/employment-hero) ``` Plain link: ```html Employment Hero Payroll on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Employment Hero Payroll is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/employment-hero-dark.png - Light: https://www.anchorterminal.com/assets/share/employment-hero-light.png