Expensify vs Navan

Accounting sync

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

   weight 3 · round to Expensify
   Expensify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   The 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.

   ⚑ flag

Close

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

   weight 2 · round to Navan
   Expensify!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

   Navan~partialclaimed7/10

   Navan'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.”

   proof ↗⚑ flag

Multi entity

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

   weight 2 · round drawn
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   Evidence 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.

   ⚑ flag

Agent access

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

   weight 2 · round to Navan
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan✓fullprobed9/10

   A 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/”

   proof ↗⚑ flag

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

   weight 2 · round to Navan
   Expensify~partialclaimed3/10

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

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

   proof ↗⚑ flag

   Navan~partialclaimed5/10

   Navan'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.”

   proof ↗⚑ flag

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

   weight 3 · round to Navan
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan✓fullprobed8/10

   Navan 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?”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Expensify—none0/10

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

   ⚑ flag

   Navan—none0/10

   The 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.)

   ⚑ flag

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

   weight 3 · round to Navan
   Expensify✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Navan✓fullprobed8/10

   Navan 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.”

   proof ↗⚑ flag

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

   weight 2 · round to Navan
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan~partialprobed3/10

   Navan'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/”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Navan
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan~partialprobed5/10

   Navan 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/”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Expensify—none0/10

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

   ⚑ flag

   Navan—none0/10

   Webhooks 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…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Navan
   Expensify!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

   Navan✓fullclaimed8/10

   Navan'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?”

   proof ↗⚑ flag

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

   weight 2 · round to Expensify
   Expensify~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   Evidence 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”

   proof ↗⚑ flag

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

   weight 3 · round to Navan
   Expensify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Navan✓fullclaimed7/10

   Navan 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…”

   proof ↗⚑ flag

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

   weight 2 · round to Navan
   Expensify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Navan✓fullprobed7/10

   Navan'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/”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   Evidence 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.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   Navan'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.”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Expensify—none0/10

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

   ⚑ flag

   Navan—none0/10

   No 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.

   ⚑ flag

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

   weight 2 · round drawn
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   The 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.”

   proof ↗⚑ flag

Ai coding

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

   weight 2 · round to Navan
   Expensify!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

   Navan~partialprobed6/10

   Navan'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/”

   proof ↗⚑ flag

Ai policy

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

   weight 2 · round to Navan
   Expensify~partialcommunity4/10

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

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

   proof ↗⚑ flag

   Navan~partialclaimed5/10

   The 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…”

   proof ↗⚑ flag

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

   weight 2 · round to Navan
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan~partialclaimed4/10

   The 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…”

   proof ↗⚑ flag

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

   weight 3 · round to Expensify
   Expensify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Navan~partialclaimed4/10

   Navan 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…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   Navan'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.

   ⚑ flag

Bill pay

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

   weight 2 · round drawn
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   Evidence 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.

   ⚑ flag

Card controls

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

   weight 3 · round to Expensify
   Expensify~partialclaimed3/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   Evidence 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, …”

   proof ↗⚑ flag

Card issuance

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

   weight 3 · round to Expensify
   Expensify~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   Evidence 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”

   proof ↗⚑ flag

Virtual cards

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

   weight 2 · round drawn
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   The 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…”

   proof ↗⚑ flag

Agent access

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

   weight 3 · round to Navan
   Expensify~partialcommunity4/10

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

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

   proof ↗⚑ flag

   Navan~partialclaimed5/10

   The 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.”

   proof ↗⚑ flag

Api access

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

   weight 3 · round to Navan
   Expensify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Navan✓fullclaimed8/10

   Navan'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”

   proof ↗⚑ flag

Card api

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

   weight 2 · round drawn
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   The 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…”

   proof ↗⚑ flag

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

   weight 2 · round to Navan
   Expensify~partialprobed3/10

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

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

   proof ↗⚑ flag

   Navan~partialprobed5/10

   Navan'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/”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Expensify—none0/10

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

   ⚑ flag

   Navan—none0/10

   Evidence 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.

   ⚑ flag

Approvals

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

   weight 2 · round to Navan
   Expensify—none0/10

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

   ⚑ flag

   Navan~partialclaimed2/10

   Navan 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, …”

   proof ↗⚑ flag

Audit trail

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

   weight 2 · round to Navan
   Expensify—none0/10

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

   ⚑ flag

   Navan~partialclaimed4/10

   Navan 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…”

   proof ↗⚑ flag

Policy engine

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

   weight 3 · round to Navan
   Expensify~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Navan~partialclaimed5/10

   Navan 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…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Expensify—none0/10

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

   ⚑ flag

   Navan—none0/10

   No 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.

   ⚑ flag

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

   weight 3 · round drawn
   Expensify—none0/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   No 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.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Expensify—none0/10

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

   ⚑ flag

   Navan—none0/10

   No 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.

   ⚑ flag

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

   weight 2 · round drawn
   Expensify—none0/10

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

   ⚑ flag

   Navan—none0/10

   No 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.

   ⚑ flag

Mileage perdiem

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

   weight 2 · round drawn
   Expensify—none0/10

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

   ⚑ flag

   Navan—none0/10

   Evidence 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.

   ⚑ flag

Receipt capture

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

   weight 3 · round to Navan
   Expensify!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

   Navan~partialclaimed5/10

   Docs 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…”

   proof ↗⚑ flag

Receipt matching

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

   weight 2 · round to Expensify
   Expensify~partialcommunity4/10

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

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

   proof ↗⚑ flag

   Navan—none0/10

   Evidence 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…”

   proof ↗⚑ flag

Domestic

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

   weight 3 · round to Navan
   Expensify—none0/10

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

   ⚑ flag

   Navan~partialclaimed3/10

   Navan 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”

   proof ↗⚑ flag

International

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

   weight 2 · round drawn
   Expensify—none0/10

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

   ⚑ flag

   Navan—none0/10

   Evidence 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”

   proof ↗⚑ flag

Budgets

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

   weight 2 · round to Navan
   Expensify~partialclaimed3/10

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

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

   proof ↗⚑ flag

   Navan~partialclaimed4/10

   Navan 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.”

   proof ↗⚑ flag

Dashboards

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

   weight 3 · round to Navan
   Expensify!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

   Navan✓fullclaimed7/10

   Navan'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…”

   proof ↗⚑ flag

Booking

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

   weight 2 · round to Navan
   Expensify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Navan✓fullclaimed8/10

   Navan'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…”

   proof ↗⚑ flag

Trip expenses

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

   weight 1 · round to Navan
   Expensify!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

   Navan~partialclaimed6/10

   Navan'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”

   proof ↗⚑ flag