Pilot vs FreshBooks

Agent access

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

   weight 2 · round to Pilot
   Pilot~partialprobed4/10

   A probe confirms Pilot serves an llms.txt file at HTTP 200, so an agent can indeed be pointed at it — but the content shown is minimal (just entity/category metadata, no structured docs or API references), and other agent-doc formats (docs-md, openapi) return 404. Missing for 10: substantive llms.txt content beyond basic metadata, markdown docs mirror, and any first-party statement about agent-oriented documentation strategy.

   • [probe] “PROBE llms.txt: HTTP 200 at https://pilot.com/llms.txt # Pilot [Entity: Pilot] [Category: Professional Services] [Subcategory: Acco…”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

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

   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

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

   weight 3 · round drawn
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any MCP server offering; docs mention integrations (Bill.com, Stripe, Gusto) but nothing about AI agent connectivity via MCP, and API/openapi probes returned 404s.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to FreshBooks
   Pilot—none0/10

   No evidence of a public API for Pilot; OpenAPI/swagger probes all returned 404 and no docs mention an API for driving the product programmatically. Pilot is a human-service accounting/bookkeeping product with integrations, not an API-driven platform.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

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

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

   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

6. ai-native userBuild against official SDKs

   weight 2 · round to FreshBooks
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any official SDKs; probes for API/OpenAPI specs returned 404s, and no docs mention developer SDKs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

7. ai-native userSubscribe to events via webhooks

   weight 2 · round to FreshBooks
   Pilot—none0/10

   No evidence of any webhook subscription capability or event API; Pilot is an accounting/bookkeeping service and probes show no OpenAPI or developer API surface exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round to Pilot
   Pilot~partialclaimed4/10

   Pilot's marketing mentions 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead' (pilot-docs-7), which points to some AI-generated insight capability inside the product, and scenario/cash-flow modeling features (pilot-docs-8, pilot-docs-21) suggest similar analytical output, though these are framed as human CFO-delivered rather than explicitly AI-driven. There is no independent/hands-on corroboration of the AI feature actually working, and community reviews focus on bookkeeping accuracy/time savings rather than AI insights. Missing for 10: detailed documentation of the AI feature's scope/accuracy, independent user testimony specifically about the AI insights, and clarity on whether insights are AI-generated vs. human-analyst-generated.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Model cash flow scenarios Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Track company expenses in real time Find the $2,000/month you didn't know you were wasting.”
   • [claimed-docs] “Find the $2,000/month you didn't know you were wasting.”

   proof ↗⚑ flag

   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

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

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

   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

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

   weight 3 · round to Pilot
   Pilot~partialclaimed3/10

   Pilot's pricing page mentions an AI feature offering 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' which is a thin, single-mention hint of an in-product AI assistant capable of some task-like actions (scenario modeling). There's no further documentation on scope, autonomy, or how tasks are delegated to it, and community evidence focuses on human bookkeepers/CFOs rather than the AI assistant. Missing for 10: detailed documentation of the AI assistant's task-delegation capabilities, independent/hands-on corroboration of it actually performing delegated tasks, and clarity on its scope beyond Q&A.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Pilot
   Pilot~partialclaimed3/10

   Pilot's marketing mentions 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' implying some natural-language Q&A interface, but there's no evidence of broader natural-language command execution (e.g., initiating actions, workflows) or any API/CLI to support it. missing for 10: evidence of NL commands beyond Q&A, independent/hands-on corroboration, technical documentation of the AI interface, API or programmatic access.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round to FreshBooks
   Pilot—none0/10

   Pilot is an accounting/bookkeeping service with no evidence of any developer API reference or runnable examples; probes for OpenAPI/docs-md all returned 404, and no evidence pack items mention an API reference.

   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Pilot—none0/10

   Probe explicitly checked common OpenAPI/swagger endpoints and all returned 404, and no documentation mentions a machine-readable API spec. Missing for 10: any published OpenAPI/Swagger spec, API documentation, or developer portal.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

   weight 1 · round drawn
   Pilot—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

   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

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

   weight 2 · round drawn
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with no evidence of any public API, versioning scheme, or deprecation policy; probes for OpenAPI specs all returned 404s. missing for 10: any public API documentation, versioning scheme, deprecation policy, or developer-facing API references.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service; no evidence describes any bulk-operation or batch-processing capability across items (transactions, invoices, etc.) for AI-native automation. Missing for 10: any mention of bulk edit/import/export tools, batch API operations, or automation-scale item processing.

   ⚑ flag

   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

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

   weight 3 · round to FreshBooks
   Pilot—none0/10

   Pilot is a bookkeeping/accounting service with dedicated human experts and integrations, but there is no evidence of a rules engine or automation-trigger system letting users define event-based automated actions; features described are AI Q&A and integrations, not user-defined trigger/action rules.

   ⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

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

   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

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 Pilot
   Pilot~partialcommunity3/10

   Pilot's evidence shows human bookkeepers finalize monthly books with integration-driven transaction classification (pilot-comm-1, pilot-docs-18, pilot-docs-26), which is directionally toward automated reconciliation, but there is no evidence of an autonomous agent matching transactions, flagging exceptions, and preparing a close package end-to-end without human bookkeeper involvement. Missing for 10: explicit agentic exception-flagging workflow, evidence of AI (not human staff) doing the matching/reconciliation, and documentation of an automated close-prep output for review.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Bank feeds

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

   weight 3 · round to Pilot
   Pilot✓fullcommunity7/10

   Pilot's docs and a first-hand customer testimonial confirm bank/credit-card/expense integrations automatically feed transaction data for classification, with real-time account data in the portal, eliminating manual founder bookkeeping work. missing for 10: no explicit list of supported banks, no detail on daily-sync frequency or setup flow, and no independent technical documentation beyond marketing/community claims.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Categorization

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

   weight 2 · round drawn
   Pilot—none0/10

   Evidence shows Pilot's transaction classification is handled by integrations plus human bookkeepers/accountants (pilot-comm-1, pilot-docs-17), not by an AI categorization engine that learns from founder corrections. No documentation describes a self-serve ML suggestion-and-correction loop. Missing for 10: any mention of an AI/ML categorization suggestion feature, evidence of a correction/feedback loop, or founder-facing UI for adjusting categorizations.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Reconciliation

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

   weight 3 · round to FreshBooks
   Pilot—none0/10

   Pilot's evidence describes bank/tool integrations and automated transaction classification (pilot-comm-1, pilot-docs-17) but never describes a reconciliation workflow that surfaces matched, unmatched, and duplicate transactions for accountant review. Missing for 10: any documentation or user report of a reconciliation screen or matched/unmatched/duplicate transaction handling.

   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Bill management

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

   weight 2 · round to FreshBooks
   Pilot~partialclaimed3/10

   Pilot's pricing page lists 'Full accounts payable' as a service line item and mentions integration with Bill.com, implying vendor bill handling, but there is no documented detail on bill capture, approval routing, or payment scheduling mechanics within a single workflow — AP appears to be a done-for-you service rather than a described self-serve workflow. Missing for 10: bill capture/OCR details, approval routing configuration, payment scheduling functionality, and any hands-on/independent confirmation of the AP workflow.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”
   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”

   proof ↗⚑ flag

   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

Payables

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

   weight 2 · round to Pilot
   Pilot~partialclaimed4/10

   Pilot advertises 'Full accounts payable' as a service feature and real-time account data access via its portal, implying some visibility into AP status, but there is no specific mention of AP aging reports or vendor balance tracking at a point in time. missing for 10: explicit AP aging report feature, vendor balance detail/history, point-in-time reporting capability, screenshots or hands-on evidence of AP aging views.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Close process

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

   weight 2 · round drawn
   Pilot—none0/10

   No evidence in the pack mentions period locking, closing periods, or preventing retroactive changes to prior-period financials; the evidence only covers bookkeeping, tax, CFO, and integration features. Missing for 10: any mention of period-lock/close controls, reopening workflow, or audit trail preventing prior-period edits.

   ⚑ flag

   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

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

   weight 3 · round to Pilot
   Pilot~partialclaimed3/10

   Pilot's monthly bookkeeping service closes books and lets customers communicate on 'outstanding items needed to finalize your books every month' via a portal, implying some close-tracking process, but there is no evidence of an actual checklist artifact tracking reconciliations, accruals, and review sign-offs as distinct trackable steps. missing for 10: explicit reconciliation checklist UI, accrual tracking, and sign-off/approval workflow evidence.

   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Collaboration

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

   weight 3 · round to FreshBooks
   Pilot—none0/10

   Pilot's evidence describes its own bookkeeping team communicating with the founder via a portal (docs-18, docs-26) and lets customers keep QuickBooks data so any tax preparer can access it (docs-24), but there is no evidence of a feature to invite an external accountant/bookkeeper into Pilot's own system with role-scoped permissions to review or adjust books. missing for 10: any documentation of user/role invitation, permission scoping, or external collaborator access controls within Pilot's platform.

   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”

   proof ↗⚑ flag

   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

Data access

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

   weight 3 · round to FreshBooks
   Pilot—none0/10

   No evidence of a documented API for pulling general ledger or trial balance data; probes for OpenAPI/docs endpoints returned 404s and no API documentation is mentioned anywhere in the evidence pack.

   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

Integrations

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

   weight 2 · round to Pilot
   Pilot✓fullcommunity8/10

   Pilot explicitly integrates with banking, payments, and payroll systems (e.g. Bill.com, Stripe, Gusto, 10k+ integrations) to feed real-time transaction data into the ledger, and community testimonials confirm bank/card/payment integrations auto-handle transaction classification with minimal founder effort. missing for 10: no explicit first-party detail on the breadth/setup process of bank feed connections beyond named partners, no independent audit of integration reliability at scale.

   • [claimed-docs] “We integrate with hundreds of tools like Bill.com, Stripe, and Gusto.”
   • [claimed-docs] “10k+ Integrations”
   • [claimed-docs] “If you use Gusto, we’ve partnered with Gusto to automatically apply the credit, saving you time.”
   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”

   proof ↗⚑ flag

   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

Migration

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

   weight 1 · round to Pilot
   Pilot~partialclaimed5/10

   Pilot markets that switching providers is supported and mentions keeping existing QuickBooks account and historical data, implying migration support, but there's no detail on how historical transaction-level detail is preserved or migrated from other systems (e.g., Xero, Wave, spreadsheets) beyond QuickBooks. missing for 10: documented migration process, evidence of no data/detail loss, support for non-QuickBooks source systems, independent confirmation of successful migrations.

   • [claimed-docs] “Whether you’re starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding, underst…”
   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Whether you're starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding, underst…”
   • [claimed-docs] “Whether you’re starting fresh or switching providers, your dedicated accounting expert is with you from day one handling onboarding”

   proof ↗⚑ flag

   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

Invoicing

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

   weight 3 · round to FreshBooks
   Pilot—none0/10

   Evidence only shows Pilot offers 'full accounts receivable' as a bookkeeping service item, but there is no mention of self-serve invoice creation, online payment collection, or view/paid tracking features for founders—Pilot is a done-for-you bookkeeping service, not an invoicing tool. Missing for 10: invoice creation UI, online payment processing, read-receipt/paid-status tracking evidence.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Pilot—none0/10

   Evidence mentions 'Full accounts receivable' as a service but nothing about recurring invoicing or automated overdue payment reminders specifically. Pilot is positioned as a bookkeeping/accounting service, not an invoicing tool with these automation features documented anywhere in the pack.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   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

Receivables

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

   weight 2 · round drawn
   Pilot~partialclaimed4/10

   Pilot's pricing page lists 'Full accounts receivable' as a service offering, confirming AR management is part of the product, but there is no evidence of specific features like aging reports or per-customer balance tracking/reporting in the evidence pack. missing for 10: documentation of aging reports, per-customer balance views, AR-specific dashboards or reports, and independent/hands-on confirmation of these features.

   • [claimed-docs] “Full accounts receivable Full accounts payable Payroll administration”
   • [claimed-docs] “Full accounts receivable Full accounts payable”

   proof ↗⚑ flag

   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

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

   No evidence of any API, agent integration, or journal entry review queue functionality; Pilot is a human-service bookkeeping/accounting company with no documented API (openapi probes 404). Missing for 10: any API existence, journal entry draft/post capability, review queue workflow, agent-facing endpoints.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE llms.txt: HTTP 200 at https://pilot.com/llms.txt # Pilot [Entity: Pilot] [Category: Professional Services] [Subcategory: Acco…”

   proof ↗⚑ flag

   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

Chart of accounts

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

   weight 3 · round to FreshBooks
   Pilot—none0/10

   Pilot is a done-for-you bookkeeping/accounting service, so ledger customization is a fair question, but the evidence pack only mentions generic 'custom workflows and reporting' with no mention of chart of accounts structure, account types, sub-accounts, or class/tag dimensions. Missing for 10: any documentation of COA setup, account type hierarchy, sub-account creation, or class/tag dimension tagging controlled by the accountant.

   • [claimed-docs] “Custom workflows and reporting”

   proof ↗⚑ flag

   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

Journal entries

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

   weight 3 · round to FreshBooks
   Pilot—none0/10

   Pilot's evidence describes a done-for-you bookkeeping/CFO service built on QuickBooks with dedicated experts handling books, but there is no mention of any interface for accountants to post manual journal entries with debits/credits and memos. Missing for 10: any UI or workflow for manual JE creation, debit/credit balancing, or memo attachment.

   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”

   proof ↗⚑ flag

   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

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

   Pilot's evidence covers bookkeeping, tax, CFO services, and AI Q&A on transactions, but there is no mention of an autonomous agent that monitors the ledger, flags spend anomalies, or detects duplicate transactions before close. missing for 10: anomaly-detection feature, duplicate-transaction flagging, any agentic monitoring capability, pre-close audit workflow evidence.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Track company expenses in real time Find the $2,000/month you didn't know you were wasting.”
   • [claimed-docs] “Communicate directly with your team through our user-friendly portal, where you can ask questions and provide feedback on any outstanding it…”

   proof ↗⚑ flag

   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

Audit trail

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

   weight 3 · round drawn
   Pilot—none0/10

   No evidence in the pack describes any audit trail, change history, or user-activity logging feature within Pilot's platform; the material focuses on bookkeeping services, integrations, CFO advisory, and tax credits. Missing for 10: any mention of audit logs, change tracking, user attribution, or timestamped edit history across the ledger.

   ⚑ flag

   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

Multi entity

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

   weight 2 · round to Pilot
   Pilot~partialclaimed4/10

   Pilot's FAQ mentions it can provide consolidated reporting for US entities with foreign subsidiaries, but there is no evidence of multi-entity management for domestic entities, no detail on consolidation methodology, and no independent/hands-on corroboration of this feature. missing for 10: multi-entity dashboard/management capability, domestic multi-entity consolidation support, detailed consolidation workflow, independent verification.

   • [claimed-docs] “We can also provide US entities with foreign subsidiaries with consolidated reporting.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to FreshBooks
   Pilot—none0/10

   No evidence of any public API for Pilot; probes for OpenAPI/swagger endpoints all returned 404, and all documentation describes only the human portal/UI and service offerings. missing for 10: any documented API, API parity claims, or developer endpoints.

   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”

   proof ↗⚑ flag

   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

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

   weight 3 · round to FreshBooks
   Pilot—none0/10

   While Pilot mentions QuickBooks compatibility and tax-preparer portability, there is no evidence of a dedicated data export feature, open-format export (CSV/JSON/API), or a documented process to fully extract and leave with all financial data; probes even show no public API/OpenAPI spec.

   • [claimed-docs] “Keep your existing QuickBooks account and historical data”
   • [claimed-docs] “Virtually every tax preparer in the US knows how to work with QuickBooks. You’ll have the freedom to choose any tax preparer you want.”
   • [probe] “PROBE docs-md: HTTP 404 at https://pilot.com/faq.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Pilot—none0/10

   No evidence in the pack addresses data residency, region selection, or storage location controls; Pilot is an accounting/bookkeeping service with no mention of infrastructure or data-residency options. Missing for 10: any documentation of data storage regions, residency guarantees, or configurable data location.

   ⚑ flag

   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

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Pilot—none0/10

   Pilot is an accounting/bookkeeping service; the evidence pack contains no privacy policy statements, opt-out controls, or AI-training data usage terms addressing whether customer financial data is used to train AI models. This is a fair question given Pilot advertises 'AI answers' features, but no evidence confirms any data-training opt-out or exclusion mechanism. Missing for 10: privacy policy/ToS language on AI training data usage, an opt-out mechanism, or any statement on data handling for AI features.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”

   proof ↗⚑ flag

   FreshBooks—none0/10

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

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Pilot—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy settings for Pilot's AI features or data; the pack only covers accounting, bookkeeping, and tax service offerings. Missing for 10: any documentation of data retention/deletion controls, privacy settings, or data handling policies for AI or customer data.

   ⚑ flag

   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

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

   Pilot advertises an in-app AI feature offering 'Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead,' which aligns with the 'can we afford X' query use case, but there is no evidence this is exposed via an API for external agents to query — the openapi probe returned 404s and no API/agent-integration docs exist. missing for 10: evidence of a public API/endpoint an external AI agent could call, documentation of grounding in live ledger data via API, and any independent confirmation the AI answer feature works as described.

   • [claimed-docs] “Instant AI answers about past transactions and current cash flow, plus run scenarios to plan ahead”
   • [claimed-docs] “Model cash flow scenarios Know if you can afford new hires well before you make the offers.”
   • [claimed-docs] “Know if you can afford new hires well before you make the offers.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://pilot.com/openapi.json, https://pilot.com/swagger.json, https://pilot.com/api/openapi.json, …”

   proof ↗⚑ flag

   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

Custom reports

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

   weight 2 · round drawn
   Pilot—none0/10

   Evidence only mentions generic 'custom workflows and reporting' (pilot-docs-10) with no mention of class, location, or tag dimension filtering/grouping capabilities typical of QuickBooks-style reports; missing for 10: any documentation of dimension-based (class/location/tag) filtering or grouping in reports.

   • [claimed-docs] “Custom workflows and reporting”

   proof ↗⚑ flag

   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

Statements

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

   weight 3 · round drawn
   Pilot~partialcommunity5/10

   Pilot's bookkeeping and CFO service pages reference real-time account data, custom workflows/reporting, and budget-vs-actuals/scenario planning, implying standard financial statements are produced as part of monthly bookkeeping, and community reviews confirm books are kept accurate and up to date. However, no evidence explicitly confirms generation of a P&L, balance sheet, and cash-flow statement for any arbitrary period on demand. Missing for 10: explicit documentation of the three core statements, confirmation of on-demand/any-period generation (vs. standard monthly close), and independent verification of statement accuracy/timeliness.

   • [claimed-docs] “Custom workflows and reporting”
   • [claimed-docs] “stay up to date with real time account data directly in the portal”
   • [claimed-docs] “Custom financial model with strategic insights Budget vs actuals variance analysis Scenario planning model”
   • [claimed-docs] “Plus stay up to date with real time account data directly in the portal.”
   • [community] “I'm a Pilot customer... Pilot basically solved that problem. I just do my normal business and their integrations with my banks, expensify, c…”
   • [community] “Pilot customer here; they are amazing. It's pretty different from a regular bookkeeper largely in that Pilot is super accurate and timely. M…”

   proof ↗⚑ flag

   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