On November 5, Anthropic rolled out Personal Finance in Claude: connect your bank and card accounts through Plaid and ask questions in plain English. The consumer press covered it as a budgeting tool. For a business owner, it's something else entirely — a read-only AI agent that can see up to two years of your transactions. That makes the connection decision a vendor-access question, not a feature announcement.
The good news is that Anthropic published an unusually detailed scoped-visibility contract — what it sees, what it doesn't, and where the data goes. That contract is itself a template for how to evaluate any AI tool that asks to touch your financial data.
What Claude Actually Sees (And What It Doesn't)
Per Anthropic's own announcement and help documentation, here's the exact scope:
- For only the accounts you choose to connect: bank name, account name and type, last four digits, balances, credit limits, and up to two years of transactions.
- What it cannot see: your bank password (you sign in through Plaid yourself; Claude never handles credentials).
- What it cannot do: move, manage, or invest money. Access is read-only by design.
- Training use: conversations inside the Personal Finance hub are not used to train Anthropic's models. Conversations outside the hub follow your existing privacy settings.
- Revocation: you can unlink an account anytime, and Claude immediately loses access.
That level of specificity is rare. Most AI tools that touch financial data bury their access scope in a Terms of Service link. Anthropic's explicit list gives you a model for what to demand from every vendor.
The Business Owner's Pre-Connect Checklist
Consumer advice says "connect your accounts and track spending." A business owner should run a tighter protocol:
1. Pick the Right Account
Connect a dedicated operating account — the one that receives customer payments and pays routine vendors. Do not connect the account that holds payroll tax withholdings, your line of credit, or any account tied to sensitive regulatory reporting. If you don't have a clean operating account, open one before connecting anything.
Why: limiting scope is the cheapest security control. The narrower the account's contents, the smaller the blast radius if the access model ever changes or gets misconfigured.
2. Ask the Three Questions That Matter
Before connecting, write down what you'll actually ask. Consumer users ask "Where did my money go?" Business owners should ask:
- Cash-flow pattern by client or season: "Show me deposits by source for the last 90 days." This tells you which revenue streams are stable and which are lumpy — information you already have in QuickBooks or your bank portal, but Claude can surface it faster if the pattern is buried across statements.
- Subscription and recurring charge sprawl: "List every recurring charge and when it last changed amount." Many small businesses accumulate SaaS subscriptions on a card and lose track. Two years of transaction history is enough to catch annual renewals you forgot about.
- Receivables aging signal: "Flag any deposit that looks like a late customer payment based on past patterns." This is approximate — Claude can spot deviations, not run a formal aging report — but it can surface the conversation you need to have with your bookkeeper.
Write these questions down before connecting. If you can't articulate a specific question, you don't need the connection yet.
3. Draw the Boundary Before You Grant Access
Read-only analysis is one thing. Automation is another. Set this rule in writing before the first connection:
Claude (or any AI tool with bank access) may read and summarize. It may never initiate a transfer, approve a payment, or change an account setting without a human in the loop.
This boundary matters because the feature set will expand. Anthropic has already launched Claude for Financial Services and is exploring integrations with wealth managers. Today's read-only tool is tomorrow's semi-automated assistant. The boundary you write now becomes the standard you hold future versions to.
Use Anthropic's Contract as Your Vendor Template
The next AI tool that asks for your financial data probably won't publish an access scope this clearly. Demand one anyway. For any vendor, ask four questions:
- What categories of data does it touch? (Not "financial data" — which fields, which accounts, which time window.)
- What are your compliance constraints? (PCI, SOC 2, provincial privacy laws — know which ones apply to your industry.)
- What's the revocation path? (Can you unlink instantly? Does the vendor retain transaction history after unlinking?)
- Can you test with non-sensitive data first? (Run the tool on a test account or a sample file before connecting real customer money.)
Anthropic happened to answer these proactively. Most vendors won't. That doesn't mean you skip them.
Honest Boundaries
- This is US-only and beta. Personal Finance is rolling out to Pro, Max, and Ultra plans in the United States. If you're outside the US or on a lower-tier plan, you can't access it yet — and the scope may change before wider release.
- Claude can make mistakes. Anthropic says so explicitly. Check important figures against your bank's own records. An AI summary is a starting point, not an audit.
- Read-only access today is not a guarantee. Terms change. The safest habit is to review which accounts are connected quarterly, just like you review subscription bills.
- This is not investment advice. The tool is designed for spending understanding, not portfolio management. Don't ask it to evaluate investment decisions.
The Bottom Line
Connecting an AI to your bank account is becoming normal. The businesses that do it well won't be the ones with the most accounts linked — they'll be the ones with the narrowest scope, the clearest questions, and a written boundary before the first login.
If you're not sure what AI tools already touch your financial data — or which ones your team connected without telling you — that's a larger problem than any single feature launch. The AI Clarity Sprint maps every AI touchpoint in your business, including the shadow connections that never went through procurement. Two weeks, one fixed fee, and you end with a plan instead of another platform subscription.
Top comments (0)