{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/spend-management.approve-requests/",
    "json": "https://www.anchorterminal.com/niches/spend-management.approve-requests/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/spend-management.approve-requests/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/spend-management.approve-requests/index.min.md"
  },
  "markdown": "One company's 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| 1 | 3 | 10 | 10 | 1 |\n\n## What counts as done\n\nEach approval or rejection applied once with the approver as the actor and a success field the agent can read, and any step the agent cannot complete (step-up verification, payment release) handed to a person with a link, not reported as done.\n\nHow agents ask for it: approve the pending reimbursements under 100 pounds; reject this out-of-policy charge; what is waiting for my approval; approve this bill\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **BILL (Bill.com, LLC)**: GET pending-user-approvals lists bills awaiting the signed-in user, POST bill-approvals/actions approves or denies an array and returns a status object, and reimbursements have their own approve or deny action; the session works as that user, and payments stop at an MFA challenge.\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- **Payhawk API + MCP (Payhawk Limited)**: GET expenses/{id}/workflow returns approval and review status and POST status marks an expense reviewed or returns it, but no approve or reject call for the approval step itself was found; the MCP prepares approvals.\n- **Pleo API + MCP (Pleo Technologies A/S)**: The MCP use cases list pending reviews and approve or reject them as the user, but the tool's response schema is not published, so a readable outcome cannot be confirmed; Pleo leaves write confirmation to the client.\n- **Ramp (Ramp Business Corporation)**: GET /approvals lists pending approval data and add-step adds an approver, but the REST API approves only blank-canvas workflow steps. acc-04 found two CLI approve tools return no success field, though step-up verification does hand a URL to a person.\n\n- not this job: Airwallex Spend and Issuing (Airwallex US, LLC): Expenses and bills expose status and approvers, but no approve or reject operation is in the Spend guides.\n- not this job: Brex (Brex LLC): No approve or reject operation in the REST reference or the MCP tool list.\n- not this job: Expensify (Expensify, Inc.): The report status updater sets only REIMBURSED, returning 207 with skipped and failed report lists; no approve or reject action is documented.\n- not this job: Mercury API (Mercury Technologies, Inc.): request-send-money and transfer requests create approval requests that the API can list and read, but approving happens in Mercury; no approve or reject call.\n- not this job: Spendesk API + MCP (Spendesk SAS): Requests can be listed and read, but no approve or reject operation is in the public API.\n\n## What stops agents finishing\n\n- approve tools that return no outcome (acc-04)\n- step-up verification only in a browser\n- payment release kept in the app for its audit trail\n\n## Around it\n\nBefore: spend-management.bills-and-invoices. After: messaging.notify.\n\n## Where this comes from\n\nWeight 10 of 100 in Spend management \u0026 procurement: 1 of 18 accounts (acc-04); Ramp reports 12% of weekly assistant users batch-approve (vendor figure); weight set by hand\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/spend-management.approve-requests.json, or the MCP tool get_use_case with id spend-management.approve-requests. 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": "Approve or reject spend within the company's policy",
        "url": ""
      }
    ],
    "description": "Approve or reject spend within the company's policy: 1 companies fully do it, 3 with a limit, 10 carry the tag. Every listing in Spend management \u0026 procurement with the reason and a source.",
    "facts": null,
    "h1": "Approve or reject spend within the company's policy",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/spend-management.approve-requests/",
    "published": "",
    "section": "agents",
    "title": "Approve or reject spend within the company's policy | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/spend-management.approve-requests/"
  },
  "tokens": {
    "markdown": 1050,
    "slim": 230
  },
  "version": 1
}
