FreshBooks vs Wave

Agent access

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

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

   Wave—none0/10

   A direct probe found no llms.txt file (404) and no agent-oriented docs surface; Wave's marketing pages contain no mention of llms.txt or agent-consumable documentation, and its developer portal is blocked to crawlers.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

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

   Wave—none0/10

   Wave is a small-business accounting/invoicing SaaS with no evidence of a CLI, headless mode, or CI-friendly automation surface; llms.txt and OpenAPI probes both 404, and the developer/API portal is walled off with no documented programmatic interface. Nothing suggests Wave can be run headlessly or scripted in a CI pipeline.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

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

   Wave—none0/10

   Wave is an accounting SaaS product, so an official MCP server is a plausible axis, but there is no evidence of any MCP server, API docs accessible, or agent integration; probes for llms.txt and OpenAPI both 404, and the developer portal is walled off from crawling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   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

   Wave—none0/10

   No evidence of any official CLI for Wave; probes for llms.txt and API docs both 404/403, and marketing pages document no CLI, API, or agent tooling surface.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

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

   Wave—none0/10

   Marketing pages document no public API, and direct probes for llms.txt/OpenAPI both 404; the developer portal exists but is blocked to crawlers so no documented, accessible API surface is evidenced.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 2 · round to FreshBooks
   FreshBooks~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Wave—none0/10

   No evidence of any API credential system, scoped tokens, or agent-oriented access controls; Wave's role-based access is for human collaborators (admin/editor/viewer), and its developer/API portal could not even be crawled to confirm any credentialing mechanism exists.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”

   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

   Wave—none0/10

   No evidence of official SDKs for AI-native/programmatic use; llms.txt and OpenAPI probes both 404, and the developer/GraphQL API portal is walled off from crawling with no documentation surfaced. Marketing pages describe only end-user accounting features, not SDKs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   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

   Wave—none0/10

   No evidence of webhook support anywhere in Wave's marketing pages or developer portal; the developer portal itself couldn't be crawled and is described as documenting no webhook surface, and llms.txt/openapi probes both returned 404.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

Agentic features

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

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

   Wave—none0/10

   Evidence shows OCR data extraction and automation (auto-categorize, reminders) but no AI-generated insights, analysis, or suggestions surfaced to users; reports are static comparisons, not AI-driven recommendations. No mention of AI/ML-based insight generation anywhere in the pack.

   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag

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

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

   Wave~partialprobed4/10

   Wave ships several fixed, always-on background automations (auto bank import/categorization, recurring invoices with auto payment reminders, auto payroll tax filing) that run without manual triggering, per wave-docs-2, wave-docs-5, wave-docs-10, wave-docs-14. However these are hard-coded product features, not a general-purpose automation/agent framework the user can configure, and there is no API, webhook, or MCP surface documented for building custom autonomous workflows (wave-probe-1, wave-probe-2, wave-supp-dev-portal-wall). Missing for 10: a configurable automation builder, any AI-agent/orchestration capability, and a documented API/webhook layer for extending automations.

   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

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

   Wave—none0/10

   No evidence anywhere in the pack of a built-in AI assistant or agentic feature; Wave's docs describe automation (auto-import, OCR, reminders) but nothing about delegating tasks to an AI assistant, and the developer portal is inaccessible with no API/AI mention on marketing pages.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”

   proof ↗⚑ flag

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

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

   Wave—none0/10

   No evidence of any natural-language command interface, chat assistant, or AI-native control surface; Wave's marketing pages describe only manual UI-based accounting/invoicing features, and probes for llms.txt/openapi found nothing, with the developer portal walled off from crawling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to FreshBooks
   FreshBooks~partialprobed3/10

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

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

   proof ↗⚑ flag

   Wave—none0/10

   There is no evidence of an interactive API reference or runnable examples; probes for openapi/llms.txt returned 404s, and the developer portal itself is blocked from crawling with no documented API surface accessible.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

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

   Wave—none0/10

   Direct probes for OpenAPI/swagger specs and llms.txt returned 404s, and Wave's developer portal (GraphQL API) is blocked to crawlers with no machine-readable spec surfaced; marketing pages document no API spec at all.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   FreshBooks—none0/10

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

   ⚑ flag

   Wave—none0/10

   No evidence of any sandbox, staging, test-mode, or dev environment for Wave; the developer portal is inaccessible and marketing pages document no API/test environment for isolating data from production.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

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

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

   Wave—none0/10

   No evidence of versioned APIs or a documented deprecation policy; the developer/API portal is inaccessible for crawling and Wave's public marketing pages document no API surface at all, with llms.txt and OpenAPI probes both returning 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   proof ↗⚑ flag

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

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

   Wave~partialprobed2/10

   Wave documents a narrow bulk feature (uploading up to 10 receipts at once with OCR), but there is no evidence of broader bulk operations (e.g., bulk invoice creation/edits, bulk transaction updates) or any API/CLI/MCP surface an AI-native user could script against — the developer portal is crawl-walled and no OpenAPI/llms.txt exists. missing for 10: bulk invoice/transaction/customer operations, programmatic API or CLI access for scripted bulk actions, evidence beyond the 10-item receipt cap.

   • [claimed-docs] “Scan unlimited receipts and bulk import up to 10 at once to save time. Our smart OCR technology extracts and organizes the data—meaning less…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   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

   Wave—none0/10

   Wave offers only a handful of fixed, vendor-built automations (recurring invoices, overdue reminders, auto payroll tax filing, bank auto-categorization) — none of these let a user define custom rules or trigger-action logic on arbitrary events. No evidence of a rules engine, webhooks, or conditional automation builder; the developer/API surface is walled off (403) and marketing pages document no such capability.

   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   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

   Wave~partialprobed3/10

   Wave supports one narrow recurring automation — recurring invoices and payment reminders (wave-docs-10, wave-docs-2) — but there is no evidence of a general-purpose scheduler, API-triggered jobs, or workflow automation platform that an AI-native user could hook into; its developer/API surface is walled off from public documentation (wave-supp-dev-portal-wall, wave-probe-1, wave-probe-2). Missing for 10: programmable/scriptable recurring jobs beyond invoicing, API or webhook-based scheduling, and any AI/automation-platform integration evidence.

   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

Ai reconciliation

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

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

   Wave—none0/10

   Wave's evidence covers auto-import/categorization, invoicing, payroll, and receipts, but there is no mention of an AI agent performing end-to-end reconciliation, flagging exceptions, or preparing a close for human review; no automation/agent framework or API for such orchestration is documented, and the developer portal is a crawl wall with no public API/agent hooks shown.

   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

Bank feeds

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

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

   Wave✓fullclaimed8/10

   Wave's Pro Plan explicitly documents automatic daily bank/credit-card feed import with auto-merge and categorization, directly matching the story, and this is corroborated across multiple marketing pages. Missing for 10: independent/hands-on verification (e.g., user reviews confirming daily reliability) beyond vendor claims, and no detail on credit-card-specific connection flow distinct from bank accounts.

   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”

   proof ↗⚑ flag

Categorization

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

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

   Wave~partialclaimed4/10

   Wave documents automatic bank transaction import and categorization on the Pro Plan (auto-merge/categorize), but no evidence anywhere describes the system learning from user corrections over time — a core part of the story. Missing for 10: any documentation of a learning/adaptive categorization mechanism, evidence that manual recategorization improves future suggestions, and independent/hands-on confirmation of categorization accuracy improving.

   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”

   proof ↗⚑ flag

Reconciliation

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

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

   Wave~partialclaimed4/10

   Wave documents bank auto-import with auto-merge and categorization (implying some duplicate/match handling), but there is no evidence of a dedicated reconciliation view that explicitly surfaces matched, unmatched, and duplicate transactions for accountant review, nor of bank-to-ledger balance reconciliation reporting. Missing for 10: explicit unmatched-transaction review UI, duplicate-transaction flagging documentation, and a formal reconciliation/statement-balance-match report.

   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Auto-import bank transactions... Auto-merge and categorize bank transactions”

   proof ↗⚑ flag

Bill management

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

   weight 2 · round to FreshBooks
   FreshBooks~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Wave—none0/10

   Evidence only shows Wave lets users 'create unlimited... bills' as a record type (wave-docs-7); there is no mention of vendor bill capture workflow, approval routing, or scheduled bill payments anywhere in the pack. Wave's payments feature is explicitly for receiving customer payments on invoices, not paying vendors (wave-supp-payments), and no AP-specific workflow is documented.

   • [claimed-docs] “Create unlimited estimates, invoices, bills, and bookkeeping records”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

   proof ↗⚑ flag

Payables

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

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

   Wave—none0/10

   Evidence confirms Wave supports creating bills and general accounting reports (month-to-month/year-to-year comparisons), but nothing documents an accounts-payable aging report or vendor balance tracking at a point in time. Missing for 10: AP aging report, vendor balance summary/statement, point-in-time vendor ledger view.

   • [claimed-docs] “Create unlimited estimates, invoices, bills, and bookkeeping records”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   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

   Wave—none0/10

   No evidence Wave offers period locking or close controls; docs mention role-based access and reports but nothing about locking closed periods or preventing prior-period edits without explicit reopening.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”

   proof ↗⚑ flag

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

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

   Wave—none0/10

   No evidence of any month-end close checklist, reconciliation tracking, accrual management, or review sign-off workflow; Wave's evidence covers invoicing, payroll, receipts, and basic reports only, and it explicitly positions itself as built for small business owners rather than accountants performing formal close processes.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag

Collaboration

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

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

   Wave✓fullclaimed7/10

   Wave explicitly documents inviting an accountant/bookkeeper with role-scoped access (payroll manager, admin, editor, viewer on Pro, or free accountant/tax pro role), directly matching the story. Missing for 10: independent/hands-on verification of the invite/permissions flow and finer detail on what each role can/cannot edit.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   proof ↗⚑ flag

Data access

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

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

   Wave—none0/10

   Evidence shows Wave's developer/GraphQL API portal exists but is crawl-walled and unverifiable, and explicit probes for llms.txt/openapi/swagger all return 404; no documentation confirms GL or trial balance export via API in open formats (CSV/JSON/XML). Marketing pages describe UI-based 'reports' but never reference an API endpoint for ledger/trial balance data.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

Integrations

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

   weight 2 · round to FreshBooks
   FreshBooks✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Wave~partialclaimed6/10

   Wave clearly documents automatic bank-feed import/categorization (Pro plan) and integrated online payments that flow directly into invoicing/accounting records, so banking and payments activity does land in the ledger automatically. However, the payroll product's features (direct deposit, tax filing, employee portal) are described in isolation with no explicit statement that payroll transactions sync into the accounting ledger the way bank/payment data does, and there's no evidence of an API/webhook layer for connecting external banking, payment, or payroll systems beyond Wave's own native modules. Missing for 10: explicit documentation that payroll runs automatically post to the general ledger, and any API/integration surface for external banking or payroll systems.

   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Connect your bank accounts in seconds with the Pro Plan. Transactions will appear in your bookkeeping automatically, and you'll say goodbye …”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”
   • [claimed-docs] “Run payroll in minutes”
   • [claimed-docs] “Wave’s complete payroll tax service will automatically pay and file your state and federal payroll taxes.”
   • [claimed-docs] “Deposit payments directly into your employees’ bank accounts. Less work for you, and your team will love it.”

   proof ↗⚑ flag

Migration

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

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

   Wave~partialclaimed3/10

   Wave mentions an 'onboarding' process for switching from other accounting software like Freshbooks, but this is a single glancing bullet point with no detail on how historical transactions, ledgers, or account balances are actually imported or whether transaction-level detail is preserved. missing for 10: documented import/migration tool, description of data mapping (chart of accounts, historical invoices, journal entries), evidence that no transaction detail is lost, and any independent user reports of successful bookkeeping migrations.

   • [claimed-docs] “Onboarding when switching from other accounting software, like Freshbooks”
   • [claimed-docs] “When you switch from another payroll software, migrating your data is simple.”

   proof ↗⚑ flag

Invoicing

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

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

   Wave✓fullclaimed9/10

   Wave's docs directly cover invoice creation, branded templates, online payment via 'Pay now' (credit card/bank/Apple Pay), and status tracking (viewed, due, paid) plus overdue reminders — exactly matching the story. Missing for 10: independent/hands-on corroboration beyond vendor marketing pages.

   • [claimed-docs] “Know when an invoice is viewed, becomes due, or gets paid, so you can take the right actions to manage your cash flow.”
   • [claimed-docs] “Customers can click a “Pay now” button on invoices and pay instantly by credit card or secure bank payment (ACH/EFT) for as little as 1%2 pe…”
   • [claimed-docs] “Add your logo and brand colors to our professional invoice templates. Drag-and-drop editing makes it easy to customize!”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”
   • [claimed-docs] “"Wave's online payments software helps you get paid quickly by bank deposit, credit card, and Apple Pay... Customers can pay instantly by cr…”

   proof ↗⚑ flag

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

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

   Wave✓fullclaimed8/10

   Wave's documentation explicitly covers both halves of the story: recurring invoices with automatic credit card payments for repeat customers (wave-docs-10), and automatic overdue payment reminders scheduled at 3/7/14 days (wave-docs-2, wave-supp-invoicing). Missing for 10: independent/hands-on corroboration beyond vendor marketing pages, and detail on customizing reminder cadence beyond the fixed schedule.

   • [claimed-docs] “Set up recurring invoices and automatic credit card payments for your repeat customers and stop chasing payments.”
   • [claimed-docs] “Schedule reminders to automatically deploy 3, 7, and 14 days after sent invoices are due, so you don't have to keep chasing customers.”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

   proof ↗⚑ flag

Receivables

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

   weight 2 · round to FreshBooks
   FreshBooks~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Wave—none0/10

   Evidence describes general accounting reports (cash-flow trend comparisons) and per-invoice status tracking (viewed/due/paid), but nothing in the pack specifically documents an accounts-receivable aging report or a per-customer balance summary. Missing for 10: explicit AR aging report feature, per-customer balance/statement view, any documentation naming 'aging' or customer-level receivables tracking.

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Know when an invoice is viewed, becomes due, or gets paid, so you can take the right actions to manage your cash flow.”
   • [claimed-docs] “Invoicing with payment collection built in: "Send professional invoices... Get paid fast via credit card, bank payment, or Apple Pay... Auto…”

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

   Wave—none0/10

   No evidence of an API for posting journal entries, nor any review-queue/approval workflow; the developer portal is inaccessible (403) and marketing pages document no API/MCP/CLI surface, and probes for llms.txt/openapi return 404s.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

Chart of accounts

1. accountantCustomize the chart of accounts with account types, sub-accounts, and class or tag dimensions

   weight 3 · round to FreshBooks
   FreshBooks~partialclaimed3/10

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

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

   proof ↗⚑ flag

   Wave—none0/10

   The evidence pack contains no documentation of chart-of-accounts customization, account types, sub-accounts, or class/tag dimensions in Wave; it only vaguely mentions 'Tag it, track it' without describing COA structure, and positions Wave as built for non-accountants using standard double-entry books without customizable account hierarchies. missing for 10: any mention of account type management, sub-account creation, or class/tag dimension reporting.

   • [claimed-docs] “Tag it, track it, and see what's working for your business.”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   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

   Wave~partialclaimed3/10

   Wave explicitly markets itself as 'real, double-entry accounting software,' implying journal-entry mechanics under the hood, but no evidence pack item documents a manual journal-entry screen, debit/credit balancing UI, or memo field for such entries. Missing for 10: explicit manual journal entry feature documentation, debit/credit balance validation details, memo/note field support, and any independent or hands-on confirmation of this specific workflow.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

Ai audit

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

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

   Wave—none0/10

   No evidence of any AI agent, anomaly detection, duplicate transaction flagging, or automated audit monitoring capability; Wave's evidence covers manual/human-facing bookkeeping, invoicing, payroll and receipts features only, plus a note that its API/developer surface is not documented publicly.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “Bank feeds and auto-categorization are a paid-tier feature, stated plainly: "With the Pro Plan, automatically import, merge, and categorize …”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   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

   Wave—none0/10

   Evidence shows multi-user role access (admin/editor/viewer, accountant access) but nowhere documents an audit trail or change log tracking who edited what and when across the ledger. No mention of audit logs, version history, or edit tracking exists in the pack.

   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

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

   Wave—none0/10

   Wave's pricing is explicitly per-business (subscribe and pay separately for each business), with no mention of consolidation, inter-entity eliminations, or a multi-entity reporting view; evidence explicitly frames Wave as built for individual small business owners, not multi-entity accounting.

   • [claimed-docs] “A perpetual free Starter plan plus a per-business Pro plan: "The subscription fee for the Pro Plan is per business, not per owner... you'd s…”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

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

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

   Wave—none0/10

   Evidence shows no accessible API documentation (developer portal returns 403, no OpenAPI/llms.txt found), and marketing pages document no API/CLI surface that would let users mirror UI actions programmatically. There's no evidence of API parity with UI features like invoicing, payroll, or bank feeds.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   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

   Wave—none0/10

   No evidence anywhere in the pack of a data export feature (e.g., CSV/QIF export, open-format backups) or data portability tooling; marketing pages focus on invoicing, payroll, receipts, and payments with no mention of exporting or leaving with your data, and the developer/API surface is walled off (403) with no llms.txt or OpenAPI found. Missing for 10: any documented export-to-open-format feature, data portability docs, or migration-out tooling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”

   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

   Wave—none0/10

   No evidence anywhere in the pack mentions data residency, regional storage options, or compliance controls for choosing where data is stored; Wave's marketing pages focus entirely on accounting/invoicing/payroll features with no privacy-posture or data-location documentation.

   ⚑ 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

   Wave—none0/10

   Wave is a small-business accounting/invoicing product with no evidence of any data retention or deletion controls, privacy dashboard, or export/erasure tooling in its marketing pages; the developer portal is inaccessible and no API/CLI/MCP docs exist to inspect further.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   FreshBooks—none0/10

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

   ⚑ flag

   Wave—none0/10

   Wave is a small-business accounting/invoicing SaaS product with no evidence of any telemetry opt-out, privacy controls, or usage-tracking settings documented anywhere in its marketing pages; the developer portal is also inaccessible for verification. No mention of an AI-native usage context or telemetry controls exists in the pack.

   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”

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

   Wave—none0/10

   No evidence of any AI agent, chat interface, or query capability grounded in live ledger data; the probes show no llms.txt/OpenAPI surface exposed on marketing domain, and the developer/GraphQL API portal is walled off from crawling with no documented AI integration. Marketing pages only describe reports/dashboards, not agent-accessible querying.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.waveapps.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.waveapps.com/openapi.json, https://www.waveapps.com/swagger.json, https://www.waveapps.c…”
   • [claimed-docs] “Honest crawl-wall note: Wave's developer portal (developer.waveapps.com, the documented home of its GraphQL API) answers HTTP 403 Forbidden …”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”

   proof ↗⚑ flag

Custom reports

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

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

   Wave—none0/10

   Wave's evidence pack shows only basic month-to-month/year-to-year comparison reports; there is no mention of class, location, or tag-based report filtering/grouping, which is a QuickBooks/Xero-style feature Wave does not advertise (Wave is explicitly positioned as not built for accountants' advanced needs).

   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”
   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”

   proof ↗⚑ flag

Statements

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

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

   Wave~partialclaimed6/10

   Wave uses real double-entry accounting and explicitly offers accounting reports with month-to-month/year-to-year comparisons to identify cash flow trends, implying core financial statements are generated from bookkeeping data. However, evidence never explicitly names or confirms a formal P&L, balance sheet, and cash-flow statement generated on-demand for any custom period — only general 'accounting reports' are described. Missing for 10: explicit documentation of P&L/balance sheet/cash-flow statement outputs, ability to select arbitrary custom date ranges, and independent/hands-on confirmation of statement accuracy.

   • [claimed-docs] “"Wave uses real, double-entry accounting software. Don't know what that is? No sweat. Accountants do, and they'll thank you for it." Positio…”
   • [claimed-docs] “"Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify…”
   • [claimed-docs] “Our robust small business accounting reports are easy to use and show month-to-month or year-to-year comparisons so you can easily identify …”

   proof ↗⚑ flag