# Approve or reject spend within the company's policy

> 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 & procurement with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/spend-management.approve-requests/
- Markdown: https://www.anchorterminal.com/niches/spend-management.approve-requests/index.md (~1,050 tokens)
- Slim: https://www.anchorterminal.com/niches/spend-management.approve-requests/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/spend-management.approve-requests/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 3 | 10 | 10 | 1 |

## What counts as done

Each 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.

How 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

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **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.

## Does the job, with a limit

It 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.

- **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.
- **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.
- **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.

- 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.
- not this job: Brex (Brex LLC): No approve or reject operation in the REST reference or the MCP tool list.
- 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.
- 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.
- 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.

## What stops agents finishing

- approve tools that return no outcome (acc-04)
- step-up verification only in a browser
- payment release kept in the app for its audit trail

## Around it

Before: spend-management.bills-and-invoices. After: messaging.notify.

## Where this comes from

Weight 10 of 100 in Spend management & procurement: 1 of 18 accounts (acc-04); Ramp reports 12% of weekly assistant users batch-approve (vendor figure); weight set by hand

As 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.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
