Xero vs Digits

Agent access

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

   weight 2 · round to Digits
   Xero~partialprobed5/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

   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