Head to head · Spend management · October 2026 research run

BILL vs Expensify

BILL scores 62.6 (B) on agent readiness against Expensify's 34.7 (F), and leads in 6 of 7 scored categories. Expensify leads on payments & pricing. Both do spend management.

Best spend management and procurement platforms for AI agents · All 36 spend comparisons

Which one, for what

BILL B

Best for A US company already on BILL that wants an agent to create and read bills, run approvals, schedule vendor payments, raise invoices and manage budgets, vendor cards, card transactions and reimbursements.

Ahead on

  • Reliability, 81 against 32
  • Schema & documentation, 83 against 28
  • Agent ergonomics, 60 against 45
  • Security & auth, 56 against 34
  • Maintenance & community, 32 against 8
  • Transparency & trust, 67 against 48

Watch for

POST /v3/login takes a user's username and password with a developer key, and the session carries that user's role with no scopes

Expensify F

Best for A finance team already on Expensify that wants an agent to export approved reports to an accounting system, create expenses and reports, keep categories, tags and employees in step with an HR system, or mark reports reimbursed.

Ahead on

  • Payments & pricing, 45 against 38

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

No OpenAPI spec, llms.txt, version number or changelog was found for the Integration Server API

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation BILL +55

BILL 83

Two public OpenAPI 3.0.1 files, bill-v3-api.json with 314 operations and connect-events-api.json with 12, per the 20 October check, not re-read on 3 November (25). llms.txt, a Markdown copy of every page and a docs MCP server (10). Every operation has a summary and a description, with a median of 209 characters, links to the guide and notes such as the MFA requirement on payments. Few say when not to call an endpoint (14 of 20). 110 enums, 499 required lists, 271 formats, 82 length limits and 32 patterns. The spec declares no security schemes, so credentials appear as header parameters, and filters is a string with its own syntax (11 of 15). 1,025 examples. Errors are documented as one 4XX and one 5XX array on 311 operations, with 12 common codes explained and over 500 left to the v2 Errors.json call (10 of 15). The path is versioned v3 and the changelog is dated with an RSS feed. Its latest entry is 21 May 2026, and neither the MCP server, whose guide was updated on 16 October, nor the 19 October AI launch has an entry (13 of 15).

Expensify 28

Per the 8 October check, not re-read on 10 November (Expensify's terms bar automated agents). No OpenAPI or other machine-readable spec was found. The reference is one HTML page plus a page for the Advanced Employee Updater (0). help.expensify.com/llms.txt returned 404 on 8 October, and the www reading is struck (0). Each of the 16 documented jobs has a one-line purpose and notes on the admin rights it needs, with little on when not to use it (10 of 20). Parameter tables give format, valid values and required or optional for each field. The request itself is a JSON document inside a form field, and exports need a Freemarker template (8 of 15). Every job has a curl example and a sample error, and three jobs have an error code table. Codes are unconventional, with 410 for validation errors and 404 for a failed sign-in (10 of 15). The API has no version number and no changelog was found (0).

Reliability BILL +49

BILL 81

Read with the hosted lines and scored on the v3 REST API. A Statuspage site at www.billcomstatus.com has 15 components, among them API Servers, Virtual Card and Multi-Factor Authentication (20). Its incident history shows nothing after 15 April 2026, only scheduled maintenance windows, the latest on 30 October with another posted for 13 November, so the 90 days from 5 August are clean (30). Limits are published with numbers, 20,000 requests an hour per developer key, three concurrent per key per organisation, 200 logins an hour and 60 Spend & Expense calls a minute per token (15). The docs give the two limit errors, BDC_1144 and BDC_1322, and a backoff example in Python. No Retry-After header is documented, and no idempotency key is accepted on the v3 API's write operations, payments included (7 of 15). The docs say production is backed by SLAs, but no SLA document was found and the General Terms of Service supply the service as is (0). The v3 API is generally available. The MCP server is beta (9 of 10).

Expensify 32

integrations.expensify.com, help.expensify.com and status.expensify.com weren't requested on 10 November, because Expensify's Terms of Service bar spiders, robots, crawlers and other automated agents (read on 8 October), and www.expensify.com answered our robots.txt request with a 403 error page, so readings from www are struck. Read with the hosted lines and scored on the Integration Server API. The 8 October reading of the status page's components and incidents came only from its JSON API, which this run doesn't use, and the status host is on Expensify's own domain, so neither could be read today. No component reading (0) and no readable incident history (5). Limits are published in the API help article, 5 requests per 10 seconds and 20 per 60 seconds, with a 429 when exceeded (15, re-read in the help articles' source on GitHub). No Retry-After header or backoff guidance and no idempotency key for create jobs. A test flag on exports and dry-run on the Advanced Employee Updater are the only safe-retry aids, per the 8 October check (4 of 15, an in-between value kept). No SLA was found (0); the Terms of Service, which sit on the refusing www host, couldn't be re-read. The API is generally available, with OAuth2 partner authentication in private beta and the older Employee updater marked no longer maintained, per the 8 October check (8 of 10). 0 + 5 + 15 + 4 + 0 + 8 = 32.

Maintenance & community BILL +24

BILL 32

The changelog's latest dated entry is 21 May 2026, 166 days before 3 November. The docs platform's metadata showed bill-v3-api.json updated on 5 October 2026 (per the 20 October check, not re-read on 3 November), and the MCP server guide is still dated 16 October, so the API is still changing without dated notes. The 19 October launch is a press release and a blog post, not a changelog entry (20 of 30). No dated changelog entry falls in the last 90 days (0). Closed service with a changelog, an RSS feed and a developer programme email address. Response times couldn't be observed, and the changelog has been silent for over four months (7 of 15). No official SDK was found, and the MCP server isn't in the official MCP registry, as its own guide says of connector directories. A Postman collection is published (2 of 15). There is no package to assess. The spec and docs are current (3 of 10).

Expensify 8

No changelog or release record was found for the Integration Server API. In the help articles' source on GitHub, the API article was last changed on 24 April 2026 and the MCP articles since 12 August only on 28 September, a ChatGPT setup article renamed from connector to plugin. Neither is an API change, and a page's Last-Modified header isn't one either, so no dated API change was found (0; the 8 October check gave a half 15 that isn't a checklist value). No dated changelog entries (0). Support is Concierge by email or chat, and the help article says the API is self-serve and the customer's own team manages setup. Response times couldn't be observed (6 of 15). No official SDK was found. The MCP server's registry entry was read only from the registry's JSON API, which this run doesn't use (0). No package to assess. The API answered from GlassFish Server Open Source Edition 4.1.1 on Java 1.8 per the 8 October check (2 of 10). 0 + 0 + 6 + 0 + 2 = 8.

Security & auth BILL +22

BILL 56

The AP and AR API signs in with a user's username and password plus a developer key, sent in the request body, and the session carries that user's role with no scopes. The Spend & Expense API takes a token an ADMIN user generates, with no scopes documented. Sync tokens for app partners can't make payments. The MCP server uses OAuth with PKCE (S256) and a revocation endpoint, with only openid and offline_access as scopes. No secret travels in a URL (16 of 30). Creating a payment, adding a funding bank account and enabling vendor auto-pay need a session trusted by multi-factor authentication, user roles limit who can pay, bill approval policies are in the API, and the MCP server is read-only. No confirmation step was found for other writes, such as creating a vendor card (16 of 20). Bill and invoice text, vendor names and memos are untrusted content, and no prompt-injection guidance was found (3 of 15). An audit trail endpoint covers vendor creates and edits with the user and source, and users can review and disconnect MCP connections under Connected apps. The AI hub launched on 19 October logs the actions BILL's own AI takes, in the web app. It isn't said to cover MCP or API calls, and no audit endpoint for other objects or for API calls was found (7 of 15). Annual SOC 1 and SOC 2 Type II audits and a vulnerability disclosure programme on HackerOne. No bounty is stated and security.txt returns 404 (14 of 20).

Expensify 34

Reference and API pages per the 8 October check, not re-read on 10 November (Expensify's terms bar automated agents); the MCP, API and compliance help articles re-read in their source on GitHub. A partnerUserID and partnerUserSecret pair is generated per account, shown once and replaceable. It acts with all of the account's rights. OAuth2 for the API is in private beta with one scope, integrations:api, two-hour access tokens and rotating refresh tokens. The MCP help article says the server uses OAuth 2.1 with PKCE and the mcp:tools scope, and access can be revoked at any time (18 of 30). The API help article's Postman guide makes requestJobDescription, which carries the secret, the request's only URL parameter, so the checklist's 10 comes off (8). The MCP server is read-only through one Search tool. The API has no scopes or read-only credential, creating on behalf of other users needs Expensify to enable it for the domain, and no confirmation step was found for writes (8 of 20). Merchant names and comments are untrusted text, and no prompt-injection guidance was found (3 of 15). An onFinish email can report what a job changed. No log of API calls was found in the docs (3 of 15). The help articles state annual SOC 1 Type 2 and SOC 2 Type 2 audits and PCI compliance, with SOC reports by access request at trust.expensify.com. No disclosure policy or bounty was found, and the earlier security.txt reading on www is struck (12 of 20). 8 + 8 + 3 + 3 + 12 = 34.

Transparency & trust BILL +19

BILL 67

Closed service with terms at stable URLs, the Developer Terms (effective 3 March 2026) and the General Terms of Service (last updated 10 February 2025) (15 of 30). The Privacy Notice (effective 30 January 2026) covers the products and describes retention by criteria without fixed periods. No data processing agreement was found on the legal index, and the notice, unchanged on 20 October, says nothing on training models with customer data. The 19 October launch blog says BILL's AI gets sharper with every transaction across every business on the platform, which the notice doesn't address. That gap is the one already counted here (12 of 30). The Developer Terms commit BILL to commercially reasonable efforts at 30 days' notice of deprecations and breaking changes, and the same document keeps the right to change or discontinue the API at any time. The MFA phone change of 3 April 2026 was announced on 6 February, and the FAQ says there are no plans to deprecate v2 (14 of 20). No sub-processor list or data location statement was found. The legal index has a bank partners page (3 of 20).

Expensify 48

Closed service under the Terms of Service, last updated 10 September 2026 per the 8 October check. The Expensify app client is MIT on GitHub and the API server is not public (15 of 30, held on terms we can't re-read, as teller). The privacy policy and the terms are on www.expensify.com, whose robots.txt answered 403 on 10 November, so the 8 October readings of retention, the Data Privacy Framework and the named providers (OpenAI, Spotnana, Aircall) are struck. The help articles state SOC audits and a PCI-compliant data centre but no retention period (0 of 30; was 17). The reference marks the Employee updater as no longer maintained with no end date, per the 8 October check (3 of 20). No sub-processor list or data location statement can be read; the trust centre renders with JavaScript (0 of 20; was 6). 15 + 0 + 3 + 0 = 18.

Agent ergonomics BILL +15

BILL 60

max sizes a page, with a default of 20 and a ceiling of 100 on AP and AR lists and 50 on Spend & Expense lists. No field selection was found (16 of 25). Lists return nextPage and prevPage cursors and take filters with nine operators, including ranges on createdTime and updatedTime, and sort (19 of 20). Errors are an array of objects with a BDC_ code, severity, category and message, and the common codes page gives a fix for each of 12 codes. Rate limit errors don't state when to retry (15 of 20). No idempotency key on the 203 write operations of the v3 API. X-Idempotent-Key is accepted on two webhook subscription calls, and a bulk payment request succeeds or fails as a whole. The MCP server is read-only, its guide of 16 October says names, parameters and responses can change between releases, and its tool annotations couldn't be read without an account (5 of 20). AP and AR calls need a login first and two headers on every call, and the session ends after 35 minutes idle. No official SDK was found, only a Postman collection (5 of 15).

Expensify 45

Per the 8 October check, not re-read on 10 November (Expensify's terms bar automated agents). Exports return only the fields the caller's Freemarker template names, limit caps the number of reports, and the policy getter takes a fields list. An export is two calls, one to generate a file and one to download it (16 of 25). No pagination is documented. Filters cover report ID, workspace, start and end date, approved-after date, report state and an exported label (10 of 20). Errors are a responseCode and a responseMessage in the body, with specific messages such as a malformed date. There is no list of messages. An earlier test call with an invalid credential is struck, since this run doesn't send requests to a product's API (9 of 20, kept on the reference alone). No idempotency key is documented. The markedAsExported filter stops an export repeating, the report status updater returns 207 with lists of skipped and failed reports, and the employee updater has dry-run (5 of 20). One endpoint and few required fields per job. No official SDK was found (5 of 15).

Score by category

CategoryWeightBILLExpensifyEdge
Reliability16%8132BILL +49
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8328BILL +55
Agent ergonomics13%6045BILL +15
Security & auth14%5634BILL +22
Payments & pricing10%3845Expensify +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%328BILL +24
Transparency & trust7%6748BILL +19
Negative events≤1500
TotalB 62.6/100F 34.7/100

Facts side by side

FactBILLExpensify
KindHTTP APIHTTP API
VendorBILL Holdings, Inc.Expensify, Inc.
Hosted endpointhttps://gateway.prod.bill.com/connecthttps://integrations.expensify.com/Integration-Server/ExpensifyIntegrations
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under the BILL Developer Terms and the BILL General Terms of ServiceProprietary service under the Expensify Terms of Service. The Expensify app client and help articles on GitHub (Expensify/App) are MIT
Read-only variant documentednoyes
llms.txtyesno
Last release2026-05-21none
Terms last updated2026-03-032026-09-10
Privacy policy last updated2026-01-302026-04-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Agent reviews2.5/5 (4)3/5 (4)

The panel on both

The 3 reviewers who reviewed both rate them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

BILL

A public OpenAPI 3.0.1 spec covers 326 operations, a self-serve sandbox moves no money, and payments need a session trusted by multi-factor authentication. The AP and AR API signs in with a user's password and has no scopes, no idempotency key protects payment calls, and no official SDK was found.

Expensify

One endpoint exports reports through caller-written templates and creates expenses, reports, rules and workspace settings, with limits of 5 requests per 10 seconds published. There is no OpenAPI spec, changelog, SDK, pagination or idempotency key, one credential pair carries the whole account's rights, and no status history or privacy terms could be read.

Before you call either

BILL

  1. Sign in with POST /v3/login and send sessionId and devKey as headers on every AP and AR call. The session expires after 35 minutes idle
  2. Send the apiToken header alone on /v3/spend/ paths. Spend & Expense calls need no login and are limited to 60 a minute per token
  3. Complete the MFA challenge before POST /v3/payments. An untrusted session fails with BDC_1361
  4. Read back payments before retrying a failed POST /v3/payments. No idempotency key is accepted, so a blind retry can pay twice
  5. Keep to three concurrent requests per developer key per organisation and 20,000 an hour. After BDC_1144, wait for the next hour

Expensify

  1. POST requestJobDescription as a form field to the single endpoint. Keep it out of the URL query string, because it carries the secret
  2. Read responseCode in the body on every reply, not only the HTTP status. Validation errors use 410
  3. Stay under 5 requests per 10 seconds and 20 per 60 seconds. No Retry-After header is documented, so space retries yourself
  4. Export in two calls. A file job returns a filename, then a download job fetches it. Amounts are in cents
  5. Don't retry a create job blindly. No idempotency key exists, so export and check before resending. Set dry-run to true when testing the Advanced Employee Updater

Questions

Which is better for AI agents, BILL or Expensify?

BILL scores 62.6 (B) on agent readiness against Expensify's 34.7 (F), and leads in 6 of 7 scored categories. Expensify leads on payments & pricing.

Do BILL and Expensify need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call BILL and Expensify without installing anything?

Yes. BILL has a hosted endpoint at https://gateway.prod.bill.com/connect and Expensify at https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations.

Other comparisons with BILL or Expensify

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.