{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/payroll.payment-status/",
    "json": "https://www.anchorterminal.com/niches/payroll.payment-status/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/payroll.payment-status/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/payroll.payment-status/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 3 | 2 | 7 | 12 | 3 |\n\n## What counts as done\n\nFor each payment, a status from the vendor (pending, paid, returned or failed) with amount and pay date that matches what was sent, from the API or a signed webhook, and returned payments named with a reason.\n\nHow agents ask for it: did everyone get paid; has the driver's pay landed; which payments failed; mark this payment as paid\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Check (Check Technologies, Inc.)**: Payments carry attempts with paid, failed and refund states, failed attempts show detail and retry options, and payment webhooks are signed with HMAC-SHA-256 in Check-Signature.\n- **Gusto (Gusto, Inc.)**: GET ACH transactions returns each payment's payment_status (unsubmitted, submitted, successful, failed), recipient, check date and an error_code, with ACH return codes documented.\n- **Salsa (Salsa Software Inc.)**: Money movement exposes payment status (PENDING, AWAITING, COMPLETE, ON_HOLD, FAILED) and disbursement status including RETURNED, and webhooks carry a Webhook-Signature over id, timestamp and body.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Everee (Everee, Inc.)**: Net payouts read PENDING, PAID, RETURNED or SUPERSEDED with amount and send date, with signed, timestamped net-payout webhooks. acc-25 saw a payout stay PENDING for days after the payment was PAID, and acc-24 found payment history carried no payout status.\n- **Zeal (Puzzl Group Inc.)**: Checks carry disbursement_status and the Transaction Update webhook reports processing, settled and returned with status_detail. The webhook 'signature' is the shared secret itself in Puzzl-Signature, not a signature of the payload.\n\n- not this job: Argyle (Argyle Systems Inc.): Paystub destinations show where past pay went, but there is no payment the agent sent and no payout status to reconcile against.\n- not this job: Employment Hero Payroll (Employment Hero Pty Ltd): GET payrun/{id}/payments lists bank payment lines (account, amount, lodgement reference) and an ABA file; there is no paid, pending or returned status, since the employer's bank moves the money.\n- not this job: Finch (Profound Platform Inc. (dba Finch)): Finch reports past pay runs from the employer's system; it sends no payments and exposes no payout status.\n- not this job: Paychex (Paychex, Inc.): Checks show processed or unprocessed with net pay and check date; no paid, pending or returned status for the deposit was found.\n- not this job: PayFit (PayFit SAS): A monthly payment file can be downloaded; there is no per-payment status.\n- not this job: Worklio (Worklio, Inc.): Webhooks cover payroll states up to Finalized and check-generation progress is readable, but no per-payment paid, pending or returned status was found.\n\n## What stops agents finishing\n\n- status endpoint omits payout state (acc-24)\n- payout stays pending for days after the payment is paid (acc-25)\n\n## Around it\n\nBefore: payroll.preview-and-approve. After: accounting.journal-entry, messaging.notify.\n\n## Where this comes from\n\nWeight 12 of 100 in Payroll infrastructure: 3 of 27 accounts (acc-24, acc-25, acc-12); all three hit a gap between the payment status and the bank payout\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/payroll.payment-status.json, or the MCP tool get_use_case with id payroll.payment-status. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Confirm a payment reached the worker",
        "url": ""
      }
    ],
    "description": "Confirm a payment reached the worker: 3 companies fully do it, 2 with a limit, 7 carry the tag. Every listing in Payroll infrastructure with the reason and a source.",
    "facts": null,
    "h1": "Confirm a payment reached the worker",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/payroll.payment-status/",
    "published": "",
    "section": "agents",
    "title": "Confirm a payment reached the worker: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/payroll.payment-status/"
  },
  "tokens": {
    "markdown": 1100,
    "slim": 230
  },
  "version": 1
}
