Accounting & Bookkeeping Arena
FreshBooks vs Mercury Books
FreshBooks
FreshBooks (2ndSite Inc.)
FreshBooks wins · 16–15 (18 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to Mercury BooksFreshBooksnone0/10Direct 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.
Mercury Booksdisputedcontradicted2/10Mercury's blog promises a future MCP layer for agents, but direct probes show no llms.txt file (404) and no discoverable OpenAPI/agent-oriented docs at any candidate path, meaning there is currently nothing an agent could be pointed at. Missing for 10: a live llms.txt or agent-readable docs file, a shipped API/MCP endpoint, any evidence of the promised MCP layer actually existing.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to FreshBooksFreshBooks 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”
Mercury Booksnone0/10Mercury explicitly frames a full API and MCP layer as a future roadmap item ('Soon...'), and direct probes for API/OpenAPI/llms.txt endpoints all returned 404s, confirming no headless/CI-usable interface exists today. Command is a plain-language, in-app assistant, not a scriptable or automatable interface.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnFreshBooksnone0/10FreshBooks 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, …”
Mercury Booksnone0/10Mercury only states that an MCP layer is coming 'soon' for AI agents, with no evidence it currently exists; probes for API/OpenAPI/llms.txt endpoints all return 404s, confirming no official MCP server is live today.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userUse an official CLI
weight 2 · round drawnFreshBooksnone0/10No 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”
Mercury Booksnone0/10No evidence of a CLI; only future-planned API/MCP layer is mentioned, and probes for llms.txt/openapi endpoints returned 404s, indicating no current programmatic or CLI tooling exists.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userDrive the product through a documented public API
weight 3 · round to FreshBooksFreshBooks 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" —…”
Mercury Booksnone0/10Mercury explicitly says a full accounting API and MCP layer are coming 'soon,' not currently available, and direct probes for llms.txt and OpenAPI docs both returned 404s, confirming no public API exists today.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to FreshBooksFreshBooks 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”
Mercury Booksnone0/10Evidence only mentions a future accounting API and MCP layer as 'soon' (not yet shipped), with no mention of API keys, OAuth scopes, or least-privilege credential issuance; probes confirm no OpenAPI/spec or docs endpoints currently exist. There is no evidence Mercury Books lets a user issue scoped credentials for an agent today.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userBuild against official SDKs
weight 2 · round to FreshBooksFreshBooks 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”
Mercury Booksnone0/10Mercury explicitly frames the accounting API and MCP layer as future ('Soon'), and probes confirm no live OpenAPI/llms.txt endpoints exist yet — there is no official SDK currently available to build against.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userSubscribe to events via webhooks
weight 2 · round to FreshBooksFreshBooks 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…”
Mercury Booksnone0/10No evidence pack item mentions webhooks or event subscriptions; the only programmatic-access claim is a forward-looking 'soon' API/MCP mention, and probes confirm no public API/openapi spec exists yet. Missing for 10: any webhook documentation, event types, or subscription mechanism.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to Mercury BooksFreshBooksnone0/10No 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.
Mercury Command lets users ask natural-language questions about their financial data and get AI-grounded answers, plus AI-driven GL code suggestions and categorization, directly inside Books. missing for 10: independent/hands-on verification of insight quality, no detail on proactive suggestion generation beyond categorization/GL coding, and Mercury's own caveat that automation is not full autopilot.
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [claimed-docs] “The banking side feeds clean data to any ledger: "Transactions on Mercury are now automatically assigned GL codes based on your categorizati…”
- [claimed-docs] “Ask Mercury Command a question about your books, or hand off a bookkeeping task to it directly, in plain language.”
- [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to Mercury BooksFreshBooks 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…”
Mercury Books documents continuous, automatic categorization/reconciliation and a Command assistant that can be handed bookkeeping tasks in plain language (bulk GL coding, categorization rules), which is real background automation. However, the vendor itself explicitly cautions that 'a connected system isn't the same as fully automated' and that it should not be treated as 'putting your books on autopilot,' and the promised MCP/agent layer for end-to-end autonomous handling is described as 'soon,' not shipped. Missing for 10: a live, user-configurable autonomous automation/agent layer (MCP) with independent confirmation it runs unattended in production.
- [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”
- [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to Mercury BooksFreshBooksnone0/10The 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.)
Mercury Books ships a built-in AI assistant called Command that users can query in plain language and delegate bookkeeping tasks to (journal entries, chart of accounts organization, bulk categorization), described as 'AI built-in, not bolted on.' Missing for 10: independent/hands-on verification of Command's task-delegation reliability, and the vendor's own caveat that automation isn't 'autopilot' tempers full agentic delegation claims.
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [claimed-docs] “Ask Mercury Command a question about your books, or hand off a bookkeeping task to it directly, in plain language.”
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
- [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
ai-native userOperate the product with natural-language commands
weight 2 · round to Mercury BooksFreshBooksnone0/10No 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 …”
Mercury Command lets users ask questions and hand off bookkeeping tasks 'in plain language,' directly matching the natural-language command story, and this is documented across multiple first-party sources describing bulk actions, categorization, and Q&A. Missing for 10: independent/hands-on verification of Command's NL capabilities and confirmation that the broader agent-facing API/MCP layer (still described as 'soon') doesn't gate deeper command coverage.
- [claimed-docs] “Ask Mercury Command a question about your books, or hand off a bookkeeping task to it directly, in plain language.”
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to FreshBooksFreshBooks 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”
Mercury Booksnone0/10There is no evidence of any interactive API reference or runnable examples; the API is described only as 'soon' coming, and probes for openapi/llms.txt specs both returned 404s, indicating no public API docs exist yet.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnFreshBooksnone0/10FreshBooks 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”
Mercury Booksnone0/10Direct probes for llms.txt and OpenAPI/Swagger spec files all return 404, and docs only mention a future accounting API/MCP layer as an upcoming feature, not something currently downloadable. No machine-readable API spec exists today.
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnFreshBooksnone0/10No 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.
Mercury Booksnone0/10No evidence of any sandbox, staging, or test environment for Mercury Books; the API/MCP layer is described only as forthcoming with no mention of a non-production mode, and probes for docs/OpenAPI endpoints returned 404s.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnFreshBooksnone0/10FreshBooks 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”
Mercury Booksnone0/10The API is described as forthcoming ('Soon, a full accounting API will make every core Books action available programmatically'), and direct probes for openapi/llms.txt specs return 404s, showing no versioned API or deprecation policy currently exists.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to Mercury BooksFreshBooksnone0/10The 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”
Mercury Command explicitly supports bulk actions like bulk GL code assignment, categorization rules, and clearing categorization backlogs in bulk, which directly addresses bulk operations for an AI-native user. However, this is limited to bookkeeping/categorization tasks rather than a general-purpose bulk API, and the promised full accounting API/MCP layer for broader programmatic bulk actions is only 'coming soon,' with probes confirming no public API/OpenAPI spec exists yet. missing for 10: a live public API or MCP layer enabling arbitrary bulk operations, independent/hands-on verification of bulk actions working at scale, and documentation of bulk operation limits or scope beyond categorization/GL codes.
- [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to Mercury BooksFreshBooks 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”
Mercury Command explicitly supports creating 'categorization rules' and bulk GL code assignment, which is a form of user-defined rule-based automation triggered by transaction events, and automatic categorization/reconciliation is built-in. However, there's no evidence of a general-purpose rule/trigger-action framework beyond categorization (e.g., rules for invoicing, alerts, or other business events), and Mercury's own docs caution that automation isn't full autopilot. Missing for 10: broader event types beyond categorization, explicit rule configuration UI/API details, and independent confirmation of rule reliability.
- [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to FreshBooksFreshBooks 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…”
Mercury Booksnone0/10Evidence shows automatic categorization/reconciliation and an AI assistant (Command) that can be asked to do tasks, but there is no mention of user-defined recurring/scheduled jobs or workflows; the API/MCP layer that might enable this is explicitly described as 'soon' (not yet shipped), and probes for API endpoints 404. Missing for 10: any documented scheduling/recurring-workflow feature, evidence of a live automation API or MCP layer, and independent confirmation of scheduled task execution.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
Banking reconciliation — stories about banking reconciliation in this arenaBanking reconciliation
Stories about banking reconciliation in this arena
Ai reconciliation
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 Mercury BooksFreshBooksnone0/10FreshBooks 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…”
Mercury Books has continuous automatic reconciliation/categorization and Command can answer questions and offload bookkeeping tasks like journal entries and bulk categorization, but Mercury explicitly states automation is not 'autopilot' and requires human decision-making, and there's no evidence of an agent autonomously running a full month-end close with exception flagging and review prep end-to-end — the MCP/agent layer is only announced as 'soon'. missing for 10: evidence of an actual agent (not just Command chat) performing a full month-end close, explicit exception-flagging workflow, and a shipped MCP/API layer rather than a 'soon' roadmap item.
- [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
Bank feeds
founderConnect bank and credit-card accounts so transactions import automatically every day
weight 3 · round to Mercury BooksFreshBooks' 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…”
Mercury Books explicitly supports linking external bank accounts, cards, and payroll platforms with transactions pulled in automatically and reconciled/categorized continuously in real time, directly matching the founder story. Multiple first-party docs corroborate this (linking, auto-categorization, continuous reconciliation) and Mercury even publishes an honest caveat that 'connected' isn't 'fully automated,' showing transparency rather than contradiction. missing for 10: independent/hands-on verification beyond Mercury's own docs, and detail on daily import cadence/reliability guarantees.
- [claimed-docs] “Link external bank accounts, cards, payroll platforms, and more for the complete story of your business.”
- [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
- [claimed-docs] “Third-party data flows in alongside Mercury's own: Books "connects to a growing set of third-party platforms, including Stripe, PayPal, and …”
- [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
Categorization
founderGet automatic categorization suggestions for imported transactions that learn from my corrections
weight 2 · round to Mercury BooksFreshBooksnone0/10FreshBooks 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…”
Mercury explicitly states that transactions are 'automatically assigned GL codes based on your categorization history and AI-driven suggestions,' directly supporting the idea of categorization suggestions that improve from past corrections, and Command lets users bulk-adjust GL codes and create rules that presumably feed this history. Mercury's own blog post also candidly notes automation has limits and isn't 'autopilot,' which sets realistic expectations rather than contradicting the feature. Missing for 10: independent/hands-on verification that suggestions specifically adapt after user corrections, and a public API/schema showing the correction-learning mechanism.
- [claimed-docs] “The banking side feeds clean data to any ledger: "Transactions on Mercury are now automatically assigned GL codes based on your categorizati…”
- [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
- [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”
- [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
Reconciliation
accountantReconcile each bank account against the ledger with matched, unmatched, and duplicate transactions surfaced for review
weight 3 · round to Mercury BooksFreshBooks 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…”
Mercury Books claims accounts 'reconcile in real time' automatically with categorization pulled directly from linked banking data (mercury-books-supp-auto-rec, mercury-books-supp-launch), and Mercury's own honest-scope post acknowledges that full automation still requires human review of ambiguous decisions (mercury-books-supp-honest-scope), implying some reconciliation review workflow exists. However, none of the evidence specifically describes a UI or workflow that surfaces matched, unmatched, and duplicate transactions as distinct categories for accountant review — the emphasis is on automation eliminating manual reconciliation work entirely rather than a structured review interface. Missing for 10: explicit documentation of matched/unmatched/duplicate transaction states, a dedicated reconciliation review screen, and independent/hands-on confirmation of this workflow.
- [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
- [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
Bills ap — stories about bills ap in this arenaBills ap
Stories about bills ap in this arena
Bill management
accountantCapture vendor bills, route them for approval, and schedule payments from one workflow
weight 2 · round to FreshBooksFreshBooks 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.”
Evidence only shows that 'bill pay' transactions are pulled into Mercury Books automatically alongside banking and invoicing data, implying some underlying bill-pay capability exists, but there is no description of a capture-to-approval-to-payment-scheduling workflow, approval routing, or scheduled payments within Books itself. missing for 10: vendor bill capture/OCR, approval routing rules, payment scheduling UI, evidence tying bill pay into an AP-specific workflow rather than just a transaction category.
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
Payables
accountantSee accounts payable aging and vendor balances at any point in time
weight 2 · round drawnFreshBooksnone0/10FreshBooks 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.”
Mercury Booksnone0/10Evidence confirms Mercury Books generates P&L, cash flow, and balance sheet reports and mentions 'bill pay' as a data source, but there is no mention of an accounts payable aging report or vendor-balance tracking feature anywhere in the evidence pack. missing for 10: AP aging report, vendor balance report/ledger, point-in-time vendor balance lookups.
- [claimed-docs] “Generate P&L, cash flow, and balance sheet reports from today’s numbers, not last quarter’s.”
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
- [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”
Close collaboration — stories about close collaboration in this arenaClose collaboration
Stories about close collaboration in this arena
Close process
accountantLock closed periods so prior-period numbers cannot change without an explicit reopening
weight 2 · round drawnFreshBooksnone0/10No 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.
accountantRun a month-end close against a checklist that tracks reconciliations, accruals, and review sign-offs
weight 3 · round drawnFreshBooksnone0/10FreshBooks 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…”
Mercury Booksnone0/10Evidence shows continuous automated reconciliation, accrual/cash accounting choice, and accountant collaboration via comments/tagging, but there is no mention of an actual month-end close checklist artifact, accrual entry tracking, or formal review sign-off workflow that an accountant could run through and mark complete. missing for 10: a defined close checklist feature, accrual scheduling/tracking, sign-off/approval workflow tied to close tasks.
- [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
- [claimed-docs] “Accountant collaboration without seat caps: "You can invite your bookkeeper or accountant directly to your Mercury account with permissions …”
- [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”
- [claimed-docs] “The banking side feeds clean data to any ledger: "Transactions on Mercury are now automatically assigned GL codes based on your categorizati…”
Collaboration
founderInvite my external accountant or bookkeeper with role-scoped access to review and adjust the books
weight 3 · round to Mercury BooksFreshBooks 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…”
Mercury Books explicitly supports inviting bookkeepers/accountants in-product with role-tailored permissions and no seat caps, allowing them to view transactions, categorizations, and comment/tag on entries. Missing for 10: no independent/hands-on corroboration of the granularity of role-scoping (e.g., specific permission levels) and no detail on whether accountants can directly adjust vs. only comment.
- [claimed-docs] “Invite your bookkeeper in-product, with unlimited seats at no extra cost.”
- [claimed-docs] “Accountant collaboration without seat caps: "You can invite your bookkeeper or accountant directly to your Mercury account with permissions …”
- [claimed-docs] “The banking side feeds clean data to any ledger: "Transactions on Mercury are now automatically assigned GL codes based on your categorizati…”
Integrations data — stories about integrations data in this arenaIntegrations data
Stories about integrations data in this arena
Data access
developerPull the full general ledger and trial balance through a documented API in open formats
weight 3 · round to FreshBooksFreshBooks 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 …”
Mercury Booksnone0/10The evidence explicitly states a full accounting API is only planned ('Soon, a full accounting API will make every core Books action available programmatically'), and direct probes for OpenAPI/llms.txt docs returned 404s, confirming no current documented API for pulling GL/trial balance data in open formats.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
Integrations
founderConnect my banking, payments, and payroll systems so their activity flows into the ledger automatically
weight 2 · round to Mercury BooksFreshBooks 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…”
Mercury Books explicitly supports linking external bank accounts, cards, and payroll platforms, plus named integrations with Stripe, PayPal, and Gusto, with activity flowing automatically into the ledger via continuous categorization and reconciliation. Mercury itself is candid that this is a strong starting point rather than full autopilot, which tempers but doesn't contradict the core claim. Missing for 10: independent/hands-on verification of these integrations working in practice, and a public API/OpenAPI spec was found to 404, indicating limited programmatic verification.
- [claimed-docs] “Link external bank accounts, cards, payroll platforms, and more for the complete story of your business.”
- [claimed-docs] “Third-party data flows in alongside Mercury's own: Books "connects to a growing set of third-party platforms, including Stripe, PayPal, and …”
- [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
- [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
- [claimed-docs] “Customers with enriched integrations to QuickBooks and NetSuite can now attach Classes to transactions on Mercury.”
Migration
founderMigrate historical books from another accounting system without losing transaction detail
weight 1 · round drawnFreshBooksnone0/10No 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.
Mercury Booksnone0/10No evidence describes an import/migration tool for bringing historical transaction-level data in from QuickBooks/NetSuite or other systems; in fact Mercury explicitly frames Books as a replacement rather than an integration/sync layer for prior accounting systems, and the cited third-party integrations (Stripe, PayPal, Gusto, bank feeds) are for ongoing data flow, not one-time historical migration.
- [claimed-docs] “Does Mercury Books replace QuickBooks? Yes. Mercury Books is a complete accounting system — not an add-on or integration layer for another p…”
- [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”
- [claimed-docs] “Third-party data flows in alongside Mercury's own: Books "connects to a growing set of third-party platforms, including Stripe, PayPal, and …”
Invoicing ar — stories about invoicing ar in this arenaInvoicing ar
Stories about invoicing ar in this arena
Invoicing
founderCreate and send invoices with online payment options and see when they are viewed and paid
weight 3 · round to FreshBooksFreshBooks 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, …”
Mercury Booksnone0/10Evidence only mentions 'invoicing' as one of many transaction types Mercury Books pulls in automatically (alongside banking, bill pay); there is no evidence of invoice creation/sending, online payment collection, or view/paid status tracking within Mercury Books itself.
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
- [claimed-docs] “Third-party data flows in alongside Mercury's own: Books "connects to a growing set of third-party platforms, including Stripe, PayPal, and …”
founderSet up recurring invoices and automatic payment reminders for overdue customers
weight 2 · round drawnFreshBooksnone0/10The 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.
Mercury Booksnone0/10The evidence pack mentions invoicing only as one data stream feeding into books (transactions across 'banking, invoicing, bill pay'), but there is no mention of recurring invoice scheduling or automated overdue payment reminders anywhere in the docs. This is a fair capability for a full accounting system to offer, so absence of evidence is 'none' rather than 'na'.
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
- [claimed-docs] “Link external bank accounts, cards, payroll platforms, and more for the complete story of your business.”
Receivables
accountantTrack accounts receivable with aging reports and per-customer balances
weight 2 · round to FreshBooksFreshBooks 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”
Mercury Booksnone0/10Mercury Books documents P&L, cash flow, and balance sheet reports and mentions invoicing as one of the pulled-in transaction types, but no evidence describes accounts-receivable aging reports or per-customer balance tracking specifically. missing for 10: AR aging report feature, per-customer balance view, any invoicing/AR-specific reporting documentation.
- [claimed-docs] “Generate P&L, cash flow, and balance sheet reports from today’s numbers, not last quarter’s.”
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
- [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”
Ledger coa — stories about ledger coa in this arenaLedger coa
Stories about ledger coa in this arena
Ai ledger
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 FreshBooksFreshBooks' 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, …”
Mercury Booksnone0/10The only mention of a programmatic API and MCP layer for agents is explicitly framed as a future roadmap item ('Soon, a full accounting API... will let AI agents handle bookkeeping tasks end-to-end'), not a shipped capability, and probes confirm no live OpenAPI/MCP endpoints exist today (404s on all candidate paths). While Command can draft journal entries via chat and accountants can be invited to collaborate, there is no evidence of an API-driven posting workflow or a formal 'review queue' gating agent-drafted entries for accountant approval.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [claimed-docs] “Accountant collaboration without seat caps: "You can invite your bookkeeper or accountant directly to your Mercury account with permissions …”
Chart of accounts
accountantCustomize the chart of accounts with account types, sub-accounts, and class or tag dimensions
weight 3 · round to Mercury BooksFreshBooks 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…”
Evidence shows GL code assignment, bulk categorization rules, and Class/tag attachment to transactions (via enriched QuickBooks/NetSuite integrations), plus Command's ability to help 'organize your chart of accounts' — indicating some COA customization exists. However there's no explicit documentation of defining account types or creating sub-accounts within the ledger structure itself. missing for 10: explicit account-type configuration, sub-account creation/hierarchy, and native (non-integration) class/tag dimension setup.
- [claimed-docs] “Use Mercury Command to bulk assign GL codes, create categorization rules, and more”
- [claimed-docs] “Customers with enriched integrations to QuickBooks and NetSuite can now attach Classes to transactions on Mercury.”
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [claimed-docs] “The banking side feeds clean data to any ledger: "Transactions on Mercury are now automatically assigned GL codes based on your categorizati…”
Journal entries
accountantPost manual journal entries with balanced debits, credits, and supporting memos
weight 3 · round to FreshBooksFreshBooks 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”
Books is confirmed as a double-entry accounting system with journal entries as a core capability ("writing journal entries" is explicitly listed as a task Command can help with), implying balanced debit/credit posting, but there's no direct documentation of a manual journal-entry UI, memo/note fields, or debit=credit validation for accountant-initiated entries — most journal entry evidence frames it as an AI-assisted/automated task rather than manual accountant entry. Missing for 10: explicit manual entry screen documentation, memo/attachment support on journal entries, and confirmation of balance validation.
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
Multi entity audit — stories about multi entity audit in this arenaMulti entity audit
Stories about multi entity audit in this arena
Ai audit
ai-native userHave an agent monitor the ledger and flag anomalies in spend or duplicate transactions before the close
weight 3 · round drawnFreshBooksnone0/10FreshBooks 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…”
Mercury Booksnone0/10Evidence shows Command can answer questions and bulk-categorize/reconcile transactions, and an MCP layer for agents is only promised as 'soon,' but nothing describes proactive anomaly detection, duplicate-transaction flagging, or pre-close audit alerts.
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
- [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
Audit trail
accountantSee a complete audit trail of who changed what and when across the entire ledger
weight 3 · round drawnFreshBooksnone0/10No 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'.
Mercury Booksnone0/10No evidence describes an audit trail, change log, user attribution, or history of edits across the ledger; the pack focuses on automation, categorization, reporting, and accountant seat invites, none of which document who-changed-what-when tracking. This is a plausible and expected feature for a full accounting system, so absence of evidence yields 'none' rather than 'na'.
Multi entity
accountantManage multiple legal entities and produce consolidated financials across them
weight 2 · round drawnFreshBooksnone0/10FreshBooks 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…”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to FreshBooksFreshBooks 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…”
Mercury Booksnone0/10Mercury's own docs say a full accounting API is coming 'soon' — it does not exist yet — and probes for llms.txt/openapi specs both return 404, confirming no current API parity with the UI.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to FreshBooksFreshBooks 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”
Mercury Booksnone0/10No evidence pack item mentions any data export feature, open format (CSV/OFX/JSON) download, or account-closure data portability path; the only related probes (llms.txt, openapi.json) return 404s, and Mercury explicitly positions Books as a replacement system rather than an interoperable one ('not an add-on or integration layer for another platform').
- [claimed-docs] “Does Mercury Books replace QuickBooks? Yes. Mercury Books is a complete accounting system — not an add-on or integration layer for another p…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnFreshBooksnone0/10No 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.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnFreshBooksnone0/10No 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.
Mercury Booksnone0/10The evidence pack contains no mention of data-training opt-outs, AI model training policies, or privacy controls specific to preventing customer data from being used to train AI models; Mercury Books' AI features (Command) are described functionally but with no privacy-posture documentation on this axis. Missing for 10: any privacy policy language, opt-out mechanism, or documentation addressing whether user financial data is used to train AI models.
ai-native userControl data retention and deletion
weight 2 · round drawnFreshBooksnone0/10No 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.
Mercury Booksnone0/10The evidence pack contains no mention of data retention policies, deletion controls, export/purge mechanisms, or any privacy-posture settings a user could control; it focuses entirely on accounting features, AI assistant capabilities, and pricing. This is a fair axis for a financial SaaS product handling sensitive business data, but no supporting evidence exists.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnFreshBooksnone0/10No 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.
Mercury Booksnone0/10No evidence anywhere in the pack mentions telemetry, usage tracking, data collection settings, or opt-out controls; the material focuses entirely on accounting features, AI assistant capabilities, and pricing. This is a fair privacy-posture question for any SaaS product, so absence of evidence yields 'none' rather than 'na'.
Reporting statements — stories about reporting statements in this arenaReporting statements
Stories about reporting statements in this arena
Ai insights
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 FreshBooksFreshBooks 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”
Mercury Booksnone0/10Mercury's own docs frame the accounting API and MCP layer for external agents as a future ('Soon') capability, not something shipped today, and direct probes for an OpenAPI spec or llms.txt on Mercury's docs return 404s, indicating no live API for third-party agents yet. The only grounded Q&A shown (Command) is an in-product assistant, not an externally callable API an outside agent could query.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
- [claimed-docs] “The built-in AI assistant is Command: "Ask Command anything about your finances — spend, trends, GL codes — and get immediate answers ground…”
Custom reports
accountantBuild custom reports filtered and grouped by class, location, or tag dimensions
weight 2 · round drawnFreshBooksnone0/10FreshBooks' 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”
Mercury Booksnone0/10Evidence shows Mercury Books generates standard P&L, cash flow, and balance sheet reports, and mentions attaching 'Classes' to transactions only for customers with enriched QuickBooks/NetSuite integrations — not a native custom report builder. No evidence of location or tag dimensions, or of building custom reports filtered/grouped by these dimensions within Books itself.
- [claimed-docs] “Generate P&L, cash flow, and balance sheet reports from today’s numbers, not last quarter’s.”
- [claimed-docs] “Customers with enriched integrations to QuickBooks and NetSuite can now attach Classes to transactions on Mercury.”
Statements
founderGenerate an accurate P&L, balance sheet, and cash-flow statement for any period on demand
weight 3 · round to Mercury BooksFreshBooks 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…”
Mercury Books explicitly generates P&L, cash-flow, and balance-sheet reports on demand from real-time reconciled data, with cash/accrual choice, positioned as a full double-entry replacement for QuickBooks. This is a core advertised feature with detailed first-party docs, though there's no independent/hands-on corroboration of report accuracy and Mercury itself cautions that automation isn't fully hands-off. Missing for 10: independent verification of statement accuracy, and confirmation that reports are audit-grade/error-free in practice.
- [claimed-docs] “Generate P&L, cash flow, and balance sheet reports from today’s numbers, not last quarter’s.”
- [claimed-docs] “Mercury Books is "Double-entry accounting that pulls directly from your Mercury data", generating "P&L, cash flow, and balance sheet reports…”
- [claimed-docs] “From the launch post: "All your transactions across banking, invoicing, bill pay, and more are pulled in automatically as you build your bus…”
- [claimed-docs] “Reconciliation and categorization are automatic and continuous: "Data across banking, cards, invoicing, and more are categorized automatical…”
- [claimed-docs] “Mercury's own honest framing of automation limits: "a 'connected' system isn't the same as fully automated. Bank-connected bookkeeping can e…”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableFreshBooksn/aFreshBooks is an accounting/invoicing SaaS product, not an AI agent; the evidence shows only a traditional REST API/SDK/webhooks, with no mention of MCP server support for plugging into AI tools. The story concerns MCP client capability which is not a fair axis for this kind of product beyond having an API (which itself is not MCP), so this falls outside category expectations rather than being a failed capability.
- [claimed-docs] “Authentication - FreshBooks”
- [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.”
Mercury Booksnone0/10The only MCP-related evidence is a forward-looking statement that an MCP layer is coming 'soon' to let external agents call Mercury Books' own actions — this describes Mercury exposing an MCP server, not the product consuming external MCP servers' tools, and it is explicitly not yet shipped (confirmed by 404 probes for API/openapi endpoints). There is no evidence users can plug third-party MCP servers into Mercury Books today.
- [claimed-docs] “Soon, a full accounting API will make every core Books action available programmatically, and an MCP layer will let AI agents handle bookkee…”
- [probe] “PROBE llms.txt: HTTP 404 at https://support.mercury.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://support.mercury.com/openapi.json, https://support.mercury.com/swagger.json, https://support.…”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableFreshBooksn/aFreshBooks is an invoicing/accounting SaaS product, not an automation-building platform with version control, review, and rollback of workflows/automations; the evidence pack shows API/webhook integration features but no concept of automation versioning or rollback, and this is not a fair axis for this kind of product.
Mercury Booksnone0/10Evidence shows Mercury Books has automation features (Command AI assistant, categorization rules, bulk GL code assignment) but nothing about versioning automation rules, reviewing changes, or rolling back automated actions/decisions. No audit trail, undo, or history/version-control feature is mentioned anywhere in the pack.
ai-native userRead the product's source under an open license
weight 2 · not comparableFreshBooksn/aFreshBooks is closed-source commercial SaaS accounting software; source-code openness is not a category-relevant axis for this type of product, unlike an SDK/API being available.
ai-native userSelf-host the core product
weight 3 · not comparableFreshBooksn/aFreshBooks is a proprietary SaaS accounting product with no self-hosted or open-source distribution; self-hosting is not a coherent axis for this category of hosted commercial software.