Zoho Books vs Digits

Agent access

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

   weight 2 · round to Digits
   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

   Digits✓fullprobed9/10

   Digits publishes both a top-level llms.txt (digits.com/llms.txt) and a developer-docs llms.txt (developer.digits.com/llms.txt), confirmed live via probe with HTTP 200, plus .md mirrors of every doc page — exactly the agent-oriented docs format the story asks for. missing for 10: independent third-party confirmation that an agent successfully consumed the llms.txt end-to-end (only first-party probes and docs are available).

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.digits.com/llms.txt # Digits Connect API Documentation > Documentation for Digits Connect API…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.digits.com/docs/overview.md --- updatedAt: 2026-08-31T23:35:53.000Z --- Fetch the complete doc…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Digits~partialprobed5/10

   Digits exposes a full programmatic REST API (OAuth 2.0, OpenAPI spec, batch sync with idempotent writes, webhooks) and a resettable developer sandbox, which supports scripted/automated use outside a GUI, and the MCP server is also a headless, auth-gated JSON-RPC endpoint. However, there is no explicit CI/CD documentation, no service-to-service (client-credentials) auth flow described, and OAuth authorization-code grant typically requires an initial interactive login step, so pure unattended CI automation isn't directly documented. Missing for 10: explicit CI/headless-automation guide, client-credentials or machine-to-machine auth flow, and independent confirmation of unattended pipeline use.

   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “"The Digits Connect API uses OAuth 2.0 with the authorization code grant type... API access in 3 steps: 1. User Authorization via https://co…”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Zoho Books—none0/10

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

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

   proof ↗⚑ flag

   Digits—none0/10

   All MCP evidence describes Digits exposing itself AS an MCP server (api.digits.com/mcp) so that other AI tools like Claude, ChatGPT, or Cursor can pull Digits' financial data — the opposite direction from this story, which asks whether a user can plug external MCP servers INTO Digits so Digits' own AI (e.g. Ask Digits) can call their tools. No evidence shows Digits acting as an MCP client or supporting user-added MCP server connections.

   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The MCP launch post positions the ledger as the agent surface: Digits MCP "is now available as an official Claude Connector, making it even …”
   • [probe] “official MCP server documented at https://help.digits.com/firms-connections/digits-mcp”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

   proof ↗⚑ flag

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

   weight 3 · round to Digits
   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

   Digits✓fullprobed9/10

   Digits ships a documented, hosted official MCP server at https://api.digits.com/mcp with OAuth against a user's own account, listed setup steps for Claude Desktop/Code, ChatGPT, Cursor, and Perplexity, and this is independently confirmed live via a probe showing a proper auth-gated JSON-RPC endpoint with RFC 9728 metadata. Missing for 10: broader independent third-party hands-on usage reports beyond the vendor docs and one live probe.

   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The MCP launch post positions the ledger as the agent surface: Digits MCP "is now available as an official Claude Connector, making it even …”
   • [probe] “official MCP server documented at https://help.digits.com/firms-connections/digits-mcp”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   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

   Digits—none0/10

   Digits ships an OpenAPI spec, SDG codegen, and an MCP server, but nothing in the evidence pack documents an official Digits CLI tool for developers; the only CLI mentioned is Claude's own 'claude mcp add' command, which is a third-party client CLI, not Digits'.

   ⚑ flag

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

   weight 3 · round drawn
   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

   Digits✓fullprobed9/10

   Digits publishes a full public REST API (Connect API) with OAuth2 authorization-code flow, versioned routes, OpenAPI 3.0 spec, generated SDKs across 50+ languages, a free resettable developer sandbox, and documented read/write endpoints (ledger, statements, bills workflow, webhooks) — this is a comprehensive, documented, programmatically-drivable API confirmed live by independent probes. missing for 10: the raw openapi.json file itself 404'd on direct probe (docs reference it at /openapi rather than the paths tried), so full spec accessibility wasn't independently verified end-to-end.

   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “"The Digits Connect API uses OAuth 2.0 with the authorization code grant type... API access in 3 steps: 1. User Authorization via https://co…”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”
   • [claimed-docs] “"The Digits Connect API uses route-based versioning with the version number as a URL path prefix" — a published versioning policy on the dev…”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.digits.com/docs/overview.md --- updatedAt: 2026-08-31T23:35:53.000Z --- Fetch the complete doc…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.digits.com/openapi.json, https://developer.digits.com/swagger.json, https://develo…”

   proof ↗⚑ flag

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

   weight 2 · round to Digits
   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

   Digits~partialprobed6/10

   The Connect API documents granular OAuth 2.0 scopes (e.g., 'source:sync ledger:read documents:write', 'bills:manage') that a developer/agent app can request, and the MCP server is fixed to read-only scope with its own OAuth flow, which together support least-privilege credential issuance. However there is no documented feature for a user to self-issue named, revocable API keys per-agent with custom scope selection (only the developer OAuth app flow, and the MCP server's scope is fixed read-only, not user-configurable). Missing for 10: dedicated 'create scoped API key for this agent' UI/API, per-agent revocation/audit trail, and evidence of narrower-than-read-only or custom scope combinations being selectable for MCP/agent use.

   • [claimed-docs] “"The Digits Connect API uses OAuth 2.0 with the authorization code grant type... API access in 3 steps: 1. User Authorization via https://co…”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Digits
   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

   Digits~partialprobed5/10

   Digits documents a full OpenAPI 3.0 spec and offers OpenAPI-Generator based codegen for 50+ languages/frameworks, plus a developer sandbox and OAuth flow — enabling AI-native developers to build integrations — but there is no evidence of dedicated, first-party maintained SDK packages (e.g., official Python/Node/Go client libraries), and a probe for the raw OpenAPI file at common paths returned 404s, casting some doubt on spec accessibility. missing for 10: dedicated first-party SDK repositories/packages, confirmed live OpenAPI spec file, independent corroboration of codegen usage.

   • [claimed-docs] “The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response sc…”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.digits.com/openapi.json, https://developer.digits.com/swagger.json, https://develo…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Digits
   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

   Digits~partialclaimed6/10

   Digits' API reference documents webhook event delivery — "Digits sends this JSON request body to your configured webhook endpoint" — confirming a webhook mechanism exists for event notifications, which supports agentic/event-driven integration alongside the OAuth API and MCP server. However, evidence lacks detail on how a user subscribes/manages webhook endpoints (create/list/delete subscription endpoints), the catalog of event types, retry/signing/security details, or independent confirmation of reliability. Missing for 10: webhook subscription management API details, event type catalog, delivery guarantees/signing docs, and independent/hands-on verification.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Digits
   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

   Digits✓fullprobed8/10

   Digits ships 'Ask Digits' as an in-product AI assistant that answers financial questions and completes tasks ('Ask questions. Complete tasks. Understand your business'), plus AI-driven trend insights, exception surfacing, and quality-control checks embedded in dashboards and the Agentic Close workflow. This is corroborated by a live, auth-gated MCP server exposing the same ledger data for AI-generated insights externally, reinforcing the product's AI-native insight capability. Missing for 10: independent/hands-on user reviews validating the quality of Ask Digits' insights beyond vendor claims.

   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “Digits Dashboards provide real-time, customizable views of revenue, expenses, cash, and other key metrics so founders and finance teams alwa…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

   proof ↗⚑ flag

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

   weight 2 · round to Zoho Books
   Zoho Books✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Digits~partialclaimed7/10

   Digits documents strong built-in autonomous background processing: auto-booking 95%+ of transactions in real time, automated reconciliations, and an 'Agentic Close' workflow that continuously collects activity, books transactions, starts reconciliation, generates schedules, runs QC, and surfaces exceptions without user intervention. It also supports webhook event delivery and an 'Ask Digits' task mode. However, there's no evidence of user-configurable automation rules, triggers, or a workflow builder that an AI-native user could set up themselves — the automation is largely pre-built rather than user-defined. Missing for 10: user-configurable automation/trigger setup, scheduling controls, or evidence of custom rule-based automations beyond the fixed AGL pipeline.

   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”
   • [claimed-docs] “an AI-native month-end close workflow that collects financial activity continuously, books transactions inside the ledger, starts reconcilia…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

   proof ↗⚑ flag

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

   weight 3 · round to Zoho Books
   Zoho Books✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Digits~partialclaimed6/10

   Digits ships 'Ask Digits', a built-in AI assistant that answers financial questions and has a documented 'task mode' to 'Get it Done', which supports delegation of tasks within the product itself. However, evidence for the task-execution side is thin — only a marketing blurb, with no detailed docs, workflow examples, or independent/hands-on confirmation of what tasks it can actually complete autonomously. missing for 10: detailed documentation or hands-on evidence of the range/reliability of tasks Ask Digits can execute, independent corroboration of agentic task completion, and any limits/guardrails on delegated actions.

   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “Ask Digits Your AI financial assistant”

   proof ↗⚑ flag

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

   weight 2 · round to Zoho Books
   Zoho Books✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Digits✓fullprobed7/10

   Digits ships "Ask Digits", an in-product AI assistant that lets users ask natural-language questions about financials and invoke a documented task mode ("Ask Digits to Get it Done") to complete actions, and additionally exposes an MCP server so natural-language agents in Claude/ChatGPT/Cursor can query live ledger data. Missing for 10: independent/hands-on verification that Ask Digits' task execution actually works as described, and clarification of how far natural-language commands can go given the MCP server is documented as read-only.

   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “Ask Digits Your AI financial assistant”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The MCP launch post positions the ledger as the agent surface: Digits MCP "is now available as an official Claude Connector, making it even …”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Digits
   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

   Digits~partialprobed6/10

   Digits publishes a full OpenAPI 3.0 spec, an interactive-friendly llms.txt/markdown mirror of docs, and a free resettable developer sandbox with demo data, which together support exploring the API with real requests; however, the probe found no hosted interactive reference UI (openapi.json/swagger.json paths 404'd) and no evidence of embedded runnable code examples within the docs themselves. missing for 10: a live interactive API-reference UI (e.g., Swagger/Redoc/Stoplight) with clickable 'try it' runnable examples, and confirmation that the OpenAPI spec is actually renderable/explorable rather than just downloadable.

   • [claimed-docs] “The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response sc…”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.digits.com/openapi.json, https://developer.digits.com/swagger.json, https://develo…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.digits.com/docs/overview.md --- updatedAt: 2026-08-31T23:35:53.000Z --- Fetch the complete doc…”

   proof ↗⚑ flag

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

   weight 2 · round to Zoho Books
   Zoho Books✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Digits✓fullprobed8/10

   Digits explicitly documents a 'complete OpenAPI 3.0 specification' covering all endpoints/params/schemas, hosted at a stated URL and paired with OpenAPI Generator codegen support for 50+ languages, plus a parallel llms.txt and per-page .md mirrors for machine-readable docs (digits-supp-openapi-llms, digits-docs-5, digits-probe-1, digits-probe-2). A probe attempting to fetch the spec failed, but it only tried guessed generic paths (openapi.json, swagger.json, etc.) rather than the actually documented '/openapi' URL, so this is not a concrete contradiction. Missing for 10: independent verification that the documented '/openapi' URL itself returns a valid spec live.

   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [claimed-docs] “The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response sc…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.digits.com/llms.txt # Digits Connect API Documentation > Documentation for Digits Connect API…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.digits.com/docs/overview.md --- updatedAt: 2026-08-31T23:35:53.000Z --- Fetch the complete doc…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.digits.com/openapi.json, https://developer.digits.com/swagger.json, https://develo…”

   proof ↗⚑ flag

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

   weight 1 · round to Digits
   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

   Digits✓fullclaimed8/10

   Digits documents a dedicated developer sandbox with a resettable demo instance pre-loaded with realistic data, entirely separate from production, and free/self-serve access via Development API keys that auto-select the demo client in OAuth. This directly satisfies testing without touching production data. Missing for 10: independent/hands-on confirmation that the sandbox behaves identically to production and covers write endpoints (e.g., bills workflow) without side effects.

   • [claimed-docs] “Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo …”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”

   proof ↗⚑ flag

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

   weight 2 · round to Digits
   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

   Digits~partialclaimed5/10

   Digits documents route-based API versioning (version number as URL path prefix) on a dedicated versioning docs page, showing intentional version management for AI/agent consumers of its Connect API and MCP server. However, no evidence describes an explicit deprecation policy (timelines, sunset notices, migration guidance for old versions) — missing for 10: documented deprecation timeline/process, evidence of past version sunsets, and confirmation this policy also covers the MCP server surface.

   • [claimed-docs] “The Digits Connect API uses route-based versioning with the version number as a URL path prefix.”
   • [claimed-docs] “"The Digits Connect API uses route-based versioning with the version number as a URL path prefix" — a published versioning policy on the dev…”

   proof ↗⚑ flag

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

   weight 2 · round to Zoho Books
   Zoho Books✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Digits~partialclaimed6/10

   The Connect API documents batch transaction sync with external-ID idempotence ("Idempotence and deduplication is handled via the external_id field") and auto-books 95%+ of transactions in real time, showing the platform can process many items at once programmatically. However there's no documented bulk-edit UI, bulk categorization/reclassification endpoint, or explicit multi-item action beyond transaction sync and bill workflows. Missing for 10: dedicated bulk-update/bulk-edit endpoints or UI, evidence of bulk operations across other object types (invoices, reports, vendors) beyond transactions, and independent confirmation of batch scale limits.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”

   proof ↗⚑ flag

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

   weight 3 · round to Zoho Books
   Zoho Books✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Digits~partialclaimed3/10

   Digits offers webhook event delivery (JSON payloads on ledger events) and internal automated actions like auto-booking, flagging, and quality checks, but these are pre-built automations rather than a user-facing rule engine where an AI-native user can define custom 'if event X then action Y' triggers. Missing for 10: a documented rule-builder/automation configuration UI or API, examples of user-defined trigger-action pairs, and evidence of arbitrary custom actions being executed on arbitrary events beyond fixed webhook notifications.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

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

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

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

   proof ↗⚑ flag

   Digits—none0/10

   Digits offers webhooks, background auto-booking, and month-end close automation, but there is no evidence of a user-facing scheduler for recurring jobs/workflows (e.g., cron-like triggers, scheduled report generation, or workflow automation builder) that an AI-native user could configure. missing for 10: any documented scheduling/cron API or UI, recurring job configuration, or workflow trigger system.

   ⚑ flag

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

   weight 1 · round drawn
   Zoho Books—none0/10

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

   ⚑ flag

   Digits—none0/10

   Digits documents automated bookkeeping, auto-booking, agentic close, and exception surfacing, but nothing in the evidence describes versioning, reviewing change history, or rolling back automations/rules themselves — no changelog, rule-versioning, or undo mechanism for its automated workflows is documented.

   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “an AI-native month-end close workflow that collects financial activity continuously, books transactions inside the ledger, starts reconcilia…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”

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

   Digits~partialclaimed6/10

   Digits documents an 'Agentic Close' workflow that continuously books transactions, starts reconciliation before month-end, generates schedules, surfaces exceptions with context, and produces reports from the live ledger, plus 95%+ auto-booking and quality-control checks — strong first-party alignment with the story. However, this is all vendor-authored marketing/docs with no independent or hands-on verification of end-to-end autonomous execution, no example of an agent actually running a full close via API/MCP, and the MCP server is explicitly read-only (cannot book, flag, or take reconciliation actions itself), meaning the 'agent-driven' close is only demonstrated through the closed first-party product, not via the agent-facing surfaces. missing for 10: independent/hands-on evidence of an agent executing the full reconciliation-to-close workflow, and MCP/API write access enabling an external agent to perform booking/exception-flagging rather than just read data.

   • [claimed-docs] “an AI-native month-end close workflow that collects financial activity continuously, books transactions inside the ledger, starts reconcilia…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “Digits adds 11 new quality checks to make closing the books that much easier!”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

   proof ↗⚑ flag

Bank feeds

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

   weight 3 · round drawn
   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

   Digits✓fullclaimed8/10

   Digits documents real-time bank/credit-card connectivity across 12,000+ financial institutions with auto-booking of 95%+ of transactions in real time, and help docs describe adding new connections, positioning daily automatic import as a core feature. missing for 10: independent/hands-on confirmation of daily import reliability beyond vendor claims.

   • [claimed-docs] “"Digits Connect API seamlessly integrates with 12,000+ financial institutions, giving you real-time visibility into the metrics that matter—…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “Real-time Integrations 12,000+ financial institutions”
   • [claimed-docs] “Where do I add a new connection?”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”

   proof ↗⚑ flag

Categorization

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

   weight 2 · round to Digits
   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

   Digits~partialclaimed6/10

   Digits documents AI-native auto-categorization (AGL trained on 170M+ transactions, 95%+ auto-booking) and 'transaction flagging & smart reviews' suggesting a learning/correction loop, but there is no explicit documentation of a feedback mechanism where founder corrections are captured and used to retrain or adjust future suggestions. missing for 10: explicit description of a correction-feedback loop showing suggestions improve from user edits, independent/hands-on verification of accuracy improving over time, and details on how manual overrides are ingested by the categorization model.

   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “The AGL is a purpose-trained model suite: "Proprietary AI models trained on over 170 Million transactions totaling $875 Billion", doing "Rea…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”

   proof ↗⚑ flag

Reconciliation

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

   weight 3 · round to Zoho Books
   Zoho Books~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Digits~partialclaimed5/10

   Digits documents automated reconciliation, transaction flagging/smart reviews, and exception surfacing as part of its AI-driven bookkeeping and 'Agentic Close' workflow, which implies reconciliation review happens, but duplicates are described as being prevented via idempotent writes rather than surfaced as a reviewable duplicate queue. Missing for 10: explicit documentation of a per-bank-account reconciliation view distinguishing matched, unmatched, and duplicate transactions, and any hands-on/independent confirmation of this UI.

   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”
   • [claimed-docs] “Digits adds 11 new quality checks to make closing the books that much easier!”

   proof ↗⚑ flag

Bill management

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

   weight 2 · round to Digits
   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

   Digits~partialclaimed7/10

   Digits documents a dedicated 'Bill Pay' feature (drag/drop/approve/pay) and a full bills workflow API covering ingest, query, submit, approve, pay, reject, and void gated by a bills:manage scope, which maps directly to capture, approval routing, and payment. However, evidence doesn't detail payment scheduling specifics (e.g., future-dated batch runs, approval chains/rules) or provide independent/hands-on confirmation the workflow works end-to-end. Missing for 10: explicit payment-scheduling mechanics, multi-step approval routing configuration details, and third-party corroboration.

   • [claimed-docs] “Bill Pay Drag. Drop. Approve. Pay.”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

   proof ↗⚑ flag

Payables

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

   weight 2 · round to Digits
   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

   Digits~partialclaimed7/10

   The developer API reference explicitly lists an 'accounts payable aging report' generator and a full bills workflow (ingest, query, submit, approve, pay, reject, void) gated by a bills:manage scope, implying vendor balance tracking within the AGL ledger. However, evidence doesn't explicitly confirm as-of-date/historical point-in-time snapshots for AP aging, and there's no independent/hands-on corroboration of the report's accuracy or usability. Missing for 10: explicit historical/point-in-time date parameter documentation, independent user validation of AP aging accuracy.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “Bill Pay Drag. Drop. Approve. Pay.”

   proof ↗⚑ flag

Close process

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

   weight 2 · round drawn
   Zoho Books—none0/10

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

   ⚑ flag

   Digits—none0/10

   The evidence pack covers AGL categorization, the Agentic Close workflow, quality checks, and reporting, but nothing describes a period-lock or reopening-approval mechanism that prevents prior-period figures from changing. This is a reasonable axis for close-collaboration accounting software, so absence of evidence yields 'none'.

   ⚑ flag

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

   weight 3 · round to Digits
   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

   Digits~partialclaimed6/10

   Digits documents an 'Agentic Close' workflow that starts reconciliation before month-end, generates accrual/depreciation schedules from ledger activity, runs quality-control checks, and surfaces exceptions with context, plus 11 dedicated closing quality checks — covering reconciliations, accruals, and QC review. However, there is no explicit documentation of a checklist UI or formal review/sign-off tracking (who approved what, sign-off status) as the story specifies. Missing for 10: an explicit close checklist artifact and documented sign-off/approval tracking mechanism.

   • [claimed-docs] “an AI-native month-end close workflow that collects financial activity continuously, books transactions inside the ledger, starts reconcilia…”
   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “Digits adds 11 new quality checks to make closing the books that much easier!”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”

   proof ↗⚑ flag

Collaboration

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

   weight 3 · round to Zoho Books
   Zoho Books~partialclaimed7/10

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

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

   proof ↗⚑ flag

   Digits~partialclaimed6/10

   Digits documents collaboration features letting 'business owners, finance teams, and accountants review and share financials' (digits-docs-11) and firm-tier plans that add 'roles and permissions' and 'flexible client-level plans' (digits-supp-pricing), indicating some support for external accountant access. However, there is no concrete documentation of an invite flow, specific role scopes (e.g., view-only vs. edit/adjust), or how a founder specifically grants an external bookkeeper adjust-level access. missing for 10: detailed invite/role-management UI docs, granular permission levels for external accountants, and independent confirmation of the collaboration workflow.

   • [claimed-docs] “Digits Financials generates real-time, customizable financial statements and reports directly from the AGL with collaboration features that …”
   • [claimed-docs] “Published self-serve pricing, per business not per seat: "Yes, Digits offers a 30-day free trial", and "Digits generates real-time financial…”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”

   proof ↗⚑ flag

Data access

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

   weight 3 · round to Digits
   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

   Digits~partialprobed6/10

   Digits documents a full OpenAPI 3.0 spec, ledger endpoints including trial balance, balance sheet, P&L, and full chart of accounts retrieval, plus sandbox/dev environment access — satisfying most of the story. However, a live probe found the OpenAPI spec file itself returning 404 at all standard paths, and there's no explicit mention of exporting data in open/portable formats (e.g., CSV/JSON export of GL) beyond API JSON responses. missing for 10: working/reachable OpenAPI spec file (probe returned 404), explicit open-format export (CSV/JSON bulk export) of GL and trial balance, independent third-party confirmation of API completeness.

   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.digits.com/openapi.json, https://developer.digits.com/swagger.json, https://develo…”
   • [claimed-docs] “"Digits has a demo environment with realistic data pre-loaded from other connections. Each developer has access to their own resettable demo…”

   proof ↗⚑ flag

Integrations

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

   weight 2 · round to Digits
   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

   Digits✓fullclaimed8/10

   Digits documents real-time connections to 12,000+ financial institutions with named payments/payroll connectors (Stripe, Gusto, Ramp), auto-booking 95%+ of transactions via the AGL, and idempotent sync with deduplication so activity flows automatically into the ledger. missing for 10: independent/third-party corroboration of actual bank/payroll sync reliability and no explicit named banking connector list beyond generic '12,000+ institutions' claim.

   • [claimed-docs] “"Digits Connect API seamlessly integrates with 12,000+ financial institutions, giving you real-time visibility into the metrics that matter—…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”

   proof ↗⚑ flag

Migration

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

   weight 1 · round to Digits
   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

   Digits~partialclaimed4/10

   Digits has a help-center entry titled 'How do I migrate to Digits from Quickbooks?' and the Connect API supports idempotent, deduplicated transaction sync and chart-of-accounts fetch, suggesting some migration tooling exists, but no evidence details how historical transaction-level detail, account balances, or attachments are actually preserved during a full migration from another system. missing for 10: actual migration walkthrough/content beyond the FAQ title, evidence of historical balance/opening-balance handling, support for non-QuickBooks source systems, and independent confirmation that no transaction detail is lost.

   • [claimed-docs] “How do I migrate to Digits from Quickbooks?”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

   proof ↗⚑ flag

Invoicing

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

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

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

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

   proof ↗⚑ flag

   Digits~partialclaimed3/10

   Digits' product page lists an 'Invoicing — Get paid faster' feature, confirming the axis applies, but there is no documentation describing invoice creation workflow, online payment integration, or read/paid status tracking. missing for 10: details on invoice creation UI, supported payment methods/gateways, view-tracking or paid notifications, and any independent confirmation of the feature working.

   • [claimed-docs] “Invoicing Get paid faster”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Digits~partialclaimed2/10

   Digits' product page lists an 'Invoicing — Get paid faster' feature and the Connect API exposes A/R aging reports, but there is no documentation of recurring invoice scheduling or automatic overdue-payment reminders. missing for 10: documented recurring invoice setup, automated reminder/dunning workflow, any hands-on or independent confirmation of these AR automation features.

   • [claimed-docs] “Invoicing Get paid faster”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

   proof ↗⚑ flag

Receivables

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

   weight 2 · round to Digits
   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

   Digits~partialclaimed6/10

   Docs confirm an accounts payable aging report and A/R aging generation via the API ('Generate an accounts payable aging report', A/R aging) plus per-customer/vendor ledger queries and chart of accounts access, and Digits Financials/Dashboards surface real-time reports; but there is no dedicated UI walkthrough or independent confirmation of a per-customer AR balance view or dunning/aging workflow in the product itself, only API-level mentions in the developer llms.txt. missing for 10: hands-on/UI evidence of an AR aging report screen, per-customer balance breakdown in the app UI, independent verification of accuracy/usability.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “Digits Financials generates real-time, customizable financial statements and reports directly from the AGL with collaboration features that …”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”

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

   Digits~partialclaimed5/10

   The Connect API documents write/batch transaction sync with external_id idempotence and a bills workflow with submit/approve/reject/void steps (a review-queue-like pattern), and OAuth scopes include ledger:write-style scopes, showing agents can post financial data programmatically. However, there is no explicit documentation of a 'draft journal entry' state or an accountant-facing review queue specifically for journal entries (as opposed to bills), and the MCP server—the more natural agent surface—is explicitly read-only, so agentic posting must go through the raw Connect API rather than a documented review workflow. Missing for 10: explicit journal-entry draft/pending state, an accountant review-queue UI/API for entries, and confirmation that MCP or agent tooling can trigger this flow.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"The Digits Connect API uses OAuth 2.0 with the authorization code grant type... API access in 3 steps: 1. User Authorization via https://co…”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”

   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 Digits
   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

   Digits~partialclaimed4/10

   Digits documents the ability to fetch the full chart of accounts via the Connect API and mentions 'dimensional accounting'/'dimensional reporting' as a paid-tier feature, suggesting some support for class/tag dimensions, but there is no documentation of an accountant-facing workflow for creating account types or sub-accounts — indeed Digits' messaging emphasizes that its AI 'replaces' manual chart-of-accounts mapping rather than supporting granular manual customization. Missing for 10: explicit UI/API support for defining account types, creating/nesting sub-accounts, and configuring custom class or tag dimensions beyond the vague 'dimensional accounting' mention.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “Published self-serve pricing, per business not per seat: "Yes, Digits offers a 30-day free trial", and "Digits generates real-time financial…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”

   proof ↗⚑ flag

Journal entries

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

   weight 3 · round to Zoho Books
   Zoho Books~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Digits—none0/10

   Digits' evidence describes AI-driven auto-booking, categorization, reconciliation, and an API for batch transaction sync/ledger queries, but nowhere documents a manual journal-entry workflow with debit/credit balancing and memo fields — the product's own framing explicitly positions itself as replacing manual entry/mapping rather than supporting it.

   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “The AGL is a purpose-trained model suite: "Proprietary AI models trained on over 170 Million transactions totaling $875 Billion", doing "Rea…”

   proof ↗⚑ flag

Ai audit

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

   weight 3 · round drawn
   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

   Digits~partialclaimed6/10

   Digits documents built-in anomaly/duplicate handling (idempotent writes with external_id dedup, 11 quality checks before close, 'Agentic Close' that 'surfaces exceptions with context', and 24/7 bookkeeping with 'transaction flagging & smart reviews'), and its MCP server lets an AI agent query the live ledger. However this is largely automated system-level checking rather than a user-directed agent actively monitoring and proactively flagging anomalies/duplicates during the close cycle, and the MCP server is explicitly read-only so an agent cannot act on or resolve flagged items. Missing for 10: independent/hands-on evidence that an AI agent can be configured to continuously monitor and alert on spend anomalies or duplicates specifically before close, and confirmation the flagging pipeline is agent-driven rather than purely rule/ML-based backend automation.

   • [claimed-docs] “"The Agentic Close — From transaction to close. One system. Most accounting systems only record work. The Agentic Close does it for you." Th…”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “Digits adds 11 new quality checks to make closing the books that much easier!”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The MCP launch post positions the ledger as the agent surface: Digits MCP "is now available as an official Claude Connector, making it even …”

   proof ↗⚑ flag

Audit trail

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

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

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

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

   proof ↗⚑ flag

   Digits—none0/10

   No evidence exists of a change-log, version history, or 'who changed what and when' audit trail feature across the ledger; the pack covers categorization, APIs, MCP, security-at-rest, and pricing but nothing about audit trails or user-action logging.

   ⚑ flag

Multi entity

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

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

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

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

   proof ↗⚑ flag

   Digits—none0/10

   Evidence shows Digits is built around a single AI-native general ledger (AGL) per business, with firm plans offering multi-client seats/permissions but no documented feature for combining multiple legal entities into consolidated financial statements. Nothing in the docs, API reference, or product pages mentions inter-entity eliminations, consolidated reporting, or multi-entity ledger structures.

   • [claimed-docs] “Published self-serve pricing, per business not per seat: "Yes, Digits offers a 30-day free trial", and "Digits generates real-time financial…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Digits~partialclaimed6/10

   The Connect API exposes substantial read/write ledger functionality (financial statements, chart of accounts, bills workflow with submit/approve/pay, batch transaction sync, webhooks) matching much of the UI's bookkeeping/reporting features, and the MCP server extends programmatic access to AI tools. However, the MCP server is explicitly read-only, and several UI-surfaced features (Ask Digits AI assistant, Invoicing, Bill Pay drag-and-drop UI, Dashboards customization, mobile app features) have no documented API/MCP equivalent for full parity — missing for 10: write access via MCP, API coverage for Ask Digits conversational tasks, invoicing endpoints, dashboard customization API, and independent confirmation that all UI actions map to API calls.

   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “"The Digits Connect API uses OAuth 2.0 with the authorization code grant type... API access in 3 steps: 1. User Authorization via https://co…”
   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “Bill Pay Drag. Drop. Approve. Pay.”
   • [claimed-docs] “Invoicing Get paid faster”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Digits~partialclaimed4/10

   Digits' Connect API exposes read endpoints for financial statements, chart of accounts, ledger entries, and transactions via a documented OpenAPI spec, which could be used to pull data out into open formats. However, there is no documented bulk 'export all your data' feature, no CSV/GDPR-style data portability statement, and no mention of account closure or migrating away from Digits (only migration into Digits from QuickBooks is documented). missing for 10: a dedicated full-account data export/download feature, explicit open-format (CSV/JSON) bulk export tooling, and any documentation addressing leaving/closing an account with full data portability.

   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"The Digits Connect API provides a complete OpenAPI 3.0 specification that describes all available endpoints, request parameters, response s…”
   • [claimed-docs] “How do I migrate to Digits from Quickbooks?”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Zoho Books—none0/10

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

   ⚑ flag

   Digits—none0/10

   Digits is a closed commercial SaaS financial product; there is no evidence of any open-source license or publicly readable source code repository. Evidence only covers API docs, MCP server, and product features, not source availability.

   ⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Digits—none0/10

   No evidence anywhere in the pack mentions data residency, regional data storage options, or geographic controls for where financial data is hosted; security page only discusses encryption and SOC 2, not location choice.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Zoho Books—none0/10

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

   ⚑ flag

   Digits—none0/10

   The evidence pack covers OAuth authentication, encryption at rest/in transit, and general security posture, but nothing addresses data retention policies or user-initiated deletion of financial data/records. For a financial ledger handling sensitive data, this is a fair and applicable privacy axis, but no documentation, help-center article, or API endpoint for retention settings or deletion requests is cited.

   ⚑ 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 Digits
   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

   Digits✓fullprobed9/10

   Digits ships both a documented Connect API (OAuth, OpenAPI, live ledger endpoints for statements, balances, cash flow) and an official read-only MCP server exposing the 'live, auto-booked' AGL data to Claude, ChatGPT, Cursor etc., independently confirmed live via a working OAuth-gated MCP probe — enabling an agent to query real-time financial data to answer affordability-style questions grounded in the ledger. The Ask Digits assistant further demonstrates first-party natural-language grounding against live financials. Missing for 10: no independent third-party example of a real 'can we afford X' query/answer being run end-to-end through the API or MCP.

   • [claimed-docs] “The Digits MCP server is hosted at a documented endpoint — "Connect Digits to your AI tool using the steps below. Each tool may look a littl…”
   • [claimed-docs] “The MCP launch post positions the ledger as the agent surface: Digits MCP "is now available as an official Claude Connector, making it even …”
   • [probe] “PROBE mcp-oauth (2026-09-16): keyless JSON-RPC initialize to https://api.digits.com/mcp answers HTTP 401 with a www-authenticate Bearer chal…”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “"Meet Ask Digits — Ask questions. Complete tasks. Understand your business... Ask Digits anything about your financials—cash flow, expenses,…”
   • [claimed-docs] “auto-booking 95%+ of transactions in real time, delivering always up-to-date financials”

   proof ↗⚑ flag

Custom reports

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

   weight 2 · round to Digits
   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

   Digits~partialclaimed5/10

   Digits explicitly advertises 'dimensional reporting' and 'dimensional accounting' as a feature (gated to Core/Pro plans) and has a help doc titled 'How do I create a custom report?', suggesting some custom, dimension-based reporting capability exists. However, no evidence specifies filtering/grouping by class, location, or tag dimensions specifically, nor shows a UI walkthrough or hands-on confirmation of this granularity. Missing for 10: explicit documentation naming class/location/tag as filterable/groupable dimensions, a hands-on or independent demonstration of building such a custom report, and detail on how grouping/filtering works in the report builder.

   • [claimed-docs] “providing real-time categorization, automated reconciliations, live connected financial data, dimensional reporting, cash flow and runway tr…”
   • [claimed-docs] “How do I create a custom report?”
   • [claimed-docs] “"24/7 AI Bookkeeping & Reconciliation — Books that keep themselves": "Digits AI learns your business to provide 24/7 bookkeeping with transa…”
   • [claimed-docs] “Published self-serve pricing, per business not per seat: "Yes, Digits offers a 30-day free trial", and "Digits generates real-time financial…”

   proof ↗⚑ flag

Statements

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

   weight 3 · round to Digits
   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

   Digits✓fullclaimed8/10

   Digits explicitly generates P&L, balance sheet, and cash-flow statements on demand from its live AGL ledger, with API endpoints for 'Generate a balance sheet statement', cash flow, and P&L, plus dashboards and custom reports (help.digits.com custom report doc). Pricing page confirms 'real-time financial statements—profit & loss, balance sheet, and cash flow' updating automatically. Missing for 10: independent/hands-on verification of statement accuracy for arbitrary custom periods, and no third-party review confirming report correctness beyond vendor claims.

   • [claimed-docs] “Digits Financials generates real-time, customizable financial statements and reports directly from the AGL with collaboration features that …”
   • [claimed-docs] “The API reference (indexed in the developer llms.txt) spans read AND write ledger surfaces: financial statements on demand ("Generate a bala…”
   • [claimed-docs] “Published self-serve pricing, per business not per seat: "Yes, Digits offers a 30-day free trial", and "Digits generates real-time financial…”
   • [claimed-docs] “How do I create a custom report?”
   • [claimed-docs] “"The Digits Connect API gives you programmatic access to the AGL® — our AI-native general ledger. Legacy accounting APIs expect you to sync …”

   proof ↗⚑ flag