Wave vs Bench

Agent access

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

   weight 2 · round drawn
   Wave—none0/10

   A direct probe found no llms.txt file (404) and no agent-oriented docs surface; Wave's marketing pages contain no mention of llms.txt or agent-consumable documentation, and its developer portal is blocked to crawlers.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a bookkeeping service, not a dev tool/platform, but the axis still applies since any web product could publish agent-oriented docs; probes explicitly show llms.txt returns 404, docs-as-markdown 404, and no OpenAPI spec found. There is no evidence of any agent-oriented documentation surface.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Wave—none0/10

   Wave is a small-business accounting/invoicing SaaS with no evidence of a CLI, headless mode, or CI-friendly automation surface; llms.txt and OpenAPI probes both 404, and the developer/API portal is walled off with no documented programmatic interface. Nothing suggests Wave can be run headlessly or scripted in a CI pipeline.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—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

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

   weight 3 · round drawn
   Wave—none0/10

   Wave is an accounting SaaS product, so an official MCP server is a plausible axis, but there is no evidence of any MCP server, API docs accessible, or agent integration; probes for llms.txt and OpenAPI both 404, and the developer portal is walled off from crawling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—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

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

   weight 3 · round drawn
   Wave—none0/10

   Marketing pages document no public API, and direct probes for llms.txt/OpenAPI both 404; the developer portal exists but is blocked to crawlers so no documented, accessible API surface is evidenced.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a bookkeeping/accounting service with no evidence of a documented public API; direct probes for llms.txt, docs.md, and OpenAPI/swagger endpoints all returned 404, and no docs mention an API for AI-native integration.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Wave—none0/10

   No evidence of any API credential system, scoped tokens, or agent-oriented access controls; Wave's role-based access is for human collaborators (admin/editor/viewer), and its developer/API portal could not even be crawled to confirm any credentialing mechanism exists.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”

   proof ↗⚑ flag

   Bench—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

6. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Wave—none0/10

   No evidence of official SDKs for AI-native/programmatic use; llms.txt and OpenAPI probes both 404, and the developer/GraphQL API portal is walled off from crawling with no documentation surfaced. Marketing pages describe only end-user accounting features, not SDKs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a bookkeeping/tax service with no evidence of any public SDK, API, or developer library; probes for llms.txt, docs-md, and OpenAPI specs all returned 404. Missing for 10: any official SDK, API documentation, or developer integration surface.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

7. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Wave—none0/10

   No evidence of webhook support anywhere in Wave's marketing pages or developer portal; the developer portal itself couldn't be crawled and is described as documenting no webhook surface, and llms.txt/openapi probes both returned 404.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Bench—none0/10

   No evidence of any webhook subscription mechanism, API, or event system; probes for llms.txt, docs-md, and OpenAPI specs all return 404, and Bench is a human-plus-software bookkeeping service with no developer/webhook offering documented.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   Wave—none0/10

   Evidence shows OCR data extraction and automation (auto-categorize, reminders) but no AI-generated insights, analysis, or suggestions surfaced to users; reports are static comparisons, not AI-driven recommendations. No mention of AI/ML-based insight generation anywhere in the pack.

   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag

   Bench—none0/10

   Bench's evidence describes automation (data entry, categorization) and human bookkeeper support, but nothing describes AI-generated insights, recommendations, or suggestions surfaced to the user from their data — 'smart automation' refers to categorization mechanics, not generative analysis or advisory insights. Missing for 10: any mention of AI-generated commentary, anomaly detection, forecasting, or proactive suggestions derived from financial data.

   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”

   proof ↗⚑ flag

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

   weight 2 · round to Wave
   Wave~partialprobed4/10

   Wave ships several fixed, always-on background automations (auto bank import/categorization, recurring invoices with auto payment reminders, auto payroll tax filing) that run without manual triggering, per wave-docs-2, wave-docs-5, wave-docs-10, wave-docs-14. However these are hard-coded product features, not a general-purpose automation/agent framework the user can configure, and there is no API, webhook, or MCP surface documented for building custom autonomous workflows (wave-probe-1, wave-probe-2, wave-supp-dev-portal-wall). Missing for 10: a configurable automation builder, any AI-agent/orchestration capability, and a documented API/webhook layer for extending automations.

   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—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

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

   weight 3 · round drawn
   Wave—none0/10

   No evidence anywhere in the pack of a built-in AI assistant or agentic feature; Wave's docs describe automation (auto-import, OCR, reminders) but nothing about delegating tasks to an AI assistant, and the developer portal is inaccessible with no API/AI mention on marketing pages.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”

   proof ↗⚑ flag

   Bench—none0/10

   Bench offers human bookkeepers plus automation for data entry and categorization, but there is no evidence of a built-in AI assistant that a user can delegate tasks to conversationally — communication is described as messaging with a human team, not an AI agent. Missing for 10: any mention of an AI assistant/chat feature, agentic task delegation, or AI-driven interaction surface within the product.

   • [claimed-docs] “Effortless messaging with your Bench team for unlimited support or advice, anytime, anywhere”
   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Wave—none0/10

   No evidence of any natural-language command interface, chat assistant, or AI-native control surface; Wave's marketing pages describe only manual UI-based accounting/invoicing features, and probes for llms.txt/openapi found nothing, with the developer portal walled off from crawling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—none0/10

   Bench offers human-support messaging and a client dashboard, but there is no evidence of a natural-language command interface (chat-driven actions, NL query of financial data, etc.); probes for llms.txt, docs-md, and OpenAPI all 404, indicating no AI-native interface layer. missing for 10: any natural-language command/chat-to-action capability, NL query support, or API/agent interface evidence.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”
   • [claimed-docs] “Effortless messaging with your Bench team for unlimited support or advice, anytime, anywhere”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Wave—none0/10

   There is no evidence of an interactive API reference or runnable examples; probes for openapi/llms.txt returned 404s, and the developer portal itself is blocked from crawling with no documented API surface accessible.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a bookkeeping/accounting service with no API, no interactive API reference, and no runnable examples; probes for llms.txt, docs.md, and OpenAPI specs all returned 404. missing for 10: any API reference, interactive docs, runnable code examples.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Wave—none0/10

   Direct probes for OpenAPI/swagger specs and llms.txt returned 404s, and Wave's developer portal (GraphQL API) is blocked to crawlers with no machine-readable spec surfaced; marketing pages document no API spec at all.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—none0/10

   Probes explicitly show llms.txt, docs.md, and all openapi/swagger candidate paths return 404, and no docs mention any API spec; Bench is a bookkeeping service with no evidence of a machine-readable API for AI agents.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Wave—none0/10

   No evidence of any sandbox, staging, test-mode, or dev environment for Wave; the developer portal is inaccessible and marketing pages document no API/test environment for isolating data from production.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Bench—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

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

   weight 2 · round drawn
   Wave—none0/10

   No evidence of versioned APIs or a documented deprecation policy; the developer/API portal is inaccessible for crawling and Wave's public marketing pages document no API surface at all, with llms.txt and OpenAPI probes both returning 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a bookkeeping/tax service with no evidence of a public API at all — probes for OpenAPI specs, docs, and llms.txt all returned 404. No mention of versioning or a deprecation policy anywhere in the evidence pack. Missing for 10: any public API, version numbers, changelog, or deprecation policy documentation.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

   weight 2 · round to Wave
   Wave~partialprobed2/10

   Wave documents a narrow bulk feature (uploading up to 10 receipts at once with OCR), but there is no evidence of broader bulk operations (e.g., bulk invoice creation/edits, bulk transaction updates) or any API/CLI/MCP surface an AI-native user could script against — the developer portal is crawl-walled and no OpenAPI/llms.txt exists. missing for 10: bulk invoice/transaction/customer operations, programmatic API or CLI access for scripted bulk actions, evidence beyond the 10-item receipt cap.

   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a human-plus-software bookkeeping service focused on categorization, reporting, and tax filing for individual accounts; no evidence describes any bulk/batch operation capability across many items (e.g., bulk transaction edits, bulk uploads, batch API operations) for AI-native or power users. Probes also show no API/docs surface for programmatic bulk actions.

   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Wave—none0/10

   Wave offers only a handful of fixed, vendor-built automations (recurring invoices, overdue reminders, auto payroll tax filing, bank auto-categorization) — none of these let a user define custom rules or trigger-action logic on arbitrary events. No evidence of a rules engine, webhooks, or conditional automation builder; the developer/API surface is walled off (403) and marketing pages document no such capability.

   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a bookkeeping/accounting service with backend automation for categorization and reminders, but there is no evidence of a user-facing rule engine where AI-native users can define custom triggers/actions on events; the automation described is fixed internal workflow, not configurable rules.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Wave
   Wave~partialprobed3/10

   Wave supports one narrow recurring automation — recurring invoices and payment reminders (wave-docs-10, wave-docs-2) — but there is no evidence of a general-purpose scheduler, API-triggered jobs, or workflow automation platform that an AI-native user could hook into; its developer/API surface is walled off from public documentation (wave-supp-dev-portal-wall, wave-probe-1, wave-probe-2). Missing for 10: programmable/scriptable recurring jobs beyond invoicing, API or webhook-based scheduling, and any AI/automation-platform integration evidence.

   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Bench—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

Ai reconciliation

1. ai-native userHave an agent reconcile a month end-to-end, matching transactions, flagging exceptions, and preparing the close for human review

   weight 3 · round drawn
   Wave—none0/10

   Wave's evidence covers auto-import/categorization, invoicing, payroll, and receipts, but there is no mention of an AI agent performing end-to-end reconciliation, flagging exceptions, or preparing a close for human review; no automation/agent framework or API for such orchestration is documented, and the developer portal is a crawl wall with no public API/agent hooks shown.

   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench's evidence describes automated data entry/categorization plus human bookkeepers preparing reports, not an autonomous agent that reconciles a month end-to-end, flags exceptions, and stages a close for human review. No documentation of exception-flagging logic, agent-driven reconciliation workflow, or AI-native interface exists in the pack. Missing for 10: evidence of automated exception detection, an agentic reconciliation workflow, and any API/agent interface for month-end close.

   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

Bank feeds

1. founderConnect bank and credit-card accounts so transactions import automatically every day

   weight 3 · round to Wave
   Wave✓fullclaimed8/10

   Wave's Pro Plan explicitly documents automatic daily bank/credit-card feed import with auto-merge and categorization, directly matching the story, and this is corroborated across multiple marketing pages. Missing for 10: independent/hands-on verification (e.g., user reviews confirming daily reliability) beyond vendor claims, and no detail on credit-card-specific connection flow distinct from bank accounts.

   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”

   proof ↗⚑ flag

   Bench✓fullclaimed7/10

   Bench's docs explicitly describe connecting all financial accounts to automate daily data entry and transaction categorization, which directly matches the story of automatic daily import via connected bank/credit card accounts. Missing for 10: no independent/hands-on corroboration of connection reliability, no detail on supported bank list or sync frequency specifics beyond marketing copy.

   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”

   proof ↗⚑ flag

Categorization

1. founderGet automatic categorization suggestions for imported transactions that learn from my corrections

   weight 2 · round drawn
   Wave~partialclaimed4/10

   Wave documents automatic bank transaction import and categorization on the Pro Plan (auto-merge/categorize), but no evidence anywhere describes the system learning from user corrections over time — a core part of the story. Missing for 10: any documentation of a learning/adaptive categorization mechanism, evidence that manual recategorization improves future suggestions, and independent/hands-on confirmation of categorization accuracy improving.

   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”

   proof ↗⚑ flag

   Bench~partialclaimed4/10

   Bench documents automated, 'smart automation' transaction categorization with 'instant guidance' (bench-docs-4, bench-supp-automation), which covers the core categorization-suggestion capability, but since Bench is a human-plus-software bookkeeping service, human bookkeepers—not the software—typically apply corrections, and there is no evidence describing a feedback loop where the system learns from founder corrections. Missing for 10: any documentation of a correction-learning mechanism, founder-facing feedback UI, or improvement in suggestion accuracy over time.

   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

Reconciliation

1. accountantReconcile each bank account against the ledger with matched, unmatched, and duplicate transactions surfaced for review

   weight 3 · round to Wave
   Wave~partialclaimed4/10

   Wave documents bank auto-import with auto-merge and categorization (implying some duplicate/match handling), but there is no evidence of a dedicated reconciliation view that explicitly surfaces matched, unmatched, and duplicate transactions for accountant review, nor of bank-to-ledger balance reconciliation reporting. Missing for 10: explicit unmatched-transaction review UI, duplicate-transaction flagging documentation, and a formal reconciliation/statement-balance-match report.

   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”

   proof ↗⚑ flag

   Bench—none0/10

   Bench's evidence covers account connection, automated categorization, and reporting, but no citation describes a reconciliation workflow that surfaces matched, unmatched, and duplicate transactions for accountant review. missing for 10: explicit reconciliation UI/workflow, matched/unmatched transaction views, duplicate detection and review surface.

   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Bill management

1. accountantCapture vendor bills, route them for approval, and schedule payments from one workflow

   weight 2 · round drawn
   Wave—none0/10

   Evidence only shows Wave lets users 'create unlimited... bills' as a record type (wave-docs-7); there is no mention of vendor bill capture workflow, approval routing, or scheduled bill payments anywhere in the pack. Wave's payments feature is explicitly for receiving customer payments on invoices, not paying vendors (wave-supp-payments), and no AP-specific workflow is documented.

   • [claimed-docs] “Create unlimited estimates, invoices, bills, and bookkeeping records”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a bookkeeping/tax service focused on categorization, reporting, and human bookkeeper support; no evidence of bill capture (AP inbox/OCR), approval routing, or scheduled bill payment workflows anywhere in the docs, pricing, or banking pages.

   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “"Banking by Mainstreet — Get dedicated business accounts, debit cards, and automated financial management tools that integrate seamlessly wi…”
   • [claimed-docs] “Published service pricing: Bookkeeping Grow from $199/month ("An accessible, lighter-touch plan—built for lean businesses seeking financial …”

   proof ↗⚑ flag

Payables

1. accountantSee accounts payable aging and vendor balances at any point in time

   weight 2 · round drawn
   Wave—none0/10

   Evidence confirms Wave supports creating bills and general accounting reports (month-to-month/year-to-year comparisons), but nothing documents an accounts-payable aging report or vendor balance tracking at a point in time. Missing for 10: AP aging report, vendor balance summary/statement, point-in-time vendor ledger view.

   • [claimed-docs] “Create unlimited estimates, invoices, bills, and bookkeeping records”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench's evidence covers bookkeeping automation, categorization, income statement/balance sheet reporting, banking and tax prep, but nowhere mentions accounts payable aging, vendor balances, or bill-tracking reports at a point in time. Bench appears to focus on income statement/balance sheet reporting rather than AP-specific aging reports.

   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”

   proof ↗⚑ flag

Close process

1. accountantLock closed periods so prior-period numbers cannot change without an explicit reopening

   weight 2 · round drawn
   Wave—none0/10

   No evidence Wave offers period locking or close controls; docs mention role-based access and reports but nothing about locking closed periods or preventing prior-period edits without explicit reopening.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”

   proof ↗⚑ flag

   Bench—none0/10

   No evidence describes period locking, close controls, or reopening workflows; Bench is presented as a human-plus-software bookkeeping service with reporting/downloads, not a ledger system with period-lock controls exposed to the accountant/customer. missing for 10: any mention of period closing, locking prior periods, or explicit reopening controls.

   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”

   proof ↗⚑ flag

2. accountantRun a month-end close against a checklist that tracks reconciliations, accruals, and review sign-offs

   weight 3 · round drawn
   Wave—none0/10

   No evidence of any month-end close checklist, reconciliation tracking, accrual management, or review sign-off workflow; Wave's evidence covers invoicing, payroll, receipts, and basic reports only, and it explicitly positions itself as built for small business owners rather than accountants performing formal close processes.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag

   Bench—none0/10

   Bench markets itself as a done-for-you bookkeeping/tax service with messaging, document upload, categorization, and real-time reports, but nothing in the evidence describes a month-end close checklist tracking reconciliations, accruals, or review sign-offs — only generic 'timely reminders' are mentioned, which is not the same as a structured close workflow.

   • [claimed-docs] “Get timely reminders to stay on top of your financial tasks and deadlines”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Collaboration

1. founderInvite my external accountant or bookkeeper with role-scoped access to review and adjust the books

   weight 3 · round to Wave
   Wave✓fullclaimed7/10

   Wave explicitly documents inviting an accountant/bookkeeper with role-scoped access (payroll manager, admin, editor, viewer on Pro, or free accountant/tax pro role), directly matching the story. Missing for 10: independent/hands-on verification of the invite/permissions flow and finer detail on what each role can/cannot edit.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench's evidence describes a done-for-you bookkeeping service where Bench's own staff manage the books and communicate with the founder, with no mention of inviting an external accountant/bookkeeper as a role-scoped collaborator with adjustable permissions inside a shared ledger. The 'Add a bookkeeper to your team' claim refers to Bench's own hire-a-bookkeeper offering working inside the founder's existing systems, not the founder granting scoped access to their own outside accountant.

   • [claimed-docs] “Add a bookkeeper to your team who works with your existing systems”
   • [claimed-docs] “Published service pricing: Bookkeeping Grow from $199/month ("An accessible, lighter-touch plan—built for lean businesses seeking financial …”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

Data access

1. developerPull the full general ledger and trial balance through a documented API in open formats

   weight 3 · round drawn
   Wave—none0/10

   Evidence shows Wave's developer/GraphQL API portal exists but is crawl-walled and unverifiable, and explicit probes for llms.txt/openapi/swagger all return 404; no documentation confirms GL or trial balance export via API in open formats (CSV/JSON/XML). Marketing pages describe UI-based 'reports' but never reference an API endpoint for ledger/trial balance data.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench only offers report viewing/downloads (income statement, balance sheet) via its web app; there is no documented API, no OpenAPI/Swagger spec, and probes for llms.txt, markdown docs, and OpenAPI endpoints all returned 404s, so developers have no documented way to pull the GL or trial balance in open formats.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Integrations

1. founderConnect my banking, payments, and payroll systems so their activity flows into the ledger automatically

   weight 2 · round drawn
   Wave~partialclaimed6/10

   Wave clearly documents automatic bank-feed import/categorization (Pro plan) and integrated online payments that flow directly into invoicing/accounting records, so banking and payments activity does land in the ledger automatically. However, the payroll product's features (direct deposit, tax filing, employee portal) are described in isolation with no explicit statement that payroll transactions sync into the accounting ledger the way bank/payment data does, and there's no evidence of an API/webhook layer for connecting external banking, payment, or payroll systems beyond Wave's own native modules. Missing for 10: explicit documentation that payroll runs automatically post to the general ledger, and any API/integration surface for external banking or payroll systems.

   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”
   • [claimed-docs] “Run payroll in minutes”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [claimed-docs] “Deposit payments directly into your employees’ bank accounts. Less work for you, and your team will love it.”

   proof ↗⚑ flag

   Bench~partialclaimed6/10

   Bench's docs claim customers can 'connect all your financial accounts to automate data entry' and offers integrated banking (Banking by Bench/Mainstreet), which supports bank/payment account linking flowing into bookkeeping. However, payroll integration is never explicitly mentioned, and the ledger itself is not customer-facing/editable — it's a human-plus-software service producing reports rather than a live self-serve ledger. missing for 10: explicit payroll system integration, technical detail on connection breadth (which banks/payment processors), independent/hands-on confirmation of automated data flow reliability.

   • [claimed-docs] “Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Get dedicated business accounts, debit cards, and automated financial management tools that integrate seamlessly with your bookkeeping opera…”
   • [claimed-docs] “"Banking by Mainstreet — Get dedicated business accounts, debit cards, and automated financial management tools that integrate seamlessly wi…”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Migration

1. founderMigrate historical books from another accounting system without losing transaction detail

   weight 1 · round to Bench
   Wave~partialclaimed3/10

   Wave mentions an 'onboarding' process for switching from other accounting software like Freshbooks, but this is a single glancing bullet point with no detail on how historical transactions, ledgers, or account balances are actually imported or whether transaction-level detail is preserved. missing for 10: documented import/migration tool, description of data mapping (chart of accounts, historical invoices, journal entries), evidence that no transaction detail is lost, and any independent user reports of successful bookkeeping migrations.

   • [claimed-docs] “Onboarding when switching from other accounting software, like Freshbooks”
   • [claimed-docs] “When you switch from another payroll software, migrating your data is simple.”

   proof ↗⚑ flag

   Bench~partialclaimed5/10

   Bench explicitly offers 'Catch Up Bookkeeping' for businesses behind on their books, implying it can reconstruct/backfill historical transaction data, and its human-bookkeeper model suggests manual handling of past records. However, there is no explicit documentation of migrating data from another accounting system (e.g., QuickBooks, Xero) with transaction-level fidelity preserved, no import tooling, and no evidence addressing loss/retention of transaction detail during migration. Missing for 10: explicit migration/import process from other platforms, evidence of transaction-level data preservation, any tooling or API for historical data transfer.

   • [claimed-docs] “Catch up bookkeeping services for small businesses, no matter how far behind they are”
   • [claimed-docs] “Add a bookkeeper to your team who works with your existing systems”
   • [claimed-docs] “The buying motion is demo-led for service fit: "Book a demo with our friendly team of experts. Not sure where to start or which accounting s…”

   proof ↗⚑ flag

Invoicing

1. founderCreate and send invoices with online payment options and see when they are viewed and paid

   weight 3 · round to Wave
   Wave✓fullclaimed9/10

   Wave's docs directly cover invoice creation, branded templates, online payment via 'Pay now' (credit card/bank/Apple Pay), and status tracking (viewed, due, paid) plus overdue reminders — exactly matching the story. Missing for 10: independent/hands-on corroboration beyond vendor marketing pages.

   • [claimed-docs] “Know when an invoice is viewed, becomes due, or gets paid, so you can take the right actions to manage your cash flow.”
   • [claimed-docs] “Customers can click a “Pay now” button on invoices and pay instantly by credit card or secure bank payment (ACH/EFT) for as little as 1%2 pe…”
   • [claimed-docs] “Add your logo and brand colors to our professional invoice templates. Drag-and-drop editing makes it easy to customize!”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”

   proof ↗⚑ flag

   Bench—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

2. founderSet up recurring invoices and automatic payment reminders for overdue customers

   weight 2 · round to Wave
   Wave✓fullclaimed8/10

   Wave's documentation explicitly covers both halves of the story: recurring invoices with automatic credit card payments for repeat customers (wave-docs-10), and automatic overdue payment reminders scheduled at 3/7/14 days (wave-docs-2, wave-supp-invoicing). Missing for 10: independent/hands-on corroboration beyond vendor marketing pages, and detail on customizing reminder cadence beyond the fixed schedule.

   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a bookkeeping/tax service focused on categorization, reporting, and tax filing; there is no mention of invoicing, accounts receivable, recurring invoices, or customer payment reminders anywhere in the evidence pack.

   ⚑ flag

Receivables

1. accountantTrack accounts receivable with aging reports and per-customer balances

   weight 2 · round drawn
   Wave—none0/10

   Evidence describes general accounting reports (cash-flow trend comparisons) and per-invoice status tracking (viewed/due/paid), but nothing in the pack specifically documents an accounts-receivable aging report or a per-customer balance summary. Missing for 10: explicit AR aging report feature, per-customer balance/statement view, any documentation naming 'aging' or customer-level receivables tracking.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Know when an invoice is viewed, becomes due, or gets paid, so you can take the right actions to manage your cash flow.”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench's evidence covers reporting (income statement, balance sheet), categorization, and banking, but there is no mention of accounts receivable aging reports or per-customer balance tracking anywhere in the docs or probes. Missing for 10: any AR aging report feature, per-customer balance tracking, invoicing/AR module documentation.

   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Ai ledger

1. ai-native userHave an agent draft and post journal entries via the API and leave them in a review queue for my accountant

   weight 3 · round drawn
   Wave—none0/10

   No evidence of an API for posting journal entries, nor any review-queue/approval workflow; the developer portal is inaccessible (403) and marketing pages document no API/MCP/CLI surface, and probes for llms.txt/openapi return 404s.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Bench—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

Chart of accounts

1. accountantCustomize the chart of accounts with account types, sub-accounts, and class or tag dimensions

   weight 3 · round drawn
   Wave—none0/10

   The evidence pack contains no documentation of chart-of-accounts customization, account types, sub-accounts, or class/tag dimensions in Wave; it only vaguely mentions 'Tag it, track it' without describing COA structure, and positions Wave as built for non-accountants using standard double-entry books without customizable account hierarchies. missing for 10: any mention of account type management, sub-account creation, or class/tag dimension reporting.

   • [claimed-docs] “Tag it, track it, and see what's working for your business.”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a done-for-you bookkeeping service where a human bookkeeper manages the books; the evidence pack shows no self-serve chart-of-accounts customization, account types, sub-accounts, or class/tag dimension configuration exposed to the accountant/customer. The client-facing surface is reports and downloads, not ledger/CoA editing. Missing for 10: any mention of CoA management, account type/sub-account creation, or class/tag dimension tagging capability.

   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

Journal entries

1. accountantPost manual journal entries with balanced debits, credits, and supporting memos

   weight 3 · round to Wave
   Wave~partialclaimed3/10

   Wave explicitly markets itself as 'real, double-entry accounting software,' implying journal-entry mechanics under the hood, but no evidence pack item documents a manual journal-entry screen, debit/credit balancing UI, or memo field for such entries. Missing for 10: explicit manual journal entry feature documentation, debit/credit balance validation details, memo/note field support, and any independent or hands-on confirmation of this specific workflow.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a done-for-you bookkeeping service where Bench's own staff (not the customer) manage the books; evidence explicitly states the client-facing surface is reports/downloads, 'not a ledger the customer posts to' (bench-supp-reporting), with no mention of a journal-entry interface, debit/credit balancing, or memo fields for accountant users. Missing for 10: any UI or workflow for entering/posting journal entries, debit/credit validation, and memo/supporting-documentation attachment on entries.

   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

Ai audit

1. ai-native userHave an agent monitor the ledger and flag anomalies in spend or duplicate transactions before the close

   weight 3 · round drawn
   Wave—none0/10

   No evidence of any AI agent, anomaly detection, duplicate transaction flagging, or automated audit monitoring capability; Wave's evidence covers manual/human-facing bookkeeping, invoicing, payroll and receipts features only, plus a note that its API/developer surface is not documented publicly.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a human-plus-software bookkeeping service with automated categorization and real-time reporting, but there is no evidence of an AI agent that actively monitors the ledger for anomalies or duplicate transactions ahead of close; the closest capability is human bookkeeper review and periodic reminders. missing for 10: agent-based anomaly detection, duplicate-transaction flagging, any pre-close audit automation.

   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Audit trail

1. accountantSee a complete audit trail of who changed what and when across the entire ledger

   weight 3 · round drawn
   Wave—none0/10

   Evidence shows multi-user role access (admin/editor/viewer, accountant access) but nowhere documents an audit trail or change log tracking who edited what and when across the ledger. No mention of audit logs, version history, or edit tracking exists in the pack.

   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a service where a human bookkeeper does the books, and the client-facing surface is reports/downloads rather than a ledger with visible change history; no evidence of any audit-trail, version history, or user-attribution feature is present anywhere in the pack, and probes confirm no docs/API surfacing such capability. missing for 10: any mention of audit logs, change tracking, user attribution, or timestamped edit history across the ledger.

   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

Multi entity

1. accountantManage multiple legal entities and produce consolidated financials across them

   weight 2 · round drawn
   Wave—none0/10

   Wave's pricing is explicitly per-business (subscribe and pay separately for each business), with no mention of consolidation, inter-entity eliminations, or a multi-entity reporting view; evidence explicitly frames Wave as built for individual small business owners, not multi-entity accounting.

   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a single-entity small-business bookkeeping/tax service; nothing in the evidence mentions multi-entity management, consolidation, or intercompany eliminations. Missing for 10: multi-entity account structure, consolidated financial statements across entities, intercompany reconciliation/eliminations.

   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Wave—none0/10

   Evidence shows no accessible API documentation (developer portal returns 403, no OpenAPI/llms.txt found), and marketing pages document no API/CLI surface that would let users mirror UI actions programmatically. There's no evidence of API parity with UI features like invoicing, payroll, or bank feeds.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—none0/10

   No API, OpenAPI spec, or developer documentation exists; probes for llms.txt, docs.md, and openapi.json all return 404s, and all evidence describes a UI/human-service product with no programmatic access surface.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Wave—none0/10

   No evidence anywhere in the pack of a data export feature (e.g., CSV/QIF export, open-format backups) or data portability tooling; marketing pages focus on invoicing, payroll, receipts, and payments with no mention of exporting or leaving with your data, and the developer/API surface is walled off (403) with no llms.txt or OpenAPI found. Missing for 10: any documented export-to-open-format feature, data portability docs, or migration-out tooling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

   Bench—none0/10

   No evidence of data export in open/portable formats or account portability; reporting is limited to viewing/downloading income statements or balance sheets, not a full data export mechanism, and probes for llms.txt/openapi/docs all 404. missing for 10: explicit data export feature (CSV/QBO/API), documented data portability policy, evidence of ability to leave with full underlying data.

   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Wave—none0/10

   No evidence anywhere in the pack mentions data residency, regional storage options, or compliance controls for choosing where data is stored; Wave's marketing pages focus entirely on accounting/invoicing/payroll features with no privacy-posture or data-location documentation.

   ⚑ flag

   Bench—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls; Bench's marketing focuses on bookkeeping automation, tax, and banking, with no data-residency documentation and 404s on technical/API probes that might have revealed such settings.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Wave—none0/10

   Wave is a small-business accounting/invoicing product with no evidence of any data retention or deletion controls, privacy dashboard, or export/erasure tooling in its marketing pages; the developer portal is inaccessible and no API/CLI/MCP docs exist to inspect further.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

   Bench—none0/10

   Bench is a human-plus-software bookkeeping service; no evidence in the pack addresses data retention policies, deletion controls, or export/delete-your-data mechanisms for AI-native users. Probes for docs/llms.txt/openapi all 404, and no privacy/retention page is cited. missing for 10: retention policy documentation, data deletion/export controls, privacy posture disclosures, any AI-specific data handling terms.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”

   proof ↗⚑ flag

Ai insights

1. ai-native userAsk an agent "can we afford X?" and get an answer grounded in live ledger data pulled through the API

   weight 3 · round drawn
   Wave—none0/10

   No evidence of any AI agent, chat interface, or query capability grounded in live ledger data; the probes show no llms.txt/OpenAPI surface exposed on marketing domain, and the developer/GraphQL API portal is walled off from crawling with no documented AI integration. Marketing pages only describe reports/dashboards, not agent-accessible querying.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

   Bench—none0/10

   No evidence of any public API, MCP server, or AI-agent integration exposing ledger data; probes for llms.txt, docs-md, and OpenAPI all returned 404s, and reporting is described as human-facing downloads/dashboards, not programmatic access. missing for 10: any API/endpoint for ledger data, agent integration, documented query interface for financial questions.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.bench.co/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.bench.co/how-it-works.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.bench.co/openapi.json, https://www.bench.co/swagger.json, https://www.bench.co/api/opena…”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Custom reports

1. accountantBuild custom reports filtered and grouped by class, location, or tag dimensions

   weight 2 · round drawn
   Wave—none0/10

   Wave's evidence pack shows only basic month-to-month/year-to-year comparison reports; there is no mention of class, location, or tag-based report filtering/grouping, which is a QuickBooks/Xero-style feature Wave does not advertise (Wave is explicitly positioned as not built for accountants' advanced needs).

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   proof ↗⚑ flag

   Bench—none0/10

   Evidence only shows basic reporting (income statement, balance sheet) delivered as static downloads/reports, with no mention of custom report building or filtering/grouping by class, location, or tag dimensions. Bench is positioned as a done-for-you bookkeeping service, not a self-serve reporting tool with dimensional tagging capabilities.

   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”

   proof ↗⚑ flag

Statements

1. founderGenerate an accurate P&L, balance sheet, and cash-flow statement for any period on demand

   weight 3 · round to Bench
   Wave~partialclaimed6/10

   Wave uses real double-entry accounting and explicitly offers accounting reports with month-to-month/year-to-year comparisons to identify cash flow trends, implying core financial statements are generated from bookkeeping data. However, evidence never explicitly names or confirms a formal P&L, balance sheet, and cash-flow statement generated on-demand for any custom period — only general 'accounting reports' are described. Missing for 10: explicit documentation of P&L/balance sheet/cash-flow statement outputs, ability to select arbitrary custom date ranges, and independent/hands-on confirmation of statement accuracy.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag

   Bench✓fullclaimed8/10

   Bench explicitly markets real-time reporting with income statement (P&L) and balance sheet access/download at all times, backed by automated categorization and human bookkeeper review for accuracy. Cash-flow statement generation is not explicitly named, and there's no independent/hands-on corroboration of accuracy beyond vendor claims. Missing for 10: explicit mention of cash-flow statement as a deliverable report, and third-party or user corroboration of report accuracy.

   • [claimed-docs] “Real-time reporting. Access or download your updated income statement or balance sheet at all times”
   • [claimed-docs] “"Real-time reporting. Access or download your updated income statement or balance sheet at all times" — the client-facing surface is reports…”
   • [claimed-docs] “Accurate transaction categorization, powered by smart automation with instant guidance”
   • [claimed-docs] “"Connect all your financial accounts to automate data entry, speed up your books, reduce errors and save time", with "Accurate transaction c…”
   • [claimed-docs] “Bench is a human-plus-software service, now under new ownership: "Bench simplifies your small business accounting by combining intuitive sof…”

   proof ↗⚑ flag