FreshBooks vs Zoho Books

Agent access

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

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

   Direct probes show no llms.txt (404) and no markdown-based docs (404), and no evidence exists of an agent-oriented documentation format; only standard human-facing API docs are present.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

   proof ↗⚑ flag

   Zoho Books~partialprobed5/10

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

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

   proof ↗⚑ flag

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

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

   FreshBooks exposes a full REST API (invoices, expenses, journal entries, reports) with OAuth2 auth and an official Node.js SDK, which lets scripts/services call it headlessly outside the UI. However there is no CLI, Docker image, or explicit CI/CD integration guidance, and no evidence anyone has run FreshBooks automation in a pipeline context. missing for 10: CLI or headless runner, CI/CD-specific documentation or examples, independent evidence of CI usage.

   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [github] “Get/set data from FreshBooks using the REST API.”
   • [claimed-docs] “Authentication - FreshBooks”

   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 userConnect an agent via an official MCP server

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

   FreshBooks offers a REST API, webhooks, and SDKs, but there is no evidence of an official MCP server for agent connectivity; probes for llms.txt and docs.md both returned 404. Since FreshBooks is a SaaS platform (not itself an agent), an official MCP server is a plausible offering, so its absence is 'none' rather than 'na'.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”

   proof ↗⚑ flag

   Zoho Books✓fullclaimed8/10

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

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

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   FreshBooks—none0/10

   No evidence of an official CLI tool; FreshBooks only offers a REST API, SDKs (Node.js), and Postman collection, with no mention of a command-line interface. Probes for llms.txt and docs.md also returned 404s.

   • [github] “Get/set data from FreshBooks using the REST API.”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

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

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

   weight 3 · round to Zoho Books
   FreshBooks✓fullclaimed8/10

   FreshBooks publishes a well-documented public REST API covering invoices, expenses, payments, journal entries, reports, and webhooks, with OAuth 2.0 authentication, scopes, pagination, error handling, an official Node.js SDK, and a Postman collection — enabling programmatic/agentic control of core accounting workflows. Missing for 10: no llms.txt or machine-readable docs endpoint (probe 404s) and no independent third-party corroboration of API robustness beyond first-party docs.

   • [claimed-docs] “Authentication - FreshBooks”
   • [claimed-docs] “Search, Paging and Includes - FreshBooks”
   • [claimed-docs] “Webhook Callbacks - FreshBooks”
   • [claimed-docs] “Invoices - FreshBooks”
   • [claimed-docs] “Expenses - FreshBooks”
   • [claimed-docs] “Journal Entries - FreshBooks”
   • [claimed-docs] “Other Reports - FreshBooks”
   • [claimed-docs] “Errors - FreshBooks”
   • [claimed-docs] “Postman Collection”
   • [github] “Get/set data from FreshBooks using the REST API.”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”

   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

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

   weight 2 · round to FreshBooks
   FreshBooks~partialclaimed6/10

   FreshBooks documents OAuth 2.0 authentication with per-endpoint scopes and a dedicated tutorial for finding the right scopes for an app, which supports issuing least-privilege credentials to any third-party client including an agent. However, there is no explicit mention of AI-agent use cases, no granular API-key/service-account model beyond OAuth scopes, and no guidance on revocation or monitoring specifically for autonomous agents. Missing for 10: agent-specific credential guidance, fine-grained scope examples beyond a generic tutorial reference, and independent confirmation of scope enforcement in practice.

   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “Authentication - FreshBooks”

   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

7. ai-native userBuild against official SDKs

   weight 2 · round to FreshBooks
   FreshBooks~partialprobed6/10

   FreshBooks publishes an official Node.js SDK on GitHub with REST API bindings and pre-configured auth, backed by extensive REST API docs (auth, webhooks, invoices, expenses, payments, journal entries, reports) and a Postman collection/'Tools and Libraries' page for building integrations. However, evidence only shows one official SDK (Node.js) with no other languages, no AI-native docs formats (llms.txt and docs.md both return 404), and no independent developer corroboration of SDK quality or maintenance. Missing for 10: multi-language official SDKs, machine-readable/agent-friendly docs, and third-party validation of the SDK's reliability.

   • [github] “Get/set data from FreshBooks using the REST API.”
   • [github] “Pre-configured [ExpressJS](https://expressjs.com/) app. Includes authentication via [PassportJS](http://www.passportjs.org/).”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “Postman Collection”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

   proof ↗⚑ flag

   Zoho Books—none0/10

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

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

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to FreshBooks
   FreshBooks✓fullclaimed8/10

   FreshBooks documents a real webhook subscription system: registering callbacks (e.g. invoice.create), a verification handshake, and HMAC-based signature verification, with an explicit caveat about delivery latency. This directly satisfies the story of subscribing to events via webhooks. Missing for 10: independent/hands-on developer confirmation of webhook reliability and no evidence of a broader event catalog beyond a few examples.

   • [claimed-docs] “Webhook Callbacks - FreshBooks”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”

   proof ↗⚑ flag

   Zoho Books—none0/10

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

   ⚑ flag

Agentic features

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

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

   No evidence of AI-generated insights, suggestions, or analytics features anywhere in the docs, API surface, or community mentions; the product focuses on invoicing, expense tracking, and reporting without any AI/ML layer mentioned. Missing for 10: any mention of AI-driven insights, anomaly detection, predictive suggestions, or natural-language analysis of financial data.

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

   FreshBooks offers building blocks—webhooks, journal entry/reports APIs, bank reconciliation automation, and Bill Pay automated scheduling—that could support autonomous background workflows, but there is no evidence of a native automation/agent framework, scheduled triggers, or persistent background jobs configurable by an AI-native user. missing for 10: a documented automation/rules engine or agent-runnable scheduler, evidence of autonomous multi-step workflows beyond webhooks+bill pay, and independent confirmation of reliability for unattended background operation.

   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”

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

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Zoho Books✓fullclaimed7/10

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

   No evidence of a natural-language interface, chatbot, or AI assistant for operating FreshBooks; only a developer REST/OAuth API and webhooks are documented, which require code, not NL commands. Probes for llms.txt and machine-readable docs both returned 404, further suggesting no AI-native interaction layer.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”

   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 to FreshBooks
   FreshBooks~partialprobed3/10

   FreshBooks publishes a full REST API reference (auth, endpoints, errors, webhooks) and offers a Postman Collection that lets developers run example requests, which partially satisfies 'runnable examples,' but there's no evidence of an embedded interactive console (e.g., try-it-now code snippets) in the docs themselves, and llms.txt/docs-md probes returned 404s indicating no AI-native doc tooling. missing for 10: an in-browser interactive API console with live runnable requests, AI-readable doc formats (llms.txt/markdown), and independent confirmation of the Postman collection's usability.

   • [claimed-docs] “Postman Collection”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

   proof ↗⚑ flag

   Zoho Books—none0/10

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

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

   proof ↗⚑ flag

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

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

   FreshBooks documents a REST API with a Postman collection and SDKs, but nothing in the evidence indicates an OpenAPI/Swagger spec or other machine-readable API description is published or downloadable; explicit probes for llms.txt and a machine-readable docs endpoint both returned 404.

   • [claimed-docs] “Postman Collection”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

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

   No evidence of a sandbox/test environment, test-mode API keys, or demo accounts; the API docs cover authentication, endpoints, and webhooks but nothing about non-production 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
   FreshBooks—none0/10

   FreshBooks publishes a REST API with docs, authentication, webhooks, and an API changelog note about swapping legacy bearer tokens for JWTs, but there is no evidence of a versioning scheme (e.g., v1/v2 endpoints) or a documented deprecation policy/timeline for API changes. The changelog mention shows change happened but not a stated deprecation process, and llms.txt/docs-md probes 404, showing no AI-native API governance documentation.

   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

   proof ↗⚑ flag

   Zoho Books~partialprobed4/10

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

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

   proof ↗⚑ flag

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

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

   The API docs cover single-resource CRUD endpoints (invoices, expenses, payments, journal entries) plus search/paging/webhooks, but no evidence describes batch or bulk-operation endpoints (e.g., bulk invoice creation, bulk expense updates) that would let an AI agent act on many items in one call.

   • [claimed-docs] “Search, Paging and Includes - FreshBooks”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “Invoices - FreshBooks”
   • [claimed-docs] “Expenses - FreshBooks”

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

   FreshBooks exposes webhooks for real-time event notifications (e.g., invoice.create) that could be wired to external actions, but there is no evidence of a native rules/automation engine where users define conditional triggers and actions inside the product itself; webhooks require external code to act on events. Missing for 10: in-app rule builder, conditional logic UI, natively triggered actions without custom integration, and evidence of AI-native automation workflows.

   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “Webhook Callbacks - FreshBooks”

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

   FreshBooks Bill Pay documents scheduled/recurring vendor payments ("schedule payments" and "executes your scheduled payments so nothing slips"), and webhooks provide event-driven sync, but there is no evidence of a general-purpose recurring job/workflow scheduler exposed via API for AI-native automation (e.g., recurring invoices, scheduled reports, or cron-like triggers callable by an agent). Missing for 10: API endpoint or docs for recurring invoice/report scheduling, evidence of programmatic (not just UI) recurring workflow setup, and confirmation this extends beyond bill payments to general automation.

   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “FreshBooks Bill Pay* makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check.”
   • [claimed-docs] “Forward your bills to your FreshBooks account, schedule vendor payments, and watch each payment move from created to paid.”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”

   proof ↗⚑ flag

   Zoho Books~partialclaimed4/10

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

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

   proof ↗⚑ flag

Ai reconciliation

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

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

   FreshBooks documents automated bank-reconciliation workflows and a rich API (journal entries, reports, payments, expenses) that a third party could use to build an agent, but there is no evidence of an AI agent that autonomously matches transactions, flags exceptions, and prepares a month-end close for review — reconciliation here is rule-based software automation, not an agentic capability.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”

   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
   FreshBooks✓fullclaimed6/10

   FreshBooks' own accounting page explicitly states you can 'link your bank account and create automated workflows for bank reconciliation and transaction management' and lists bank reconciliation among its 100+ automations, directly matching the founder's need for automatic daily transaction import. Missing for 10: independent/hands-on confirmation of daily import cadence, credit-card-specific linking details, and any troubleshooting/reliability reports beyond the vendor's own claim.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”

   proof ↗⚑ flag

   Zoho Books✓fullclaimed8/10

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

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

   proof ↗⚑ flag

Categorization

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

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

   FreshBooks evidence mentions bank account linking and 'automated workflows for bank reconciliation and transaction management' but contains no mention of a categorization engine that suggests categories for imported transactions or that improves from user corrections. Missing for 10: any documentation of transaction categorization suggestions, machine-learning/rules-based category prediction, or confirmation that the system learns from user corrections.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”

   proof ↗⚑ flag

   Zoho Books~partialclaimed5/10

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

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

   proof ↗⚑ flag

Reconciliation

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

   weight 3 · round to Zoho Books
   FreshBooks~partialclaimed4/10

   FreshBooks documents bank account linking and 'automated workflows for bank reconciliation and transaction management' plus a chart of accounts and accountant collaboration, but there's no evidence of the specific UI/workflow for surfacing matched, unmatched, and duplicate transactions for review. missing for 10: explicit documentation of matched/unmatched/duplicate transaction states, reconciliation review screen, independent or hands-on confirmation of the reconciliation workflow.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”

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

   FreshBooks Bill Pay documents bill capture ('Upload a file or snap a photo; Bill Pay reads the details and recreates the bill') and payment scheduling/execution by ACH or check, covering capture-to-payment scheduling in one workflow. However, there is no evidence of a distinct approval-routing step (multi-user sign-off before payment) — missing for 10: documented approval workflow/routing feature, evidence of multi-step sign-off controls, and independent/hands-on confirmation of the Bill Pay flow.

   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “FreshBooks Bill Pay* makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check.”
   • [claimed-docs] “Forward your bills to your FreshBooks account, schedule vendor payments, and watch each payment move from created to paid.”

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

   FreshBooks Bill Pay lets you manage and schedule vendor bill payments, and the Reports API exposes seven report types, but none of the evidence mentions an accounts-payable aging report or point-in-time vendor balance report — only due-date tracking and payment status. missing for 10: AP aging report, vendor balance/statement report, point-in-time historical AP view.

   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “FreshBooks Bill Pay* makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check.”

   proof ↗⚑ flag

   Zoho Books~partialclaimed3/10

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

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

   proof ↗⚑ flag

Close process

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

   weight 2 · round drawn
   FreshBooks—none0/10

   No evidence pack item mentions period locking, closing periods, or preventing edits to prior-period transactions without explicit reopening; FreshBooks docs cover invoicing, journal entries, reports, and API access but nothing about close controls.

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

   FreshBooks documents bank reconciliation automation, journal entries, and accountant collaboration, but there is no evidence of a structured month-end close checklist that tracks reconciliations, accruals, and review sign-offs as a workflow feature — no mention of accrual entries, close tasks, or approval/sign-off tracking. missing for 10: close checklist/task tracking, accrual entry workflows, review sign-off or approval features.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”

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

   FreshBooks explicitly documents accountant collaboration: "Grant your accountant access to real-time data in one central location" and accountants can "update your journal entries and chart of accounts... run reports, file taxes", alongside a paid Team Members role add-on for scoped user access. This directly matches the founder story of inviting an external accountant with role-based access to adjust books. Missing for 10: independent/hands-on confirmation of the granularity of role-scoping (what an accountant role can/cannot see or edit) and details of the actual invite UX flow.

   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “Team Members ($11/mo per user)”
   • [claimed-docs] “FreshBooks gives you the tools you need for tasks like invoicing, billing your clients, preparing detailed financial reports, and making inf…”

   proof ↗⚑ flag

   Zoho Books~partialclaimed7/10

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

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

   proof ↗⚑ flag

Data access

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

   weight 3 · round drawn
   FreshBooks~partialclaimed4/10

   FreshBooks documents a REST API with Journal Entries and 'Other Reports' endpoints (including Manual Journal Entry and Payments Collected reports) that expose ledger-level data in JSON via OAuth2, giving developers programmatic access to accounting data. However, no evidence names a dedicated 'General Ledger' or 'Trial Balance' report/endpoint, nor confirms export in open formats like CSV/OFX beyond JSON API responses. Missing for 10: explicit General Ledger and Trial Balance report endpoints, confirmation of open-format exports (CSV/OFX), independent developer confirmation of pulling these specific reports.

   • [claimed-docs] “Journal Entries - FreshBooks”
   • [claimed-docs] “Other Reports - FreshBooks”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”

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

   FreshBooks documents linking bank accounts for automated reconciliation, embedded payroll as part of its 100+ integrations, online payment collection (cards/ACH/etc.), and a dedicated Bill Pay product for vendor payments that syncs into the ledger — collectively covering banking, payments, and payroll flowing into the books automatically. Missing for 10: independent/hands-on confirmation that bank feeds and payroll sync work reliably in practice, and more detail on which specific bank/payroll providers are supported.

   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”
   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “Get paid with credit and debit cards, ACH bank transfer, Apple Pay, Google Pay, and Buy Now, Pay Later”
   • [claimed-docs] “FreshBooks Payroll ($40/mo plus $6/mo per user)”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”

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

   No evidence in the pack mentions data migration, import tools, historical transaction import, or conversion from other accounting systems (e.g., QuickBooks). The API surface (invoices, expenses, journal entries) could theoretically support a custom migration, but there's no documented migration feature, import wizard, or third-party migration tool referenced.

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

   FreshBooks docs confirm invoice creation with customizable payment options, multiple online payment methods (cards, ACH, Apple/Google Pay, BNPL), and a Payments API with webhook notifications (e.g., invoice.create) enabling read status/paid tracking. This directly covers create/send invoices, online payment, and view/paid visibility. Missing for 10: explicit documentation or screenshot of an invoice 'viewed' read-receipt status in the UI, and independent/hands-on confirmation of the view-tracking feature beyond API/webhook inference.

   • [claimed-docs] “Create professional invoices in minutes. Automatically add tracked time and expenses, calculate taxes, and customize your payment options.”
   • [claimed-docs] “Get paid with credit and debit cards, ACH bank transfer, Apple Pay, Google Pay, and Buy Now, Pay Later”
   • [claimed-docs] “Invoices - FreshBooks”
   • [claimed-docs] “Payments - FreshBooks”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”

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

   The evidence pack covers general invoicing, payment methods, expense tracking, bill pay (for outgoing vendor bills), and API endpoints, but nowhere mentions recurring invoice scheduling or automated reminders to customers for overdue invoices. This is a core, plausible capability for an invoicing/AR product, so the axis applies, but no citation confirms it. missing for 10: explicit documentation of recurring invoice setup, automatic overdue payment reminder configuration.

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

   FreshBooks documents invoicing, per-client entities (Clients API), and a Reports API with 'seven types of reports' including Invoice Details and Payments Collected, implying customer-level transaction data is queryable, but no evidence explicitly names an accounts-receivable aging report or a dedicated per-customer balance view. Missing for 10: explicit aging-report feature documentation, explicit per-customer outstanding-balance report, and any UI/API confirmation of AR-specific terminology.

   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “Invoices - FreshBooks”

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

   FreshBooks' API documents a Create Adjustment Journal Entry endpoint with required fields (account_uuid, debit/credit), OAuth2 authentication, and webhooks for real-time sync, which together could let an agent draft and post journal entries programmatically. However, there is no evidence of a native 'review queue' or draft/approval workflow before posting — entries appear to post directly rather than sit pending accountant review, and no accountant-approval or draft-state mechanism is documented. missing for 10: a documented draft/pending state or approval workflow for journal entries, evidence of an accountant-facing review queue, and any hands-on/independent confirmation of agent-driven posting.

   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”

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

   FreshBooks docs mention a 'customizable chart of accounts' and journal entries referencing account_uuid via the Get Accounts endpoint, showing basic COA existence and editability, but there is no evidence of account type configuration, sub-account hierarchies, or class/tag dimensions for transaction tagging. missing for 10: account type customization, sub-account/hierarchy support, class or tag dimension tracking, independent corroboration of these features.

   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”

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

   FreshBooks documents a Journal Entries API/UI supporting double-entry postings that require account_uuid plus debit or credit amounts, and it exposes a 'Manual Journal Entry' report, confirming balanced-entry posting is possible alongside accountant collaboration on the chart of accounts. However, evidence does not show a memo/description field for supporting notes, nor explicit validation that entries must balance, nor first-party UI walkthroughs (only API-level docs) confirming this journal entry flow end-to-end. Missing for 10: explicit memo/note field support, explicit balance-validation behavior, and independent/hands-on confirmation of the manual journal entry UI workflow.

   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “Journal Entries - FreshBooks”

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

   FreshBooks exposes API access to expenses, journal entries, and reports plus webhooks (freshbooks-supp-journal-entries, freshbooks-supp-reports-api, freshbooks-supp-webhooks), which a third party could use to build an external monitoring agent, but there is no evidence of any native AI/agent-based anomaly detection, duplicate-transaction flagging, or pre-close audit capability shipped by FreshBooks itself.

   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “Bank reconciliation is automated: "FreshBooks lets you link your bank account and create automated workflows for bank reconciliation and tra…”

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

   No evidence pack item mentions an audit log, change history, user attribution for edits, or timestamped audit trail across the ledger; only journal entries, reports, and accountant access are documented without any change-tracking feature. This is a plausible axis for accounting software, so absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

   Zoho Books~partialclaimed3/10

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

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

   proof ↗⚑ flag

Multi entity

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

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

   FreshBooks is designed for single-business invoicing/bookkeeping (per-account chart of accounts, journal entries, reports) and no evidence pack item mentions multi-entity management, inter-company eliminations, or consolidated financial statements across separate legal entities. This is a fair question for an accounting product to ask, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”

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

   FreshBooks documents a broad REST API (invoices, expenses, payments, journal entries, reports, clients, taxes, bills-beta) with OAuth, webhooks, and an official SDK, covering most core accounting workflows an AI agent could drive. However, several UI-surfaced features (Bill Pay automation, Payroll, Team member management, human Bookkeeping service tier) are only described as product/marketing features with no corresponding API endpoints in the evidence, and there's no independent confirmation of full UI-API parity. Missing for 10: API coverage confirmation for Bill Pay, Payroll, Team Members, and Bookkeeping service; independent/hands-on verification of parity claims.

   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “"Webhooks allow you to keep your application in sync with FreshBooks. You can subscribe to FreshBooks Webhooks to receive real-time notifica…”
   • [claimed-docs] “"FreshBooks Bill Pay makes it easy for small businesses to manage bills, schedule payments, and pay any vendor by ACH or check." Capture is …”
   • [claimed-docs] “FreshBooks Payroll ($40/mo plus $6/mo per user)”
   • [claimed-docs] “Team Members ($11/mo per user)”
   • [claimed-docs] “A human bookkeeping tier sits alongside the software: "Get tax-ready with professional bookkeeping services for small business" with "Dedica…”

   proof ↗⚑ flag

   Zoho Books~partialprobed7/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to FreshBooks
   FreshBooks~partialprobed5/10

   FreshBooks exposes a full REST API (invoices, expenses, payments, journal entries, reports) with an official SDK, letting AI-native users programmatically extract virtually all their data in JSON, which is a reasonably open format. However there is no documented bulk export-to-open-format (CSV/JSON dump) feature, no data portability/GDPR export tool, and probes show no llms.txt or markdown docs, suggesting export is only via manual API integration rather than a one-click 'leave with your data' path. missing for 10: a native bulk data export/download feature, documented data portability guarantees, and independent evidence of successful full-account export via the API.

   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [github] “Get/set data from FreshBooks using the REST API.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

   proof ↗⚑ flag

   Zoho Books~partialprobed4/10

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

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

   proof ↗⚑ flag

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

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

   No evidence in the pack addresses data residency, region selection, or storage location options for FreshBooks; the docs cover invoicing, API, and accounting features but never mention data-center location or residency controls.

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

   No evidence pack item addresses AI training data usage, opt-outs, or any privacy policy language about AI model training; FreshBooks materials focus solely on invoicing/accounting features and API docs.

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

   No evidence pack items address AI data retention, deletion controls, or privacy policies specific to AI-native usage; the docs focus on invoicing, API endpoints, and pricing with no mention of data retention/deletion controls or AI data handling policies.

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

   No evidence exists of any telemetry/usage-tracking opt-out control, privacy settings, or documentation addressing AI-native data collection preferences; FreshBooks' docs cover invoicing, accounting, and API surfaces only, with no privacy-posture disclosures.

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

   FreshBooks exposes a REST API with Reports, Journal Entries, Expenses, Invoices and Payments endpoints that could be queried by a third-party agent to ground a 'can we afford X' answer in live ledger data, and OAuth2/webhooks are documented for secure, real-time access. However there is no first-party AI agent, natural-language Q&A layer, or MCP server, and llms.txt/docs.md probes both 404, meaning any such experience would have to be built entirely by the developer rather than delivered out of the box. Missing for 10: a native conversational/agent interface over the ledger data, evidence of LLM-specific integration, and a working llms.txt or agent-discovery endpoint.

   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”
   • [claimed-docs] “"FreshBooks APIs use the OAuth 2.0 protocol for authentication and authorization... This method creates a token to keep your account secure …”
   • [claimed-docs] “The API documentation index spans the full accounting surface: Clients, Credits, Invoices, Invoice Profiles, Other Income, Payments, Taxes, …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.freshbooks.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.freshbooks.com/api/start.md”

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

   FreshBooks' Reports API documents only seven fixed report types (e.g., Invoice Details, Manual Journal Entry, Payments Collected) with no mention of class, location, or tag dimensions, nor any custom report builder with grouping/filtering by these attributes. This is a fair axis for accounting software but no evidence shows FreshBooks supports it.

   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “Other Reports - FreshBooks”

   proof ↗⚑ flag

   Zoho Books~partialclaimed4/10

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

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

   proof ↗⚑ flag

Statements

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

   weight 3 · round drawn
   FreshBooks~partialclaimed5/10

   FreshBooks documents core accounting infrastructure that would support these statements — double-entry chart of accounts, journal entries, accountant collaboration to 'run reports', and a Reports API exposing 'seven types of reports' (though only Invoice Details, Manual Journal Entry, and Payments Collected are named) plus generic 'tax-time reports' and 'detailed financial reports' claims. However, no evidence explicitly confirms dedicated Profit & Loss, Balance Sheet, or Cash Flow statement reports or on-demand period selection for them. Missing for 10: explicit documentation naming P&L/balance sheet/cash-flow reports, evidence of on-demand period customization, and independent/hands-on confirmation of report accuracy.

   • [claimed-docs] “"Reports in FreshBooks provide detailed data on various aspects of your business. There are seven types of reports you are able to access" —…”
   • [claimed-docs] “FreshBooks is double-entry accounting with accountant collaboration built in: "update your customizable chart of accounts", "Grant your acco…”
   • [claimed-docs] “Generate tax-time reports”
   • [claimed-docs] “FreshBooks gives you the tools you need for tasks like invoicing, billing your clients, preparing detailed financial reports, and making inf…”
   • [claimed-docs] “Agent-postable ledger writes are documented: "Journal entries are the building blocks of financial accounting and record all transactions in…”

   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