Navan vs BILL Spend & Expense
Draw · 15–15 (21 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 to BILL Spend & ExpenseNavannone0/10The evidence pack contains no mention of QuickBooks, NetSuite, Xero, or any accounting-system sync, nor GL account/class/department mapping controls — it only covers Navan's API/MCP for expense querying, travel booking, and rewards. This is a plausible and expected axis for a T&E platform, but nothing in the evidence demonstrates it.
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 NavanNavan's card-transaction API, receipt scanning, custom-field management, and policy-violation flagging (navan-docs-4, -21, -22, -23, -24) show spend arriving already tagged by merchant/category/policy status, and MCP queries let a finance lead pull flagged/over-limit items by department in natural language (navan-docs-5, -21) instead of manually reconciling. Missing for 10: explicit evidence of automatic memo generation and confirmation that coding happens in real time at swipe rather than batch/after-the-fact, plus independent (non-vendor) validation of close-time accuracy.
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Analyze spend data — query expenses, identify trends, and break down costs by department, vendor, or category.”
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
- [claimed-docs] “Discover company fields, batch-manage option values, and poll async job status.”
- [claimed-docs] “Receipt scanning for on-the-go expenses”
- [claimed-docs] “Show me every flagged expense over $500 from Q1 that hasn't been approved yet, grouped by department.”
- [claimed-docs] “Card management — see which cards are active or inactive, how many cards a user has, and other card details.”
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 drawnNavannone0/10Evidence pack covers Navan's MCP/API for expense and travel data, card management, and pricing/rewards, but contains no mention of multi-entity or multi-currency account structures, consolidated reporting, or per-entity books — core requirements for finance-lead accounting-close workflows.
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 drawnA live llms.txt file is confirmed at developer.navan.com/llms.txt (HTTP 200) describing MCP-based agent access, and the developer portal has dedicated agent-oriented docs (/mcp/, /api/) with example natural-language queries. Missing for 10: independent third-party confirmation that agents successfully consume this llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.navan.com/llms.txt # Navan Developer Portal > Connect AI assistants to Navan travel and expen…”
- [claimed-docs] “Connect AI assistants — Claude, Cursor, ChatGPT, Codex, OpenClaw — to Navan data using the Model Context Protocol.”
- [claimed-docs] “The Navan MCP lets you connect Navan to your favorite AI products, so you can query Navan spend and travel data using natural language.”
- [probe] “official MCP server documented at https://developer.navan.com/mcp/”
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 drawnNavan's API documents an OAuth 2.0 client-credentials flow (machine-to-machine auth with no interactive login), which is the kind of mechanism needed to call Navan programmatically from a CI/automation pipeline, and its REST/webhook endpoints could be scripted headlessly. However, there is no explicit CI documentation, CLI, or example of running Navan (or its MCP server) unattended in a pipeline — missing for 10: explicit CI/automation guide, headless MCP server deployment instructions, and any hands-on evidence of it being run in CI.
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Discover company fields, batch-manage option values, and poll async job status.”
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 userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnNavannone0/10All evidence describes Navan exposing its own MCP server so external AI assistants (Claude, Cursor, ChatGPT) can query Navan's travel/expense data — this is Navan acting as the MCP server/provider, not as a client consuming external MCP servers' tools. There is no evidence Navan (or its Ava assistant) can plug in and use tools from third-party MCP servers. Missing for 10: any documentation of Navan's AI features connecting to external MCP servers, any tool/plugin ecosystem for consuming outside MCP tools, and any hands-on confirmation of such client-side behavior.
- [claimed-docs] “Connect AI assistants — Claude, Cursor, ChatGPT, Codex, OpenClaw — to Navan data using the Model Context Protocol.”
- [claimed-docs] “The Navan MCP lets you connect Navan to your favorite AI products, so you can query Navan spend and travel data using natural language.”
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.navan.com/llms.txt # Navan Developer Portal > Connect AI assistants to Navan travel and expen…”
- [probe] “official MCP server documented at https://developer.navan.com/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 userConnect an agent via an official MCP server
weight 3 · round to NavanNavan publishes an official MCP server (developer.navan.com/mcp/) explicitly for connecting AI assistants like Claude, Cursor, ChatGPT to Navan spend/travel data, with documented natural-language query examples and OAuth-secured API endpoints backing it. Missing for 10: independent/hands-on third-party corroboration of the MCP server working in practice beyond vendor docs.
- [claimed-docs] “Connect AI assistants — Claude, Cursor, ChatGPT, Codex, OpenClaw — to Navan data using the Model Context Protocol.”
- [claimed-docs] “The Navan MCP lets you connect Navan to your favorite AI products, so you can query Navan spend and travel data using natural language.”
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.navan.com/llms.txt # Navan Developer Portal > Connect AI assistants to Navan travel and expen…”
- [probe] “official MCP server documented at https://developer.navan.com/mcp/”
- [claimed-docs] “Show me every flagged expense over $500 from Q1 that hasn't been approved yet, grouped by department.”
- [claimed-docs] “What's our company policy on rideshare, and which transactions from last month violate it?”
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 drawnNavannone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
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 drawnNavan provides a documented public API (developer.navan.com) with OAuth 2.0 client-credentials auth, retrieval/update endpoints across expense, card, payroll, custom fields, and webhooks, plus a first-party MCP server for natural-language AI access — corroborated by a live llms.txt probe. Missing for 10: independent third-party developer accounts of building against the API and clearer rate-limit/versioning documentation.
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Discover company fields, batch-manage option values, and poll async job status.”
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.navan.com/llms.txt # Navan Developer Portal > Connect AI assistants to Navan travel and expen…”
- [probe] “official MCP server documented at https://developer.navan.com/mcp/”
- [claimed-docs] “Connect AI assistants — Claude, Cursor, ChatGPT, Codex, OpenClaw — to Navan data using the Model Context Protocol.”
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 NavanNavan's developer docs mention an OAuth 2.0 client-credentials flow for API access (navan-docs-2), which implies some credential-based authentication, but there is no explicit documentation of scoped permissions, granular access levels, or least-privilege controls specifically for AI agents connecting via MCP or API. missing for 10: explicit scope/permission definitions, least-privilege role configuration, agent-specific credential restrictions, and any documentation or independent verification of access-control granularity.
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
- [claimed-docs] “Connect AI assistants — Claude, Cursor, ChatGPT, Codex, OpenClaw — to Navan data using the Model Context Protocol.”
- [probe] “official MCP server documented at https://developer.navan.com/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 & ExpenseNavan documents an official REST API (OAuth2 client-credentials, expense/card/travel endpoints, webhooks) and an MCP server for AI assistants, which developers can build against, but there is no evidence of language-specific official SDKs (e.g., Python/JS client libraries) — only raw API/MCP documentation. missing for 10: explicit SDK packages/libraries, code samples in multiple languages, independent developer corroboration of SDK usage.
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Discover company fields, batch-manage option values, and poll async job status.”
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.navan.com/llms.txt # Navan Developer Portal > Connect AI assistants to Navan travel and expen…”
- [probe] “official MCP server documented at https://developer.navan.com/mcp/”
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 to BILL Spend & ExpenseNavannone0/10Webhooks are mentioned only once in passing as part of the API surface (navan-docs-2), with no documentation of subscription mechanics, event types, payload formats, or delivery guarantees; nothing shows an AI-native user can actually subscribe to events via webhooks.
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
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 NavanNavan's Ava AI and MCP integration provide AI-generated insights such as analyzing travel/spend data, summarizing by category, comparing to policy, predicting future spend, and flagging policy violations, all directly from Navan data. missing for 10: independent/hands-on verification of insight quality beyond vendor blog and docs, and details on how proactive/unprompted these suggestions are versus query-driven.
- [claimed-docs] “Analyze travel spend and craft suggestions to save”
- [claimed-docs] “Summarize travel spend by month and by category”
- [claimed-docs] “Analyze travel spend and compare it to company policy”
- [claimed-docs] “Predict future travel spend habits with ease”
- [claimed-docs] “Analyze spend data — query expenses, identify trends, and break down costs by department, vendor, or category.”
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
- [claimed-docs] “Show me every flagged expense over $500 from Q1 that hasn't been approved yet, grouped by department.”
- [claimed-docs] “What's our company policy on rideshare, and which transactions from last month violate it?”
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 to BILL Spend & ExpenseNavannone0/10Evidence shows Navan's AI features (MCP, Ava) are query/chat-based tools that answer questions or analyze spend on request, and Navan Edge explicitly states it 'will always ask for your explicit confirmation before booking, changing, or canceling any trip,' which is the opposite of autonomous background automation. No workflow, trigger, or scheduling mechanism for unattended background automations is documented anywhere in the pack.
- [claimed-docs] “Navan Edge will always ask for your explicit confirmation before booking, changing, or canceling any trip.”
- [claimed-docs] “No. Navan Edge will always ask for your explicit confirmation before booking, changing, or canceling any trip.”
- [claimed-docs] “The Navan MCP lets you connect Navan to your favorite AI products, so you can query Navan spend and travel data using natural language.”
- [claimed-docs] “Analyze spend data — query expenses, identify trends, and break down costs by department, vendor, or category.”
- [claimed-docs] “Unlimited policy and approval workflows”
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 NavanNavan documents built-in AI assistants (Ava for analyzing/summarizing/predicting travel spend, and Navan Edge for booking/changing/canceling trips with confirmation) that users can delegate expense and travel tasks to. Missing for 10: independent/hands-on verification of these assistants in action and detail on broader task types beyond travel/expense.
- [claimed-docs] “Analyze travel spend and craft suggestions to save”
- [claimed-docs] “Summarize travel spend by month and by category”
- [claimed-docs] “Analyze travel spend and compare it to company policy”
- [claimed-docs] “Predict future travel spend habits with ease”
- [claimed-docs] “Navan Edge provides 24/7 access to human travel agents via chat or phone at +1-877-536-3343 in English.”
- [claimed-docs] “Navan Edge will always ask for your explicit confirmation before booking, changing, or canceling any trip.”
- [claimed-docs] “Navan Edge personalizes results based on: Your preferences shared during chat, Your booking history, Loyalty programs connected to your acco…”
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 NavanNavan's MCP server and Ava assistant let users query spend, travel, policy, and card data with natural-language commands (e.g. flagged expenses, rideshare policy violations), and Navan Edge/Ava support conversational trip booking with confirmation steps. missing for 10: independent/hands-on verification of natural-language accuracy and breadth beyond vendor docs, and no evidence of NL commands for arbitrary in-app actions beyond travel/expense domains.
- [claimed-docs] “Connect AI assistants — Claude, Cursor, ChatGPT, Codex, OpenClaw — to Navan data using the Model Context Protocol.”
- [claimed-docs] “The Navan MCP lets you connect Navan to your favorite AI products, so you can query Navan spend and travel data using natural language.”
- [claimed-docs] “Show me every flagged expense over $500 from Q1 that hasn't been approved yet, grouped by department.”
- [claimed-docs] “What's our company policy on rideshare, and which transactions from last month violate it?”
- [claimed-docs] “Analyze spend data — query expenses, identify trends, and break down costs by department, vendor, or category.”
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
- [claimed-docs] “Analyze travel spend and craft suggestions to save”
- [claimed-docs] “Navan Edge will always ask for your explicit confirmation before booking, changing, or canceling any trip.”
- [probe] “official MCP server documented at https://developer.navan.com/mcp/”
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 drawnNavannone0/10Evidence shows a developer portal describing API endpoints (OAuth, expense/card endpoints, webhooks) and an MCP server for natural-language queries, but nothing indicates an interactive API reference with runnable/try-it-now code examples (e.g., Swagger/OpenAPI explorer or live sandbox).
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Discover company fields, batch-manage option values, and poll async job status.”
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 drawnNavannone0/10Navan's developer docs describe REST API endpoints, OAuth 2.0 flows, and an MCP server, but no evidence pack item mentions a downloadable OpenAPI/Swagger spec or any machine-readable API definition file. missing for 10: explicit OpenAPI/Swagger spec file, API reference generated from a spec, or a documented download link.
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Discover company fields, batch-manage option values, and poll async job status.”
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 & ExpenseNavannone0/10No evidence pack item mentions a sandbox, staging, or test environment for Navan's API, MCP server, or app; all endpoints and integrations described operate on live/production expense, travel, and card data. Missing for 10: any mention of a sandbox/test mode, staging API keys, or demo data environment separate from production.
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 drawnNavannone0/10The evidence pack documents Navan's API/MCP endpoints and OAuth flow but contains no mention of API versioning scheme or a documented deprecation policy for consumers to rely on.
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Discover company fields, batch-manage option values, and poll async job status.”
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 NavanNavan's MCP/API and Ava AI assistant let AI query flagged expenses, analyze spend, and check policy violations (navan-docs-5, navan-docs-6, navan-docs-22), plus native receipt scanning (navan-docs-24) — covering audit/flagging aspects. However there's no explicit evidence of AI auto-suggesting categories/memos or specifically detecting duplicate/fraudulent transactions. Missing for 10: automated category/memo suggestion, explicit duplicate-detection or fraud-catching functionality, and independent verification of these AI audit claims.
- [claimed-docs] “Show me every flagged expense over $500 from Q1 that hasn't been approved yet, grouped by department.”
- [claimed-docs] “What's our company policy on rideshare, and which transactions from last month violate it?”
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
- [claimed-docs] “Receipt scanning for on-the-go expenses”
- [claimed-docs] “Analyze spend data — query expenses, identify trends, and break down costs by department, vendor, or category.”
- [probe] “official MCP server documented at https://developer.navan.com/mcp/”
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 NavanThe Navan MCP explicitly supports conversational policy Q&A — asking about policy, approval flows, and why a transaction was flagged/declined (navan-docs-22, navan-docs-6) — and Ava can compare travel spend to policy after the fact (navan-docs-19). However there is no evidence of proactive 'chasing missing receipts' workflows or a pre-spend 'can I expense this?' check before the transaction occurs; the examples shown are retrospective queries on past transactions/spend. Missing for 10: proactive missing-receipt nudges/reminders, and evidence of a pre-purchase 'is this expensable' conversational check.
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
- [claimed-docs] “What's our company policy on rideshare, and which transactions from last month violate it?”
- [claimed-docs] “Analyze travel spend and compare it to company policy”
- [claimed-docs] “Show me every flagged expense over $500 from Q1 that hasn't been approved yet, grouped by department.”
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
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 NavanThe API docs mention batch-managing custom field option values and polling async job status, implying some bulk-processing capability, but there is no evidence of general bulk operations (e.g., bulk-approving multiple expenses, bulk-updating many transactions) across the platform for an AI-native user. missing for 10: evidence of bulk approve/reject workflows, bulk transaction updates via MCP, and independent confirmation that bulk API calls work at scale.
- [claimed-docs] “Discover company fields, batch-manage option values, and poll async job status.”
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
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 BILL Spend & ExpenseNavan documents configurable 'policy and approval workflows' and webhook endpoints, which imply some rule-based triggering of actions (e.g., flags, approvals) on expense events, but there is no explicit documentation of a user-facing rule/automation builder for defining custom event-triggered actions. Missing for 10: dedicated automation/rules engine documentation, examples of custom trigger-action definitions, and independent verification of automation depth beyond basic policy enforcement.
- [claimed-docs] “Unlimited policy and approval workflows”
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
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 drawnNavannone0/10Navan's evidence covers MCP-based querying, expense/travel management, webhooks, and async job polling, but there is no mention of scheduling recurring jobs, cron-like automation, or persistent workflow triggers for AI-native users. Absence of evidence for this applicable automation-depth capability yields none.
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 drawnNavannone0/10No evidence of any versioning, review, or rollback mechanism for automations/workflows in Navan or its MCP/API offerings; the pack covers expense/travel management, MCP querying, and API endpoints but nothing about automation version control or rollback.
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 BILL Spend & ExpenseNavannone0/10Evidence covers Navan's travel and expense management (card transactions, reimbursements, receipts, policy approvals) but contains no mention of invoice capture, vendor bill management, or paying vendors via ACH, check, or wire — the core AP capabilities the story requires.
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 BILL Spend & ExpenseNavannone0/10Evidence shows general card management (active/inactive status), policy workflows, and MCP queries about flagged/violating transactions, but nothing documents configurable restrictions by category, merchant, or amount, nor automatic point-of-sale locking/declining of out-of-policy spend. missing for 10: explicit documentation of category/merchant/amount-based card controls, missing for 10: evidence of real-time auto-lock or point-of-sale decline enforcement.
- [claimed-docs] “Card management — see which cards are active or inactive, how many cards a user has, and other card details.”
- [claimed-docs] “Connect existing corporate or business credit cards”
- [claimed-docs] “Unlimited policy and approval workflows”
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
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 BILL Spend & ExpenseNavannone0/10Evidence only shows querying/viewing existing card status via MCP (navan-docs-7) and connecting existing cards (navan-docs-9), but nothing about issuing new physical or virtual cards, setting per-card spend limits, or speed of issuance ('minutes'). Missing for 10: any documentation of card issuance workflow, virtual card creation, spend-limit configuration, or time-to-issue claims.
- [claimed-docs] “Card management — see which cards are active or inactive, how many cards a user has, and other card details.”
- [claimed-docs] “Connect existing corporate or business credit cards”
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 BILL Spend & ExpenseNavannone0/10The evidence pack covers Navan's MCP/API integrations, travel booking, rewards, and pricing highlights, but contains no mention of virtual card creation, single-vendor card controls, or SaaS/procurement card issuance. Card-related evidence only covers connecting existing corporate cards and viewing/managing card transaction data, not creating new single-vendor virtual cards.
- [claimed-docs] “Card management — see which cards are active or inactive, how many cards a user has, and other card details.”
- [claimed-docs] “Connect existing corporate or business credit cards”
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
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 NavanThe API exposes retrieval and update endpoints for card/Connect-card transactions and custom-field management (navan-docs-2, navan-docs-4, navan-docs-23), and MCP lets agents query uncoded/flagged transactions and policy violations in natural language (navan-docs-5, navan-docs-6, navan-docs-21, navan-docs-22). However, MCP is documented primarily as a query/analysis interface, not a write-back tool, and there is no explicit documentation of an agent proposing categorizations/policy flags and pushing clean coding back for human review as a workflow. Missing for 10: explicit MCP write/update support for coding transactions, a documented propose-then-review workflow, and independent confirmation of this end-to-end loop.
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Show me every flagged expense over $500 from Q1 that hasn't been approved yet, grouped by department.”
- [claimed-docs] “What's our company policy on rideshare, and which transactions from last month violate it?”
- [claimed-docs] “Analyze spend data — query expenses, identify trends, and break down costs by department, vendor, or category.”
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
- [claimed-docs] “Discover company fields, batch-manage option values, and poll async job status.”
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 NavanNavan's developer portal documents a REST API with OAuth 2.0 client-credentials flow, and endpoints covering transactions, expenses, receipts, custom fields, and webhooks. Missing for 10: explicit mention of scoped/permissioned tokens (vs just client-credentials) and independent third-party corroboration of the API's documented behavior beyond vendor docs.
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Discover company fields, batch-manage option values, and poll async job status.”
- [claimed-docs] “Receipt scanning for on-the-go expenses”
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 & ExpenseNavannone0/10The API docs mention retrieving/updating card transactions and MCP tools let you view card status (active/inactive, count), but there is no evidence of creating a new card, setting a spending limit, locking a card, or updating card controls programmatically via the public API — missing for 10: card creation endpoint, limit-setting endpoint, lock/freeze endpoint, control-update endpoint documentation.
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Card management — see which cards are active or inactive, how many cards a user has, and other card details.”
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
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 drawnNavan's API/MCP covers expense retrieval/update, transactions, custom fields, receipts, webhooks, and read-style spend/policy queries, but there is no evidence of API parity for travel booking, rewards, or other core UI workflows (e.g., booking trips, managing 'price to beat', Navan Edge concierge features) — those remain UI/chat-only per docs. missing for 10: API endpoints for travel booking/itinerary management, evidence of full UI-to-API parity beyond expense/finance domain, independent confirmation of completeness.
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Discover company fields, batch-manage option values, and poll async job status.”
- [claimed-docs] “Global travel inventory and exclusive rates”
- [claimed-docs] “Navan Edge provides 24/7 access to human travel agents via chat or phone at +1-877-536-3343 in English.”
- [probe] “official MCP server documented at https://developer.navan.com/mcp/”
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 to BILL Spend & ExpenseNavannone0/10Evidence shows API/MCP access for querying and updating expense/travel data, but nothing about bulk data export in open/portable formats or any documented account-closure/data-portability process for leaving the platform. Missing for 10: bulk export functionality, open-format data dumps, documented data portability/exit process.
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 BILL Spend & ExpenseNavan mentions 'Unlimited policy and approval workflows' as a pricing feature and MCP queries reference 'who needs to approve' a transaction, confirming approval workflows exist, but there is no evidence describing configurable multi-step chains (manager → budget owner → finance), delegation, or escalation logic when approvers sit idle. missing for 10: documentation of multi-step approval chain configuration, delegation rules, escalation timers/triggers, and named approver roles.
- [claimed-docs] “Unlimited policy and approval workflows”
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
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 drawnNavan documents policy/approval workflows and the ability to query why a transaction was flagged or who must approve it, which implies some traceability, but there is no explicit documentation of an immutable audit log, edit history, or audit-survivability guarantees. Missing for 10: explicit audit-trail/version-history documentation, evidence of edit logging, and any mention of external-audit compliance or SOC/ISO controls.
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
- [claimed-docs] “Unlimited policy and approval workflows”
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
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 BILL Spend & ExpenseNavan advertises "unlimited policy and approval workflows" and its MCP/AI layer can explain which policy applies, why a transaction was flagged, and who must approve it, implying a rules engine with per-transaction policy limits (e.g., rideshare, hotel price caps). However, the evidence never explicitly describes configuring limits by category/role/context or confirms that in-policy spend auto-approves while only exceptions route to a human. Missing for 10: explicit documentation of policy-builder granularity (category/role/context), explicit auto-approval behavior for in-policy expenses, and independent/hands-on confirmation of the approval-routing logic.
- [claimed-docs] “Unlimited policy and approval workflows”
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
- [claimed-docs] “What's our company policy on rideshare, and which transactions from last month violate it?”
- [claimed-docs] “Navan shows employees a "price to beat" for every hotel search — a smart target based on location, date, and demand that's under their poli…”
- [claimed-docs] “Navan shows employees a "price to beat" for every hotel search — a smart target based on location, date, and demand that's under their polic…”
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 drawnNavannone0/10No evidence anywhere in the pack about data residency, region selection, or data storage location controls for Navan's data or its AI/MCP features; the pack only covers MCP capabilities, API endpoints, pricing features, and travel booking experience.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnNavannone0/10No evidence in the pack addresses AI training data usage, opt-out controls, or data privacy policy regarding model training; all evidence covers MCP integrations, expense/travel features, and unrelated community complaints. Missing for 10: any explicit statement on AI/model training data usage, opt-out settings, or data retention/privacy commitments.
ai-native userControl data retention and deletion
weight 2 · round drawnNavannone0/10No evidence in the pack addresses data retention policies, deletion controls, or user/admin ability to manage how long AI/assistant data is stored or how to delete it — the pack covers MCP querying, API surfaces, pricing features, and travel booking, but nothing on retention/deletion controls.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnNavannone0/10No evidence in the pack addresses telemetry/usage-tracking opt-out settings for Navan or its AI/MCP features; all evidence covers MCP data access, expense/travel features, and pricing.
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 drawnNavannone0/10Evidence covers Navan's MCP/API integrations, travel booking rewards, and generic 'receipt scanning' and 'manage expenses' pricing bullets, but nothing describes mileage tracking, map-based distance calculation, or automated per-diem rate application. Missing for 10: mileage logging with GPS/map distance capture, per-diem rate lookup/auto-application, any auto-build-expense-from-mileage workflow.
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 NavanDocs mention 'Receipt scanning for on-the-go expenses' as a pricing-page feature bullet and API docs mention a 'receipts' surface, implying photo capture and filing against transactions, but there's no detail on OCR accuracy, email-forwarding capture, or automatic matching logic. Missing for 10: technical documentation of the OCR/email-forwarding pipeline, evidence of automatic transaction matching, and independent/hands-on confirmation of accuracy.
- [claimed-docs] “Receipt scanning for on-the-go expenses”
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
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 drawnNavannone0/10Evidence only mentions generic 'receipt scanning for on-the-go expenses' and receipts as an API surface, but nothing describes automatic matching of receipts to card transactions, e-receipt pull from integrations, or smart nudging only when genuinely missing.
- [claimed-docs] “Receipt scanning for on-the-go expenses”
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
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 drawnNavan pricing page mentions it can 'manage expenses and issue reimbursements' and includes receipt scanning, but there is no evidence describing direct-deposit payout, a specific reimbursement timeline (days), or end-to-end tracking from submission to payout. missing for 10: direct deposit mechanism, reimbursement speed/SLA, submission-to-payout tracking/status visibility.
- [claimed-docs] “Manage expenses and issue reimbursements”
- [claimed-docs] “Receipt scanning for on-the-go expenses”
- [claimed-docs] “Unlimited policy and approval workflows”
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 drawnNavannone0/10Evidence only shows generic reimbursement management (docs-8) with no mention of local-currency payouts, multi-currency support, or eliminating a separate international payment process for reimbursing employees abroad.
- [claimed-docs] “Manage expenses and issue reimbursements”
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 BILL Spend & ExpenseNavan documents general 'unlimited policy and approval workflows' and card management/policy-limit features, and MCP queries can surface policy violations and approval status, implying some enforcement infrastructure exists. However, there is no direct evidence of budget allocation to specific teams/projects or of card limits being tied to those budgets and automatically enforced. Missing for 10: explicit budget-allocation-to-team/project feature docs, evidence that card limits are dynamically tied to allocated budgets, and any hands-on confirmation that approvals actually block over-budget spend.
- [claimed-docs] “Unlimited policy and approval workflows”
- [claimed-docs] “Card management — see which cards are active or inactive, how many cards a user has, and other card details.”
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
- [claimed-docs] “Show me every flagged expense over $500 from Q1 that hasn't been approved yet, grouped by department.”
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 NavanNavan's docs show spend can be queried by department, vendor/merchant, and category via MCP/API, and card transactions (including Navan-issued cards) are retrievable directly rather than waiting for statements, supporting near real-time visibility for founders. Missing for 10: explicit same-day latency claims for card feeds, a dedicated real-time dashboard description, and independent/hands-on corroboration of update speed.
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Analyze spend data — query expenses, identify trends, and break down costs by department, vendor, or category.”
- [claimed-docs] “Show me every flagged expense over $500 from Q1 that hasn't been approved yet, grouped by department.”
- [claimed-docs] “Ask questions about policies, approval flows, and flag/decline reasons — understand why a transaction was flagged, who needs to approve it, …”
- [claimed-docs] “OAuth 2.0 client-credentials flow, retrieval and update endpoints across the expense surface, custom-field management, receipts, and webhook…”
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 NavanNavan's core booking product shows in-platform flight/hotel booking with policy limits enforced at search time ('price to beat' under policy, docs-12/27), self-serve booking with 24/7 support (docs-11), human travel agents that must confirm before booking (docs-14-16), and unlimited configurable policy/approval workflows applied to travel (docs-25) plus connected corporate cards for direct billing (docs-9) rather than post-hoc expensing. Missing for 10: independent/hands-on confirmation that out-of-policy bookings are actually blocked or flagged in real time (only vendor marketing/docs cited), and no detail on how policy violations are handled during the booking flow itself.
- [claimed-docs] “Global travel inventory and exclusive rates”
- [claimed-docs] “Self-serve changes and 24/7 travel support agents”
- [claimed-docs] “Navan shows employees a "price to beat" for every hotel search — a smart target based on location, date, and demand that's under their poli…”
- [claimed-docs] “Navan Edge provides 24/7 access to human travel agents via chat or phone at +1-877-536-3343 in English.”
- [claimed-docs] “Navan Edge will always ask for your explicit confirmation before booking, changing, or canceling any trip.”
- [claimed-docs] “Unlimited policy and approval workflows”
- [claimed-docs] “Connect existing corporate or business credit cards”
- [claimed-docs] “Navan shows employees a "price to beat" for every hotel search — a smart target based on location, date, and demand that's under their polic…”
Trip expenses
employeeA trip's expenses — bookings, cards, receipts — collect themselves into one itinerary-linked report
weight 1 · round to NavanNavan's own docs describe unified handling of card transactions, manual expenses, receipts, and reimbursements within a single platform/API (navan-docs-4, navan-docs-8, navan-docs-9, navan-docs-24), implying expenses converge into one system, but no evidence explicitly confirms automatic itinerary-linked report assembly from bookings+cards+receipts without manual reconciliation steps. Missing for 10: explicit documentation of automatic itinerary-to-expense-report linkage, and independent/hands-on confirmation that receipts and card charges auto-match to trip itineraries without manual effort.
- [claimed-docs] “Retrieve and update Navan card transactions, Connect card transactions, manual expenses, payroll, repayments, fees, adjustments, daily rebat…”
- [claimed-docs] “Manage expenses and issue reimbursements”
- [claimed-docs] “Connect existing corporate or business credit cards”
- [claimed-docs] “Receipt scanning for on-the-go expenses”
- [claimed-docs] “Unlimited policy and approval workflows”
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 userRead the product's source under an open license
weight 2 · not comparableNavann/aNavan is a closed-source SaaS travel/expense platform; open-sourcing its source code is not a fair expectation for this product category, and no evidence pack item discusses source licensing.
ai-native userSelf-host the core product
weight 3 · not comparableNavann/aNavan is a SaaS travel/expense management product with no self-hosted deployment option; self-hosting the core product is a category error for this type of cloud SaaS offering.