Xero vs Zoho Books

Agent access

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

   weight 2 · round drawn
   Xero~partialprobed5/10

   llms.txt returns a 404 (xero-probe-1), so there is no dedicated agent-oriented manifest file, but Xero does provide an official MCP server and AI toolkit documentation (developer.xero.com/documentation/tools/mcp-server, xero-docs-6, xero-docs-19) that an agent could be pointed at instead. This partially satisfies the intent of agent-discoverable docs but not via the standard llms.txt convention. missing for 10: a working llms.txt endpoint, evidence of agent-oriented markdown docs beyond MCP server README, independent confirmation an agent successfully consumes these docs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developer.xero.com/llms.txt”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”

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

   Xero exposes a documented REST API with OpenAPI spec, official SDKs (xero-node), and a premium 'Custom Connections' option explicitly designed for machine-to-machine (M2M) integrations to a single org without interactive user auth — a direct enabler of headless/CI automation. Missing for 10: explicit CI/CD pipeline examples, documented service-account/headless auth walkthrough, and independent hands-on confirmation of running it unattended in automation pipelines.

   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [github] “Custom Connections - a Xero premium option for building M2M integrations to a single org”
   • [github] “custom-connections-starter - Basic app showing Custom Connections - a Xero premium option for building M2M integrations to a single org”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”

   proof ↗⚑ 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 userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Xero—none0/10

   Evidence only shows Xero publishing its own MCP server (and AI Toolkit) so external agents can call Xero's tools, not Xero acting as an MCP client that lets users plug arbitrary external MCP servers into it to extend its own tool use. No documentation of a client-side MCP integration point in Xero (e.g., JAX or other AI features consuming outside MCP servers) is present.

   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ flag

   Zoho Books—none0/10

   All MCP evidence describes Zoho positioning Books as an MCP *server* — external LLM agents (Claude, GPT) connect to Zoho's APIs and use Books' tools — the opposite direction from this story, which asks whether Zoho Books itself can act as an MCP client that plugs in and uses external MCP servers' tools. No evidence shows Books consuming outside MCP servers or its built-in Zia assistant connecting to third-party MCP tool providers.

   • [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] “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] “500+ integrations at your fingertips across Asana, Twilio, Zoho, and beyond.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Xero✓fullprobed8/10

   Xero ships an official MCP server (xero-mcp-server) documented on developer.xero.com and GitHub, providing standardized MCP protocol access to accounting features like contacts, chart of accounts, and invoices, and Xero also promotes an 'AI Toolkit' including the MCP server, OpenAI Agents SDK and LangChain integration. Missing for 10: independent/hands-on third-party verification of the MCP server's reliability and breadth of tool coverage beyond vendor docs.

   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   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

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Xero—none0/10

   Evidence shows Xero offers SDKs, an OpenAPI spec, and an MCP server, but there is no mention of an official CLI tool anywhere in the pack.

   ⚑ flag

   Zoho Books—none0/10

   Evidence covers a REST API, OAuth, OpenAPI spec, and an MCP server offering, but there is no mention of an official command-line interface (CLI) tool for Zoho Books; probes for llms.txt and doc-md endpoints also failed. This is a fair axis for an API-driven SaaS product, but no CLI evidence exists.

   ⚑ flag

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

   weight 3 · round drawn
   Xero✓fullclaimed9/10

   Xero has a well-documented public developer API with official OpenAPI spec, SDKs (xero-node), and a developer portal (developer.xero.com), enabling programmatic access; this is independently confirmed by the GitHub repos and OpenAPI descriptions. missing for 10: independent third-party hands-on verification of API robustness beyond vendor/SDK docs.

   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”

   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

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

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

   Xero's OpenAPI spec documents OAuth 2.0 security scopes, and Custom Connections offers M2M credentials scoped to a single org — both provide a technical basis for least-privilege API access, but none of the evidence specifically ties this to issuing scoped credentials for an AI agent (the MCP server docs describe protocol bridging, not credential scoping/permissions setup for agents). Missing for 10: explicit documentation of agent-specific scope selection, least-privilege credential issuance workflow for MCP/agent use, and independent confirmation of this being used for AI agents.

   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [github] “Custom Connections - a Xero premium option for building M2M integrations to a single org”
   • [github] “custom-connections-starter - Basic app showing Custom Connections - a Xero premium option for building M2M integrations to a single org”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”

   proof ↗⚑ 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

8. ai-native userBuild against official SDKs

   weight 2 · round to Xero
   Xero✓fullprobed8/10

   Xero maintains official SDKs (xero-node) generated from official OpenAPI specs, plus a dedicated AI Toolkit with an official MCP server, OpenAI Agents SDK and LangChain integration, directly enabling AI-native development against Xero's API. missing for 10: independent/hands-on developer corroboration of SDK quality and no evidence of SDKs beyond JS/OpenAPI-generated languages being actively maintained.

   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   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

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Xero—none0/10

   The evidence pack covers Xero's API, SDKs, OpenAPI spec, and MCP server, but contains no mention of webhooks or event subscription capabilities anywhere.

   ⚑ 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
   Xero~partialclaimed6/10

   Xero offers JAX, an AI feature that reconciles transactions, categorizes/matches, and extracts bill details, plus dashboards for KPIs/ratios/benchmarking and 'instant answers about cash flow, profit trends and financial health' — these are AI-generated insights/suggestions drawn from user data inside the product. However, evidence is largely marketing copy without hands-on corroboration of insight quality or breadth (e.g., proactive suggestions beyond reconciliation/invoicing/bill entry). Missing for 10: independent/hands-on verification of AI insight accuracy, broader analytical insights (e.g., forecasting, anomaly detection) beyond reconciliation and bill scanning, and detail on how 'instant answers' works.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Automate bill entry by uploading files directly to Xero or forwarding bills from your email. Xero's AI extracts the key details to create dr…”
   • [claimed-docs] “Get instant answers about your cash flow, profit trends and financial health.”
   • [claimed-docs] “Analyze KPIs and ratios”
   • [claimed-docs] “Customize performance dashboards ... Analyze KPIs and ratios”

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

   Xero provides APIs, SDKs, and an MCP server enabling third-party or AI agents to trigger accounting actions, and JAX offers some automated reconciliation/invoicing features, but there is no evidence of a native scheduler, workflow/automation builder, or persistent background job system that runs autonomously without an external trigger. missing for 10: documented autonomous scheduling/trigger mechanism, native workflow automation builder, evidence of unattended background execution beyond single AI-assisted actions like JAX.

   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX is Xero's AI invoicing tool that lets you create, edit, and send invoices using plain-language commands.”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ 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
   Xero~partialclaimed6/10

   Xero has a built-in AI assistant called JAX that handles reconciliation, invoicing, and bill entry via plain-language commands, directly matching the story of delegating tasks to an in-product AI assistant. However, JAX's scope appears limited to a few specific workflows (reconciliation, invoicing, bill extraction) rather than a general-purpose task delegate, and there's no independent/hands-on corroboration beyond vendor marketing pages. Missing for 10: broader task coverage beyond reconciliation/invoicing/bills, independent user reviews confirming JAX's real-world reliability, and clarity on how conversational/agentic the delegation experience actually is.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX is Xero's AI invoicing tool that lets you create, edit, and send invoices using plain-language commands.”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Automate bill entry by uploading files directly to Xero or forwarding bills from your email. Xero's AI extracts the key details to create dr…”

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

   Xero's JAX assistant lets users create/edit/send invoices and reconcile bank transactions using plain-language commands, directly supporting natural-language operation for end users (not just developers via MCP). However, this NL capability is documented only for invoicing and reconciliation, not the full product surface (e.g., bills, reports, contacts), and there's no independent/hands-on corroboration of JAX's reliability. Missing for 10: NL command support across broader workflows (reporting, bill pay, contact management), and independent verification of JAX's real-world accuracy.

   • [claimed-docs] “JAX is Xero's AI invoicing tool that lets you create, edit, and send invoices using plain-language commands.”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”

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

   Evidence shows Xero has a developer portal with API docs, OpenAPI specs, and SDKs, but nothing indicates an interactive API reference with runnable/try-it-now examples (e.g., Swagger UI-style live console); the OpenAPI repo is just spec files for SDK generation. missing for 10: any mention of an interactive/try-it console, runnable code examples in-browser, or sandboxed API playground.

   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”

   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 drawn
   Xero✓fullclaimed9/10

   Xero maintains an official GitHub repo of OpenAPI (Swagger) descriptions with OAuth 2.0 security schema, explicitly used to generate SDKs, giving a clear machine-readable API spec download. Missing for 10: independent third-party validation/hands-on confirmation of spec completeness or versioning practices.

   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”

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

   No evidence of a dedicated sandbox/demo company environment for testing against the Xero API without touching live production data; the developer docs, SDKs, and MCP server evidence describe general API access but never mention a sandbox, demo org, or test environment. Missing for 10: any mention of a sandbox/demo company, test credentials, or isolated non-production environment for API/agent testing.

   ⚑ 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
   Xero~partialclaimed3/10

   Xero publishes an official OpenAPI spec and developer portal (xero-docs-2, xero-docs-32) implying a versioned API surface, but no evidence describes a documented deprecation policy, version sunset timeline, or changelog for breaking changes. missing for 10: explicit deprecation/versioning policy docs, sunset timelines, changelog of API version history.

   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”

   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
   Xero~partialprobed5/10

   Xero documents native bulk-style workflows such as paying multiple bills at once and exporting a single payment file for many suppliers (xero-docs-25, xero-docs-30), and its REST API/SDK and MCP server expose programmatic access that could be scripted for batch operations (xero-gh-1, xero-docs-19). However there is no evidence of a dedicated bulk/batch API endpoint or MCP tool for bulk-updating invoices, contacts, or other records across many items at once. Missing for 10: explicit bulk/batch API or MCP tool documentation, evidence of bulk operations beyond bill payments (e.g., bulk invoicing, bulk contact updates), and independent confirmation of bulk operation reliability.

   • [claimed-docs] “Export a payment file from Xero and upload it directly to your online banking to pay multiple bills in one go. Each supplier receives a sing…”
   • [claimed-docs] “Pay multiple bills at once and automate reconciliation ensuring records are always up-to-date.”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ 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
   Xero~partialprobed3/10

   Xero shows built-in automations (JAX auto-reconciliation matching, duplicate bill detection, automated bill data extraction) and exposes APIs/webhooks plus an MCP server that could be used by developers to build custom event-triggered actions, but there is no evidence of a native user-facing rules/trigger builder where an AI-native user defines arbitrary 'if event then action' rules. Missing for 10: a documented rules engine or webhook/trigger configuration UI, evidence of custom trigger-action mapping, and independent confirmation that such automation works end-to-end.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “Automate bill entry by uploading files directly to Xero or forwarding bills from your email. Xero's AI extracts the key details to create dr…”
   • [claimed-docs] “Detect and flag duplicate bills automatically to minimize fraud and payment errors”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

   proof ↗⚑ 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
   Xero—none0/10

   No evidence Xero supports scheduling recurring jobs/workflows for AI-native automation; the pack covers APIs, SDKs, MCP server, and accounting features but nothing about scheduled/recurring automation triggers or workflow scheduling.

   ⚑ 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

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Xero—none0/10

   No evidence anywhere in the pack of versioning, review, or rollback capabilities for automations/workflows in Xero; the evidence covers API/SDK access, MCP server, invoicing, reconciliation, and multi-currency features but nothing about automation version history or rollback.

   ⚑ flag

   Zoho Books—none0/10

   Evidence shows workflow automation, AI/MCP integration, and audit trail for financial records, but there is no mention of versioning, reviewing, or rolling back automations/workflow definitions themselves. Missing for 10: automation version history, diff/review UI for workflow changes, rollback mechanism for automations.

   ⚑ 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
   Xero~partialprobed5/10

   Xero's JAX assistant automates transaction categorization/matching for bank reconciliation, and the MCP server exposes accounting objects (invoices, chart of accounts, contacts) for programmatic/agent access, so the building blocks for an agent-driven reconciliation exist. However, there is no evidence of an agent performing a full month-end close workflow — no documented exception-flagging logic, no 'prepared for human review' close package, and no first-party or hands-on report of an agent doing this end-to-end. Missing for 10: exception flagging/anomaly detection features, month-end close packaging or review workflow, and evidence of an agent (vs. human using JAX UI) orchestrating the full process via MCP.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”

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

   Xero explicitly markets bank feed connections with JAX auto-categorizing/matching transactions and integration directory entries (e.g., Mercury) show direct bank connections, supporting daily automatic import and reconciliation. Missing for 10: explicit documentation of daily-sync frequency/reliability, and independent hands-on verification of the bank-feed connection process beyond marketing copy.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Connect Mercury with Xero”
   • [claimed-docs] “Automate bill entry by uploading files directly to Xero or forwarding bills from your email. Xero's AI extracts the key details to create dr…”

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

   Xero's AI feature JAX is explicitly described as categorizing and matching imported bank transactions during reconciliation, directly matching the story's core ask. However, evidence does not confirm that JAX learns from user corrections over time or how correction-based learning works. missing for 10: evidence of learning/adaptation from user corrections, independent/hands-on verification of categorization accuracy improving over time, detail on how suggestions are generated.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”

   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 drawn
   Xero~partialclaimed6/10

   Xero's marketing docs describe an AI reconciliation feature (JAX) that connects bank accounts and matches/categorizes transactions, and pay-bills docs mention duplicate detection, but the evidence never explicitly describes the classic bank rec workflow of surfacing matched/unmatched/duplicate transactions for review in the ledger-reconciliation screen itself. missing for 10: first-party documentation of the actual bank reconciliation UI showing matched/unmatched/duplicate transaction states, independent/hands-on verification of the reconciliation workflow, and detail on how duplicates are flagged during bank rec specifically (only bill-duplicate detection is cited).

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Detect and flag duplicate bills automatically to minimize fraud and payment errors”
   • [claimed-docs] “Pay multiple bills at once and automate reconciliation ensuring records are always up-to-date.”

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

   Xero documents automated bill capture (email/upload with AI extraction to draft bills), duplicate detection, and batch payment file export/upload plus reconciliation, covering most of the bills-AP workflow. However, evidence does not clearly describe a configurable multi-step approval routing workflow (e.g., approval thresholds, multiple approvers) beyond bills being 'ready for approval'. missing for 10: explicit approval-routing/workflow rules documentation, evidence of scheduled (future-dated) payment scheduling beyond batch export, independent/hands-on confirmation of the end-to-end flow.

   • [claimed-docs] “Automate bill entry by uploading files directly to Xero or forwarding bills from your email. Xero's AI extracts the key details to create dr…”
   • [claimed-docs] “Export a payment file from Xero and upload it directly to your online banking to pay multiple bills in one go. Each supplier receives a sing…”
   • [claimed-docs] “Pay multiple bills at once and automate reconciliation ensuring records are always up-to-date.”
   • [claimed-docs] “Detect and flag duplicate bills automatically to minimize fraud and payment errors”

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

   The evidence pack covers bill payment, duplicate detection, reconciliation, and invoicing features, but contains no mention of accounts payable aging reports or point-in-time vendor balance reporting.

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

   No evidence in the pack mentions period locking, closing periods, or preventing edits to prior-period transactions; all evidence covers invoicing, payments, multi-currency, MCP/API tooling, and general reviews. missing for 10: any mention of period lock/close feature, permission controls for locked periods, or reopening workflow.

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

   Evidence shows only basic bank transaction reconciliation via JAX AI, but no evidence of a structured month-end close checklist, accrual tracking, or review sign-off workflow that an accountant could run to manage close processes.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”

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

   The evidence pack contains no mention of inviting an accountant/bookkeeper, user roles, or permission-scoped access to the books — it focuses on APIs, MCP servers, invoicing, reconciliation, and app marketplace integrations. Xero is well known to have this feature in reality, but per the rules only the evidence pack can be judged, and no citation here addresses accountant invites or role-based access.

   ⚑ 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 Xero
   Xero~partialclaimed6/10

   Xero has a documented OpenAPI-spec-based API and SDKs (xero-node) that expose accounting endpoints including reports like Trial Balance and general ledger data via the Accounting API, with an official OpenAPI description repo confirming open format specs. However, no evidence explicitly confirms a full 'general ledger' export endpoint or trial balance report details, and no independent developer corroboration of actually pulling GL/trial balance data is present. missing for 10: explicit documentation/evidence of a dedicated general ledger/trial balance endpoint, independent developer confirmation of successful GL/trial balance extraction, and detail on data completeness/limits of these reports via the API.

   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications”

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

   Xero documents direct bank-feed reconciliation via JAX (xero-docs-20/27), native Stripe payment integration (xero-docs-23, xero-intdir-3), and payroll connectivity via the Gusto app in its App Store (xero-intdir-4), all designed to feed ledger data automatically. Missing for 10: independent/hands-on verification that these integrations reliably auto-sync in practice, and clearer detail on native payroll (vs. third-party Gusto) ledger posting.

   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “Use Stripe to accept online payments by credit and debit cards, digital wallets, Klarna, ACH Debit, and more”
   • [claimed-docs] “Stripe makes it easy to accept payments from debit cards, credit cards, Apple Pay, and Google Pay for online invoices sent from Xero—so you …”
   • [claimed-docs] “Behind every successful business is a thriving team. Hire, pay, insure, and support your employees with Gusto’s all-in-one people platform.”
   • [claimed-docs] “Connect Mercury with Xero”

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

   Xero's app marketplace lists a third-party partner (Q2X) that explicitly handles QuickBooks-to-Xero migrations 'ensuring a smooth transition of your historical data,' and Xero even subsidizes 'simple conversions,' showing migration support exists. However this is a third-party service rather than a native first-party import tool, is scoped mainly to QuickBooks, and no evidence details preservation of full transaction-level granularity or migration from other accounting systems generally. Missing for 10: native first-party migration/import tooling, evidence covering non-QuickBooks source systems, and detail on transaction-level fidelity guarantees.

   • [claimed-docs] “The Q2X team ensures a seamless transition from QuickBooks to Xero. Our specialists will help set up a Xero account and handle the migration…”
   • [claimed-docs] “The Q2X team ensures a seamless transition from QuickBooks to Xero. Our specialists will help set up a Xero account and handle the migration…”

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

   Xero provides customizable invoice templates, a Pay Now button with Stripe online payments, and invoice tracking that alerts when a customer opens the invoice, directly covering creation, sending, online payment, and view/payment status tracking. Community feedback also corroborates value of invoicing/Stripe integration. Missing for 10: independent hands-on verification of read-receipt accuracy and paid-status timing beyond vendor docs.

   • [claimed-docs] “Use customizable invoice templates to create professional invoices fast – add your logo, payment terms, and branding.”
   • [claimed-docs] “Add your logo and payment terms to Xero's templates for professional invoices”
   • [claimed-docs] “Use Stripe to accept online payments by credit and debit cards, digital wallets, Klarna, ACH Debit, and more”
   • [claimed-docs] “Give customers a slick payment process with a Pay Now button on invoices – and encourage prompt payments”
   • [claimed-docs] “Invoice tracking lets you know the moment a customer opens your invoice, so you can follow up at exactly the right time.”
   • [claimed-docs] “I like Xero for its overall simplicity, especially compared to QuickBooks Online. I find the invoicing feature and Stripe integration in Xer…”
   • [claimed-docs] “Stripe makes it easy to accept payments from debit cards, credit cards, Apple Pay, and Google Pay for online invoices sent from Xero—so you …”

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

   The evidence pack covers invoicing features like templates, Pay Now buttons, invoice tracking, and JAX AI invoicing, but contains no mention of recurring/repeating invoice scheduling or automated overdue payment reminders. Missing for 10: any documentation of recurring invoice setup, reminder scheduling rules, or overdue-customer notification workflows.

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

   Evidence shows Xero has invoicing, invoice tracking (open/paid status), and contact/customer management (xero-docs-29, xero-docs-19, xero-docs-13), which are prerequisites for AR tracking, but there is no explicit mention of an aging report or per-customer balance report in the pack. missing for 10: explicit aging report feature documentation, per-customer outstanding balance report, independent/hands-on confirmation of AR reporting.

   • [claimed-docs] “Invoice tracking lets you know the moment a customer opens your invoice, so you can follow up at exactly the right time.”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [claimed-docs] “Use customizable invoice templates to create professional invoices fast – add your logo, payment terms, and branding.”
   • [claimed-docs] “Add your logo and payment terms to Xero's templates for professional invoices”

   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 drawn
   Xero~partialprobed5/10

   Xero provides a full accounting API, SDKs, OpenAPI spec, and an official MCP server with Chart of Accounts and invoice management capabilities, which an agent could use to draft journal entries programmatically. However, there is no documented review-queue/approval workflow, draft-vs-post distinction for journal entries specifically, or accountant-facing review mechanism exposed via the API/MCP server. missing for 10: explicit journal entry draft/post API documentation, a review-queue or approval-hold feature for accountant sign-off, and evidence of an accountant-facing review UI tied to agent-created entries.

   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

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

   The MCP server docs mention 'Chart of Accounts management' as a supported feature, indicating Xero exposes COA management capability, but there is no evidence detailing account types, sub-accounts, or class/tag (tracking category) dimensions. missing for 10: evidence of account type configuration, sub-account hierarchy support, and tracking category/tag/class dimension customization.

   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”

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

   The evidence pack covers invoicing, bill pay, reconciliation, multi-currency, and API/MCP tooling, but contains no mention of manual journal entries, debit/credit balancing, or journal memos anywhere in the docs, SDK, or MCP feature list. Missing for 10: any documentation of a manual journal entry feature, evidence of debit/credit balance validation, or memo/narration support on journals.

   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”

   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
   Xero~partialprobed5/10

   Xero natively flags duplicate bills (xero-docs-31) and has JAX AI reconciling/categorizing transactions (xero-docs-20/27), and its official MCP server + APIs (xero-docs-3/14/19, xero-probe-2) let a developer build a custom agent to query ledger data for anomaly detection. However there's no evidence of a purpose-built 'monitor ledger for spend anomalies pre-close' agent or workflow — this would require custom development on top of the API/MCP server rather than an out-of-box capability. Missing for 10: a documented anomaly-detection/close-audit agent feature, evidence of spend-anomaly (not just duplicate-bill) flagging, and any close-process integration.

   • [claimed-docs] “Detect and flag duplicate bills automatically to minimize fraud and payment errors”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you... Let JAX categorize and match transactions while you're busy with your …”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”

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

   No evidence in the pack references audit trails, change history, user activity logs, or ledger version tracking anywhere in Xero's documentation or community reports; the pack covers APIs, MCP servers, invoicing, reconciliation, and integrations but nothing about audit logging.

   ⚑ 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 drawn
   Xero~partialclaimed3/10

   The only relevant evidence is a marketing line claiming Xero can 'generate consolidated financial statements in multiple currencies,' which is ambiguous and likely refers to multi-currency transaction consolidation within a single entity rather than true multi-legal-entity consolidation (parent/subsidiary structures). No evidence describes managing separate legal entities, intercompany eliminations, or org-to-org consolidation tools. Missing for 10: explicit multi-entity/subsidiary management features, intercompany elimination support, and independent confirmation of cross-entity consolidated reporting.

   • [claimed-docs] “Generate consolidated financial statements in multiple currencies for a clear view of your financial position”
   • [claimed-docs] “Xero's multi-currency accounting software lets you do business in multiple currencies with ease. Get real-time foreign exchange rates, simpl…”
   • [claimed-docs] “Xero's multi-currency accounting software lets you do business in multiple currencies with ease.”

   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
   Xero~partialprobed6/10

   Xero has a comprehensive REST API with OpenAPI spec, SDKs, and an official MCP server exposing contacts, chart of accounts, and invoicing, indicating broad API coverage of core accounting workflows. However, there is no evidence confirming full parity with newer AI/UI-only features like JAX (AI invoicing/reconciliation assistant), KPI/benchmarking dashboards, or all pricing-plan features being exposed via API. missing for 10: confirmation that JAX AI features, performance dashboards/benchmarking, and all UI-exclusive workflows are accessible via API/MCP, independent verification of full UI-API parity.

   • [claimed-docs] “This includes Xero APIs, SDKs, code samples, documentation and more.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [github] “The xero-node SDK makes it easy for developers to access Xero's APIs in their JavaScript code, and build robust applications and software us…”
   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “JAX, your AI finance partner, reconciles your transactions for you. Connect your bank accounts to Xero. Let JAX categorize and match transac…”
   • [claimed-docs] “JAX is Xero's AI invoicing tool that lets you create, edit, and send invoices using plain-language commands.”
   • [claimed-docs] “Analyze KPIs and ratios”

   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 drawn
   Xero~partialclaimed4/10

   Xero exposes API/OpenAPI access and third-party migration services (Q2X) that imply data can be extracted, but there is no documented native 'export all my data' bulk/open-format export feature or data-portability policy aimed at users leaving the platform. missing for 10: a first-party bulk data export tool/feature, documented open-format (CSV/JSON) full-account export, and any explicit data-portability/exit policy statement.

   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”
   • [claimed-docs] “We are using OpenAPI generator along with these OAS yaml files to generate our new SDKs.”
   • [claimed-docs] “The Q2X team ensures a seamless transition from QuickBooks to Xero. Our specialists will help set up a Xero account and handle the migration…”

   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

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Xero—none0/10

   Xero is closed-source SaaS; while SDKs and API specs (xero-node, OpenAPI descriptions) are open, the actual product source code is proprietary and not published under any open license. No evidence of an open-source core product exists in the pack.

   ⚑ flag

   Zoho Books—none0/10

   Zoho Books is closed-source proprietary SaaS; no evidence of any open-license source code availability, and the evidence pack only covers API docs, OAuth, and MCP integration, not source code openness. This axis applies (a buyer could ask about open-source availability) but there is no evidence supporting it.

   ⚑ flag

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

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

   No evidence in the pack mentions data residency, regional data storage options, or location choice for Xero data; all evidence covers APIs, SDKs, MCP server, invoicing, and other unrelated features. missing for 10: any mention of data residency/region selection, storage location controls, or compliance documentation addressing where customer data is stored.

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

   No evidence pack item mentions AI-training data opt-out, data usage policies for model training, or any privacy controls addressing this specific concern; all evidence covers product features, SDKs, and MCP integration rather than data-training privacy controls.

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

   No evidence in the pack addresses data retention or deletion controls for AI-native usage (e.g., API-level data purge, retention policies for MCP/agent access, or user-controlled deletion settings); coverage is limited to product features and integrations unrelated to retention/deletion. missing for 10: retention policy documentation, deletion/export APIs, MCP/agent-specific data lifecycle controls.

   ⚑ 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

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

   weight 2 · round drawn
   Xero—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for AI/agent interactions with Xero; all evidence covers unrelated product features (invoicing, MCP server, integrations).

   ⚑ flag

   Zoho Books—none0/10

   No evidence in the pack addresses telemetry opt-out or usage tracking controls; the material covers API docs, OAuth, MCP integration, and accounting features but nothing about privacy settings or telemetry toggles.

   ⚑ flag

Ai insights

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

   weight 3 · round drawn
   Xero~partialprobed6/10

   Xero has a documented official MCP server exposing accounting data (contacts, chart of accounts, invoices) plus a full API/SDK/OpenAPI spec, which could let an agent pull live ledger data to answer affordability-type questions, and Xero markets 'JAX' and 'instant answers about cash flow' features. However, there's no evidence of a natural-language reasoning layer that combines live ledger pulls with a financial-affordability judgment ('can we afford X') — the MCP server's documented capabilities are CRUD-style (contacts, invoices, chart of accounts) not analytical queries, and no hands-on example shows this exact grounded Q&A flow working. missing for 10: evidence of the MCP/API surfacing cash-flow or budget-analysis endpoints usable for affordability reasoning, and a concrete example/transcript of an agent answering such a question grounded in live data.

   • [claimed-docs] “This is a Model Context Protocol (MCP) server implementation for Xero. It provides a bridge between the MCP protocol and Xero's API, allowin…”
   • [claimed-docs] “Contact management - Chart of Accounts management - Invoice creation and management - MCP protocol compliance”
   • [claimed-docs] “Get Started with Xero's AI Toolkit including OpenAI Agents SDK, MCP Server, LangChain and prompt examples.”
   • [probe] “official MCP server documented at https://developer.xero.com/documentation/tools/mcp-server”
   • [claimed-docs] “Get instant answers about your cash flow, profit trends and financial health.”
   • [claimed-docs] “This repository holds the official Xero OpenAPI descriptions... An OpenAPI (Swagger) specification for the Xero API with OAuth 2.0 security …”

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

   No evidence in the pack addresses custom report building, or filtering/grouping by class, location, or tracking-category/tag dimensions; the pack covers invoicing, payments, multi-currency, AI tools, and API/MCP integrations but nothing about the reporting/tracking-category feature set. Missing for 10: any mention of custom report builder, tracking categories (class/location), tag dimensions, or report filtering/grouping capabilities.

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

   Xero's marketing pages reference core financial reporting capability ("Get instant answers about your cash flow, profit trends and financial health", "Generate consolidated financial statements", "Analyze KPIs and ratios", customizable dashboards), consistent with an accounting platform producing P&L, balance sheet and cash-flow reports. However, the evidence pack lacks explicit documentation naming these three statements, period-selection controls, or independent corroboration of accuracy/on-demand generation. Missing for 10: explicit product docs naming P&L/balance sheet/cash-flow statement generation, evidence of date-range/period flexibility, and independent user validation of report accuracy.

   • [claimed-docs] “Get instant answers about your cash flow, profit trends and financial health.”
   • [claimed-docs] “Generate consolidated financial statements in multiple currencies for a clear view of your financial position”
   • [claimed-docs] “Analyze KPIs and ratios”
   • [claimed-docs] “Customize performance dashboards ... Analyze KPIs and ratios”

   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