Access
Try itExperimental
See what an agent can do with BILL Spend & Expense before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://gateway.prod.bill.com/connect/v3/spend/budgets # the documented v3 spend API, keyless → Unauthorizedrecorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Accounting close — stories about accounting close in this arenaAccounting closeevidence →
Stories about accounting close in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai automation — stories about ai automation in this arenaAi automationevidence →
Stories about ai automation in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Bills ap — stories about bills ap in this arenaBills apevidence →
Stories about bills ap in this arena
Cards controls — stories about cards controls in this arenaCards controlsevidence →
Stories about cards controls in this arena
Expense data access — stories about expense data access in this arenaExpense data accessevidence →
Stories about expense data access in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Policy approvals — stories about policy approvals in this arenaPolicy approvalsevidence →
Stories about policy approvals in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Receipts capture — stories about receipts capture in this arenaReceipts captureevidence →
Stories about receipts capture in this arena
Reimbursements — stories about reimbursements in this arenaReimbursementsevidence →
Stories about reimbursements in this arena
Spend visibility — stories about spend visibility in this arenaSpend visibilityevidence →
Stories about spend visibility in this arena
Travel — stories about travel in this arenaTravelevidence →
Stories about travel in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where BILL Spend & Expense stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Accounting close — stories about accounting close in this arenaAccounting close
Stories about accounting close in this arena
Transactions sync to QuickBooks, NetSuite, or Xero with GL account, class, and department mappings I control
~6/10
Spend is coded as it happens — merchant, category, memo, receipt — so month-end close is a review, not an archaeology dig
~6/10
Run multiple legal entities and currencies in one account with consolidated reporting and per-entity books
—–
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Scoped API keys · Machine-readable spec · Versioning policy · Official CLI
Subscribe to events via webhooks
✓8/10
Build against official SDKs
✓7/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
~5/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
✓7/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~3/10
unlocks → NL commands · MCP client
Operate the product with natural-language commands
—0/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
~3/10
Set up automations that run autonomously in the background
~5/10
Ai automation — stories about ai automation in this arenaAi automation
Stories about ai automation in this arena
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Automation depth
Define rules that trigger actions automatically on events
~5/10
unlocks → Versioned workflows · An AI assistant enforces policy conversationally — chasing missing receipts, explaining declines, and answering "can I expense this?" before the spend happens
Schedule recurring jobs or workflows
—0/10
Perform bulk operations across many items at once
~3/10
Version, review, and roll back my automations
—–
Bills ap — stories about bills ap in this arenaBills ap
Stories about bills ap in this arena
Cards controls — stories about cards controls in this arenaCards controls
Stories about cards controls in this arena
Restrict cards by category, merchant, and amount — and the platform auto-locks or declines out-of-policy spend at the point of sale
~4/10
Issue physical and virtual corporate cards to the team in minutes, each with its own spend limit
~5/10
Create single-vendor virtual cards for SaaS subscriptions and procurement so one compromised vendor never exposes shared credit
~6/10
Expense data access — stories about expense data access in this arenaExpense data access
Stories about expense data access in this arena
An agent can pull uncoded transactions via API or MCP, propose categorizations and policy flags, and push clean coding back for review
~4/10
Pull transactions, expenses, and receipts through a documented REST API with OAuth and scoped tokens
~6/10
Issue and manage cards programmatically — create a card with a limit, lock it, update controls — via the public API
~4/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Policy approvals — stories about policy approvals in this arenaPolicy approvals
Stories about policy approvals in this arena
Build multi-step approval chains — manager, budget owner, finance — with delegation and escalation when approvers sit on requests
~3/10
Every expense carries a full audit trail — edits, approvals, policy checks — that survives an external audit
~4/10
Codify our expense policy — limits by category, role, and context — so in-policy expenses auto-approve and only exceptions reach a human
~6/10
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Receipts capture — stories about receipts capture in this arenaReceipts capture
Stories about receipts capture in this arena
Log mileage with map-based distance and claim per-diem rates without building the expense by hand
—–
Snap a photo or forward an email and the platform OCRs the receipt and files it against the right transaction
—–
Receipts match to card transactions automatically — with e-receipts pulled from integrations — and I get nudged only when one is genuinely missing
—–
Reimbursements — stories about reimbursements in this arenaReimbursements
Stories about reimbursements in this arena
Spend visibility — stories about spend visibility in this arenaSpend visibility
Stories about spend visibility in this arena
Travel — stories about travel in this arenaTravel
Stories about travel in this arena
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 5/10 | Cclaimed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 3/10 | Cclaimed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | full | 7/10 | Cclaimed | |
Codify our expense policy — limits by category, role, and context — so in-policy expenses auto-approve and only exceptions reach a human C Policy engine | finance lead | Policy approvals — stories about policy approvals in this arenaPolicy approvals | 3 | partial | 6/10 | Cclaimed | |
Pull transactions, expenses, and receipts through a documented REST API with OAuth and scoped tokens C Api access | developer | Expense data access — stories about expense data access in this arenaExpense data access | 3 | partial | 6/10 | Tprobed | |
Transactions sync to QuickBooks, NetSuite, or Xero with GL account, class, and department mappings I control C Accounting sync | finance lead | Accounting close — stories about accounting close in this arenaAccounting close | 3 | partial | 6/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 5/10 | Cclaimed | |
Issue physical and virtual corporate cards to the team in minutes, each with its own spend limit C Card issuance | founder | Cards controls — stories about cards controls in this arenaCards controls | 3 | partial | 5/10 | Cclaimed | |
See company spend in real time — by team, category, and merchant — the day it happens, not when statements land C Dashboards | founder | Spend visibility — stories about spend visibility in this arenaSpend visibility | 3 | partial | 5/10 | Cclaimed | |
An agent can pull uncoded transactions via API or MCP, propose categorizations and policy flags, and push clean coding back for review C Agent access | ai-native user | Expense data access — stories about expense data access in this arenaExpense data access | 3 | partial | 4/10 | Cclaimed | |
Restrict cards by category, merchant, and amount — and the platform auto-locks or declines out-of-policy spend at the point of sale C Card controls | finance lead | Cards controls — stories about cards controls in this arenaCards controls | 3 | partial | 4/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 3/10 | Cclaimed | |
Submit an out-of-pocket expense and get reimbursed by direct deposit in days, tracked from submission to payout C Domestic | employee | Reimbursements — stories about reimbursements in this arenaReimbursements | 3 | partial | 3/10 | Cclaimed | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
Snap a photo or forward an email and the platform OCRs the receipt and files it against the right transaction C Receipt capture | employee | Receipts capture — stories about receipts capture in this arenaReceipts capture | 3 | none | untested | none yet | |
Allocate budgets to teams and projects and have card limits and approvals actually enforce them C Budgets | finance lead | Spend visibility — stories about spend visibility in this arenaSpend visibility | 2 | partial | 7/10 | Cclaimed | |
Create single-vendor virtual cards for SaaS subscriptions and procurement so one compromised vendor never exposes shared credit C Virtual cards | finance lead | Cards controls — stories about cards controls in this arenaCards controls | 2 | partial | 6/10 | Cclaimed | |
Spend is coded as it happens — merchant, category, memo, receipt — so month-end close is a review, not an archaeology dig C Close | finance lead | Accounting close — stories about accounting close in this arenaAccounting close | 2 | partial | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
Run accounts payable in the same platform — capture invoices, route approvals, and pay vendors by ACH, check, or wire C Bill pay | finance lead | Bills ap — stories about bills ap in this arenaBills ap | 2 | partial | 5/10 | Cclaimed | |
AI codes and audits expenses for me — reading receipts, suggesting categories and memos, and catching duplicates or fraud C Ai coding | ai-native user | Ai automation — stories about ai automation in this arenaAi automation | 2 | partial | 4/10 | Cclaimed | |
Every expense carries a full audit trail — edits, approvals, policy checks — that survives an external audit C Audit trail | finance lead | Policy approvals — stories about policy approvals in this arenaPolicy approvals | 2 | partial | 4/10 | Cclaimed | |
Issue and manage cards programmatically — create a card with a limit, lock it, update controls — via the public API C Card api | developer | Expense data access — stories about expense data access in this arenaExpense data access | 2 | partial | 4/10 | Cclaimed | |
Build multi-step approval chains — manager, budget owner, finance — with delegation and escalation when approvers sit on requests C Approvals | finance lead | Policy approvals — stories about policy approvals in this arenaPolicy approvals | 2 | partial | 3/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 3/10 | Cclaimed | |
An AI assistant enforces policy conversationally — chasing missing receipts, explaining declines, and answering "can I expense this?" before the spend happens C Ai policy | ai-native user | Ai automation — stories about ai automation in this arenaAi automation | 2 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Book flights and hotels in-platform with travel policy applied at booking time, not expensed and argued about later C Booking | employee | Travel — stories about travel in this arenaTravel | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Log mileage with map-based distance and claim per-diem rates without building the expense by hand C Mileage perdiem | employee | Receipts capture — stories about receipts capture in this arenaReceipts capture | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
Receipts match to card transactions automatically — with e-receipts pulled from integrations — and I get nudged only when one is genuinely missing C Receipt matching | employee | Receipts capture — stories about receipts capture in this arenaReceipts capture | 2 | none | untested | none yet | |
Reimburse employees abroad in their local currency without running a separate international payments process C International | finance lead | Reimbursements — stories about reimbursements in this arenaReimbursements | 2 | none | untested | none yet | |
Run multiple legal entities and currencies in one account with consolidated reporting and per-entity books C Multi entity | finance lead | Accounting close — stories about accounting close in this arenaAccounting close | 2 | none | untested | none yet | |
A trip's expenses — bookings, cards, receipts — collect themselves into one itinerary-linked report C Trip expenses | employee | Travel — stories about travel in this arenaTravel | 1 | none | 0/10 | ||
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 46 stories with headroom
What would move BILL Spend & Expense’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
The evidence only shows BILL publishing an MCP server that exposes its own API documentation to external AI tools (server role), not any capability for BILL Spend & Expense itself to consume/plug in external MCP servers to extend its own agentic features (client role).
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
partialq3/10moves Built-in AIimpact 31.5
Missing: evidence of a user-facing chat/assistant interface, examples of delegating varied tasks (not just bill coding), and independent confirmation of how the agent is invoked or controlled.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
No evidence in the pack addresses AI training data opt-out or any privacy controls regarding AI model training; the pack only covers API, webhooks, and product features unrelated to this axis.
Receipts capture — stories about receipts capture in this arenaSnap a photo or forward an email and the platform OCRs the receipt and files it against the right transaction
nonemoves PA Scoreimpact 30
The evidence pack covers APIs, webhooks, vendor network, accounting sync, and AI bill coding, but contains no mention of receipt photo capture, email-forward ingestion, or OCR matching to transactions for the Spend & Expense product.
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
Evidence shows only a documentation MCP server for developers (docs-18) and an AI-based invoice coding agent, neither of which lets an end user operate the product itself via natural-language commands (e.g., 'pay this vendor' or 'approve this expense' via chat).
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
The evidence pack details a REST API, webhooks, UI Elements SDK, and an MCP server for documentation access, but nowhere mentions an official CLI tool for interacting with BILL Spend & Expense.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Missing: any mention of API key scopes, granular permission levels, or agent-specific credential issuance mechanisms.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
Evidence confirms BILL has API docs, a sandbox test environment, and an MCP server for AI tools to query documentation, but nothing describes an interactive API reference with runnable/try-it-out examples; a probe for standard OpenAPI/Swagger specs returned 404s across all checked paths, suggesting no such interactive reference is exposed.
Showing the top 8 of 46 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 30 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs22 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Build against official SDKs
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Run accounts payable in the same platform — capture invoices, route approvals, and pay vendors by ACH, check, or wire
- Restrict cards by category, merchant, and amount — and the platform auto-locks or declines out-of-policy spend at the point of sale
- Issue physical and virtual corporate cards to the team in minutes, each with its own spend limit
- Create single-vendor virtual cards for SaaS subscriptions and procurement so one compromised vendor never exposes shared credit
- An agent can pull uncoded transactions via API or MCP, propose categorizations and policy flags, and push clean coding back for review
- Pull transactions, expenses, and receipts through a documented REST API with OAuth and scoped tokens
- Issue and manage cards programmatically — create a card with a limit, lock it, update controls — via the public API
- Do everything through the API that I can do in the UI
- Every expense carries a full audit trail — edits, approvals, policy checks — that survives an external audit
- Submit an out-of-pocket expense and get reimbursed by direct deposit in days, tracked from submission to payout
- Allocate budgets to teams and projects and have card limits and approvals actually enforce them
- See company spend in real time — by team, category, and merchant — the day it happens, not when statements land
Pricing docs14 stories
- Transactions sync to QuickBooks, NetSuite, or Xero with GL account, class, and department mappings I control
- Spend is coded as it happens — merchant, category, memo, receipt — so month-end close is a review, not an archaeology dig
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- AI codes and audits expenses for me — reading receipts, suggesting categories and memos, and catching duplicates or fraud
- Define rules that trigger actions automatically on events
- Run accounts payable in the same platform — capture invoices, route approvals, and pay vendors by ACH, check, or wire
- An agent can pull uncoded transactions via API or MCP, propose categorizations and policy flags, and push clean coding back for review
- Export all of my data in open formats and leave
- Build multi-step approval chains — manager, budget owner, finance — with delegation and escalation when approvers sit on requests
- Every expense carries a full audit trail — edits, approvals, policy checks — that survives an external audit
- Codify our expense policy — limits by category, role, and context — so in-policy expenses auto-approve and only exceptions reach a human
- Allocate budgets to teams and projects and have card limits and approvals actually enforce them
Product docs13 stories
- Spend is coded as it happens — merchant, category, memo, receipt — so month-end close is a review, not an archaeology dig
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- AI codes and audits expenses for me — reading receipts, suggesting categories and memos, and catching duplicates or fraud
- Restrict cards by category, merchant, and amount — and the platform auto-locks or declines out-of-policy spend at the point of sale
- Issue physical and virtual corporate cards to the team in minutes, each with its own spend limit
- Create single-vendor virtual cards for SaaS subscriptions and procurement so one compromised vendor never exposes shared credit
- Issue and manage cards programmatically — create a card with a limit, lock it, update controls — via the public API
- Every expense carries a full audit trail — edits, approvals, policy checks — that survives an external audit
- Codify our expense policy — limits by category, role, and context — so in-policy expenses auto-approve and only exceptions reach a human
- Allocate budgets to teams and projects and have card limits and approvals actually enforce them
- See company spend in real time — by team, category, and merchant — the day it happens, not when statements land
developer.bill.com12 stories
- Transactions sync to QuickBooks, NetSuite, or Xero with GL account, class, and department mappings I control
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Subscribe to events via webhooks
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Run accounts payable in the same platform — capture invoices, route approvals, and pay vendors by ACH, check, or wire
- Pull transactions, expenses, and receipts through a documented REST API with OAuth and scoped tokens
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Allocate budgets to teams and projects and have card limits and approvals actually enforce them
OpenAPI spec4 stories
llms.txt3 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://gateway.prod.bill.com/connect/v3/spend/budgets # the documented v3 spend API, keyless → Unauthorizedreproduced$ curl -s https://gateway.prod.bill.com/connect/v3/spend/budgets # the documented v3 spend API, [redacted]less → Unauthorized
{"message":"Unauthorized"}
$curl -sL https://developer.bill.com/llms.txt | head -4reproduced$ curl -sL https://developer.bill.com/llms.txt | head -4 # BILL API documentation Documentation > Discover how to leverage the BILL API features in your integrations
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
1 of 9 testable claims verified · 0 contradicted → integrity 11/100
12 distinct capability claims found in BILL Spend & Expense’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
1
Verified
8
Unverified
0
Contradicted
21
Undersold
Verified (1)
“Full BILL v3 API covering AP, AR, and Spend & Expense platform”
Drive the product through a documented public APIfullproof ↗
Unverified (9)
“Real-time event notifications via webhooks for AP, AR, and S&E events”
“API access to build card/expense management: budgets, users, virtual cards, transactions and reimbursements”
Issue and manage cards programmatically — create a card with a limit, lock it, update controls — via the public APIpartialproof ↗
“Automatic vendor network matching connects your vendors for faster, secure payments across 4M+ vendors”
Run accounts payable in the same platform — capture invoices, route approvals, and pay vendors by ACH, check, or wirepartialproof ↗
“Custom, configurable approval policies for spend and payments”
Build multi-step approval chains — manager, budget owner, finance — with delegation and escalation when approvers sit on requestspartialproof ↗
“AI-powered Invoice Coding Agent automatically codes multi-line bills”
AI codes and audits expenses for me — reading receipts, suggesting categories and memos, and catching duplicates or fraudpartialproof ↗
“Smart cards paired with AI-powered spend management auto-categorize and enforce compliance on every transaction”
Restrict cards by category, merchant, and amount — and the platform auto-locks or declines out-of-policy spend at the point of salepartialproof ↗
“Create purchase requests and purchase orders with tolerance rules and 2-way matching for procurement”
Run accounts payable in the same platform — capture invoices, route approvals, and pay vendors by ACH, check, or wirepartialproof ↗
“Automatic two-way sync with QuickBooks Enterprise, NetSuite, Sage Intacct, Microsoft Dynamics, and more”
Transactions sync to QuickBooks, NetSuite, or Xero with GL account, class, and department mappings I controlpartialproof ↗
“Manual accounting integration via CSV file import/export”
Export all of my data in open formats and leavepartialproof ↗
Undersold (21)
Spend is coded as it happens — merchant, category, memo, receipt — so month-end close is a review, not an archaeology digpartialproof ↗
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
Test against a sandbox environment without touching production datafullproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Issue physical and virtual corporate cards to the team in minutes, each with its own spend limitpartialproof ↗
Create single-vendor virtual cards for SaaS subscriptions and procurement so one compromised vendor never exposes shared creditpartialproof ↗
An agent can pull uncoded transactions via API or MCP, propose categorizations and policy flags, and push clean coding back for reviewpartialproof ↗
Pull transactions, expenses, and receipts through a documented REST API with OAuth and scoped tokenspartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Every expense carries a full audit trail — edits, approvals, policy checks — that survives an external auditpartialproof ↗
Codify our expense policy — limits by category, role, and context — so in-policy expenses auto-approve and only exceptions reach a humanpartialproof ↗
Submit an out-of-pocket expense and get reimbursed by direct deposit in days, tracked from submission to payoutpartialproof ↗
Allocate budgets to teams and projects and have card limits and approvals actually enforce thempartialproof ↗
See company spend in real time — by team, category, and merchant — the day it happens, not when statements landpartialproof ↗
Claims outside our story set (2)
Real capability claims found in BILL Spend & Expense’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“API to build and manage organization structure within BILL”
source ↗“Embeddable UI theme (Elements) with configurable navigation for custom app integration”
source ↗
Business model
Corporate cards plus expense software, historically interchange-funded; pricing is demo-gated — 'based on your business needs and the number of users'.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
