Brex vs Expensify

Accounting sync

1. finance leadTransactions sync to QuickBooks, NetSuite, or Xero with GL account, class, and department mappings I control

   weight 3 · round to Expensify
   Brex—none0/10

   The evidence pack shows Brex has a one-click accounting sync feature, but it is documented only as syncing to Puzzle (brex-docs-17, 18, 40), with no mention of QuickBooks, NetSuite, or Xero, nor any documentation of finance-lead-controlled GL account, class, or department mapping for such syncs. Cost-center/department fields exist in the user API filters (brex-docs-19, 33) but these aren't tied to any accounting-sync mapping capability.

   • [claimed-docs] “Prepared expense data sync automatically to eliminate manual set up or matching between Brex and Puzzle.”
   • [claimed-docs] “Get global card and a treasury product that earns yield†, plus modern accounting from Puzzle.”
   • [claimed-docs] “Set up your accounting system in one click.”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”

   proof ↗⚑ flag

   Expensify~partialclaimed6/10

   Docs confirm real integrations with QuickBooks Online (export sync) and NetSuite (expense syncing/reporting/accounting), plus a 'multi-level GL coding' feature suggesting GL account/class/department mapping control, but there's no explicit mention of Xero or of finance-lead-controlled class/department field mapping specifically. Missing for 10: explicit Xero integration evidence, detailed documentation of user-controlled class/department mapping configuration, and independent/hands-on confirmation that mappings work as configured.

   • [claimed-docs] “Finalized reports are exported automatically to QuickBooks Online.”
   • [claimed-docs] “A QuickBooks Online connection lets you sync Expensify expenses with your accounting system.”
   • [claimed-docs] “Connect your Expensify Workspace to NetSuite to streamline expense syncing, reporting, and accounting.”
   • [claimed-docs] “Multi-level GL coding”

   proof ↗⚑ flag

Close

1. finance leadSpend is coded as it happens — merchant, category, memo, receipt — so month-end close is a review, not an archaeology dig

   weight 2 · round to Brex
   Brex✓fullclaimed8/10

   Brex documents real-time spend coding at point of transaction: receipt auto-matching to expenses (brex-docs-7, brex-docs-27), AI agents auto-categorizing/approving and writing memos (brex-docs-23, brex-docs-16, brex-docs-41), policy/budget enforcement applied per transaction (brex-docs-8, brex-docs-15, brex-docs-36), and explicit close-in-real-time messaging (brex-docs-37) plus one-click accounting sync (brex-docs-17, brex-docs-40). This directly maps to merchant/category/memo/receipt capture happening automatically rather than at month-end. Missing for 10: independent/hands-on verification that AI-drafted memos and auto-categorization are accurate in practice, and no third-party case study confirming reduced close time.

   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”
   • [claimed-docs] “Manage global spend and close the books in real time — with unmatched automation of manual expense work.”
   • [claimed-docs] “Prepared expense data sync automatically to eliminate manual set up or matching between Brex and Puzzle.”
   • [claimed-docs] “Set up your accounting system in one click.”

   proof ↗⚑ flag

   Expensify!disputedcontradicted5/10

   Expensify's docs promise automatic merchant/date/total capture (SmartScan), AI-driven categorization, multi-level GL coding, and syncing to QuickBooks/NetSuite so reports are close-ready, but hands-on community reports directly contradict the categorization claim, citing ~70% miscategorization and slow, human-mediated (mechanical turk) receipt processing that undermines 'real-time coding'. Missing for 10: independent verification that categorization accuracy has improved, more recent (post-mturk-era) hands-on accounts confirming reliable real-time coding, and evidence of memo/note fields being auto-populated.

   • [claimed-docs] “Create, categorize, tag, approve, and reject expenses using plain language, no clicking required”
   • [claimed-docs] “Open the app, tap the camera, and SmartScan reads the merchant, date, total, and currency automatically.”
   • [claimed-docs] “Multi-level GL coding”
   • [claimed-docs] “SmartScan extracts receipt data in realtime, with no batch processing or overnight delays.”
   • [claimed-docs] “Finalized reports are exported automatically to QuickBooks Online.”
   • [community] “Expensify does pretty horrible categorization. It does a really good job at determining amount, but approx 70% of the time manages to screw …”
   • [community] “Lots of companies like Expensify, Bills.com, ReceiptHog use MTurk to extract data from financial documents. Accuracy is not 100% guaranteed …”
   • [community] “I used expensify and it took like 20 mins to process a few receipt images.. I ended up doing it myself anyway.”

   proof ↗⚑ flag

Multi entity

1. finance leadRun multiple legal entities and currencies in one account with consolidated reporting and per-entity books

   weight 2 · round to Brex
   Brex~partialclaimed3/10

   Evidence shows Brex's API supports a `legal_entity_id` field for filtering users, implying some multi-entity data modeling exists, and general mentions of 'global spend'/'more currencies' support, but there is no documentation of consolidated cross-entity reporting or dedicated per-entity books for finance close workflows. missing for 10: consolidated reporting across entities, per-entity books/ledgers, multi-currency accounting close workflow, any first-party or independent confirmation of multi-entity account structure.

   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Manage global spend and close the books in real time — with unmatched automation of manual expense work.”
   • [claimed-docs] “Create a virtual card instantly to pay by card and earn rewards. Send ACH, checks, and wires from any bank account or a Brex business accoun…”
   • [claimed-docs] “Get global card and a treasury product that earns yield†, plus modern accounting from Puzzle.”

   proof ↗⚑ flag

   Expensify—none0/10

   No evidence describes multi-entity account structures, per-entity books, or consolidated multi-entity reporting; only generic multi-currency invoicing and single ERP connections (QuickBooks/NetSuite) are mentioned, which is not the same as multi-entity consolidation.

   • [claimed-docs] “Upload your logo, add custom terms, VAT, sales tax, or multiple currencies, and make every invoice look polished and professional.”
   • [claimed-docs] “A QuickBooks Online connection lets you sync Expensify expenses with your accounting system.”
   • [claimed-docs] “Connect your Expensify Workspace to NetSuite to streamline expense syncing, reporting, and accounting.”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Brex
   Brex✓fullprobed9/10

   Brex hosts a live llms.txt at developer.brex.com/llms.txt (confirmed via HTTP 200 probe) that provides a structured table of contents for AI agents, and it also documents an official MCP server for agentic access to Brex data, showing clear agent-oriented documentation design. Missing for 10: independent third-party confirmation that agents actually consume llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.brex.com/llms.txt # Brex Developer API > APIs to build on top of the Brex financial OS. ## T…”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [probe] “official MCP server documented at https://developer.brex.com/docs/mcp”

   proof ↗⚑ flag

   Expensify—none0/10

   No evidence of an llms.txt file, agent-oriented documentation, or any machine-readable docs endpoint; the docs-md probe returned a 404, and no other citation mentions such a resource.

   • [probe] “PROBE docs-md: HTTP 404 at https://integrations.expensify.com/Integration-Server/doc/.md”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Brex
   Brex~partialclaimed6/10

   Brex exposes a full REST API with token-based auth (no interactive login required), webhook subscriptions, and Postman/Zapier/Workato/Pipedream automation examples (bulk card creation, scheduled exports), all of which support headless, non-interactive use suitable for scripted/CI-style automation. However there is no explicit mention of CI/CD pipelines, SDKs, or headless test/deploy tooling — missing for 10: explicit CI/CD integration docs, official SDKs for scripting, and confirmation of non-interactive token refresh/rotation suitable for unattended pipelines.

   • [claimed-docs] “Sign in to dashboard.brex.com as an account admin or card admin... Click Create Token. Create a name for your token... Choose what level of …”
   • [claimed-docs] “generate a user token from your Brex dashboard and pass it along in your API call headers”
   • [claimed-docs] “Register a URL to receive the webhooks using the [register webhook] endpoint.”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”

   proof ↗⚑ flag

   Expensify~partialclaimed3/10

   Expensify exposes an Integration Server API with OAuth2 token-based programmatic access, which could technically be scripted into a CI pipeline, but there is no documentation, CLI, SDK, or example showing headless/CI usage specifically. Missing for 10: explicit CI/automation documentation, a headless CLI or SDK, and any hands-on evidence of running Expensify unattended in a pipeline.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “use the OAuth2 authorization code flow to obtain a short-lived access token”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Brex
   Brex✓fullprobed8/10

   Brex is not itself an AI agent but a financial platform, so publishing an official MCP server is a fair ecosystem capability, and Brex documents a first-party MCP server letting AI assistants manage expenses, users, cards, transactions, and bills. Missing for 10: independent/hands-on confirmation of setup and reliability beyond vendor docs.

   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [probe] “official MCP server documented at https://developer.brex.com/docs/mcp”

   proof ↗⚑ flag

   Expensify—none0/10

   Expensify offers a REST API with OAuth2 credentials, but there is no evidence of an official MCP server for agent connectivity; the AI features described (Ask Expensify) are first-party assistant features, not an MCP integration point.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “Create, categorize, tag, approve, and reject expenses using plain language, no clicking required”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Brex—none0/10

   Evidence pack shows Brex's developer platform (APIs, Postman collection, MCP server, Zapier/Pipedream/Workato integrations) but no mention of an official CLI tool anywhere in docs or changelog.

   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.brex.com/llms.txt # Brex Developer API > APIs to build on top of the Brex financial OS. ## T…”

   proof ↗⚑ flag

   Expensify—none0/10

   Evidence shows an API/Integration Server with OAuth2, and a GitHub repo for the app itself, but no official CLI tool for AI-native workflows is documented anywhere in the pack.

   ⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Brex
   Brex✓fullprobed8/10

   Brex has extensive documented public REST APIs (transactions, budgets, expenses, payments, onboarding, webhooks) with authentication via dashboard-generated tokens, Postman collections, and a llms.txt developer index, giving AI-native users a clear path to programmatically drive the product. Missing for 10: a live discoverable OpenAPI spec (probe found 404s on standard OpenAPI paths) and independent/hands-on third-party corroboration of API robustness beyond vendor docs.

   • [claimed-docs] “Sign in to dashboard.brex.com as an account admin or card admin... Click Create Token. Create a name for your token... Choose what level of …”
   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “generate a user token from your Brex dashboard and pass it along in your API call headers”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.brex.com/llms.txt # Brex Developer API > APIs to build on top of the Brex financial OS. ## T…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

   Expensify✓fullclaimed7/10

   Expensify documents a public Integration Server API with credential generation and OAuth2 authorization-code flow for acting on behalf of users, indicating programmatic access beyond the UI. Missing for 10: independent/hands-on developer corroboration of the API's completeness, rate limits, or breadth of endpoints, and no evidence of SDKs or community usage confirming real-world API-driven workflows.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “use the OAuth2 authorization code flow to obtain a short-lived access token”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Brex
   Brex✓fullprobed7/10

   Brex's developer docs show admins can create named API tokens and choose specific data-access scopes at creation time (brex-docs-2, brex-docs-26), which is a direct least-privilege credentialing mechanism that would apply to any API consumer, including an AI agent calling the API or via the documented MCP server (brex-docs-3, brex-probe-3). Missing for 10: an explicit enumerated list of available scopes, agent-specific credential guidance, per-agent revocation/audit trail details, and independent corroboration of scope enforcement in practice.

   • [claimed-docs] “Sign in to dashboard.brex.com as an account admin or card admin... Click Create Token. Create a name for your token... Choose what level of …”
   • [claimed-docs] “generate a user token from your Brex dashboard and pass it along in your API call headers”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [probe] “official MCP server documented at https://developer.brex.com/docs/mcp”

   proof ↗⚑ flag

   Expensify—none0/10

   Expensify's API docs describe generating general API credentials and using OAuth2 to obtain short-lived tokens on behalf of a user, but there's no evidence of scoped/least-privilege credential issuance specifically designed for agent use cases (e.g., granular permission scopes, agent-specific role restrictions). Missing for 10: scoped/permissioned API key or token creation, agent-specific credential controls, documentation of least-privilege design.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “use the OAuth2 authorization code flow to obtain a short-lived access token”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Brex—none0/10

   Brex documents REST APIs (OpenAPI specs), authentication, webhooks, a Postman workspace, and third-party integrations (Pipedream, Zapier, Workato), but nowhere in the evidence pack is there mention of official client-library SDKs (e.g., Node.js, Python, Java packages) that AI-native developers could build against.

   ⚑ flag

   Expensify—none0/10

   Evidence shows only a proprietary Integration Server REST API with API credentials/OAuth2, not an official SDK (client library) for building AI-native integrations; no mention of SDKs in any language, and a probe attempt to find developer docs even returned a 404. Missing for 10: any official SDK/client library, language-specific packages, or AI-agent oriented developer kit.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “use the OAuth2 authorization code flow to obtain a short-lived access token”
   • [probe] “PROBE docs-md: HTTP 404 at https://integrations.expensify.com/Integration-Server/doc/.md”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Brex
   Brex✓fullclaimed8/10

   Brex documents a dedicated webhooks API and guide for registering endpoints and receiving selected events, including examples like referral activation, indicating genuine subscribe-to-event support. missing for 10: no independent/hands-on corroboration of webhook delivery reliability, and no explicit AI-native/agent-triggered subscription workflow shown.

   • [claimed-docs] “Register a URL to receive the webhooks using the [register webhook] endpoint.”
   • [claimed-docs] “you can receive a webhook when a referral you made has activated”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”

   proof ↗⚑ flag

   Expensify—none0/10

   The evidence pack shows Expensify has an API with OAuth2 auth and credential generation, but nothing describes a webhook/event subscription mechanism for AI agents to consume. Missing for 10: any documentation of webhook endpoints, event types, subscription setup, or push-notification callback support.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Brex
   Brex✓fullclaimed7/10

   Brex AI features (audit agent, review agent, policy-based auto-approval, PO/payment matching suggestions) are documented as generating insights and suggestions directly from account/expense data. Evidence is first-party marketing/docs only, with no independent hands-on corroboration of these AI insight features in practice. missing for 10: independent/hands-on verification of AI insight quality, UI examples showing generated suggestions in context.

   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Brex AI will capture every itemized detail, suggest the matching PO, and draft a payment.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”

   proof ↗⚑ flag

   Expensify!disputedcontradicted5/10

   Expensify markets an 'Ask Expensify AI' feature that lets users create/categorize/approve expenses and even fix workspace configuration via plain-language requests, which matches the AI-insights/suggestions story (expensify-docs-3, expensify-docs-4). However, independent community reports say Expensify's automated categorization (the core AI-driven suggestion mechanism) is wrong roughly 70% of the time unless obvious, undercutting the reliability of these AI suggestions (expensify-comm-1, expensify-comm-4). Missing for 10: independent hands-on validation of the newer 'Ask Expensify AI' feature specifically (not just older SmartScan categorization), and evidence of proactive 'insights' beyond conversational commands.

   • [claimed-docs] “Create, categorize, tag, approve, and reject expenses using plain language, no clicking required”
   • [claimed-docs] “Configure workspaces, build rules, and fix your own setup mistakes by just asking”
   • [community] “Expensify does pretty horrible categorization. It does a really good job at determining amount, but approx 70% of the time manages to screw …”
   • [community] “Lots of companies like Expensify, Bills.com, ReceiptHog use MTurk to extract data from financial documents. Accuracy is not 100% guaranteed …”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Brex
   Brex✓fullclaimed7/10

   Brex documents autonomous background agents (audit agent monitoring expenses, review agent auto-approving low-risk items and escalating exceptions) plus webhook events and third-party automation platforms (Zapier, Workato, Pipedream) that can run unattended once configured, and an MCP server for AI assistant integration. This covers the core 'runs autonomously in background' story via policy-driven agents and event-driven webhooks/automations. missing for 10: independent/hands-on verification that these agents truly run unattended without human triggers, and technical detail on scheduling/trigger architecture beyond marketing copy

   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “Register a URL to receive the webhooks using the [register webhook] endpoint.”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”

   proof ↗⚑ flag

   Expensify~partialclaimed4/10

   Expensify documents rule-based background automations (auto-export to QuickBooks/NetSuite, SmartScan, workflow rules) and an 'Ask Expensify AI' assistant that can categorize/approve/configure via plain language, plus an API/OAuth flow for building custom integrations — but these are largely interactive or preset triggers rather than a documented capability for AI-native users to configure agentic background automations that run autonomously on their own schedule. Missing for 10: explicit support for user-defined autonomous/scheduled AI agent workflows, independent confirmation that 'Ask Expensify AI' actions can run unattended in the background, and evidence of persistent agent-triggered automation beyond fixed export rules.

   • [claimed-docs] “Create, categorize, tag, approve, and reject expenses using plain language, no clicking required”
   • [claimed-docs] “Configure workspaces, build rules, and fix your own setup mistakes by just asking”
   • [claimed-docs] “Finalized reports are exported automatically to QuickBooks Online.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “use the OAuth2 authorization code flow to obtain a short-lived access token”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Brex
   Brex✓fullclaimed7/10

   Brex documents built-in AI agents (audit agent, review agent, Brex AI) that autonomously categorize expenses, auto-approve low-risk spend, write memos, fetch receipts, and file reimbursements, allowing users to delegate financial tasks directly within the product. This is distinct from the MCP server (which is for external AI clients) and represents genuine in-product agentic delegation. Missing for 10: independent/hands-on verification of these AI agent features actually working, and more detail on how users configure/invoke the assistant.

   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Brex AI will capture every itemized detail, suggest the matching PO, and draft a payment.”

   proof ↗⚑ flag

   Expensify~partialclaimed6/10

   Expensify's own blog documents 'Ask Expensify AI Anything,' a built-in assistant that can create/categorize/approve expenses and even configure workspaces via plain language, matching the delegation story. However, this is first-party marketing copy with no independent hands-on corroboration, and community feedback in the pack focuses only on SmartScan's older categorization/data-handling issues rather than validating the AI assistant itself. Missing for 10: independent/hands-on verification of the AI assistant's task delegation, details on scope/limits of what it can autonomously do, and any user reports specifically about this AI feature.

   • [claimed-docs] “Create, categorize, tag, approve, and reject expenses using plain language, no clicking required”
   • [claimed-docs] “Configure workspaces, build rules, and fix your own setup mistakes by just asking”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Brex
   Brex~partialprobed7/10

   Brex documents a first-party MCP server explicitly built so 'AI assistants interact directly with your Brex account... through natural language' for expenses, cards, banking, and bills, plus AI agents (audit/review) that act on policies automatically. This directly supports natural-language operation for AI-native users, though it's vendor-documented only. Missing for 10: independent/hands-on evidence of the MCP server's natural-language commands working reliably, and detail on command coverage limits.

   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [probe] “official MCP server documented at https://developer.brex.com/docs/mcp”

   proof ↗⚑ flag

   Expensify~partialclaimed5/10

   First-party blog claims 'Ask Expensify AI' lets users create/categorize/tag/approve/reject expenses and configure workspaces via plain language, directly matching the story, but this is vendor marketing copy with no independent/hands-on verification of the natural-language feature itself. Community evidence discusses categorization accuracy and UX issues but doesn't specifically test or contradict the AI natural-language assistant. Missing for 10: independent hands-on confirmation that the AI chat actually executes commands reliably, details on scope/limits of supported natural-language operations, and evidence it's broadly available rather than a beta/blog announcement.

   • [claimed-docs] “Create, categorize, tag, approve, and reject expenses using plain language, no clicking required”
   • [claimed-docs] “Configure workspaces, build rules, and fix your own setup mistakes by just asking”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Brex
   Brex~partialprobed4/10

   Brex provides detailed API reference docs (openapi/*.md pages) and a Postman workspace with collections for all APIs, which allows some hands-on exploration, but there's no evidence of an interactive in-browser API reference with embedded runnable examples (e.g., a Swagger/OpenAPI explorer); a probe for standard openapi.json/swagger endpoints returned 404s. Missing for 10: an embedded interactive console/try-it feature, confirmation of runnable code snippets directly in docs, and independent corroboration of hands-on use.

   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”
   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

   Expensify—none0/10

   Evidence shows only a basic API doc requiring credentials and OAuth2 setup, with no mention of an interactive reference, runnable examples, or sandbox/console; a probe for a machine-readable docs endpoint returned 404.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [probe] “PROBE docs-md: HTTP 404 at https://integrations.expensify.com/Integration-Server/doc/.md”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Brex
   Brex~partialprobed4/10

   Brex publishes API reference docs under an /openapi/ path pattern (transactions_api.md, budgets_api.md, expenses_api.md, etc.) and offers a Postman collection covering all Brex APIs, both of which imply structured, machine-readable spec data. However, a direct probe for standard OpenAPI/Swagger JSON files (openapi.json, swagger.json, etc.) returned 404s, meaning there is no confirmed single downloadable OpenAPI spec file. Missing for 10: a discoverable raw OpenAPI/Swagger JSON or YAML file, and confirmation that the Postman collection is exported in OpenAPI format.

   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

   Expensify—none0/10

   Evidence shows Expensify has an API with OAuth2 credentials but no mention of a downloadable machine-readable spec like OpenAPI/Swagger; the docs page is only HTML documentation, not a spec file.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “use the OAuth2 authorization code flow to obtain a short-lived access token”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Brex—none0/10

   No evidence of a sandbox/test environment separate from production data; the docs pack covers authentication, webhooks, MCP server, and API endpoints but never mentions a sandbox mode or test credentials. Missing for 10: any mention of a sandbox environment, test API keys, or documentation distinguishing test vs. production data.

   ⚑ flag

   Expensify—none0/10

   No evidence of a sandbox or test environment for Expensify's API/integration platform; docs only cover OAuth2 credentials and production-oriented integrations (QuickBooks, NetSuite). This is a fair axis for an API-driven product, but nothing in the evidence pack mentions sandbox, staging, or test-mode accounts.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Brex—none0/10

   The evidence shows a changelog tracking feature additions (e.g., new filter params, policy fields) but nothing documenting API versioning scheme or a deprecation policy for breaking changes. No mention of version numbers, sunset timelines, or backward-compatibility guarantees appears anywhere in the pack.

   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”

   proof ↗⚑ flag

   Expensify—none0/10

   Evidence shows Expensify has an Integration Server API with OAuth2 credentials, but nothing about API versioning, version numbers, or a documented deprecation/sunset policy is present anywhere in the pack. Missing for 10: any mention of API version numbers, changelog, breaking-change policy, or deprecation timeline/notice process.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “use the OAuth2 authorization code flow to obtain a short-lived access token”

   proof ↗⚑ flag

Ai coding

1. ai-native userAI codes and audits expenses for me — reading receipts, suggesting categories and memos, and catching duplicates or fraud

   weight 2 · round to Brex
   Brex✓fullclaimed8/10

   Brex AI explicitly offers audit and review agents that read receipts, categorize/flag violations by risk level, auto-approve low-risk expenses, and write memos/fetch receipts/file reimbursements automatically, matching the story closely. missing for 10: independent/hands-on verification of accuracy (duplicate/fraud catching specifically) and no third-party corroboration beyond vendor marketing copy.

   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”

   proof ↗⚑ flag

   Expensify!disputedcontradicted4/10

   Expensify markets 'Ask Expensify AI' for categorizing, tagging, and approving expenses via plain language, and SmartScan for reading receipt data (expensify-docs-3, expensify-docs-4, expensify-docs-6, expensify-docs-18), but hands-on community reports directly contradict the accuracy claims: users report ~70% mis-categorization rates and note SmartScan historically relied on human mechanical-turk workers (with resulting PII exposure) rather than pure AI (expensify-comm-1, expensify-comm-2, expensify-comm-3, expensify-comm-4). No evidence at all addresses duplicate or fraud detection. Missing for 10: verified fraud/duplicate-catching capability, independent confirmation that categorization/audit is now AI-driven and accurate, and resolution of the human-labor/accuracy concerns.

   • [claimed-docs] “Create, categorize, tag, approve, and reject expenses using plain language, no clicking required”
   • [claimed-docs] “Configure workspaces, build rules, and fix your own setup mistakes by just asking”
   • [claimed-docs] “Open the app, tap the camera, and SmartScan reads the merchant, date, total, and currency automatically.”
   • [claimed-docs] “SmartScan extracts receipt data in realtime, with no batch processing or overnight delays.”
   • [community] “Expensify does pretty horrible categorization. It does a really good job at determining amount, but approx 70% of the time manages to screw …”
   • [community] “TL;DR: Expensify's deceptive mechanical turk army may have resulted in me coming within seconds of losing $30k, giving away PII to low-paid …”
   • [community] “Some of the receipts had enough info to identify people - store card numbers, buyer phone number, etc. My wife occasionally does mturk and l…”
   • [community] “Lots of companies like Expensify, Bills.com, ReceiptHog use MTurk to extract data from financial documents. Accuracy is not 100% guaranteed …”

   proof ↗⚑ flag

Ai policy

1. ai-native userAn AI assistant enforces policy conversationally — chasing missing receipts, explaining declines, and answering "can I expense this?" before the spend happens

   weight 2 · round to Brex
   Brex~partialclaimed7/10

   Brex explicitly markets AI agents that follow up on out-of-compliance spend, fetch receipts, and offer policy help ('AI assistants do employees' expenses... fetching receipts, offering policy help' and 'review agent... follows up with anyone out of compliance'), plus an MCP server letting assistants query expenses/policy conversationally. However, there's no concrete evidence of the assistant proactively answering 'can I expense this?' before spend occurs or explaining specific decline reasons conversationally. Missing for 10: documented pre-spend conversational policy checks, explicit decline-explanation flows, and independent/hands-on confirmation of these AI behaviors in practice.

   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”

   proof ↗⚑ flag

   Expensify~partialcommunity4/10

   Expensify's 'Ask Expensify AI Anything' assistant supports plain-language creation, categorization, approval/rejection of expenses and workspace rule configuration, which is conversational policy interaction, but the evidence never shows it proactively chasing missing receipts, explaining specific declines, or answering pre-spend 'can I expense this?' queries. Community reports also flag poor categorization accuracy (~70% error rate), undermining confidence in the conversational engine's reliability. Missing for 10: explicit documentation of proactive receipt-chasing, decline explanations, and pre-spend eligibility checks, plus independent verification of these specific behaviors.

   • [claimed-docs] “Create, categorize, tag, approve, and reject expenses using plain language, no clicking required”
   • [claimed-docs] “Configure workspaces, build rules, and fix your own setup mistakes by just asking”
   • [community] “Expensify does pretty horrible categorization. It does a really good job at determining amount, but approx 70% of the time manages to screw …”
   • [community] “Lots of companies like Expensify, Bills.com, ReceiptHog use MTurk to extract data from financial documents. Accuracy is not 100% guaranteed …”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Brex
   Brex✓fullclaimed8/10

   Brex documents explicit bulk operations via automation platforms (bulk create virtual cards via Pipedream, bulk create users/set limits via Workato) and supports filtering/listing at scale via API query params, plus bulk-friendly endpoints for users, cards, vendors, and expenses. This is corroborated by first-party developer docs across multiple integration guides, not just a single mention. Missing for 10: no native in-product bulk-action UI evidence or independent hands-on confirmation of bulk API throughput/limits.

   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”

   proof ↗⚑ flag

   Expensify—none0/10

   Evidence shows an API/OAuth integration and a natural-language AI assistant for single-item actions (create/categorize/approve expenses), but nothing describes bulk or batch operations across many items at once via API or AI. Missing for 10: documented bulk endpoints, batch API calls, or AI commands operating on multiple items simultaneously, plus any independent confirmation of such bulk capability.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “Create, categorize, tag, approve, and reject expenses using plain language, no clicking required”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Brex
   Brex~partialclaimed7/10

   Brex offers webhooks that fire on events (brex-docs-1, brex-docs-25, brex-docs-35) plus built-in policy rules that auto-trigger actions like blocking out-of-policy spend, auto-approving low-risk expenses, and escalating exceptions (brex-docs-8, brex-docs-9, brex-docs-16, brex-docs-36, brex-docs-41). Third-party integrations (Zapier, Workato, Pipedream) extend this into custom event-triggered automations (brex-docs-30, brex-docs-31, brex-docs-32). Missing for 10: a native no-code rule-builder UI for arbitrary custom triggers/actions beyond preset expense/travel/approval policies, and independent hands-on confirmation that webhook-to-action automations work reliably in practice.

   • [claimed-docs] “Register a URL to receive the webhooks using the [register webhook] endpoint.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”

   proof ↗⚑ flag

   Expensify~partialclaimed5/10

   Expensify's AI assistant lets users 'build rules... by just asking' and the product already ships built-in automations like auto-export of finalized reports to QuickBooks, showing some event-triggered automation. However, there is no documentation of a general-purpose, API/webhook-based rule engine where an AI-native user can programmatically define arbitrary event→action rules; the API docs only cover credential/auth flows, not rule creation. Missing for 10: documented API/webhook endpoints for creating custom triggers, examples of user-defined event-action rules beyond a handful of built-in workflows, and independent confirmation these AI-set rules work reliably.

   • [claimed-docs] “Configure workspaces, build rules, and fix your own setup mistakes by just asking”
   • [claimed-docs] “Finalized reports are exported automatically to QuickBooks Online.”
   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “use the OAuth2 authorization code flow to obtain a short-lived access token”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Brex
   Brex~partialclaimed3/10

   Brex offers webhooks for event-driven automation and third-party integration examples (Zapier, Workato, Pipedream) that can implement recurring workflows like a 'Monthly Export of Brex Card Transactions to CSV', but there is no native Brex scheduling/cron API for recurring jobs — the scheduling logic lives entirely in external tools. Missing for 10: a first-party recurring-job/schedule API or documented native cron-like trigger, and any hands-on evidence that AI-native users actually configure recurring automations directly through Brex rather than third-party platforms.

   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Register a URL to receive the webhooks using the [register webhook] endpoint.”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”

   proof ↗⚑ flag

   Expensify—none0/10

   Expensify's API/integration docs describe authentication and one-off actions but no evidence of scheduling recurring jobs or automated workflows on a timer; automatic exports (e.g., QuickBooks) are triggered by report finalization, not user-defined recurring schedules exposed to AI-native automation.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “Finalized reports are exported automatically to QuickBooks Online.”

   proof ↗⚑ flag

Bill pay

1. finance leadRun accounts payable in the same platform — capture invoices, route approvals, and pay vendors by ACH, check, or wire

   weight 2 · round to Brex
   Brex✓fullclaimed8/10

   Brex Bill Pay covers invoice capture (AI extracts itemized detail and matches PO), configurable multi-level approval routing by amount/vendor/role, vendor onboarding via secure payment-detail links, and payment via virtual card, ACH, checks, or wires from a Brex or external bank account — all in one platform, backed by both marketing docs and API endpoints (vendor creation, payments API). missing for 10: independent/hands-on verification of AP workflow reliability (only vendor docs, no third-party case study or user report specific to bill pay), and detail on check-payment mechanics/timing.

   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Enter your vendor's email address and Brex will send a secure link where they can upload their payment details.”
   • [claimed-docs] “Brex AI will capture every itemized detail, suggest the matching PO, and draft a payment.”
   • [claimed-docs] “Create a virtual card instantly to pay by card and earn rewards. Send ACH, checks, and wires from any bank account or a Brex business accoun…”
   • [claimed-docs] “This endpoint creates a new vendor.”
   • [claimed-docs] “Eliminate data entry, automate approvals, and spin up virtual cards in one click to maximize your rewards.”

   proof ↗⚑ flag

   Expensify—none0/10

   The evidence pack covers expense reporting, receipt scanning, corporate cards, travel, and outbound client invoicing (AR), plus accounting syncs to QuickBooks/NetSuite, but contains no mention of vendor bill/invoice capture for payables, AP-specific approval routing, or vendor payment via ACH, check, or wire. This is a distinct AP workflow not evidenced here.

   • [claimed-docs] “Upload your logo, add custom terms, VAT, sales tax, or multiple currencies, and make every invoice look polished and professional.”
   • [claimed-docs] “Offer clients diverse payment options, use customizable and branded invoice templates, and receive realtime payment notifications”
   • [claimed-docs] “Finalized reports are exported automatically to QuickBooks Online.”
   • [claimed-docs] “A QuickBooks Online connection lets you sync Expensify expenses with your accounting system.”
   • [claimed-docs] “Connect your Expensify Workspace to NetSuite to streamline expense syncing, reporting, and accounting.”

   proof ↗⚑ flag

Card controls

1. finance leadRestrict cards by category, merchant, and amount — and the platform auto-locks or declines out-of-policy spend at the point of sale

   weight 3 · round to Brex
   Brex✓fullclaimed7/10

   Brex's product docs explicitly describe auto-blocking out-of-policy purchases with preset rules and limits, auto-enforced spend controls, and a Budgets/Spend Limits API for programmatic control, matching the finance-lead story of restricting and declining spend by policy. Missing for 10: explicit documentation of category/merchant-level rule granularity and independent/hands-on confirmation that point-of-sale declines work as described in practice.

   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”

   proof ↗⚑ flag

   Expensify~partialclaimed3/10

   Expensify markets 'Smart Limits on cards' as a feature, suggesting some spend-control capability, but the evidence pack gives no detail on restricting by category/merchant/amount or on real-time auto-lock/decline at point of sale. Missing for 10: documentation of category/merchant-based restriction rules, confirmation of real-time POS decline/lock behavior, and any independent corroboration of these controls working as described.

   • [claimed-docs] “Smart Limits on cards”

   proof ↗⚑ flag

Card issuance

1. founderIssue physical and virtual corporate cards to the team in minutes, each with its own spend limit

   weight 3 · round to Brex
   Brex✓fullclaimed8/10

   Brex documents physical and virtual card issuance on Mastercard with instant/one-click virtual card creation, per-card/employee spend limits and budgets, mobile app management, and bulk issuance via Workato/Pipedream integrations for teams. This directly matches the founder story of quickly issuing cards with individual limits. Missing for 10: independent hands-on timing verification ("minutes") and no first-party case study explicitly confirming founder-level self-service issuance speed.

   • [claimed-docs] “Physical and virtual cards issued on the leading worldwide network, Mastercard, with acceptance in 210+ countries and territories.”
   • [claimed-docs] “Get a card limit that keeps pace with your business based on financial factors such as revenue or dollars raised.”
   • [claimed-docs] “Manage your card from your phone. Pay with Apple Pay, cancel your card, and view your spend all in one app.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “Eliminate data entry, automate approvals, and spin up virtual cards in one click to maximize your rewards.”

   proof ↗⚑ flag

   Expensify~partialclaimed4/10

   Expensify's spend-management page mentions 'Smart Limits on cards' and the product supports 'bring your own cards,' implying corporate card issuance with limit controls, but there is no documentation of physical vs. virtual card issuance speed, per-card limit setup workflow, or any concrete 'minutes to issue' claim. missing for 10: evidence of physical card issuance process, virtual card creation flow, time-to-issue claims, and per-card individual limit configuration details.

   • [claimed-docs] “Smart Limits on cards”
   • [claimed-docs] “Bring your own cards (BYOC). You don't have to switch corporate cards to use Expensify.”

   proof ↗⚑ flag

Virtual cards

1. finance leadCreate single-vendor virtual cards for SaaS subscriptions and procurement so one compromised vendor never exposes shared credit

   weight 2 · round to Brex
   Brex✓fullclaimed7/10

   Brex documents virtual card creation (docs-14, docs-38), bulk virtual-card issuance for employees/vendors (docs-30, docs-32), and procurement-specific spend limits (docs-9), which together support finance leads creating vendor-specific virtual cards to isolate compromise risk. Missing for 10: explicit documentation of a 'lock card to single vendor' control or vendor-merchant-locking mechanism, and independent/hands-on evidence confirming this containment behavior in practice.

   • [claimed-docs] “Create a virtual card instantly to pay by card and earn rewards. Send ACH, checks, and wires from any bank account or a Brex business accoun…”
   • [claimed-docs] “Eliminate data entry, automate approvals, and spin up virtual cards in one click to maximize your rewards.”
   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “Physical and virtual cards issued on the leading worldwide network, Mastercard, with acceptance in 210+ countries and territories.”

   proof ↗⚑ flag

   Expensify—none0/10

   Evidence shows Expensify Card with 'Smart Limits' and general spend management, but nothing about issuing single-vendor-locked virtual cards for SaaS/procurement use cases. Missing for 10: any documentation of virtual card issuance, vendor-locking/merchant-locking controls, or single-use card workflows for subscriptions.

   • [claimed-docs] “Smart Limits on cards”
   • [claimed-docs] “The Collect workspace is now a flat $5/member/mo – with no annual commitment, even if you don't use the Expensify Card!”

   proof ↗⚑ flag

Agent access

1. ai-native userAn agent can pull uncoded transactions via API or MCP, propose categorizations and policy flags, and push clean coding back for review

   weight 3 · round to Brex
   Brex~partialprobed6/10

   Brex offers a Transactions API to pull transaction data, an official MCP server that lets AI assistants 'manage expenses' and 'review banking transactions,' and AI features (audit/review agents) that categorize spend and flag policy violations (policy field on bookings, out-of-policy detection). However, the evidence never shows a specific 'uncoded transactions' filter/endpoint or an explicit write-back/update-category API call that pushes AI-proposed coding for human review — it only shows general expense/transaction read access and rule-based auto-approval. Missing for 10: explicit uncoded-transaction query capability, explicit category/coding update endpoint, and documented human-review workflow tying AI-proposed codes back to approval.

   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”
   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [probe] “official MCP server documented at https://developer.brex.com/docs/mcp”

   proof ↗⚑ flag

   Expensify~partialcommunity4/10

   Expensify documents a general API with OAuth2 credential-based access (expensify-docs-1/2) and an AI assistant that can categorize/approve expenses via plain language (expensify-docs-3/4), suggesting some machinery exists for pulling and coding transactions, but there is no documentation of an MCP server, no specific 'uncoded transactions' API endpoint, and no described workflow for pushing proposed codings back for human review. Community reports also raise concerns about categorization accuracy historically (expensify-comm-1/4), casting doubt on the 'propose categorizations' reliability. missing for 10: MCP server/connector evidence, explicit API support for uncoded-transaction retrieval and coding-review push-back, verified categorization accuracy at scale.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “Create, categorize, tag, approve, and reject expenses using plain language, no clicking required”
   • [claimed-docs] “Configure workspaces, build rules, and fix your own setup mistakes by just asking”
   • [community] “Expensify does pretty horrible categorization. It does a really good job at determining amount, but approx 70% of the time manages to screw …”
   • [community] “Lots of companies like Expensify, Bills.com, ReceiptHog use MTurk to extract data from financial documents. Accuracy is not 100% guaranteed …”

   proof ↗⚑ flag

Api access

1. developerPull transactions, expenses, and receipts through a documented REST API with OAuth and scoped tokens

   weight 3 · round to Brex
   Brex~partialprobed7/10

   Brex has a documented REST API covering transactions, expenses, receipts (upload/match), budgets, and webhooks, with token-based authentication using scopes (brex-docs-2, brex-docs-4, brex-docs-7, brex-docs-27, brex-docs-19). However, the auth mechanism is described as dashboard-generated 'user tokens' with scopes rather than a full OAuth flow, and an OpenAPI spec could not be located via standard endpoints (brex-probe-2). missing for 10: explicit OAuth 2.0 flow documentation (vs. static token generation), publicly discoverable OpenAPI/swagger spec, and independent developer corroboration of the API working as documented.

   • [claimed-docs] “Sign in to dashboard.brex.com as an account admin or card admin... Click Create Token. Create a name for your token... Choose what level of …”
   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “generate a user token from your Brex dashboard and pass it along in your API call headers”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

   Expensify~partialclaimed5/10

   Expensify documents an Integration Server API with API credentials and OAuth2 authorization code flow for short-lived access tokens, which supports scoped-token access on behalf of users. However, there is no clear evidence of granular scoped tokens, comprehensive REST endpoint documentation for pulling transactions/expenses/receipts specifically, or independent developer corroboration of the API's usability. missing for 10: detailed REST endpoint reference for transactions/receipts, explicit scope definitions, independent developer confirmation of working OAuth flow.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “use the OAuth2 authorization code flow to obtain a short-lived access token”

   proof ↗⚑ flag

Card api

1. developerIssue and manage cards programmatically — create a card with a limit, lock it, update controls — via the public API

   weight 2 · round to Brex
   Brex~partialclaimed4/10

   Evidence shows Brex exposes a broad API surface with a Postman workspace for 'all Brex APIs' and third-party integration recipes (Pipedream, Workato) that issue virtual cards and set spend limits/monthly limits, plus a budgets/spend-limits API. However, there is no first-party documentation of a dedicated Cards API (create/lock/update card controls) in the evidence pack — no cards_api.md or explicit lock/update-controls endpoints are cited, only inferred usage via third-party automation platforms. Missing for 10: a documented Cards API reference showing create-with-limit, lock/freeze, and update-controls endpoints, and any independent hands-on confirmation of programmatic card lifecycle management.

   • [claimed-docs] “we’ll show you how to bulk create virtual cards for your employees”
   • [claimed-docs] “Workato...to enable various use cases including bulk creating users, setting monthly limits for users, issuing virtual cards, and sending ve…”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”

   proof ↗⚑ flag

   Expensify—none0/10

   Evidence shows a general Expensify API exists for expense/report operations with OAuth2 credentials, and mentions Smart Limits on cards as a product feature, but there is no documentation of API endpoints for programmatically creating, locking, or updating card controls/limits. missing for 10: card-issuing API endpoints, card lock/unlock API calls, programmatic control update examples, any developer reference for card management via API.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [claimed-docs] “Smart Limits on cards”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Brex
   Brex~partialprobed5/10

   Brex exposes a broad public API (transactions, budgets, expenses, users, webhooks) and an official MCP server for AI-assistant access, covering many core UI workflows, but there is no evidence of full parity — e.g. no documented API for bill pay approval routing, travel policy management, or card issuance settings that mirror the UI feature set. missing for 10: explicit parity statement, bill-pay/travel/card-management API endpoints, independent confirmation that all UI actions are API-reachable.

   • [claimed-docs] “Sign in to dashboard.brex.com as an account admin or card admin... Click Create Token. Create a name for your token... Choose what level of …”
   • [claimed-docs] “The Brex MCP server lets AI assistants interact directly with your Brex account: manage expenses, look up users, check cards, review banking…”
   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Create a virtual card instantly to pay by card and earn rewards. Send ACH, checks, and wires from any bank account or a Brex business accoun…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.brex.com/llms.txt # Brex Developer API > APIs to build on top of the Brex financial OS. ## T…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.brex.com/openapi.json, https://developer.brex.com/swagger.json, https://developer.…”

   proof ↗⚑ flag

   Expensify~partialprobed3/10

   Evidence confirms Expensify has an API with OAuth2 credential/token flow for acting on behalf of users, but there is no documentation or claim that the API exposes the full breadth of UI capabilities (workspace configuration, travel booking, invoicing, card limits, SmartScan review, etc.) — the probe also shows a broken docs endpoint. missing for 10: evidence of API endpoints covering workspace/rule configuration, travel, invoicing, card management, and any independent confirmation of full UI/API parity.

   • [claimed-docs] “To use the API, you will need to generate API credentials.”
   • [claimed-docs] “To act on behalf of individual Expensify users, use the OAuth2 authorization code flow to obtain a short-lived access token.”
   • [probe] “PROBE docs-md: HTTP 404 at https://integrations.expensify.com/Integration-Server/doc/.md”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Brex
   Brex~partialclaimed4/10

   Brex exposes APIs for transactions, expenses, users, budgets, etc. and a documented Zapier example for CSV export of card transactions, which lets a user pull data out in open formats; but there is no first-party documentation of a comprehensive 'export all your data' feature, bulk archive export, or account-closure data-portability process. missing for 10: a dedicated full-account data export tool, documentation of exporting all data types (not just transactions) in one open format, and any offboarding/portability guidance for leaving the platform.

   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “Monthly Export of Brex Card Transactions to CSV in Google Drive”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “go to the Brex developer workspace which has collections for all of the Brex APIs”

   proof ↗⚑ flag

   Expensify—none0/10

   No evidence of a bulk/open-format data export or account-portability feature; Expensify offers accounting-system connections (QuickBooks, NetSuite) and an API requiring OAuth credentials, but nothing about exporting all user data in open formats for departure from the platform.

   ⚑ flag

Approvals

1. finance leadBuild multi-step approval chains — manager, budget owner, finance — with delegation and escalation when approvers sit on requests

   weight 2 · round to Brex
   Brex~partialclaimed5/10

   Brex documents multi-level, rule-based approval routing (by amount, vendor, employee role) and an AI review agent that auto-approves low-risk items and escalates exceptions, which covers the core approval-chain and escalation concept. However there is no explicit documentation of delegation (e.g., proxy approver when someone is OOO) or a named manager→budget-owner→finance sequential chain structure. Missing for 10: explicit delegation/out-of-office reassignment mechanism, documented sequential role hierarchy (manager, budget owner, finance) rather than generic 'role-based routing', and independent/hands-on confirmation of escalation behavior.

   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “Assign top-line budgets, and track spend instantly, ensuring every dollar is allocated where it has the biggest impact.”

   proof ↗⚑ flag

   Expensify—none0/10

   No evidence pack items describe multi-step approval chains (manager/budget owner/finance), delegation, or escalation logic; documentation covers API auth, SmartScan, integrations, invoicing, and pricing but nothing on approval workflow configuration.

   ⚑ flag

Audit trail

1. finance leadEvery expense carries a full audit trail — edits, approvals, policy checks — that survives an external audit

   weight 2 · round to Brex
   Brex~partialclaimed6/10

   Brex documents policy-violation flags on bookings, multi-level approval routing, budget/spend limits, and a dedicated 'audit agent' that monitors and categorizes policy violations — all elements that would feed an audit trail. However, there is no explicit documentation of an immutable, exportable audit log capturing edit history, approval timestamps, and policy-check results in a form built for external audit review. missing for 10: explicit immutable/exportable audit-log documentation, evidence of edit-history tracking per expense, independent confirmation the trail survives external audit scrutiny.

   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Your audit agent monitors company expenses according to your internal processes and categorizes potential violations by risk level.”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”

   proof ↗⚑ flag

   Expensify—none0/10

   The evidence pack shows approval workflows (AI-driven approve/reject) and accounting sync (QuickBooks, NetSuite) but no documentation of an immutable audit trail, edit/approval history log, or audit-ready reporting that would survive external audit scrutiny. Community evidence focuses on categorization accuracy and billing complaints, not audit-trail integrity.

   ⚑ flag

Policy engine

1. finance leadCodify our expense policy — limits by category, role, and context — so in-policy expenses auto-approve and only exceptions reach a human

   weight 3 · round to Brex
   Brex✓fullclaimed8/10

   Brex documents policy codification by category, role, vendor, and context (limits, spend rules, multi-level approval routing by amount/vendor/role) and explicit auto-approval of in-policy items with exceptions escalated to humans via its review/audit AI agents. Budgets API and policy-violation flags further support programmatic enforcement. Missing for 10: independent/hands-on verification of auto-approval accuracy and no detailed docs on granular category-level rule configuration UI.

   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”
   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”
   • [claimed-docs] “Stop waiting for people to categorize, review, or approve spend. Let AI agents do it instantly, based on your policies and with total transp…”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”

   proof ↗⚑ flag

   Expensify~partialclaimed4/10

   Evidence shows some policy-adjacent features (Smart Limits on cards, multi-level GL coding, and 'build rules' via AI assistant) but no explicit documentation of a full policy engine enforcing limits by category/role/context with automatic in-policy approval and exception routing to a human approver. missing for 10: documented approval workflow/exception routing, role-based limit configuration, and evidence of auto-approval logic actually functioning as described.

   • [claimed-docs] “Smart Limits on cards”
   • [claimed-docs] “Multi-level GL coding”
   • [claimed-docs] “Configure workspaces, build rules, and fix your own setup mistakes by just asking”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Brex—none0/10

   No evidence pack items mention data residency, regional storage options, or any control over where data is stored; Brex evidence covers financial product features, APIs, and MCP integration only.

   ⚑ flag

   Expensify—none0/10

   No evidence in the pack addresses data residency, regional storage options, or any data-location controls for Expensify; all citations concern API auth, product features, integrations, or general community complaints unrelated to data residency.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Brex—none0/10

   No evidence pack item addresses AI training data usage, opt-out settings, or a data-privacy policy regarding model training; the evidence only covers API/product features and unrelated community complaints about account closures.

   ⚑ flag

   Expensify—none0/10

   No evidence of any AI-training opt-out, data-use control, or privacy settings related to AI model training; in fact community evidence shows receipt data was historically routed to third-party human contractors (MTurk) without confidentiality protections, suggesting weak data-handling controls generally.

   • [community] “TL;DR: Expensify's deceptive mechanical turk army may have resulted in me coming within seconds of losing $30k, giving away PII to low-paid …”
   • [community] “Some of the receipts had enough info to identify people - store card numbers, buyer phone number, etc. My wife occasionally does mturk and l…”
   • [community] “Lots of companies like Expensify, Bills.com, ReceiptHog use MTurk to extract data from financial documents. Accuracy is not 100% guaranteed …”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Brex—none0/10

   No evidence pack item discusses data retention, deletion policies, or AI data usage/training controls specific to AI-native workflows; the API, MCP, and product docs focus on functionality (expenses, cards, bill pay) rather than privacy/data lifecycle controls. Missing for 10: any documentation on data retention periods, deletion requests, opt-out of AI training, or data residency/handling policies.

   ⚑ flag

   Expensify—none0/10

   No evidence in the pack of any user-facing controls to set data retention periods or delete data/AI interaction history; only community reports raise privacy concerns around SmartScan's use of contractor-based data extraction, which is unrelated to retention/deletion controls.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Brex—none0/10

   No evidence in the pack mentions telemetry, usage tracking, or an opt-out/privacy control mechanism for AI-native users; the docs focus on APIs, webhooks, MCP server, and financial products with no privacy-posture disclosures.

   ⚑ flag

   Expensify—none0/10

   No evidence of any telemetry opt-out or AI usage-tracking control; evidence pack covers unrelated features (API, integrations, expense management) and community complaints about accuracy/billing, none addressing privacy/telemetry controls for AI-native usage.

   ⚑ flag

Mileage perdiem

1. employeeLog mileage with map-based distance and claim per-diem rates without building the expense by hand

   weight 2 · round drawn
   Brex—none0/10

   No evidence in the pack mentions mileage tracking, GPS/map-based distance calculation, or per-diem rate claims; Brex's expense documentation focuses on card transactions, receipt upload/matching, and policy enforcement but never describes mileage or per-diem automation. This is a fair capability to expect from an expense management product, so absence of evidence means none rather than na.

   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “Manage global spend and close the books in real time — with unmatched automation of manual expense work.”

   proof ↗⚑ flag

   Expensify—none0/10

   The evidence pack covers SmartScan receipt capture, categorization, integrations (QuickBooks, NetSuite), travel booking, and invoicing, but contains no mention of mileage tracking, map-based distance calculation, or per-diem rate claims. This is a fair axis for an expense management product like Expensify, but no supporting evidence exists in the pack. Missing for 10: any documentation or community mention of mileage/distance logging or per-diem rate automation.

   ⚑ flag

Receipt capture

1. employeeSnap a photo or forward an email and the platform OCRs the receipt and files it against the right transaction

   weight 3 · round to Brex
   Brex~partialclaimed6/10

   Brex supports receipt upload with automatic matching to expenses via API ("Upload receipt and match automatically", pre-signed S3 URL matching to existing expenses) and AI agents that 'fetch receipts' automatically, but there's no explicit evidence of OCR technology, photo-snap mobile capture flow, or email-forwarding-to-receipt-filing as described in the story. missing for 10: explicit OCR mention, mobile photo-capture UX details, email-forwarding ingestion mechanism, independent/hands-on confirmation of accuracy.

   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”

   proof ↗⚑ flag

   Expensify!disputedcontradicted5/10

   Expensify's SmartScan is documented to OCR receipts in real time (merchant, date, total, currency) via camera capture, but hands-on community reports contradict the polish of this claim: users report categorization is wrong ~70% of the time unless obvious, that scans took ~20 minutes to process, and that outsourced (MTurk) human review was used behind the scenes with data accuracy not guaranteed. There is also no evidence in the pack for the 'forward an email' capture path. missing for 10: evidence of email-forward receipt capture, independent verification of categorization/filing accuracy against transactions, resolution of the community-reported OCR/categorization failures.

   • [claimed-docs] “Open the app, tap the camera, and SmartScan reads the merchant, date, total, and currency automatically.”
   • [claimed-docs] “SmartScan extracts receipt data in realtime, with no batch processing or overnight delays.”
   • [community] “Expensify does pretty horrible categorization. It does a really good job at determining amount, but approx 70% of the time manages to screw …”
   • [community] “Lots of companies like Expensify, Bills.com, ReceiptHog use MTurk to extract data from financial documents. Accuracy is not 100% guaranteed …”
   • [community] “I used expensify and it took like 20 mins to process a few receipt images.. I ended up doing it myself anyway.”

   proof ↗⚑ flag

Receipt matching

1. employeeReceipts match to card transactions automatically — with e-receipts pulled from integrations — and I get nudged only when one is genuinely missing

   weight 2 · round to Brex
   Brex~partialclaimed6/10

   Brex's API/docs confirm automatic receipt-to-transaction matching ("Upload receipt and match automatically" and pre-signed S3 upload that tries to match existing expenses), and its AI feature page claims agents can 'fetch receipts' and file expenses automatically, plus a review agent that 'follows up with anyone out of compliance.' However, there's no explicit evidence of e-receipts being pulled automatically from third-party integrations (e.g., travel/vendor e-receipt feeds) nor documentation describing smart nudging logic that only triggers when a receipt is genuinely missing rather than generic compliance follow-ups. missing for 10: explicit e-receipt integration sourcing, documented logic for suppressing false-positive missing-receipt nudges, independent user confirmation of matching accuracy.

   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Your review agent auto-approves low-risk expenses and requests, escalates exceptions, and follows up with anyone out of compliance.”

   proof ↗⚑ flag

   Expensify~partialcommunity4/10

   Expensify documents SmartScan for automatic receipt data extraction (docs-6, docs-18) and supports bringing your own corporate cards (docs-5, docs-10), which implies some card-transaction integration, but there is no direct evidence describing automatic receipt-to-transaction matching, e-receipt pulling from vendor integrations, or a 'nudge only when missing' notification flow. Community reports also flag categorization/accuracy issues that could undercut a fully automated match (comm-1, comm-4). Missing for 10: explicit documentation of automatic receipt-card matching logic, e-receipt integration pulls, and a missing-receipt notification/nudge feature.

   • [claimed-docs] “Open the app, tap the camera, and SmartScan reads the merchant, date, total, and currency automatically.”
   • [claimed-docs] “SmartScan extracts receipt data in realtime, with no batch processing or overnight delays.”
   • [claimed-docs] “Bring your own cards (BYOC). You don't have to switch corporate cards to use Expensify.”
   • [claimed-docs] “Smart Limits on cards”
   • [community] “Expensify does pretty horrible categorization. It does a really good job at determining amount, but approx 70% of the time manages to screw …”
   • [community] “Lots of companies like Expensify, Bills.com, ReceiptHog use MTurk to extract data from financial documents. Accuracy is not 100% guaranteed …”

   proof ↗⚑ flag

Domestic

1. employeeSubmit an out-of-pocket expense and get reimbursed by direct deposit in days, tracked from submission to payout

   weight 3 · round to Brex
   Brex~partialclaimed5/10

   Brex's docs confirm out-of-pocket expense submission (receipt upload/matching in brex-docs-7/27) and AI-driven automatic reimbursement filing (brex-docs-23), implying an end-to-end expense workflow, but there is no explicit documentation of direct-deposit payout mechanics, reimbursement timing ('days'), or a submission-to-payout tracking status view. missing for 10: explicit direct-deposit reimbursement flow, payout SLA/timing details, and a visible tracking/status dashboard for reimbursement progress.

   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “AI assistants do employees' expenses for them, writing memos, fetching receipts, offering policy help, even filing reimbursements automatica…”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”

   proof ↗⚑ flag

   Expensify—none0/10

   The evidence pack covers receipt scanning, categorization, accounting integrations, and pricing, but contains no documentation of the direct-deposit reimbursement flow, payout timing, or tracking from submission to payout. Community items focus on categorization accuracy and billing complaints, not reimbursement speed or tracking. missing for 10: reimbursement/payout documentation, direct deposit setup details, submission-to-payout tracking evidence.

   ⚑ flag

International

1. finance leadReimburse employees abroad in their local currency without running a separate international payments process

   weight 2 · round drawn
   Brex—none0/10

   Evidence covers global card acceptance (210+ countries), bill pay wires 'in more currencies' for vendor payments, and general 'global spend' messaging, but nothing specifically addresses reimbursing employees abroad in their local currency or eliminating a separate international payments process for reimbursements.

   ⚑ flag

   Expensify—none0/10

   The evidence pack contains no mention of multi-currency reimbursement or international payment processing to employees abroad; it covers receipt scanning, accounting integrations, invoicing, and API auth, but nothing about local-currency reimbursement or cross-border payouts.

   ⚑ flag

Budgets

1. finance leadAllocate budgets to teams and projects and have card limits and approvals actually enforce them

   weight 2 · round to Brex
   Brex✓fullclaimed8/10

   Brex documents budgets/spend limits API and dashboard features for assigning top-line budgets, auto-enforced spend limits, policy-based blocking of out-of-policy purchases, and multi-level approval routing, directly matching the finance-lead's need to allocate budgets and have limits/approvals enforce them. missing for 10: independent/hands-on evidence confirming enforcement works reliably in practice (community evidence only covers account closures, not budget/approval enforcement), and no case study showing team/project-level allocation granularity in real use.

   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Set rules for how employees can spend, what they need to document, and who needs to approve. Brex AI applies them to every transaction.”
   • [claimed-docs] “Create limits for stipends, travel, procurement, and more. Auto-enforced controls empower employees to spend with confidence.”
   • [claimed-docs] “Assign top-line budgets, and track spend instantly, ensuring every dollar is allocated where it has the biggest impact.”
   • [claimed-docs] “Tailor multi-level approval flows based on amount, vendor, employee role, and more — and Brex will route for you automatically to ensure the…”
   • [claimed-docs] “Automatically block out-of-policy purchases, with preset rules and limits.”

   proof ↗⚑ flag

   Expensify~partialclaimed3/10

   Evidence only shows generic 'Smart Limits on cards' and 'multi-level GL coding' features, with no documentation of allocating budgets specifically to teams/projects or details on how approvals/card limits enforce those budgets end-to-end. Missing for 10: team/project-level budget allocation workflows, approval-chain enforcement mechanics, and any independent verification that limits actually block overspend.

   • [claimed-docs] “Smart Limits on cards”
   • [claimed-docs] “Multi-level GL coding”

   proof ↗⚑ flag

Dashboards

1. founderSee company spend in real time — by team, category, and merchant — the day it happens, not when statements land

   weight 3 · round to Brex
   Brex✓fullclaimed7/10

   Brex provides real-time spend tracking via the mobile app ("view your spend all in one app"), budgets API tracked instantly by team/cost-center, transactions API for granular transaction-level data, and webhooks for live event notifications, plus marketing claims of managing spend and closing books in real time. Category/department/merchant segmentation is supported via cost_center_id/department_id filters and the transactions API, though merchant-level breakdown isn't explicitly documented as a dashboard feature. Missing for 10: explicit merchant-level dashboard breakdown documentation, independent/hands-on verification that spend updates instantly rather than with delay, and no clear evidence of a dedicated real-time analytics dashboard beyond mobile app spend view.

   • [claimed-docs] “The transactions API lets you view your transactions, accounts, and statements.”
   • [claimed-docs] “The budgets API lets you manage your Brex Budgets and Spend Limits.”
   • [claimed-docs] “Assign top-line budgets, and track spend instantly, ensuring every dollar is allocated where it has the biggest impact.”
   • [claimed-docs] “Manage your card from your phone. Pay with Apple Pay, cancel your card, and view your spend all in one app.”
   • [claimed-docs] “Manage global spend and close the books in real time — with unmatched automation of manual expense work.”
   • [claimed-docs] “Added filter query parameters to List users: `name`, `email[]`, `status[]`, `manager_id[]`, `department_id[]`, `location_id[]`, `title_id[]`…”
   • [claimed-docs] “Register an endpoint to start receiving selected webhook events”

   proof ↗⚑ flag

   Expensify!disputedcontradicted4/10

   Expensify claims real-time capture via SmartScan (data extracted 'in realtime, no batch processing') and offers categorization/workspaces, which would support real-time spend visibility by merchant and category, but independent user reports directly contradict the categorization accuracy claim — one reports ~70% miscategorization and use of outsourced human labor (MTurk) rather than reliable automated categorization, undermining the 'by category' promise. Missing for 10: evidence of a real-time company-wide spend dashboard broken down by team/department, and any rebuttal or fix to the categorization accuracy complaints.

   • [claimed-docs] “SmartScan extracts receipt data in realtime, with no batch processing or overnight delays.”
   • [claimed-docs] “Open the app, tap the camera, and SmartScan reads the merchant, date, total, and currency automatically.”
   • [community] “Expensify does pretty horrible categorization. It does a really good job at determining amount, but approx 70% of the time manages to screw …”
   • [community] “Lots of companies like Expensify, Bills.com, ReceiptHog use MTurk to extract data from financial documents. Accuracy is not 100% guaranteed …”
   • [community] “TL;DR: Expensify's deceptive mechanical turk army may have resulted in me coming within seconds of losing $30k, giving away PII to low-paid …”

   proof ↗⚑ flag

Booking

1. employeeBook flights and hotels in-platform with travel policy applied at booking time, not expensed and argued about later

   weight 2 · round to Brex
   Brex✓fullcommunity8/10

   Brex Travel is a first-party product explicitly combining booking with 'global inventory and auto-enforced expense policies on one platform' (brex-docs-39), and the API changelog shows booking objects carry a `policy` field flagging out-of-policy violations at booking time (brex-docs-6), confirming policy is applied during booking rather than after. Community evidence corroborates actual usage of Brex Travel for booking ('Brex Travel was luxurious') (brex-comm-1). Missing for 10: independent review of the booking flow's policy enforcement UX and more detail on flight/hotel inventory breadth.

   • [claimed-docs] “Simplify travel with global inventory and auto-enforced expense policies on one platform.”
   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”
   • [community] “I really liked the dynamic credit card generator, and Brex Travel was luxurious...”

   proof ↗⚑ flag

   Expensify~partialclaimed5/10

   Expensify Travel offers in-platform booking of flights, hotels, cars, and rail, positioned to avoid a 'pile of receipts,' but the evidence doesn't confirm that travel policy is enforced/applied at the moment of booking (e.g., blocking out-of-policy fares) rather than after the fact. Missing for 10: explicit documentation of policy rules enforced at booking time, approval workflows integrated into the booking flow, and independent/hands-on confirmation of the travel booking experience.

   • [claimed-docs] “Expensify's corporate travel management solution means business trips don't end in a pile of receipts.”
   • [claimed-docs] “Book flights, hotels, cars, rail”

   proof ↗⚑ flag

Trip expenses

1. employeeA trip's expenses — bookings, cards, receipts — collect themselves into one itinerary-linked report

   weight 1 · round to Brex
   Brex~partialclaimed5/10

   Brex Travel and expense docs show pieces of this workflow — bookings carry policy metadata (brex-docs-6), corporate cards integrate with the platform (brex-docs-20/21), and receipts auto-match to expenses (brex-docs-7/brex-docs-27) — and the Travel product page claims to "simplify travel with global inventory and auto-enforced expense policies on one platform" (brex-docs-39). However, no evidence explicitly describes a trip/itinerary object that automatically aggregates bookings, card transactions, and receipts into a single itinerary-linked expense report for the employee. Missing for 10: explicit itinerary/trip-report generation feature, documentation of automatic booking-to-card-to-receipt linkage within one report, and any hands-on/independent confirmation of this consolidated view.

   • [claimed-docs] “Simplify travel with global inventory and auto-enforced expense policies on one platform.”
   • [claimed-docs] “Added `policy` to booking objects, exposing whether a booking was out of policy and which travel policy rules it violated.”
   • [claimed-docs] “The uri will be a pre-signed S3 URL allowing you to upload the receipt securely... we will try to match the receipt with existing expenses.”
   • [claimed-docs] “Upload receipt and match automatically.”
   • [claimed-docs] “Physical and virtual cards issued on the leading worldwide network, Mastercard, with acceptance in 210+ countries and territories.”

   proof ↗⚑ flag

   Expensify!disputedcontradicted5/10

   Expensify documents travel booking (flights/hotels/cars/rail) alongside SmartScan receipt capture and BYOC card support, which together could populate a trip report, but there's no explicit documentation of itinerary-linked auto-consolidation tying bookings+card charges+receipts into one report. Community evidence directly contradicts the 'automatic, accurate' framing of SmartScan: users report ~70% miscategorization and that receipt data was processed by low-paid, unvetted Mechanical Turk workers who could see PII, undermining the 'collect themselves' promise. Missing for 10: explicit itinerary-report linking mechanism, and resolution of the accuracy/privacy contradiction in receipt processing.

   • [claimed-docs] “Expensify's corporate travel management solution means business trips don't end in a pile of receipts.”
   • [claimed-docs] “Book flights, hotels, cars, rail”
   • [claimed-docs] “Open the app, tap the camera, and SmartScan reads the merchant, date, total, and currency automatically.”
   • [claimed-docs] “SmartScan extracts receipt data in realtime, with no batch processing or overnight delays.”
   • [claimed-docs] “Bring your own cards (BYOC). You don't have to switch corporate cards to use Expensify.”
   • [community] “Expensify does pretty horrible categorization. It does a really good job at determining amount, but approx 70% of the time manages to screw …”
   • [community] “TL;DR: Expensify's deceptive mechanical turk army may have resulted in me coming within seconds of losing $30k, giving away PII to low-paid …”
   • [community] “Some of the receipts had enough info to identify people - store card numbers, buyer phone number, etc. My wife occasionally does mturk and l…”
   • [community] “Lots of companies like Expensify, Bills.com, ReceiptHog use MTurk to extract data from financial documents. Accuracy is not 100% guaranteed …”

   proof ↗⚑ flag