Pilot vs Zoho Books

Agent access

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

   weight 2 · round to Zoho Books
   Pilot~partialprobed4/10

   A probe confirms Pilot serves an llms.txt file at HTTP 200, so an agent can indeed be pointed at it — but the content shown is minimal (just entity/category metadata, no structured docs or API references), and other agent-doc formats (docs-md, openapi) return 404. Missing for 10: substantive llms.txt content beyond basic metadata, markdown docs mirror, and any first-party statement about agent-oriented documentation strategy.

   • [probe] “PROBE llms.txt: HTTP 200 at https://pilot.com/llms.txt # Pilot [Entity: Pilot] [Category: Professional Services] [Subcategory: Acco…”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Zoho Books
   Pilot—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

   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

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

   weight 3 · round to Zoho Books
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any MCP server offering; docs mention integrations (Bill.com, Stripe, Gusto) but nothing about AI agent connectivity via MCP, and API/openapi probes returned 404s.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Zoho Books
   Pilot—none0/10

   No evidence of a public API for Pilot; OpenAPI/swagger probes all returned 404 and no docs mention an API for driving the product programmatically. Pilot is a human-service accounting/bookkeeping product with integrations, not an API-driven platform.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Zoho Books
   Pilot—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

   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

6. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any official SDKs; probes for API/OpenAPI specs returned 404s, and no docs mention developer SDKs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

7. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Pilot—none0/10

   No evidence of any webhook subscription capability or event API; Pilot is an accounting/bookkeeping service and probes show no OpenAPI or developer API surface exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round to Zoho Books
   Pilot~partialclaimed4/10

   Pilot's marketing mentions 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead' (pilot-docs-7), which points to some AI-generated insight capability inside the product, and scenario/cash-flow modeling features (pilot-docs-8, pilot-docs-21) suggest similar analytical output, though these are framed as human CFO-delivered rather than explicitly AI-driven. There is no independent/hands-on corroboration of the AI feature actually working, and community reviews focus on bookkeeping accuracy/time savings rather than AI insights. Missing for 10: detailed documentation of the AI feature's scope/accuracy, independent user testimony specifically about the AI insights, and clarity on whether insights are AI-generated vs. human-analyst-generated.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Model cash flow scenarios Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Track company expenses in real time Find the $2,000/month you didn't know you were wasting.”
   • [claimed-docs] “Find the $2,000/month you didn't know you were wasting.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Zoho Books
   Pilot—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

   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

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

   weight 3 · round to Zoho Books
   Pilot~partialclaimed3/10

   Pilot's pricing page mentions an AI feature offering 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' which is a thin, single-mention hint of an in-product AI assistant capable of some task-like actions (scenario modeling). There's no further documentation on scope, autonomy, or how tasks are delegated to it, and community evidence focuses on human bookkeepers/CFOs rather than the AI assistant. Missing for 10: detailed documentation of the AI assistant's task-delegation capabilities, independent/hands-on corroboration of it actually performing delegated tasks, and clarity on its scope beyond Q&A.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Zoho Books
   Pilot~partialclaimed3/10

   Pilot's marketing mentions 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' implying some natural-language Q&A interface, but there's no evidence of broader natural-language command execution (e.g., initiating actions, workflows) or any API/CLI to support it. missing for 10: evidence of NL commands beyond Q&A, independent/hands-on corroboration, technical documentation of the AI interface, API or programmatic access.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Pilot—none0/10

   Pilot is an accounting/bookkeeping service with no evidence of any developer API reference or runnable examples; probes for OpenAPI/docs-md all returned 404, and no evidence pack items mention an API reference.

   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Zoho Books
   Pilot—none0/10

   Probe explicitly checked common OpenAPI/swagger endpoints and all returned 404, and no documentation mentions a machine-readable API spec. Missing for 10: any published OpenAPI/Swagger spec, API documentation, or developer portal.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

   weight 1 · round drawn
   Pilot—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

   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

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

   weight 2 · round to Zoho Books
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any public API, versioning scheme, or deprecation policy; probes for OpenAPI specs all returned 404s. missing for 10: any public API documentation, versioning scheme, deprecation policy, or developer-facing API references.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Zoho Books
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service; no evidence describes any bulk-operation or batch-processing capability across items (transactions, invoices, etc.) for AI-native automation. Missing for 10: any mention of bulk edit/import/export tools, batch API operations, or automation-scale item processing.

   ⚑ flag

   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

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

   weight 3 · round to Zoho Books
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with dedicated human experts and integrations, but there is no evidence of a rules engine or automation-trigger system letting users define event-based automated actions; features described are AI Q&A and integrations, not user-defined trigger/action rules.

   ⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Zoho Books
   Pilot—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

   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

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
   Pilot~partialcommunity3/10

   Pilot's evidence shows human bookkeepers finalize monthly books with integration-driven transaction classification (pilot-comm-1, pilot-docs-18, pilot-docs-26), which is directionally toward automated reconciliation, but there is no evidence of an autonomous agent matching transactions, flagging exceptions, and preparing a close package end-to-end without human bookkeeper involvement. Missing for 10: explicit agentic exception-flagging workflow, evidence of AI (not human staff) doing the matching/reconciliation, and documentation of an automated close-prep output for review.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Bank feeds

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

   weight 3 · round to Zoho Books
   Pilot✓fullcommunity7/10

   Pilot's docs and a first-hand customer testimonial confirm bank/credit-card/expense integrations automatically feed transaction data for classification, with real-time account data in the portal, eliminating manual founder bookkeeping work. missing for 10: no explicit list of supported banks, no detail on daily-sync frequency or setup flow, and no independent technical documentation beyond marketing/community claims.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Categorization

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

   weight 2 · round to Zoho Books
   Pilot—none0/10

   Evidence shows Pilot's transaction classification is handled by integrations plus human bookkeepers/accountants (pilot-comm-1, pilot-docs-17), not by an AI categorization engine that learns from founder corrections. No documentation describes a self-serve ML suggestion-and-correction loop. Missing for 10: any mention of an AI/ML categorization suggestion feature, evidence of a correction/feedback loop, or founder-facing UI for adjusting categorizations.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Reconciliation

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

   weight 3 · round to Zoho Books
   Pilot—none0/10

   Pilot's evidence describes bank/tool integrations and automated transaction classification (pilot-comm-1, pilot-docs-17) but never describes a reconciliation workflow that surfaces matched, unmatched, and duplicate transactions for accountant review. Missing for 10: any documentation or user report of a reconciliation screen or matched/unmatched/duplicate transaction handling.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Bill management

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

   weight 2 · round to Pilot
   Pilot~partialclaimed3/10

   Pilot's pricing page lists 'Full accounts payable' as a service line item and mentions integration with Bill.com, implying vendor bill handling, but there is no documented detail on bill capture, approval routing, or payment scheduling mechanics within a single workflow — AP appears to be a done-for-you service rather than a described self-serve workflow. Missing for 10: bill capture/OCR details, approval routing configuration, payment scheduling functionality, and any hands-on/independent confirmation of the AP workflow.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”

   proof ↗⚑ flag

   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

Payables

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

   weight 2 · round to Pilot
   Pilot~partialclaimed4/10

   Pilot advertises 'Full accounts payable' as a service feature and real-time account data access via its portal, implying some visibility into AP status, but there is no specific mention of AP aging reports or vendor balance tracking at a point in time. missing for 10: explicit AP aging report feature, vendor balance detail/history, point-in-time reporting capability, screenshots or hands-on evidence of AP aging views.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Close process

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

   weight 2 · round drawn
   Pilot—none0/10

   No evidence in the pack mentions period locking, closing periods, or preventing retroactive changes to prior-period financials; the evidence only covers bookkeeping, tax, CFO, and integration features. Missing for 10: any mention of period-lock/close controls, reopening workflow, or audit trail preventing prior-period edits.

   ⚑ flag

   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

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

   weight 3 · round to Zoho Books
   Pilot~partialclaimed3/10

   Pilot's monthly bookkeeping service closes books and lets customers communicate on 'outstanding items needed to finalize your books every month' via a portal, implying some close-tracking process, but there is no evidence of an actual checklist artifact tracking reconciliations, accruals, and review sign-offs as distinct trackable steps. missing for 10: explicit reconciliation checklist UI, accrual tracking, and sign-off/approval workflow evidence.

   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Collaboration

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

   weight 3 · round to Zoho Books
   Pilot—none0/10

   Pilot's evidence describes its own bookkeeping team communicating with the founder via a portal (docs-18, docs-26) and lets customers keep QuickBooks data so any tax preparer can access it (docs-24), but there is no evidence of a feature to invite an external accountant/bookkeeper into Pilot's own system with role-scoped permissions to review or adjust books. missing for 10: any documentation of user/role invitation, permission scoping, or external collaborator access controls within Pilot's platform.

   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Data access

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

   weight 3 · round to Zoho Books
   Pilot—none0/10

   No evidence of a documented API for pulling general ledger or trial balance data; probes for OpenAPI/docs endpoints returned 404s and no API documentation is mentioned anywhere in the evidence pack.

   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

Integrations

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

   weight 2 · round to Pilot
   Pilot✓fullcommunity8/10

   Pilot explicitly integrates with banking, payments, and payroll systems (e.g. Bill.com, Stripe, Gusto, 10k+ integrations) to feed real-time transaction data into the ledger, and community testimonials confirm bank/card/payment integrations auto-handle transaction classification with minimal founder effort. missing for 10: no explicit first-party detail on the breadth/setup process of bank feed connections beyond named partners, no independent audit of integration reliability at scale.

   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “10k+ Integrations”
   • [claimed-docs] “If you use Gusto, we’ve partnered with Gusto to automatically apply the credit, saving you time.”
   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Migration

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

   weight 1 · round to Pilot
   Pilot~partialclaimed5/10

   Pilot markets that switching providers is supported and mentions keeping existing QuickBooks account and historical data, implying migration support, but there's no detail on how historical transaction-level detail is preserved or migrated from other systems (e.g., Xero, Wave, spreadsheets) beyond QuickBooks. missing for 10: documented migration process, evidence of no data/detail loss, support for non-QuickBooks source systems, independent confirmation of successful migrations.

   • [claimed-docs] “Whether you’re starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding, underst…”
   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Whether you're starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding, underst…”
   • [claimed-docs] “Whether you’re starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding”

   proof ↗⚑ flag

   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

Invoicing

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

   weight 3 · round to Zoho Books
   Pilot—none0/10

   Evidence only shows Pilot offers 'full accounts receivable' as a bookkeeping service item, but there is no mention of self-serve invoice creation, online payment collection, or view/paid tracking features for founders—Pilot is a done-for-you bookkeeping service, not an invoicing tool. Missing for 10: invoice creation UI, online payment processing, read-receipt/paid-status tracking evidence.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Zoho Books
   Pilot—none0/10

   Evidence mentions 'Full accounts receivable' as a service but nothing about recurring invoicing or automated overdue payment reminders specifically. Pilot is positioned as a bookkeeping/accounting service, not an invoicing tool with these automation features documented anywhere in the pack.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   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

Receivables

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

   weight 2 · round to Pilot
   Pilot~partialclaimed4/10

   Pilot's pricing page lists 'Full accounts receivable' as a service offering, confirming AR management is part of the product, but there is no evidence of specific features like aging reports or per-customer balance tracking/reporting in the evidence pack. missing for 10: documentation of aging reports, per-customer balance views, AR-specific dashboards or reports, and independent/hands-on confirmation of these features.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   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

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

   No evidence of any API, agent integration, or journal entry review queue functionality; Pilot is a human-service bookkeeping/accounting company with no documented API (openapi probes 404). Missing for 10: any API existence, journal entry draft/post capability, review queue workflow, agent-facing endpoints.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE llms.txt: HTTP 200 at https://pilot.com/llms.txt # Pilot [Entity: Pilot] [Category: Professional Services] [Subcategory: Acco…”

   proof ↗⚑ flag

   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

Chart of accounts

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

   weight 3 · round drawn
   Pilot—none0/10

   Pilot is a done-for-you bookkeeping/accounting service, so ledger customization is a fair question, but the evidence pack only mentions generic 'custom workflows and reporting' with no mention of chart of accounts structure, account types, sub-accounts, or class/tag dimensions. Missing for 10: any documentation of COA setup, account type hierarchy, sub-account creation, or class/tag dimension tagging controlled by the accountant.

   • [claimed-docs] “Custom workflows and reporting”

   proof ↗⚑ flag

   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

Journal entries

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

   weight 3 · round to Zoho Books
   Pilot—none0/10

   Pilot's evidence describes a done-for-you bookkeeping/CFO service built on QuickBooks with dedicated experts handling books, but there is no mention of any interface for accountants to post manual journal entries with debits/credits and memos. Missing for 10: any UI or workflow for manual JE creation, debit/credit balancing, or memo attachment.

   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”

   proof ↗⚑ flag

   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

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

   Pilot's evidence covers bookkeeping, tax, CFO services, and AI Q&A on transactions, but there is no mention of an autonomous agent that monitors the ledger, flags spend anomalies, or detects duplicate transactions before close. missing for 10: anomaly-detection feature, duplicate-transaction flagging, any agentic monitoring capability, pre-close audit workflow evidence.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Track company expenses in real time Find the $2,000/month you didn't know you were wasting.”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”

   proof ↗⚑ flag

   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

Audit trail

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

   weight 3 · round to Zoho Books
   Pilot—none0/10

   No evidence in the pack describes any audit trail, change history, or user-activity logging feature within Pilot's platform; the material focuses on bookkeeping services, integrations, CFO advisory, and tax credits. Missing for 10: any mention of audit logs, change tracking, user attribution, or timestamped edit history across the ledger.

   ⚑ flag

   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

Multi entity

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

   weight 2 · round to Pilot
   Pilot~partialclaimed4/10

   Pilot's FAQ mentions it can provide consolidated reporting for US entities with foreign subsidiaries, but there is no evidence of multi-entity management for domestic entities, no detail on consolidation methodology, and no independent/hands-on corroboration of this feature. missing for 10: multi-entity dashboard/management capability, domestic multi-entity consolidation support, detailed consolidation workflow, independent verification.

   • [claimed-docs] “We can also provide US entities with foreign subsidiaries with consolidated reporting.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Zoho Books
   Pilot—none0/10

   No evidence of any public API for Pilot; probes for OpenAPI/swagger endpoints all returned 404, and all documentation describes only the human portal/UI and service offerings. missing for 10: any documented API, API parity claims, or developer endpoints.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Zoho Books
   Pilot—none0/10

   While Pilot mentions QuickBooks compatibility and tax-preparer portability, there is no evidence of a dedicated data export feature, open-format export (CSV/JSON/API), or a documented process to fully extract and leave with all financial data; probes even show no public API/OpenAPI spec.

   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Zoho Books
   Pilot—none0/10

   No evidence in the pack addresses data residency, region selection, or storage location controls; Pilot is an accounting/bookkeeping service with no mention of infrastructure or data-residency options. Missing for 10: any documentation of data storage regions, residency guarantees, or configurable data location.

   ⚑ flag

   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

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

   weight 3 · round drawn
   Pilot—none0/10

   Pilot is an accounting/bookkeeping service; the evidence pack contains no privacy policy statements, opt-out controls, or AI-training data usage terms addressing whether customer financial data is used to train AI models. This is a fair question given Pilot advertises 'AI answers' features, but no evidence confirms any data-training opt-out or exclusion mechanism. Missing for 10: privacy policy/ToS language on AI training data usage, an opt-out mechanism, or any statement on data handling for AI features.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”

   proof ↗⚑ flag

   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

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Pilot—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy settings for Pilot's AI features or data; the pack only covers accounting, bookkeeping, and tax service offerings. Missing for 10: any documentation of data retention/deletion controls, privacy settings, or data handling policies for AI or customer data.

   ⚑ flag

   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

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
   Pilot~partialprobed4/10

   Pilot advertises an in-app AI feature offering 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' which aligns with the 'can we afford X' query use case, but there is no evidence this is exposed via an API for external agents to query — the openapi probe returned 404s and no API/agent-integration docs exist. missing for 10: evidence of a public API/endpoint an external AI agent could call, documentation of grounding in live ledger data via API, and any independent confirmation the AI answer feature works as described.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Model cash flow scenarios Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Know if you can afford new hires well before you make the offers.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

Custom reports

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

   weight 2 · round to Zoho Books
   Pilot—none0/10

   Evidence only mentions generic 'custom workflows and reporting' (pilot-docs-10) with no mention of class, location, or tag dimension filtering/grouping capabilities typical of QuickBooks-style reports; missing for 10: any documentation of dimension-based (class/location/tag) filtering or grouping in reports.

   • [claimed-docs] “Custom workflows and reporting”

   proof ↗⚑ flag

   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

Statements

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

   weight 3 · round drawn
   Pilot~partialcommunity5/10

   Pilot's bookkeeping and CFO service pages reference real-time account data, custom workflows/reporting, and budget-vs-actuals/scenario planning, implying standard financial statements are produced as part of monthly bookkeeping, and community reviews confirm books are kept accurate and up to date. However, no evidence explicitly confirms generation of a P&L, balance sheet, and cash-flow statement for any arbitrary period on demand. Missing for 10: explicit documentation of the three core statements, confirmation of on-demand/any-period generation (vs. standard monthly close), and independent verification of statement accuracy/timeliness.

   • [claimed-docs] “Custom workflows and reporting”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Custom financial model with strategic insights Budget vs actuals variance analysis Scenario planning model”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”
   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [community] “Pilot customer here; they are amazing. It's pretty different from a regular bookkeeper largely in that Pilot is super accurate and timely. M…”

   proof ↗⚑ flag

   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