Ramp vs BILL Spend & Expense
Ramp wins · 33–3 (14 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…”
BILL docs confirm automatic 2-way sync with QuickBooks Enterprise, NetSuite, Sage Intacct, and other accounting systems, and reference building an organization structure via the API, but Xero is not named among the sync targets and there is no explicit documentation of finance-lead-controlled GL account/class/department mapping rules. missing for 10: explicit Xero sync confirmation, documented GL account/class/department mapping controls, independent corroboration of mapping accuracy.
- [claimed-docs] “Automatic 2-way sync with QuickBooks Enterprise, Oracle NetSuite, Sage Intacct, Microsoft Dynamics, & more”
- [claimed-docs] “Use the BILL API to build your organization structure in BILL.”
- [claimed-docs] “**Manually integrate** with accounting software via CSV file import/export”
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.”
Vendor docs claim that BILL Spend & Expense cards make every transaction 'controlled, categorized, and automatically compliant' and pair with AI-driven bill coding (docs-8, docs-9), plus automatic 2-way sync to major accounting systems (docs-12), which supports real-time coding for close. However, there is no explicit documentation of automatic merchant/memo capture or receipt-matching workflows, and no independent/hands-on evidence corroborating that categorization actually eliminates manual review at month-end. Missing for 10: explicit receipt-capture/matching evidence, memo-field automation detail, and independent verification of coding accuracy.
- [claimed-docs] “Automatic AI multi-line bill coding with the Invoice Coding Agent”
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
- [claimed-docs] “Automatic 2-way sync with QuickBooks Enterprise, Oracle NetSuite, Sage Intacct, Microsoft Dynamics, & more”
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…”
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 drawnRamp 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.”
A probe confirms a live, HTTP 200 llms.txt file at developer.bill.com/llms.txt with structured documentation index, and BILL also documents an official MCP server for its API docs enabling agents like Cursor, Windsurf, and Claude Desktop to interact directly with the documentation. Missing for 10: independent/community confirmation of agent usage beyond BILL's own docs.
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.bill.com/llms.txt # BILL API documentation Documentation > Discover how to leverage the BILL …”
- [claimed-docs] “The BILL API documentation MCP server enables AI-powered code editors like Cursor and Windsurf, plus general-purpose tools like Claude Deskt…”
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”
BILL exposes a full v3 REST API with webhooks and a sandbox environment that let developers script and automate AP/AR/S&E workflows programmatically, which supports headless/automated use cases like CI pipelines. However, there is no explicit CLI, GitHub Action, or documented CI-specific integration pattern in the evidence. Missing for 10: a dedicated CLI/automation tool, explicit CI/CD examples, and independent confirmation of headless operation in production pipelines.
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
- [claimed-docs] “BILL offers a comprehensive sandbox environment where you can test workflows, from creating bills to completing AP payments, without moving …”
- [claimed-docs] “When you set up a subscription for your choice of BILL events, you receive real time event notifications when those events are triggered.”
- [claimed-docs] “You can create up to 10 webhook subscriptions per organization.”
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”
BILL provides an official MCP server for developer documentation, letting tools like Cursor, Windsurf, and Claude Desktop interact with BILL API docs, which is a genuine first-party MCP offering. However, it is scoped only to documentation lookup, not to actually invoking BILL API actions (payments, bills, expense data) via MCP, so it's a limited agentic bridge rather than a full action-capable MCP server. Missing for 10: an MCP server exposing live API/data operations (not just docs), independent/community confirmation of usage, and details on scope/auth for agent actions.
- [claimed-docs] “The BILL API documentation MCP server enables AI-powered code editors like Cursor and Windsurf, plus general-purpose tools like Claude Deskt…”
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”
BILL Spend & Expensenone0/10The evidence pack details a REST API, webhooks, UI Elements SDK, and an MCP server for documentation access, but nowhere mentions an official CLI tool for interacting with BILL Spend & Expense. Since BILL offers a developer platform, a CLI is a plausible axis, but there is no evidence one exists.
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”
BILL publishes a documented v3 API covering AP/AR/S&E, webhooks, sandbox environment, and even an MCP server for AI-agent access to docs, indicating a genuinely documented public API surface usable programmatically. Missing for 10: a discoverable OpenAPI/swagger spec (probe found all candidate paths 404) and independent third-party corroboration of API robustness.
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
- [claimed-docs] “Subscribe to & receive real-time notifications for AP & AR events and S&E events.”
- [claimed-docs] “BILL offers a comprehensive sandbox environment where you can test workflows, from creating bills to completing AP payments, without moving …”
- [claimed-docs] “When you set up a subscription for your choice of BILL events, you receive real time event notifications when those events are triggered.”
- [claimed-docs] “The BILL API documentation MCP server enables AI-powered code editors like Cursor and Windsurf, plus general-purpose tools like Claude Deskt…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.bill.com/llms.txt # BILL API documentation Documentation > Discover how to leverage the BILL …”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.bill.com/openapi.json, https://developer.bill.com/swagger.json, https://developer.…”
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”
BILL Spend & Expensenone0/10The evidence shows BILL has a v3 API, webhooks, and an apiToken concept, but there is no documentation of scoped or least-privilege credential issuance (e.g., role-based API keys, granular permission scopes for agents). Missing for 10: any mention of API key scopes, granular permission levels, or agent-specific credential issuance mechanisms.
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
- [claimed-docs] “Spend & Expense: apiToken is missing”
ai-native userBuild against official SDKs
weight 2 · round to BILL Spend & ExpenseRampnone0/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”
BILL provides an official v3 API and developer docs covering AP/AR/S&E, webhooks, sandbox environment, and even an MCP server for AI code editors, giving AI-native developers a real SDK/API surface to build against. However, evidence lacks explicit language-specific SDK libraries (e.g., Python/Node client packages) and OpenAPI spec discovery failed (404s), leaving some doubt about full programmatic tooling maturity. missing for 10: explicit official client SDK libraries in multiple languages, publicly discoverable OpenAPI/swagger spec, independent developer corroboration of SDK quality.
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
- [claimed-docs] “BILL offers a comprehensive sandbox environment where you can test workflows, from creating bills to completing AP payments, without moving …”
- [claimed-docs] “The BILL API documentation MCP server enables AI-powered code editors like Cursor and Windsurf, plus general-purpose tools like Claude Deskt…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.bill.com/llms.txt # BILL API documentation Documentation > Discover how to leverage the BILL …”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.bill.com/openapi.json, https://developer.bill.com/swagger.json, https://developer.…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnRamp 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.”
BILL's developer platform explicitly documents webhook subscriptions for real-time event notifications, including S&E events, HMAC-SHA256 signing for security, subscription limits (up to 10 per org), and error handling docs, indicating a mature, well-documented webhook system. missing for 10: independent/hands-on third-party corroboration beyond first-party docs, and more detail on the breadth of subscribable event types for Spend & Expense specifically.
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
- [claimed-docs] “Subscribe to & receive real-time notifications for AP & AR events and S&E events.”
- [claimed-docs] “When you set up a subscription for your choice of BILL events, you receive real time event notifications when those events are triggered.”
- [claimed-docs] “BILL uses the HMAC-SHA256 algorithm to sign all event notifications sent to your `notificationUrl` with the `securityKey`.”
- [claimed-docs] “Spend & Expense: apiToken is missing”
- [claimed-docs] “You can create up to 10 webhook subscriptions per organization.”
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”
Evidence shows AI-powered automation like automatic transaction categorization/compliance and an 'Invoice Coding Agent' for multi-line bill coding, but there's no documentation of AI-generated insights, recommendations, or proactive suggestions surfaced to users from their spend data. Missing for 10: explicit AI insight/analytics dashboards, natural-language querying of data, proactive spend recommendations, and independent corroboration of any such feature.
- [claimed-docs] “Automatic AI multi-line bill coding with the Invoice Coding Agent”
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnRamp 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”
BILL offers background automation primitives — vendor autopay that automatically pays bills when created, an AI Invoice Coding Agent that auto-codes multi-line bills, custom approval policies, and webhook-driven event subscriptions — all of which run without manual intervention once configured. However, there's no evidence of a general-purpose, AI-native automation/agent builder that lets users define arbitrary autonomous workflows; these are fixed, pre-built automation features rather than a configurable agentic automation layer. Missing for 10: a documented no-code/AI automation builder for custom autonomous workflows, evidence of user-defined multi-step agentic automations, and independent confirmation these run reliably unattended.
- [claimed-docs] “Automatic AI multi-line bill coding with the Invoice Coding Agent”
- [claimed-docs] “When this feature is enabled for a vendor, BILL automatically pays the vendor when a bill is created for the vendor.”
- [claimed-docs] “Set custom approval policies”
- [claimed-docs] “When you set up a subscription for your choice of BILL events, you receive real time event notifications when those events are triggered.”
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to RampRamp 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”
BILL advertises an 'Invoice Coding Agent' that automatically performs AI multi-line bill coding and general 'AI-powered spend management,' showing some built-in AI capability, but this is an automated background feature rather than a conversational assistant the user can actively delegate arbitrary tasks to. Missing for 10: evidence of a user-facing chat/assistant interface, examples of delegating varied tasks (not just bill coding), and independent confirmation of how the agent is invoked or controlled.
- [claimed-docs] “Automatic AI multi-line bill coding with the Invoice Coding Agent”
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
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”
BILL Spend & Expensenone0/10Evidence shows only a documentation MCP server for developers (docs-18) and an AI-based invoice coding agent, neither of which lets an end user operate the product itself via natural-language commands (e.g., 'pay this vendor' or 'approve this expense' via chat). No evidence of a conversational/agentic interface for actually performing S&E actions in natural language.
- [claimed-docs] “The BILL API documentation MCP server enables AI-powered code editors like Cursor and Windsurf, plus general-purpose tools like Claude Deskt…”
- [claimed-docs] “Automatic AI multi-line bill coding with the Invoice Coding Agent”
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…”
BILL Spend & Expensenone0/10Evidence confirms BILL has API docs, a sandbox test environment, and an MCP server for AI tools to query documentation, but nothing describes an interactive API reference with runnable/try-it-out examples; a probe for standard OpenAPI/Swagger specs returned 404s across all checked paths, suggesting no such interactive reference is exposed.
- [claimed-docs] “BILL offers a comprehensive sandbox environment where you can test workflows, from creating bills to completing AP payments, without moving …”
- [claimed-docs] “The BILL API documentation MCP server enables AI-powered code editors like Cursor and Windsurf, plus general-purpose tools like Claude Deskt…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.bill.com/openapi.json, https://developer.bill.com/swagger.json, https://developer.…”
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.”
BILL Spend & Expensenone0/10BILL has a developer API portal and docs, but a direct probe for standard OpenAPI/Swagger spec locations (openapi.json, swagger.json, etc.) returned 404 across all candidates, and no evidence pack item links to a downloadable machine-readable spec file.
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.bill.com/openapi.json, https://developer.bill.com/swagger.json, https://developer.…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.bill.com/llms.txt # BILL API documentation Documentation > Discover how to leverage the BILL …”
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to BILL Spend & ExpenseRampnone0/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.
BILL's developer docs explicitly state a comprehensive sandbox environment exists for testing AP/S&E workflows without moving real money, directly matching the story. missing for 10: independent/hands-on confirmation of sandbox parity with production and details on how sandbox data isolation works for Spend & Expense specifically.
- [claimed-docs] “BILL offers a comprehensive sandbox environment where you can test workflows, from creating bills to completing AP payments, without moving …”
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
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.
BILL Spend & Expensenone0/10Evidence shows BILL has a versioned v3 API and a changelog for tracking changes, but there is no mention of a documented deprecation policy, versioning strategy, or sunset timeline for API versions. missing for 10: explicit deprecation policy documentation, version lifecycle/sunset timeline, migration guidance between versions.
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
- [claimed-docs] “You can create up to 10 webhook subscriptions per organization.”
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.”
BILL Spend & Expense is explicitly marketed as 'AI-powered spend management' that automatically categorizes and ensures compliance for every transaction (docs-9), and BILL's platform includes an 'Invoice Coding Agent' for automatic AI bill coding (docs-8), suggesting some automated categorization/coding capability. However, there is no evidence of receipt OCR/reading, memo suggestion, or duplicate/fraud detection specifically for expense transactions. Missing for 10: explicit receipt-reading/OCR evidence, memo-suggestion detail, and duplicate or fraud detection functionality for Spend & Expense.
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
- [claimed-docs] “Automatic AI multi-line bill coding with the Invoice Coding Agent”
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”
BILL Spend & Expensenone0/10Evidence shows AI-powered categorization/coding agents and custom approval policy configuration, but nothing describes a conversational assistant that chases missing receipts, explains declines, or answers pre-spend 'can I expense this?' queries. Missing for 10: any conversational interface, proactive receipt-chasing behavior, decline explanations, or pre-purchase policy Q&A capability.
- [claimed-docs] “Automatic AI multi-line bill coding with the Invoice Coding Agent”
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
- [claimed-docs] “Set **custom** approval policies”
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.”
The BILL v3 API exposes programmatic access to transactions, budgets, users, and virtual cards, which could in principle be used to script bulk operations, but there is no explicit documentation of batch/bulk endpoints, bulk import/export of records, or any dedicated bulk-action tooling for AI-native use. Missing for 10: explicit bulk/batch API endpoints, documented bulk create/update/delete operations, and any first-party or independent evidence of large-scale batch processing.
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
- [claimed-docs] “Use the BILL API to build your organization structure in BILL.”
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…”
BILL supports webhooks for real-time event notifications and custom approval policies/tolerance rules, which enable some automated reactions to events, but there is no evidence of a native rules engine where users define arbitrary if-this-then-that automation triggering actions — webhooks require external code to consume and act on events. missing for 10: a documented no-code/low-code rule builder that lets users define trigger-condition-action automations natively within the product, evidence of arbitrary action-taking (not just notification) on events, and independent confirmation of this workflow in practice.
- [claimed-docs] “When you set up a subscription for your choice of BILL events, you receive real time event notifications when those events are triggered.”
- [claimed-docs] “Subscribe to & receive real-time notifications for AP & AR events and S&E events.”
- [claimed-docs] “Set **custom** approval policies”
- [claimed-docs] “Set custom approval policies”
- [claimed-docs] “When this feature is enabled for a vendor, BILL automatically pays the vendor when a bill is created for the vendor.”
- [claimed-docs] “You can create up to 10 webhook subscriptions per organization.”
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.
BILL Spend & Expensenone0/10BILL's developer platform offers webhooks and an API for event-driven notifications and vendor autopay, but there is no evidence of a scheduler, cron-like job, or recurring workflow automation feature that an AI-native user could configure. Missing for 10: any scheduling/recurring-job API, workflow orchestration tooling, or documentation describing recurring automated tasks beyond vendor autopay's one-off trigger.
- [claimed-docs] “When you set up a subscription for your choice of BILL events, you receive real time event notifications when those events are triggered.”
- [claimed-docs] “When this feature is enabled for a vendor, BILL automatically pays the vendor when a bill is created for the vendor.”
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
ai-native userVersion, review, and roll back my automations
weight 1 · round drawnRampnone0/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.
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”
The evidence pack (mostly from the shared bill.com/pricing and developer.bill.com pages) shows AP-adjacent capabilities such as custom approval policies, AI invoice coding, purchase orders/2-way matching, vendor network connectivity, and vendor autopay, suggesting AP functionality exists somewhere in the BILL platform. However, none of the evidence explicitly confirms these AP features (invoice capture, approval routing, ACH/check/wire payments) are part of the core Spend & Expense product itself rather than BILL's separate AP product/bundle, and no citation names ACH, check, or wire payment rails at all. Missing for 10: explicit confirmation that invoice capture/approval/payment (ACH, check, wire) run natively inside Spend & Expense rather than a separate BILL AP SKU, and any mention of specific payment rail support.
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
- [claimed-docs] “Set **custom** approval policies”
- [claimed-docs] “Automatic AI multi-line bill coding with the Invoice Coding Agent”
- [claimed-docs] “Easily create purchase requests Create and send purchase orders Set tolerance rules 2-way matching”
- [claimed-docs] “Securely connect with +4M vendors via the BILL network”
- [claimed-docs] “When this feature is enabled for a vendor, BILL automatically pays the vendor when a bill is created for the vendor.”
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…”
Marketing copy claims cards are 'controlled, categorized, and automatically compliant' via AI-powered spend management, implying policy-based restrictions, but there is no documentation detailing category/merchant/amount-level card controls or confirming real-time auto-lock/decline at the point of sale. Missing for 10: specific docs on setting category/merchant/amount limits per card, technical description of point-of-sale enforcement, and independent/hands-on confirmation that out-of-policy transactions are actually declined in real time.
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
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.”
Docs confirm virtual card issuance and spend/budget management (doc-2, doc-9) as part of the S&E product, implying per-card spend controls, but no explicit mention of physical card issuance, onboarding speed ('minutes'), or per-card individual limits is provided. Missing for 10: explicit physical card issuance details, quick setup/time-to-issue claims, and explicit per-card spend limit configuration evidence.
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
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.”
Docs confirm BILL Spend & Expense supports creating virtual cards and card/expense management (budgets, users, virtual cards) via its API and product, which aligns with issuing per-vendor cards for SaaS/procurement. However, no evidence explicitly shows merchant-locking or single-vendor restriction controls that would guarantee a card is usable only with one vendor. missing for 10: explicit documentation of vendor/merchant-lock restrictions on virtual cards, and independent confirmation of single-vendor isolation.
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
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”
BILL's v3 API supports transaction/expense management and webhooks, and there's an internal 'Invoice Coding Agent' for AI-based coding, but the only MCP server documented is for browsing API docs (not transaction data), and no endpoint/workflow is documented for pulling specifically 'uncoded' transactions, proposing categorizations, or pushing coding back for human review via API or MCP. Missing for 10: MCP data-access server (not just doc server), explicit uncoded-transaction query endpoint, API-exposed categorization/policy-flag proposal workflow, and a documented review/approval push-back API flow.
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
- [claimed-docs] “Automatic AI multi-line bill coding with the Invoice Coding Agent”
- [claimed-docs] “The BILL API documentation MCP server enables AI-powered code editors like Cursor and Windsurf, plus general-purpose tools like Claude Deskt…”
- [claimed-docs] “Subscribe to & receive real-time notifications for AP & AR events and S&E events.”
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…”
BILL's v3 API is documented and explicitly covers Spend & Expense transactions, cards, budgets, and reimbursements, with webhooks, sandbox, and changelog evidence showing an active, versioned REST platform (docs-1,2,3,15,16,22). However, the evidence never confirms OAuth or scoped token authentication—only an 'apiToken' concept appears (docs-19)—and there's no explicit mention of receipt retrieval endpoints or OAuth scope definitions, and openapi spec probes 404 (probe-2). Missing for 10: explicit OAuth 2.0/scoped-token auth documentation, dedicated receipts endpoint evidence, and a discoverable OpenAPI spec.
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
- [claimed-docs] “BILL offers a comprehensive sandbox environment where you can test workflows, from creating bills to completing AP payments, without moving …”
- [claimed-docs] “Spend & Expense: apiToken is missing”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.bill.com/openapi.json, https://developer.bill.com/swagger.json, https://developer.…”
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 BILL Spend & ExpenseRamp'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…”
Docs confirm a card & expense management API surface ("virtual cards", budgets, users, transactions) and webhook notifications, implying some programmatic card management, but there is no explicit documentation of endpoints for creating a card with a limit, locking a card, or updating card controls. missing for 10: explicit API reference/endpoints for card creation with limits, card lock/unlock actions, control updates, and any hands-on or independent confirmation these operations work as described.
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
- [claimed-docs] “When you set up a subscription for your choice of BILL events, you receive real time event notifications when those events are triggered.”
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”
BILL exposes a broad v3 API covering AP/AR/S&E, card & expense management, budgets, virtual cards, org structure, and webhooks, suggesting substantial UI-parity coverage. However, there is no evidence confirming full parity — e.g., no explicit statement that every UI action (like custom approval policy setup or AI invoice coding features) is API-accessible, and no public OpenAPI spec was found (404s on standard paths). missing for 10: explicit UI-API parity statement, discoverable OpenAPI/swagger schema, confirmation that AI-powered features (Invoice Coding Agent) are API-exposed.
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
- [claimed-docs] “Use the BILL API to build your organization structure in BILL.”
- [claimed-docs] “Embed low-code BILL UI Elements into your application. Get access to the BILL AP workflow with minimal development effort.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.bill.com/openapi.json, https://developer.bill.com/swagger.json, https://developer.…”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnRamp 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…”
The only relevant evidence is manual CSV import/export for accounting sync, not a comprehensive data-export/account-portability feature; the API exists but is aimed at integration, not bulk self-service export for leaving the platform. Missing for 10: a documented full data export tool, open-format bulk export of all transactions/records, and any account closure/data portability workflow.
- [claimed-docs] “**Manually integrate** with accounting software via CSV file import/export”
- [claimed-docs] “Use the BILL v3 API & access the full breadth of the BILL API Platform: AP, AR, & S&E. Receive real-time event notifications with webhooks.”
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.”
Evidence only shows a bare pricing-page bullet 'Set custom approval policies' repeated twice, with no documentation of multi-step chains (manager/budget owner/finance), delegation, or escalation logic. missing for 10: documentation of multi-step approval chain configuration, delegation of approvals, escalation on stalled requests, and any hands-on or independent corroboration.
- [claimed-docs] “Set **custom** approval policies”
- [claimed-docs] “Set custom approval policies”
Audit trail
finance leadEvery expense carries a full audit trail — edits, approvals, policy checks — that survives an external audit
weight 2 · round drawnRamp'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.”
Evidence shows custom approval policies and automatic compliance/categorization plus real-time webhook event notifications for S&E events, which could support an audit trail, but there is no explicit documentation of a persistent, exportable audit log covering edits, approvals, and policy checks suitable for external audit. Missing for 10: explicit audit-log/history feature, immutable record retention, export-for-audit functionality, and independent confirmation that this trail survives external audits.
- [claimed-docs] “Set **custom** approval policies”
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
- [claimed-docs] “When you set up a subscription for your choice of BILL events, you receive real time event notifications when those events are triggered.”
- [claimed-docs] “Set custom approval policies”
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…”
BILL markets 'custom approval policies', budgets/tolerance rules, and 'automatically compliant' spend controls (docs-7, docs-9, docs-10, docs-20), which supports rule-based policy codification and in-policy auto-handling. However, the evidence is mostly marketing copy from the pricing page rather than detailed documentation on how limits are defined by category/role/context or how exceptions are specifically routed to a human approver. Missing for 10: granular documentation of category/role/context-based limit configuration, explicit auto-approve logic, and evidence of exception-routing workflow to humans.
- [claimed-docs] “Set **custom** approval policies”
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
- [claimed-docs] “Easily create purchase requests Create and send purchase orders Set tolerance rules 2-way matching”
- [claimed-docs] “Set custom approval policies”
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.
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.
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…”
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.”
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…”
BILL Spend & Expensenone0/10The evidence pack covers API/developer platform features (webhooks, sandbox, vendor network, accounting sync) but contains no mention of receipt-to-transaction auto-matching, e-receipt pulls from integrations, or smart nudges for missing receipts — capabilities central to this employee expense-capture story. Axis clearly applies to an expense/card management product, but no supporting evidence exists in the pack.
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.”
The only relevant evidence is a brief API description stating you can 'manage transactions & reimbursements,' with no detail on the employee experience, direct deposit mechanics, or submission-to-payout tracking. Missing for 10: description of employee reimbursement submission flow, confirmation of direct deposit payout method, timeline/SLA for reimbursement, and any tracking/status visibility for employees.
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
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…”
BILL Spend & Expensenone0/10The evidence pack covers BILL's API platform, webhooks, vendor network, accounting sync, and card/expense management, but contains no mention of international/multi-currency reimbursement or foreign employee payout capability for BILL Spend & Expense. This is a plausible axis for a spend/expense product, but absence of any supporting documentation means it cannot be credited.
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…”
Docs confirm core building blocks: setting up budgets, virtual cards, and custom approval policies, plus org-structure configuration and per-transaction control language, which together map to budget allocation with enforced card limits/approvals. However, evidence is vendor-only marketing/docs with no independent or hands-on confirmation that limits/approvals actually block out-of-policy spend in practice, and no explicit project-level (vs team-level) allocation detail. Missing for 10: independent/hands-on verification of real-time enforcement, explicit project-based budget allocation evidence, and detail on how approvals interact with card limits at transaction time.
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
- [claimed-docs] “Set **custom** approval policies”
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
- [claimed-docs] “Use the BILL API to build your organization structure in BILL.”
- [claimed-docs] “Set custom approval policies”
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.”
BILL Spend & Expense markets 'AI-powered spend management' where transactions are automatically categorized and controlled, and it supports real-time event webhooks for S&E events, suggesting near-instant visibility into spend as it happens. However, there is no explicit documentation of a founder-facing dashboard breaking down spend by team, category, and merchant in real time — the webhook/API evidence is developer-facing, not a described reporting UI. Missing for 10: explicit product documentation of a real-time spend dashboard with team/category/merchant breakdowns, and independent/hands-on confirmation of same-day visibility in the actual UI.
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
- [claimed-docs] “Subscribe to & receive real-time notifications for AP & AR events and S&E events.”
- [claimed-docs] “When you set up a subscription for your choice of BILL events, you receive real time event notifications when those events are triggered.”
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+.”
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…”
BILL Spend & Expensenone0/10Evidence covers card issuance, AI-powered spend categorization, vendor network payments, and accounting sync, but there is no mention of travel bookings, itineraries, or automatic linking of trip-related expenses into a single itinerary-based report. Missing for full credit: any travel-booking integration, itinerary data model, or automatic trip-expense aggregation feature.
- [claimed-docs] “BILL Spend & Expense gives small and mid-size businesses smart, flexible cards paired with AI-powered spend management —so every transaction…”
- [claimed-docs] “Build with card & expense management services. Set up budgets, users, & virtual cards. Manage transactions & reimbursements.”
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”
BILL Spend & Expensenone0/10The evidence only shows BILL publishing an MCP server that exposes its own API documentation to external AI tools (server role), not any capability for BILL Spend & Expense itself to consume/plug in external MCP servers to extend its own agentic features (client role). No evidence of an MCP client integration point, plugin system, or tool-calling framework within the product.
- [claimed-docs] “The BILL API documentation MCP server enables AI-powered code editors like Cursor and Windsurf, plus general-purpose tools like Claude Deskt…”
ai-native userRead the product's source under an open license
weight 2 · not comparableRampnone0/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.
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.