Ramp vs Expensify
Expensify
Expensify, Inc.
Ramp wins · 38–1 (11 drawn)
Accounting close — stories about accounting close in this arenaAccounting close
Stories about accounting close in this arena
Accounting sync
finance leadTransactions sync to QuickBooks, NetSuite, or Xero with GL account, class, and department mappings I control
weight 3 · round drawnRamp documents native QuickBooks, NetSuite, and Xero integrations with transaction sync, GL account coding, and reconciliation/matching tools (ramp-docs-25, ramp-docs-26, ramp-docs-27, ramp-docs-28, ramp-docs-32), plus multi-entity sync (ramp-docs-24). However, none of the evidence explicitly describes finance-lead control over class or department dimension mappings, only general GL account coding and reconciliation. Missing for 10: explicit documentation of class/department mapping configuration and user control over those field mappings during sync.
- [claimed-docs] “Sync your transaction and reimbursement data to multiple entities in a single step, for less work.”
- [claimed-docs] “Eliminate manual verification with Ramp's 3-way matching of purchase orders, receipts, and invoices”
- [claimed-docs] “Gain confidence in your numbers with Ramp's built-in reconciliation tool that verifies balances between both platforms”
- [claimed-docs] “Process vendor bills from start to finish: initiate your process in either NetSuite or Ramp, and complete it with Ramp payments”
- [claimed-docs] “initiate your process in either Xero or Ramp and complete it with Ramp payments”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
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”
Close
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 RampRamp documents real-time receipt capture, auto-fill of merchant/category/memo at swipe, GL coding, and auto-approval within policy (ramp-docs-8, ramp-docs-32, ramp-docs-21), plus reconciliation/3-way matching tools for close (ramp-docs-25, ramp-docs-26). This directly matches the story of spend being coded at time-of-swipe rather than reconstructed later. Missing for 10: independent/hands-on verification of accuracy claims and no explicit end-to-end month-end close workflow walkthrough beyond marketing copy.
- [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
- [claimed-docs] “Ramp gives you infinite teammates who work around the clock—flagging fraud, coding expenses, and enforcing policy.”
- [claimed-docs] “Eliminate manual verification with Ramp's 3-way matching of purchase orders, receipts, and invoices”
- [claimed-docs] “Gain confidence in your numbers with Ramp's built-in reconciliation tool that verifies balances between both platforms”
- [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
Expensifydisputedcontradicted5/10Expensify'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.”
Multi entity
finance leadRun multiple legal entities and currencies in one account with consolidated reporting and per-entity books
weight 2 · round to RampRamp has a dedicated multi-entity page indicating it can sync transactions and reimbursement data across multiple entities in one step, and reimbursements support 70+ countries/40 currencies, suggesting multi-entity/multi-currency support. However, the evidence pack lacks detail on consolidated reporting dashboards or explicit per-entity books/chart-of-accounts separation. Missing for 10: explicit consolidated reporting evidence, per-entity ledger/books detail, multi-currency accounting (not just reimbursement) specifics.
- [claimed-docs] “Sync your transaction and reimbursement data to multiple entities in a single step, for less work.”
- [claimed-docs] “Reimburse employees with confidence in more than 70 countries and 40 currencies, knowing they can be paid in two days or less in their local…”
Expensifynone0/10No 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.”
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to RampRamp hosts a live, HTTP-200 llms.txt index (ramp-probe-1) plus a full suite of llms-guides/*.txt agent-oriented docs covering getting started, auth, webhooks, CLI, and MCP for AI agents (ramp-docs-1 through ramp-docs-6), directly matching the story of pointing an agent at machine-readable docs. Missing for 10: independent third-party confirmation that agents actually consume/parse this index successfully in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to RampRamp exposes a public API (OAuth token auth) and an official CLI that can be scripted 'from your terminal or AI agent' (ramp-docs-1, ramp-docs-2, ramp-docs-4, ramp-probe-3), which supports headless/automated use, and webhooks enable event-driven automation (ramp-docs-3). However, there is no explicit documentation of running Ramp in a CI pipeline, no CI/CD examples, and no mention of non-interactive auth flows suited for CI (e.g., service accounts) — missing for 10: explicit CI/CD usage examples, headless auth flow documentation for automated pipelines, independent confirmation of CLI use in CI.
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
- [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
- [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”
- [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
- [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
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”
ai-native userConnect an agent via an official MCP server
weight 3 · round to RampRamp documents an official MCP server ('Ramp MCP') letting users connect AI assistants like ChatGPT and Claude to query data and take actions, with a dedicated support article and docs page confirming it exists and works (e.g., locking a card, finding missing receipts). This is corroborated by both first-party docs and a support-article walkthrough with concrete example prompts. Missing for 10: independent third-party (non-Ramp) hands-on review of the MCP server's reliability.
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
- [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
- [claimed-docs] “Lock my card — I can't find it.”
- [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
Expensifynone0/10Expensify 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”
ai-native userUse an official CLI
weight 2 · round to RampRamp documents an official CLI (docs.ramp.com/llms-guides/cli.txt and github.com/ramp-public/ramp-cli) explicitly designed for AI-native use, allowing OAuth authentication, expense management, bill approval, and travel booking 'from your terminal or AI agent,' and positions it alongside MCP for agentic workflows. Missing for 10: independent/hands-on verification of CLI usage and more detail on command coverage/maturity beyond first-party docs.
- [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”
- [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
- [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
ai-native userDrive the product through a documented public API
weight 3 · round to RampRamp documents a public REST API (Transactions, OAuth 2.0 authorization, webhooks) with a machine-readable llms.txt index, plus a CLI and MCP server explicitly built for driving Ramp actions programmatically or via AI agents. This covers documented public API access comprehensively across auth, data retrieval, and actions. Missing for 10: independent third-party developer reports/hands-on confirmation of API robustness beyond Ramp's own docs.
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
- [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
- [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
- [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
- [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
- [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
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”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to RampRamp's OAuth 2.0 implementation provides granular scoped permissions for API access (ramp-docs-2), and dedicated Agent Cards plus MCP/CLI docs show explicit support for issuing scoped credentials/action authority to AI agents specifically (ramp-docs-6, ramp-docs-7, ramp-docs-5). This directly matches the least-privilege-for-agents story. Missing for 10: independent/hands-on verification of scope granularity in practice and explicit documentation of per-agent credential revocation/audit trails.
- [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
- [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
- [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
Expensifynone0/10Expensify'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”
ai-native userBuild against official SDKs
weight 2 · round drawnRampnone0/10Evidence shows Ramp offers a REST API, OAuth, webhooks, a CLI, and an MCP server, but nowhere mentions official client SDKs (e.g., Python, JS, Go libraries) for building against Ramp's API. Missing for 10: any documentation of official SDKs/client libraries in specific languages, package registry listings, or SDK-specific quickstart guides.
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
- [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
- [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
Expensifynone0/10Evidence 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”
ai-native userSubscribe to events via webhooks
weight 2 · round to RampRamp docs explicitly describe webhooks for real-time event notifications from a Ramp account, directly matching the story. Missing for 10: no details on event types/payload schema, delivery guarantees, or independent/hands-on verification of webhook reliability.
- [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
Expensifynone0/10The 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.
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to RampRamp Intelligence and related features surface AI-generated recommendations (recommended actions on spend requests, auto-coding of expenses, fraud flagging, contract parsing) directly inside the product, and Ramp MCP lets users query data and get AI-driven suggestions like drafting reminders for missing receipts. missing for 10: independent/hands-on validation of insight quality and a fuller first-party doc detailing the breadth of proactive insights beyond the marketing snippets and MCP examples.
- [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
- [claimed-docs] “Ramp gives you infinite teammates who work around the clock—flagging fraud, coding expenses, and enforcing policy.”
- [claimed-docs] “Drop in a contract or screenshot and Ramp's AI parses details and auto-fills the request form”
- [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
- [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
Expensifydisputedcontradicted5/10Expensify 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 …”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to RampRamp offers webhooks, an API, MCP server, and CLI that agents can use to take actions like locking cards or drafting reminders, which supports agentic workflows, but these are largely triggered interactions rather than documented autonomous/scheduled background automations that run without a prompting event. Rules-based workflows (e.g., procurement routing, policy enforcement) run automatically but are conditional business rules, not general-purpose autonomous agent automations. missing for 10: explicit support for scheduled/recurring autonomous agent runs, evidence of persistent background agent execution without user-initiated trigger, and independent confirmation of such autonomous operation.
- [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
- [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
- [claimed-docs] “Lock my card — I can't find it.”
- [claimed-docs] “Rules-based workflows route requests to the right stakeholders automatically based on vendor type, spend category, or dollar amount”
- [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
- [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
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”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to ExpensifyRamp offers agentic automation ('infinite teammates' handling fraud flagging, coding, policy enforcement) and lets users delegate tasks via natural language through its MCP integration (e.g., 'Find transactions with missing receipts...', 'Lock my card'), but these delegated-task examples run through external AI assistants (ChatGPT, Claude) connected via MCP rather than a native, built-in conversational assistant inside the Ramp product itself. Missing for 10: evidence of an in-app chat/assistant UI natively embedded in Ramp (not via MCP to third-party LLMs), and independent confirmation of task delegation working end-to-end within the product.
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
- [claimed-docs] “Ramp gives you infinite teammates who work around the clock—flagging fraud, coding expenses, and enforcing policy.”
- [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
- [claimed-docs] “Lock my card — I can't find it.”
- [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
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”
ai-native userOperate the product with natural-language commands
weight 2 · round to RampRamp ships an official MCP server and CLI explicitly designed for natural-language operation ("query Ramp data and take actions with natural language"), with documented examples like locking a card or drafting reminder messages via plain-English commands, plus a CLI usable directly by AI agents. Missing for 10: independent/hands-on validation beyond vendor docs and no broad third-party confirmation of reliability across all agentic actions.
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
- [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
- [claimed-docs] “Lock my card — I can't find it.”
- [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”
- [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
- [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
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”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnRampnone0/10Evidence shows Ramp has API docs, OAuth guides, webhooks, and a machine-readable llms.txt index, but nothing describes an interactive API reference with runnable/live code examples (e.g., a Swagger/Postman-style explorer). Missing for 10: any mention of an interactive console or runnable example feature in the docs.
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
- [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
Expensifynone0/10Evidence 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”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to RampRamp exposes a machine-readable llms.txt index for its Developer API docs, which is AI-native friendly, but there's no evidence of an actual OpenAPI/Swagger spec file being published or downloadable. Missing for 10: an explicit OpenAPI/Swagger spec document, a documented download endpoint, or third-party confirmation that the API schema is available in a standard machine-readable spec format.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
Expensifynone0/10Evidence 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”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnRampnone0/10No evidence of a sandbox/test environment for Ramp's API, CLI, or MCP integrations; all docs reference live transactions, cards, and production data flows. Missing for 10: any mention of a sandbox/test mode, test API keys, or non-production environment for developers/AI agents.
Expensifynone0/10No 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.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnRampnone0/10Evidence shows Ramp has an API, OAuth, webhooks, CLI, and MCP server, but nothing in the pack documents API versioning practices or a formal deprecation policy. missing for 10: versioning scheme documentation, deprecation policy/notice process, changelog or migration guidance for breaking changes.
Expensifynone0/10Evidence 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”
Ai automation — stories about ai automation in this arenaAi automation
Stories about ai automation in this arena
Ai coding
ai-native userAI codes and audits expenses for me — reading receipts, suggesting categories and memos, and catching duplicates or fraud
weight 2 · round to RampRamp's docs show automatic receipt capture with AI-filled memos/categories (ramp-docs-8, ramp-docs-32), OCR line-item accuracy (ramp-docs-16), fraud flagging and expense coding via 'infinite teammates' AI (ramp-docs-21), duplicate/missing-item detection via MCP prompts (ramp-docs-29), and policy/match-based auditing (ramp-docs-17, ramp-docs-25, ramp-docs-9). This covers reading receipts, categorization/memo suggestion, and fraud/duplicate catching across first-party marketing and support docs. Missing for 10: independent/hands-on verification of accuracy claims and explicit named 'duplicate detection' feature documentation beyond marketing copy.
- [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
- [claimed-docs] “Ramp's OCR captures each detail and line item with 99% accuracy.”
- [claimed-docs] “Ramp checks every line item with two and three-way matching, so you know if something's off before sending.”
- [claimed-docs] “Ramp gives you infinite teammates who work around the clock—flagging fraud, coding expenses, and enforcing policy.”
- [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
- [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
Expensifydisputedcontradicted4/10Expensify 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 …”
Ai policy
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 RampRamp's MCP/AI assistant explicitly chases missing receipts with drafted reminders (ramp-docs-29, ramp-docs-13), and policy enforcement happens conversationally with recommended actions and pre-spend policy visibility (ramp-docs-9, ramp-docs-10, ramp-docs-18). This covers the core of the story, though 'explaining declines' and answering 'can I expense this?' pre-spend are only indirectly evidenced via policy-status/recommended-action features rather than a direct conversational decline-explanation example. Missing for 10: independent/hands-on confirmation of the assistant explaining a specific decline conversationally, and an explicit pre-spend Q&A example beyond travel-booking policy status.
- [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
- [claimed-docs] “Let Ramp send reminders for missing items or request repayments for you.”
- [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
- [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
- [claimed-docs] “See policy status for every option. No digging through static policy PDFs or wondering if trips will get rejected.”
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
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 …”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to RampRamp's API/MCP/CLI let users query and act on data programmatically (e.g., finding all transactions missing receipts across the last 14 days) and sync data to multiple entities in one step, suggesting some bulk-style automation. However, there is no explicit documentation of true bulk endpoints (e.g., batch update/create across many items) or bulk card issuance/approval workflows via API. Missing for 10: explicit bulk API endpoints, batch transaction/approval operations, and independent confirmation of bulk-scale automation.
- [claimed-docs] “Sync your transaction and reimbursement data to multiple entities in a single step, for less work.”
- [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”
Expensifynone0/10Evidence 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”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to RampRamp supports webhooks for real-time event notifications, rules-based workflows that automatically route requests based on vendor/category/amount, spend limits and merchant blocking enforced pre-spend, automatic reminders/repayment requests, and auto-approval of in-policy transactions without manual filing — collectively demonstrating rule-driven automatic actions on events across its expense/procurement/card platform. Missing for 10: a documented general-purpose 'if-this-then-that' custom rule builder exposed to end users (vs. built-in policy categories) and independent/hands-on corroboration of these automation flows working as described.
- [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
- [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
- [claimed-docs] “Create personalized workflows that only notify the right people, based on spend amount or team role, and keep visibility high.”
- [claimed-docs] “Let Ramp send reminders for missing items or request repayments for you.”
- [claimed-docs] “Rules-based workflows route requests to the right stakeholders automatically based on vendor type, spend category, or dollar amount”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
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”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnRampnone0/10Ramp's automation is event-driven (webhooks) or rules-based (route requests, reminders, auto-rebooking) rather than a documented recurring-job/scheduler capability that an AI agent could invoke via API, MCP, or CLI. No evidence of cron-like or interval-based scheduling for workflows.
Expensifynone0/10Expensify'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.”
Bills ap — stories about bills ap in this arenaBills ap
Stories about bills ap in this arena
Bill pay
finance leadRun accounts payable in the same platform — capture invoices, route approvals, and pay vendors by ACH, check, or wire
weight 2 · round to RampRamp's Bill Pay evidence shows invoice OCR capture (99% accuracy), 2/3-way matching, and rules-based approval routing (ramp-docs-16, ramp-docs-17, ramp-docs-23), plus 'complete it with Ramp payments' in NetSuite/Xero integrations (ramp-docs-27, ramp-docs-28) confirming payment execution within the platform. However, none of the evidence explicitly states support for ACH, check, or wire as distinct payment rails for vendor payments. Missing for 10: explicit documentation of ACH/check/wire payment method options, and independent/hands-on confirmation of the full AP workflow.
- [claimed-docs] “Ramp's OCR captures each detail and line item with 99% accuracy.”
- [claimed-docs] “Ramp checks every line item with two and three-way matching, so you know if something's off before sending.”
- [claimed-docs] “Rules-based workflows route requests to the right stakeholders automatically based on vendor type, spend category, or dollar amount”
- [claimed-docs] “Process vendor bills from start to finish: initiate your process in either NetSuite or Ramp, and complete it with Ramp payments”
- [claimed-docs] “initiate your process in either Xero or Ramp and complete it with Ramp payments”
Expensifynone0/10The 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.”
Cards controls — stories about cards controls in this arenaCards controls
Stories about cards controls in this arena
Card controls
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 RampDocs explicitly describe issuing cards with attached controls, custom permissions per vendor/category/team, blocking risky merchants or categories before spend happens, and per-vendor spending limits on virtual cards — matching category/merchant/amount restriction and pre-spend enforcement. Missing for 10: independent/hands-on confirmation of real-time point-of-sale decline behavior and explicit 'auto-lock' mechanics beyond policy blocking language.
- [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
- [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
- [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
- [claimed-docs] “A finance team issues instant virtual cards for each software subscription with per-vendor spending limits, giving real-time visibility into…”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
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”
Card issuance
founderIssue physical and virtual corporate cards to the team in minutes, each with its own spend limit
weight 3 · round to RampRamp docs explicitly describe issuing physical and virtual cards with per-card/per-vendor spend limits, permissions, and real-time visibility (ramp-docs-7, ramp-docs-11, ramp-docs-31), matching the founder story closely. Missing for 10: independent hands-on confirmation of the 'minutes' setup speed and explicit UI walkthrough evidence beyond marketing copy.
- [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
- [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
- [claimed-docs] “A finance team issues instant virtual cards for each software subscription with per-vendor spending limits, giving real-time visibility into…”
- [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
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.”
Virtual cards
finance leadCreate single-vendor virtual cards for SaaS subscriptions and procurement so one compromised vendor never exposes shared credit
weight 2 · round to RampRamp documents creating custom/virtual cards with per-vendor spend limits explicitly for SaaS subscriptions, avoiding shared card numbers (ramp-docs-31, ramp-docs-11, ramp-docs-7), plus spend controls and merchant blocking (ramp-docs-9). missing for 10: independent/hands-on third-party corroboration beyond vendor marketing copy.
- [claimed-docs] “A finance team issues instant virtual cards for each software subscription with per-vendor spending limits, giving real-time visibility into…”
- [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
- [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
- [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
Expensifynone0/10Evidence 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!”
Expense data access — stories about expense data access in this arenaExpense data access
Stories about expense data access in this arena
Agent access
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 RampRamp offers both API (Transactions API, OAuth) and MCP access, and MCP examples show pulling uncoded transactions (missing receipts/memos) and drafting messages, plus AI auto-coding of transactions to GL accounts. However, there's no explicit documented workflow showing an agent proposing categorizations/policy flags and pushing 'clean coding back for review' via MCP/API as a distinct human-review step. missing for 10: explicit end-to-end example of agent proposing coding+policy flags and submitting for human review via MCP/API, independent/hands-on confirmation of this workflow.
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [claimed-docs] “Ramp gives you infinite teammates who work around the clock—flagging fraud, coding expenses, and enforcing policy.”
- [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
- [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
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 …”
Api access
developerPull transactions, expenses, and receipts through a documented REST API with OAuth and scoped tokens
weight 3 · round to RampRamp documents a Transactions API accessed via access tokens, and OAuth 2.0 with scopes and multiple authorization flows for API access, plus webhooks for event notifications, confirming a documented REST API with scoped OAuth tokens for transaction/expense data. missing for 10: no explicit mention of a dedicated receipts endpoint or independent third-party corroboration of API behavior beyond vendor docs.
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
- [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
- [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
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”
Card api
developerIssue and manage cards programmatically — create a card with a limit, lock it, update controls — via the public API
weight 2 · round to RampRamp's marketing pages describe issuing virtual/physical cards with spend controls (ramp-docs-7, ramp-docs-11) and the MCP integration shows a 'lock my card' action (ramp-docs-30), suggesting the underlying platform supports card issuance/locking, but the developer docs index only explicitly names a Transactions API (ramp-docs-1) and the llms.txt probe doesn't surface a dedicated Cards API with create/lock/update-controls endpoints. Missing for 10: explicit public API reference/endpoints for card creation, locking, and limit/control updates, and any independent confirmation these are callable outside the MCP/CLI natural-language layer.
- [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
- [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
- [claimed-docs] “Lock my card — I can't find it.”
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
Expensifynone0/10Evidence 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”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to RampRamp exposes a broad public API, CLI, and MCP server covering many UI actions (transactions, cards, bill approval, travel booking, expense management) per ramp-docs-1,3,4,5,6,29,30, but no documentation explicitly claims full feature parity between API/CLI/MCP and the UI, and several UI-only workflows (e.g., detailed policy configuration, multi-entity setup, procurement OCR flows) are not shown as API-accessible. Missing for 10: an explicit parity statement or exhaustive endpoint list covering all UI functions, and independent confirmation that no UI-only gaps exist.
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
- [claimed-docs] “Authenticate with OAuth, manage expenses, approve bills, book travel, and more from your terminal or AI agent.”
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
- [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
- [claimed-docs] “Lock my card — I can't find it.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
- [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
- [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
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”
ai-native userExport all of my data in open formats and leave
weight 3 · round to RampRamp exposes a Transactions API and OAuth-based developer access that lets a user programmatically pull data, but there is no documented full-account data export/portability feature (e.g., a 'download all my data' or GDPR-style export in open formats). missing for 10: explicit full data export/takeout functionality, confirmation of open-format (CSV/JSON) bulk export, evidence of exporting all data types (bills, cards, reimbursements) not just transactions.
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
- [claimed-docs] “Ramp uses OAuth 2.0 for secure API access, providing granular permission control through scopes and supporting multiple authorization flows …”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
Expensifynone0/10No 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.
ai-native userRead the product's source under an open license
weight 2 · round drawnRampnone0/10Ramp is a closed commercial fintech SaaS product; no evidence of any open-source license covering its core product source. The GitHub repo referenced is for a CLI tool, not the product source itself, and no license details are given.
Expensifynone0/10While a public GitHub repo (Expensify/App) with build instructions exists, none of the evidence specifies any open-source license or terms governing that code, so we cannot confirm the source is available under an open license. missing for 10: explicit license file/terms, confirmation of open-source licensing, any documentation asserting open licensing.
- [github] “Install dependencies: `npm install`”
Policy approvals — stories about policy approvals in this arenaPolicy approvals
Stories about policy approvals in this arena
Approvals
finance leadBuild multi-step approval chains — manager, budget owner, finance — with delegation and escalation when approvers sit on requests
weight 2 · round to RampRamp's docs show rule-based approval routing to stakeholders based on vendor/category/amount and role-based notification workflows, plus policy-grounded recommended approve/reject actions, which supports building structured approval chains. However, there is no evidence of explicit multi-step manager→budget-owner→finance sequencing, delegation of approval authority, or escalation logic when an approver doesn't act. missing for 10: explicit delegation feature, escalation/timeout rules, and multi-tier approval chain configuration details.
- [claimed-docs] “Rules-based workflows route requests to the right stakeholders automatically based on vendor type, spend category, or dollar amount”
- [claimed-docs] “Create personalized workflows that only notify the right people, based on spend amount or team role, and keep visibility high.”
- [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
Audit trail
finance leadEvery expense carries a full audit trail — edits, approvals, policy checks — that survives an external audit
weight 2 · round to RampRamp's docs show policy enforcement (submission requirements, spend limits, policy status checks) and approval workflows with recommended actions, plus reconciliation/3-way matching tools that touch on audit-adjacent controls (ramp-docs-9, ramp-docs-10, ramp-docs-17, ramp-docs-26). However, there is no explicit documentation of an immutable audit log, edit history tracking, or export/report designed specifically to survive an external audit review. Missing for 10: explicit audit-trail/edit-history logging feature, statement on audit log immutability or retention, and third-party/independent evidence of audit compliance (e.g., SOC2 audit trail usage).
- [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
- [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
- [claimed-docs] “Ramp checks every line item with two and three-way matching, so you know if something's off before sending.”
- [claimed-docs] “Gain confidence in your numbers with Ramp's built-in reconciliation tool that verifies balances between both platforms”
- [claimed-docs] “Create personalized workflows that only notify the right people, based on spend amount or team role, and keep visibility high.”
Expensifynone0/10The 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.
Policy engine
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 RampRamp docs describe configurable spend limits by category/role/context, submission requirements, and blocking risky merchants/categories before spend happens (ramp-docs-9), plus in-policy auto-approval with GL coding and no expense report needed (ramp-docs-32), and recommended approve/reject actions grounded in policy for exceptions (ramp-docs-10). Custom card permissions and role/team-based notification routing further support codifying policy by role and context (ramp-docs-11, ramp-docs-12). Missing for 10: independent/hands-on verification of policy engine granularity and confirmation that auto-approval works reliably at scale beyond marketing copy.
- [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
- [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
- [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
- [claimed-docs] “Create personalized workflows that only notify the right people, based on spend amount or team role, and keep visibility high.”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
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”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnRampnone0/10No evidence in the pack addresses data residency, regional storage options, or geographic control over where data is stored; evidence only covers API, MCP, CLI, and expense-management features.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnRampnone0/10No evidence pack item addresses AI training data usage, opt-out controls, or data-privacy policies regarding model training; all evidence concerns product features (cards, expense management, MCP/CLI integrations) rather than data governance for AI training. Missing for 10: any privacy policy statement, opt-out mechanism, or documentation about AI training data usage.
Expensifynone0/10No 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 …”
ai-native userControl data retention and deletion
weight 2 · round drawnRampnone0/10No evidence pack items address data retention policies, deletion controls, or user-configurable data lifecycle settings for AI/agent-related data; the pack focuses on API/MCP/CLI functionality and expense automation, not privacy/retention controls.
Expensifynone0/10No 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.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnRampnone0/10No evidence in the pack addresses telemetry opt-out or usage-tracking controls for AI-native users; Ramp's documentation covers APIs, MCP, CLI, and expense features but nothing about telemetry settings.
Receipts capture — stories about receipts capture in this arenaReceipts capture
Stories about receipts capture in this arena
Mileage perdiem
employeeLog mileage with map-based distance and claim per-diem rates without building the expense by hand
weight 2 · round to RampRamp's own docs confirm automatic mileage calculation via Google Maps integration for reimbursements and automatic per-diem rate adjustment based on trip location/duration, directly matching the story's request for map-based mileage and per-diem claims without manual entry. Missing for 10: independent/hands-on verification of the mileage logging UX and per-diem claim flow, and no detail on how these integrate into a single expense submission step.
- [claimed-docs] “Our integration with Google Maps keeps repayments precise with automatic mileage calculations.”
- [claimed-docs] “Per diem shows exactly what you can purchase, and automatically adjusts based on trip location and duration.”
- [claimed-docs] “Reimburse employees with confidence in more than 70 countries and 40 currencies, knowing they can be paid in two days or less in their local…”
Expensifynone0/10The 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.
Receipt capture
employeeSnap a photo or forward an email and the platform OCRs the receipt and files it against the right transaction
weight 3 · round to RampEvidence confirms Ramp automatically captures receipts and applies OCR/coding when a card is swiped, with edits/submission via SMS, Slack, or Teams (ramp-docs-8, ramp-docs-32), and general OCR accuracy claims exist for bill-pay (ramp-docs-16). However, none of the evidence specifically describes an employee snapping a photo of a paper receipt or forwarding an email receipt that gets OCR'd and matched to a transaction — the described flow is card-swipe-triggered capture, not employee-initiated photo/email submission. Missing for 10: explicit documentation of photo-upload or email-forwarding receipt intake and its OCR matching to transactions, plus independent/hands-on confirmation.
- [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
- [claimed-docs] “Ramp's OCR captures each detail and line item with 99% accuracy.”
Expensifydisputedcontradicted5/10Expensify'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.”
Receipt matching
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 RampRamp documents automatic receipt capture and coding at swipe time, auto-approval when in policy, and reminders/nudges only for transactions with missing receipts or memos (ramp-docs-8, ramp-docs-13, ramp-docs-29, ramp-docs-32). However, there's no explicit evidence of e-receipts being pulled in from email/vendor integrations (e.g., Amazon, Lyft, Uber) as the story specifies. Missing for 10: documentation of e-receipt integrations sourcing receipts automatically, and independent/hands-on confirmation that nudges only trigger for genuinely missing receipts.
- [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
- [claimed-docs] “Let Ramp send reminders for missing items or request repayments for you.”
- [claimed-docs] “Find transactions with missing receipts or memos in the last 14 days and draft reminder messages I can send to the team.”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
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 …”
Reimbursements — stories about reimbursements in this arenaReimbursements
Stories about reimbursements in this arena
Domestic
employeeSubmit an out-of-pocket expense and get reimbursed by direct deposit in days, tracked from submission to payout
weight 3 · round to RampRamp explicitly supports out-of-pocket reimbursements paid within two days or less in local currency across 70+ countries (ramp-docs-14), with automated receipt capture, submission via SMS/Slack/Teams, and policy-based auto-approval reducing manual expense reports (ramp-docs-8, ramp-docs-32). Approval workflows and reminders support the submission-to-payout tracking narrative (ramp-docs-10, ramp-docs-13). Missing for 10: explicit end-to-end status tracking UI/dashboard evidence for an individual employee, and independent/hands-on confirmation of the 2-day payout claim.
- [claimed-docs] “Reimburse employees with confidence in more than 70 countries and 40 currencies, knowing they can be paid in two days or less in their local…”
- [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
- [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
- [claimed-docs] “Let Ramp send reminders for missing items or request repayments for you.”
Expensifynone0/10The 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.
International
finance leadReimburse employees abroad in their local currency without running a separate international payments process
weight 2 · round to RampRamp explicitly advertises reimbursing employees in 70+ countries and 40 currencies with local-currency payout in two days or less, directly matching the story, and this is embedded in its core reimbursement product rather than a separate process. Missing for 10: independent/hands-on verification of actual cross-border payout speed/accuracy and details on FX handling or fees.
- [claimed-docs] “Reimburse employees with confidence in more than 70 countries and 40 currencies, knowing they can be paid in two days or less in their local…”
Spend visibility — stories about spend visibility in this arenaSpend visibility
Stories about spend visibility in this arena
Budgets
finance leadAllocate budgets to teams and projects and have card limits and approvals actually enforce them
weight 2 · round to RampRamp's documentation directly supports budget allocation to teams/projects with card controls that enforce them: custom virtual cards with per-team/vendor spend permissions (ramp-docs-11, ramp-docs-31), pre-spend enforcement of limits and blocked merchants/categories (ramp-docs-9), policy-grounded recommended approve/reject actions (ramp-docs-10), and role/amount-based notification workflows (ramp-docs-12). This covers allocation, limit enforcement, and approvals working together. Missing for 10: no independent/hands-on verification of enforcement accuracy, and no explicit 'budget' object/API distinct from card limits shown in evidence.
- [claimed-docs] “Set submission requirements, enforce spend limits, and block risky merchants or categories all before spend happens.”
- [claimed-docs] “All spend requests come with a recommended action grounded in your policies, budgets, and funds, so you can approve or reject in seconds.”
- [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
- [claimed-docs] “Create personalized workflows that only notify the right people, based on spend amount or team role, and keep visibility high.”
- [claimed-docs] “A finance team issues instant virtual cards for each software subscription with per-vendor spending limits, giving real-time visibility into…”
- [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
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”
Dashboards
founderSee company spend in real time — by team, category, and merchant — the day it happens, not when statements land
weight 3 · round to RampRamp captures spend in real time at swipe (receipt/memo/category auto-filled), issues cards with real-time spend tracking per team/vendor, and offers Transactions API/webhooks for real-time data feeds by team, category, and merchant. This directly matches the founder's need for same-day visibility rather than waiting on statements. Missing for 10: no independent/third-party corroboration or explicit dashboard screenshot evidence of a unified real-time cross-team/category/merchant view.
- [claimed-docs] “Issue cards, attach controls, and watch spend in real time — physical for employee in-person spend, virtual for reusable payment details, or…”
- [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
- [claimed-docs] “Create custom virtual cards and set permissions for everything from ad marketplace spend to remote work stipends, for individual teams or yo…”
- [claimed-docs] “A finance team issues instant virtual cards for each software subscription with per-vendor spending limits, giving real-time visibility into…”
- [claimed-docs] “Webhooks allow your application to receive real-time notifications about events that occur in your Ramp account.”
- [claimed-docs] “You'll create an access token and call the Transactions API to retrieve transaction data.”
Expensifydisputedcontradicted4/10Expensify 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 …”
Travel — stories about travel in this arenaTravel
Stories about travel in this arena
Booking
employeeBook flights and hotels in-platform with travel policy applied at booking time, not expensed and argued about later
weight 2 · round to RampRamp Travel explicitly shows policy status at time of booking ('See policy status for every option... wondering if trips will get rejected'), applies per diem automatically, and even auto-rebooks hotels when rates drop, indicating in-platform booking with policy enforced upfront rather than post-hoc expense review. This directly matches the story of not having to expense-and-argue later. Missing for 10: independent/hands-on verification of the booking flow UX, and detail on flight booking specifically (most evidence focuses on hotel/per diem) plus confirmation of real-time policy blocking vs. just visibility.
- [claimed-docs] “See policy status for every option. No digging through static policy PDFs or wondering if trips will get rejected.”
- [claimed-docs] “Per diem shows exactly what you can purchase, and automatically adjusts based on trip location and duration.”
- [claimed-docs] “Ramp monitors hotel rates and automatically rebooks if the price decreases by $50+.”
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”
Trip expenses
employeeA trip's expenses — bookings, cards, receipts — collect themselves into one itinerary-linked report
weight 1 · round to RampRamp documents automatic receipt capture and card-based expense coding (ramp-docs-8, ramp-docs-32) and travel-specific policy/per-diem/hotel tools (ramp-docs-18, ramp-docs-19, ramp-docs-20), suggesting trip spend is tracked and can be booked within policy, but there is no explicit documentation that bookings, cards, and receipts are automatically consolidated into a single itinerary-linked expense report for the employee. missing for 10: explicit description of a unified trip/itinerary report view, evidence that booking data auto-links to card transactions and receipts under one trip record, and any hands-on confirmation of this consolidation.
- [claimed-docs] “As soon as you swipe your card, Ramp captures the receipt and fills in memos and categories. Make edits and submit via SMS, Slack, or Micros…”
- [claimed-docs] “See policy status for every option. No digging through static policy PDFs or wondering if trips will get rejected.”
- [claimed-docs] “Per diem shows exactly what you can purchase, and automatically adjusts based on trip location and duration.”
- [claimed-docs] “Ramp monitors hotel rates and automatically rebooks if the price decreases by $50+.”
- [claimed-docs] “the receipt is captured automatically, coded to the correct GL account, and auto-approved because it's within policy — no expense report fil…”
Expensifydisputedcontradicted5/10Expensify 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 …”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableRampn/aRamp's MCP integration is one-directional: it exposes itself as an MCP server so external AI assistants (ChatGPT, Claude, agents) can call Ramp's tools, not a mechanism for users to plug arbitrary external MCP servers into Ramp so Ramp can consume their tools. As a fintech/expense platform (not an agent or IDE), acting as an MCP client host is outside its product category.
- [claimed-docs] “Ramp MCP allows you to securely connect Ramp with AI assistants like ChatGPT and Claude, so you can query Ramp data and take actions with na…”
- [claimed-docs] “Give an AI agent read access, action authority, and (with approval) real purchasing power on Ramp — through MCP, the Ramp CLI, or both.”
- [probe] “official MCP server documented at https://support.ramp.com/hc/en-us/articles/45516494479891-Ramp-MCP”
Expensifyn/aExpensify is an expense management SaaS product, not an AI agent; the evidence shows only its own API/integration server and AI-assistant features, with no mention of MCP server support for plugging in external tool servers. This axis (agent-role MCP client capability) does not apply to a SaaS platform's own product surface.
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableRampnone0/10Ramp's evidence covers automating expense/spend workflows, MCP/CLI/API access, and policy enforcement, but there is no mention of versioning automations/workflows, reviewing changes, or rolling back to prior configurations. Rules-based workflows (docs-23) and permissioning are described but no version history, diff/audit trail, or rollback mechanism is documented.
Expensifyn/aExpensify's AI features (Concierge/Ask Expensify AI) are conversational automation for expense actions, not an agent/workflow-building product with versioned automations to review or roll back. No evidence pack item addresses automation versioning, review, or rollback—this axis is a category error for an expense management SaaS.
ai-native userSelf-host the core product
weight 3 · not comparableRampn/aRamp is a SaaS fintech/expense-management platform, not open-source software; self-hosting a financial services product is a category error, not a missing feature.
Expensifynone0/10Expensify is a hosted SaaS product; while its App repo is open source on GitHub, there is no evidence of a self-hostable backend/server deployment for the core expense-management product—only a client app install step (npm install) is shown, not a full self-host path.
- [github] “Install dependencies: `npm install`”