Zoho Books vs Bench

Agent access

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

   weight 2 · round to Zoho Books
   Zoho Books~partialprobed5/10

   No llms.txt exists (confirmed 404) and the docs-in-markdown probe also 404s, so there's no dedicated agent-consumption doc format. However, Zoho does publish a downloadable OpenAPI spec (live-verified zip) and an explicit MCP integration page describing how to connect LLMs/agents to Zoho Books' APIs and actions, which serves a similar agent-onboarding purpose. Missing for 10: an actual llms.txt or markdown-native docs, and independent confirmation that agents can successfully parse/use the MCP or OpenAPI docs autonomously.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.zoho.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.zoho.com/books/api/v3/introduction/.md”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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 to Zoho Books
   Zoho Books~partialprobed6/10

   Zoho Books exposes a full REST API with OAuth2 tokens, documented rate limits, and a published OpenAPI spec, all of which support scripted/CI-driven automation without a UI, and MCP support adds agent-drivable actions. However, there is no evidence of a CLI, official SDK examples for CI pipelines, or headless/batch execution patterns beyond API calls, and OAuth token flow typically requires an initial interactive consent step not shown to be scriptable end-to-end. missing for 10: CLI tool, CI/headless-specific documentation or examples, fully non-interactive OAuth token provisioning, independent verification of automation in CI environments.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [claimed-docs] “Documented rate limits: "You can make 100 requests per minute per organization", per-plan daily call caps (the error payload for exceeding t…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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 to Zoho Books
   Zoho Books✓fullclaimed8/10

   Zoho documents a Zoho MCP service (mcp.zoho.com) that explicitly connects LLMs like GPT/Claude to Zoho Books' APIs and actions, with customer quotes confirming real use for invoicing, bookkeeping, and reconciliation via Claude. This is an official first-party MCP server, not just client-side integration. Missing for 10: independent/hands-on verification of the MCP connection flow beyond vendor marketing quotes, and the hosted endpoint is sign-in-gated so behavior couldn't be directly probed.

   • [claimed-docs] “It connects LLMs like GPT or Claude to Zoho's APIs, data models, and actions, so agents gain the context, access, and control they need to t…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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 to Zoho Books
   Zoho Books✓fullprobed9/10

   Zoho Books ships a comprehensive, well-documented public REST API with OAuth2 auth, rate limits, extensive endpoint coverage (contacts, banking, reconciliation, orgs), and a live-verified downloadable OpenAPI spec confirming machine-readability. This directly satisfies an AI-native user's need to drive the product programmatically via documented public API. Missing for 10: independent third-party developer corroboration beyond vendor docs, and the llms.txt/openapi.json well-known probes returned 404 (though the actual OpenAPI zip works).

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [claimed-docs] “Documented rate limits: "You can make 100 requests per minute per organization", per-plan daily call caps (the error payload for exceeding t…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [claimed-docs] “Step3: Generating Access and Refresh Tokens”

   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 to Zoho Books
   Zoho Books~partialclaimed5/10

   Zoho Books documents OAuth 2.0 with a scopes catalog gating access per module, which provides a mechanism for issuing credentials with limited access rather than full account access, and MCP integration references agent-driven access. However, there is no evidence of fine-grained, per-action or per-record least-privilege scoping (e.g., read-only vs. write, or resource-level restriction) beyond module-level scopes, nor documentation of agent-specific credential issuance/revocation workflows distinct from human OAuth clients. missing for 10: granular least-privilege scope examples beyond module-level, agent-specific credential lifecycle management (issuance/rotation/revocation tailored to AI agents), independent/hands-on verification that scoped tokens restrict agent actions as claimed.

   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Step3: Generating Access and Refresh Tokens”

   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
   Zoho Books—none0/10

   The evidence pack documents a REST API, OAuth flow, rate limits, and a downloadable OpenAPI spec, but nowhere mentions official client SDKs (e.g., Python, Node, Java, PHP libraries) for Zoho Books; an OpenAPI zip is not itself an SDK. Missing for 10: any documentation of official language SDKs, package registry listings (npm/PyPI/Maven), or SDK usage guides.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”

   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
   Zoho Books—none0/10

   The evidence pack covers Zoho Books' REST API, OAuth, rate limits, OpenAPI spec, and MCP integration, but contains no mention of webhooks or event subscription mechanisms anywhere. Since webhook support is a plausible and common capability for an API-driven accounting platform, its complete absence from the evidence means the axis applies but is undocumented.

   ⚑ 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 to Zoho Books
   Zoho Books✓fullclaimed7/10

   Zoho Books ships built-in AI (Zia) that gives plain-English queries, anomaly detection, and auto-suggested next actions on financial data, plus MCP-based agent access letting LLMs reason over and act on Books data. Evidence is vendor-sourced with some third-party customer quotes but lacks independent hands-on verification of insight quality. Missing for 10: independent/hands-on evaluation of Zia's insight accuracy, and concrete examples of specific AI-generated suggestions beyond marketing copy.

   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “It connects LLMs like GPT or Claude to Zoho's APIs, data models, and actions, so agents gain the context, access, and control they need to t…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”

   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 Zoho Books
   Zoho Books✓fullclaimed7/10

   Zoho Books documents native workflow automation (trigger workflows, bank rules, bulk categorization) and an MCP integration explicitly framed for 'fully autonomous agents [that] monitor, reason, and act without human input,' with customer quotes describing autonomous month-end closures and invoice handling via Claude/OpenClaw. This directly supports background, autonomous automation setups beyond simple manual triggers. missing for 10: independent/hands-on verification that MCP-driven agents persist and run unattended over time, and more detail on scheduling/triggers for background workflow execution beyond vendor marketing language.

   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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 to Zoho Books
   Zoho Books✓fullclaimed7/10

   Zoho Books documents a built-in AI assistant, Zia, that users can delegate tasks to in plain English — e.g. 'Ask Zia in plain English', sending bulk collection reminders, categorizing bank statements, and building workflow Blueprints automatically, all inside the product UI, distinct from the separate MCP-based external agent integration. This is first-party vendor documentation with concrete examples of task delegation. Missing for 10: independent or hands-on corroboration of Zia's task-delegation capability, and deeper documentation (e.g. feature list, screenshots) beyond a single marketing page's quotes.

   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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 to Zoho Books
   Zoho Books✓fullclaimed8/10

   Zoho Books ships an official MCP server connecting LLMs like GPT/Claude to its APIs so agents can act on natural instructions, plus built-in Zia AI for 'plain English' commands, with customer testimonials describing invoice/bill/bookkeeping tasks done via simple AI-driven instructions. Missing for 10: independent (non-vendor-quoted) hands-on verification of the MCP server's reliability and breadth of natural-language command coverage beyond the cited testimonials.

   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “It connects LLMs like GPT or Claude to Zoho's APIs, data models, and actions, so agents gain the context, access, and control they need to t…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”

   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
   Zoho Books—none0/10

   Evidence shows static API docs, OAuth guides, and a downloadable OpenAPI zip, but nothing indicates an interactive reference with runnable/try-it-now examples; probes for machine-readable/live docs endpoints (llms.txt, docs.md, openapi.json paths) returned 404s, and there's no mention of a sandbox or 'try it' console.

   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.zoho.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.zoho.com/books/api/v3/introduction/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.zoho.com/openapi.json, https://www.zoho.com/swagger.json, https://www.zoho.com/api/opena…”

   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 to Zoho Books
   Zoho Books✓fullprobed9/10

   Zoho Books publishes a downloadable OpenAPI document, live-verified via HEAD request returning HTTP 200 with a 349KB zip of the full API corpus, directly linked from the official API docs. missing for 10: no independent third-party confirmation of spec completeness/validity beyond the vendor-hosted file check.

   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”

   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
   Zoho Books—none0/10

   No evidence of a sandbox/test environment, demo org, or non-production API mode for AI agents to safely test against; the only isolation-like feature mentioned is a free plan with real financial thresholds, not a sandbox. There is also no mention of a 'test mode' flag or separate sandbox API endpoint distinct from the production organization_id-based API.

   ⚑ 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 to Zoho Books
   Zoho Books~partialprobed4/10

   Zoho Books documents a versioned API (v3), OAuth 2.0 auth, rate limits, and a downloadable OpenAPI spec, but there is no evidence of a documented version-deprecation policy, sunset timeline, or changelog governing how v3 will be retired or migrated. missing for 10: explicit deprecation/sunset policy, versioning changelog, migration guides between API versions, and any stated support-lifecycle commitments.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “Documented rate limits: "You can make 100 requests per minute per organization", per-plan daily call caps (the error payload for exceeding t…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”

   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 Zoho Books
   Zoho Books✓fullclaimed8/10

   Zoho Books API documents explicit bulk endpoints (assign owner to multiple contacts, mark multiple contacts for 1099, bulk update/delete bank rules) and MCP integration lets AI agents drive these actions via natural instructions, with customer testimonials describing bulk workflows (month-end closures, bulk reminders) done via AI. Missing for 10: no independent hands-on verification of bulk operation limits/scale via MCP, and no explicit bulk invoice/expense creation endpoints documented.

   • [claimed-docs] “Assign an Owner to Multiple Contacts”
   • [claimed-docs] “Mark Multiple Contacts for 1099 Tracking”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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 to Zoho Books
   Zoho Books✓fullclaimed7/10

   Zoho Books documents genuine event/condition-based automation: 'Trigger workflow' rules to notify/update/validate on events, Bank Rules API for auto-categorizing transactions, and Zia AI turning data into automatic next steps (bulk reminders, categorization, Blueprints). MCP integration also lets AI agents trigger actions from natural instructions, corroborated by customer quotes. Missing for 10: independent hands-on verification of rule complexity/reliability, and detailed docs on the full workflow-rule builder (trigger types, conditions, action chaining) beyond marketing copy.

   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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 Zoho Books
   Zoho Books~partialclaimed4/10

   Zoho Books documents workflow automation ('Trigger workflow', Blueprints, AI-driven bulk reminders/categorization) and MCP-based agent actions, suggesting automation depth, but no evidence explicitly describes scheduling recurring jobs, cron-like triggers, or persistent recurring workflows for AI agents. Missing for 10: explicit recurring/scheduled job API or documentation, evidence of interval-based triggers, and independent confirmation that AI agents can set up recurring automations.

   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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 to Zoho Books
   Zoho Books~partialclaimed7/10

   Zoho Books exposes concrete reconciliation primitives (bank transaction categorization, bank reconciliation creation/listing, bank rules with match filters) plus Zia AI anomaly detection ('Spot anomalies before they become problems') and MCP access letting LLM agents act on Books data, with a customer testimonial claiming 'Month-end closures... reduced from hours to minutes' via Claude integration. However, there is no documented end-to-end orchestrated workflow that explicitly matches transactions, compiles an exception list, and stages a close for human sign-off as a single agent-driven process. Missing for 10: a documented structured exception-flagging/close-summary output, an explicit human-review handoff step, and independent (non-vendor-testimonial) verification of full month-end automation.

   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   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 Zoho Books
   Zoho Books✓fullclaimed8/10

   Zoho Books explicitly documents connecting bank/credit-card accounts with automatic daily transaction import, categorization, and reconciliation workflows, backed by a full Bank Accounts/Bank Rules API for automation. Missing for 10: independent/hands-on user corroboration of daily-import reliability and any bank-feed coverage/outage caveats.

   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”

   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 to Zoho Books
   Zoho Books~partialclaimed5/10

   Zoho Books documents automatic bank feed import with categorization (Zia AI "categorizing bank statements") and an API/UI for categorizing transactions plus configurable Bank Rules for matching, but there is no evidence that suggestions adapt or improve specifically from user corrections (an explicit learning/feedback loop). Missing for 10: documented ML feedback loop showing suggestions improve after corrections, independent/hands-on confirmation of this adaptive behavior.

   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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 Zoho Books
   Zoho Books~partialclaimed6/10

   Zoho Books documents bank feeds, transaction categorization, bank reconciliation creation/listing, bank statement summaries, and bank rules for matching, which together support surfacing matched/unmatched items during reconciliation; accountant collaboration is also documented. However, there is no explicit description of a duplicate-transaction detection/review UI or a dedicated reconciliation screen showing matched vs unmatched vs duplicate buckets. missing for 10: explicit documentation or hands-on evidence of duplicate-transaction flagging, a unified reconciliation review screen showing matched/unmatched/duplicate side-by-side, and independent (non-vendor) confirmation of the reconciliation workflow.

   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   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
   Zoho Books—none0/10

   The evidence pack shows generic Zoho Books workflow automation (trigger workflows, notifications), bank transaction categorization as 'vendor payment', and vague MCP-agent quotes about 'managing bills,' but nothing documents a specific bill-capture → approval-routing → payment-scheduling pipeline for accounts payable. Missing for 10: vendor bill entry/OCR capture docs, an approval-routing/Blueprint workflow specific to bills, and a scheduled/batch bill payment feature.

   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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 to Zoho Books
   Zoho Books~partialclaimed3/10

   Evidence shows generic 'custom reports' and accountant collaboration for 'generating reports', plus vendor-related bank transaction categorization, but nothing explicitly documents an accounts-payable aging report or vendor balance report as of a specific date. Missing for 10: explicit AP aging report documentation, vendor balance report screenshots/specs, point-in-time reporting capability evidence.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”

   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
   Zoho Books—none0/10

   No evidence of a period-locking/closing-books feature or explicit reopening workflow anywhere in the pack; mentions of month-end closing refer to reconciliation speed, not locking prior-period transactions from edits. missing for 10: documentation of a 'close books' or 'lock period' setting, permission controls around it, and an explicit reopening workflow.

   ⚑ 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 to Zoho Books
   Zoho Books~partialclaimed4/10

   Zoho Books documents strong reconciliation tooling (bank reconciliation API, auto-categorization, bank rules) and accountant collaboration access, plus a workflow-trigger engine and audit trail, and even a customer quote referencing faster 'month-end closures.' However, there is no evidence of a dedicated close checklist feature that explicitly tracks accrual entries or formal review/sign-off steps as a structured workflow. missing for 10: a named month-end close checklist UI, accrual-tracking/journal automation tied to close, and a documented sign-off/approval mechanism for reviewers.

   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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 Zoho Books
   Zoho Books~partialclaimed7/10

   Zoho Books explicitly documents an accountant-invite feature: "Invite your accountant in Zoho Books to access real-time data... accountants can effortlessly manage your books from anywhere," covering journal entries, currency adjustments, reconciliation, and reports. However, the evidence does not detail granular role-scoping (custom permission levels, view-only vs edit controls) for that invited user. Missing for 10: explicit documentation of configurable role/permission scopes for accountant invites, and independent/hands-on confirmation of the invite flow in practice.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   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 to Zoho Books
   Zoho Books~partialprobed4/10

   Zoho Books publishes a full REST API with an OpenAPI spec download and OAuth-based access, and states the API's goal is 'all the operations you do with our web client,' implying report access, but no evidence cites specific 'General Ledger' or 'Trial Balance' report endpoints or confirms these are exportable in open formats (JSON/CSV) via API. missing for 10: explicit GL/trial-balance report endpoint documentation, confirmed open-format export options, and independent verification of report API usage.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”

   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
   Zoho Books~partialclaimed6/10

   Bank feed automation is well documented (auto-import, categorization, reconciliation APIs) and general integration breadth (500+ apps, MCP) is claimed, but there is no explicit evidence of dedicated payments-gateway or payroll-system integrations feeding the ledger. Missing for 10: explicit payroll system connectors (e.g., Zoho Payroll or Gusto), explicit payment processor integrations (Stripe/PayPal) beyond generic '500+ integrations' claim, and independent confirmation these flows work end-to-end.

   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “500+ integrations at your fingertips across Asana, Twilio, Zoho, and beyond.”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”

   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
   Zoho Books—none0/10

   The evidence pack shows general API/contact/organization creation endpoints, OAuth, banking reconciliation, and MCP/AI agent capabilities, but nothing addresses importing historical transactions, opening balances, or bulk migration from another accounting system (e.g., QuickBooks/Xero import tools, CSV bulk import, or a dedicated migration service) while preserving transaction-level detail.

   ⚑ 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 Zoho Books
   Zoho Books~partialclaimed4/10

   Evidence confirms Zoho Books can 'generate invoices' and 'track payments' (via MCP/Zia docs), implying some invoicing and payment-tracking capability, but there is no explicit documentation of online payment gateway options embedded in invoices or of invoice 'viewed' status tracking. missing for 10: dedicated docs on online payment gateway/checkout options on invoices, evidence of 'viewed' status/read-receipt tracking, and any independent/hands-on confirmation of the payment/view workflow.

   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”

   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 Zoho Books
   Zoho Books~partialclaimed5/10

   Evidence documents automated collection reminders ("sending bulk collection reminders") and workflow triggers that can notify customers, plus AI/MCP hooks for invoice tracking, but no citation explicitly describes a recurring-invoice scheduling feature. Missing for 10: explicit documentation of setting up recurring/repeating invoices, and independent/hands-on confirmation of the reminder automation working end-to-end.

   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”

   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 to Zoho Books
   Zoho Books~partialclaimed3/10

   Evidence confirms Zoho Books has contact/customer management and a customizable reporting engine ('generating reports... changing date range, adding columns, filters') that accountants can use, implying AR-related reporting capability, but no citation explicitly names an accounts-receivable aging report or per-customer balance view. missing for 10: explicit AR aging report documentation, explicit per-customer balance/statement feature, independent confirmation of these standard reports.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “Create a Contact”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”

   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 to Zoho Books
   Zoho Books~partialclaimed5/10

   Zoho Books has a documented Journal Entries-capable API, OAuth-based agent access, and MCP integration for agent-driven bookkeeping actions, plus accountant collaboration features, which together make agent-drafted journal entries plausible. However, there is no evidence of a dedicated 'draft/review queue' status or approval workflow for journal entries specifically, nor confirmation that journal entries can be created in a pending/unposted state for accountant review via API. missing for 10: explicit journal entry draft/pending status API field, a documented review-queue or approval workflow feature, and a hands-on example of an agent posting a journal entry that awaits accountant sign-off.

   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”

   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
   Zoho Books—none0/10

   The evidence pack contains no mention of chart of accounts customization, account types, sub-accounts, or class/tag dimensions—only unrelated docs on contacts, bank reconciliation, MCP, OAuth, and pricing. This is a core accounting feature that clearly applies to a bookkeeping product like Zoho Books, but no supporting evidence is provided.

   ⚑ 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 Zoho Books
   Zoho Books~partialclaimed5/10

   Zoho Books documents accountant access to 'journal entries and base currency adjustments' via the accountant collaboration feature, confirming journal entry posting exists as a core feature, but there is no direct evidence of the journal entry UI/API showing debit/credit balancing enforcement or memo/attachment support. Missing for 10: explicit documentation of journal entry creation flow, balance validation, memo/notes fields, and attachment support for journal entries.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   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 to Zoho Books
   Zoho Books~partialclaimed6/10

   Zia AI is explicitly documented to 'Spot anomalies before they become problems' and Zoho MCP lets external agents (Claude, GPT) connect to Books data to 'monitor, reason, and act without human input,' with bank feed categorization and reconciliation APIs that an agent could use to review transactions before close. However, there is no explicit documentation of duplicate-transaction detection or a dedicated anomaly-flagging workflow across multiple entities/organizations, and evidence is vendor-marketing plus generic customer quotes rather than a demonstrated anomaly-detection feature spec. Missing for 10: explicit duplicate-transaction detection capability, documented multi-entity/cross-org anomaly rollup, and independent/hands-on verification of agent-driven anomaly flagging.

   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “"Zoho Books enhances banking efficiency by enabling your business to connect with bank and credit card accounts. Automatically import transa…”

   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 to Zoho Books
   Zoho Books~partialclaimed3/10

   The features page briefly names an 'audit trail' as a Zoho Books capability, but the evidence pack gives no detail on what it captures (user, timestamp, field-level changes) or its coverage across the entire ledger/multi-entity setup — it's a single passing mention alongside unrelated features like custom reports. missing for 10: documentation of audit trail granularity (who/what/when), screenshots or hands-on verification, coverage confirmation across multiple organizations/entities, and independent corroboration.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   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 to Zoho Books
   Zoho Books~partialclaimed3/10

   Zoho Books supports creating multiple organizations and copying settings between them (zoho-books-docs-6, zoho-books-docs-7), which enables managing multiple legal entities separately, but there is no evidence of a consolidated financial reporting feature across organizations/entities. Missing for 10: documented consolidation/roll-up reporting across multiple organizations, inter-entity eliminations, or a unified consolidated financial statement feature.

   • [claimed-docs] “Create an organization”
   • [claimed-docs] “Copy settings to an organization”
   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”

   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 to Zoho Books
   Zoho Books~partialprobed7/10

   Zoho explicitly states API parity as a design goal ('perform all the operations that you do with our web client'), backs it with a large, verified OpenAPI spec covering contacts, banking, reconciliation, rules, orgs, and 1099 workflows, plus documented OAuth scopes gating module access. However, there is no independent/hands-on verification confirming true 1:1 parity (e.g., UI-only settings, some organization-level admin actions), and the llms.txt/well-known OpenAPI discovery probes 404, showing openness/discoverability gaps for AI-native tooling. Missing for 10: independent confirmation of full UI-API parity with no exceptions, and standard machine-discoverable API metadata (llms.txt, well-known openapi.json) actually resolving.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [claimed-docs] “The banking API exposes agent-drivable reconciliation primitives: endpoints to "categorize an uncategorized transaction" (including as vendo…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.zoho.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.zoho.com/openapi.json, https://www.zoho.com/swagger.json, https://www.zoho.com/api/opena…”

   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 to Zoho Books
   Zoho Books~partialprobed4/10

   Zoho Books never documents a dedicated 'export all data' or backup feature, but its REST API offers near-full parity with the web client ("perform all the operations that you do with our web client") plus a published OpenAPI spec, meaning a technical/AI-native user could programmatically pull out contacts, transactions, invoices, etc. in JSON via authenticated calls — a workaround path to open-format export rather than a first-class export/leave feature. Missing for 10: an explicit bulk-export or full-account-backup capability, documented standard export formats (CSV/Excel/JSON dump), and any migration/portability tooling or independent confirmation that a full data export actually works end-to-end.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”
   • [probe] “PROBE openapi (2026-09-16): the "Download Zoho Books OpenAPI Document" link documented on the API introduction page is live — HEAD https://w…”
   • [claimed-docs] “Authentication is OAuth 2.0 with documented steps — "Registering New Client", "Make the Authorization Request", "Generating Access and Refre…”

   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 to Zoho Books
   Zoho Books~partialclaimed3/10

   The only relevant evidence is a brief mention that the API root documents "eight regional API domains," implying Zoho Books operates data centers in multiple regions — a proxy for data residency options — but there is no explicit documentation of a user-facing region/residency selection at signup or account level, nor any privacy-page confirmation of data locality guarantees. missing for 10: explicit account creation region-selection documentation, data residency/privacy policy statement, independent confirmation of regional data storage enforcement.

   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”

   proof ↗⚑ 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 userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Zoho Books—none0/10

   No evidence in the pack addresses AI-training data usage policies, opt-outs, or data-privacy controls related to model training; the pack covers API docs, MCP integration, and features but nothing on training-data exclusion.

   ⚑ flag

   Bench—none0/10

   Bench is a bookkeeping/accounting service and no evidence pack item mentions AI training data usage, opt-out controls, or any privacy policy addressing model training; this is an applicable privacy-posture axis for any modern SaaS handling customer data, but no supporting or contradicting evidence exists. Missing for 10: any privacy policy statement, opt-out mechanism, or terms-of-service language regarding AI/ML training on customer data.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Zoho Books—none0/10

   The evidence pack covers API access, OAuth, MCP integration, and general accounting features, but contains no documentation of data retention policies, deletion controls, data export/purge APIs, or configurable retention periods for AI-native or any users. No mention of GDPR/CCPA deletion mechanisms, audit-trail retention settings, or account/data deletion workflows appears anywhere.

   ⚑ 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 to Zoho Books
   Zoho Books~partialclaimed6/10

   Zoho Books exposes live ledger data via a documented REST/OAuth API and OpenAPI spec, and Zoho MCP explicitly connects LLMs (GPT/Claude) to Books' data/actions with customer testimonials describing pulling reports and managing bookkeeping via natural-language agent instructions; Zia also markets 'pull reports just by asking'. However, there is no concrete evidence of an agent answering a specific affordability/cash-runway question grounded in live balances—no worked example, and MCP access is gated/unverified hands-on beyond vendor testimonials. Missing for 10: a demonstrated affordability-style query/answer flow, independent (non-vendor) confirmation of MCP grounding accuracy, and explicit cash-balance/afford-X reasoning support.

   • [claimed-docs] “It connects LLMs like GPT or Claude to Zoho's APIs, data models, and actions, so agents gain the context, access, and control they need to t…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”
   • [claimed-docs] “Zoho MCP covers Books: "Meet Zoho MCP (Model Context Protocol), which enables developers to instantly transform business apps into intellige…”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Full API parity is the documented design goal: "The Zoho Books API allows you to perform all the operations that you do with our web client.…”
   • [claimed-docs] “A machine-readable spec is published from the docs: "Download Zoho Books OpenAPI Document" (books/api/v3/openapi-all.zip — a 340KB+ zip of t…”

   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 to Zoho Books
   Zoho Books~partialclaimed4/10

   Evidence confirms Zoho Books supports custom reports with filters, columns, and date ranges (zoho-books-supp-accountant), but no citation explicitly documents reporting dimensions like class, location, or tags for grouping/filtering—only generic 'custom fields' and 'custom reports' are mentioned. Missing for 10: explicit documentation of class/location/tag tracking categories and their use as report filter/group dimensions, plus any hands-on or independent confirmation of this specific capability.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”

   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
   Zoho Books~partialclaimed5/10

   Evidence confirms Zoho Books supports generating financial reports generally (custom reports with date-range/filter controls, MCP-enabled 'pull reports just by asking', accountant access to 'generating reports') but never explicitly names or documents P&L, balance sheet, or cash-flow statement generation specifically. Missing for 10: explicit documentation/screenshots of P&L, balance sheet, and cash-flow statement generation for arbitrary periods, and any independent/hands-on verification of their accuracy.

   • [claimed-docs] “Accountant collaboration: "Invite your accountant in Zoho Books to access real-time data. From handling journal entries and base currency ad…”
   • [claimed-docs] “Generate invoices, track payments, log expenses, and create financial reports.”
   • [claimed-docs] “Built-in AI plus agent hooks, in the vendor's own words: "Ask Zia in plain English", "Spot anomalies before they become problems", "Whether …”
   • [claimed-docs] “Workflow automation is first-class: "Trigger workflow: Easily create and trigger unique business workflows to notify, update, or validate in…”

   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