FreshBooks vs Digits

Agent access

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

   weight 2 · round to Digits
   FreshBooks—none0/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Digits
   FreshBooks—none0/10

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

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

   proof ↗⚑ flag

   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

4. ai-native userUse an official CLI

   weight 2 · round drawn
   FreshBooks—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Digits
   FreshBooks✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   FreshBooks~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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

7. ai-native userBuild against official SDKs

   weight 2 · round to FreshBooks
   FreshBooks~partialprobed6/10

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

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

   proof ↗⚑ flag

   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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to FreshBooks
   FreshBooks✓fullclaimed8/10

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

   Digits~partialclaimed7/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Digits
   FreshBooks—none0/10

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

   No evidence of a sandbox/test environment, test-mode API keys, or demo accounts; the API docs cover authentication, endpoints, and webhooks but nothing about non-production testing.

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   Digits~partialclaimed6/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to FreshBooks
   FreshBooks~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Digits~partialclaimed3/10

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

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to FreshBooks
   FreshBooks~partialclaimed4/10

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

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

   proof ↗⚑ flag

   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

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   Digits✓fullclaimed8/10

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

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

   proof ↗⚑ flag

Categorization

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

   weight 2 · round to Digits
   FreshBooks—none0/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   Digits~partialclaimed6/10

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

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

   proof ↗⚑ flag

Data access

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

   weight 3 · round to Digits
   FreshBooks~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   Digits✓fullclaimed8/10

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

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

   proof ↗⚑ flag

Migration

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

   weight 1 · round to Digits
   FreshBooks—none0/10

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   Digits~partialclaimed4/10

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

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

   proof ↗⚑ flag

Journal entries

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

   weight 3 · round to FreshBooks
   FreshBooks~partialclaimed6/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   FreshBooks—none0/10

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

   ⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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