JPMorgan won't let outside AI agents run customer accounts. Here's what a sub's AP and billing staff should not hand to an agent
On its Oct. 13 earnings call, JPMorgan said it won't let outside AI agents operate customer accounts, and that customers who share logins carry the liability. For contractors, that is a clear rule for bank portals, payables and pay-app work.
JPMorgan Chase says outside AI agents may not operate customer accounts, and that a customer who hands an agent their login is on the hook for what it does. If you run billing or payables for a sub or GC, the practical rule is the same one: let AI read and draft, but don't give it your bank credentials.
What did JPMorgan actually say?
On its third-quarter earnings call on Oct. 13, CEO Jamie Dimon said the bank is "not going to allow just any ... outside agent to come in inside the company, because it's just too risky for clients and for JPMorgan," according to coverage by Cybernews and PYMNTS. A spokeswoman said the bank does not let third parties get a customer's banking credentials and log in on the customer's behalf.
The reported details:
| Question | What the coverage says |
|---|---|
| Can an outside agent log in as the customer? | No |
| Can it see balances? | Some read-only data, through authorized connectors such as Plaid |
| Can it send money or pay bills? | No |
| Who is liable if a customer shares a login and the agent misbehaves? | The customer ("a liability transfer," per Dimon) |
| Is there a timeline for allowing direct agent access? | None given |
The outlets disagree on small details, and the original earnings-call transcript wasn't available to confirm wording. The core points above were consistent across Cybernews, Crypto Briefing and Let's Data Science.
Why should a contractor care about a bank's retail policy?
Because the coverage describes customer accounts generally, and the direction is clear: banks will treat "an agent logged in as you" as you. That matters in construction, where one person often holds the keys to a lot of money movement:
- Operating and payroll accounts with online access held by an owner or office manager.
- Progress payments to subs and suppliers, often released against lien waivers.
- Vendor payment portals and ACH setups, where a changed bank account number is the classic fraud.
Nothing in the reporting says JPMorgan's treasury services for businesses work the same way. Ask your own bank. But a bank that won't accept "my software did it" for retail is unlikely to be more forgiving when a $180,000 progress payment goes to the wrong account.
What should AP and billing staff keep away from an agent?
A workable split for a mid-size sub or GC:
Fine to hand to AI, with review
- Reading invoices and matching them to POs, change orders and the schedule of values.
- Drafting pay applications and lien waiver packets for a person to check.
- Flagging mismatches: a vendor name that doesn't match the W-9, a bill above the committed amount, a missing conditional waiver.
- Summarizing aging reports and retainage balances.
Keep with a named person
- Logging into bank or treasury portals. Don't paste credentials into an agent or browser tool.
- Releasing payments and approving wires.
- Changing vendor bank details. Confirm by calling a known number, not an email.
- Signing waivers and certifications.
Should a small contractor change anything this week?
Likely three things, none expensive:
- List who has bank-portal access and whether any AI tool, browser extension or "computer use" agent has ever been logged in under those accounts.
- Read your online banking agreement for the sentence on shared credentials and unauthorized transactions. JPMorgan's stance suggests other banks may land in the same place.
- Use read-only connections (reports, exports) for AI analysis, rather than a live login.
What's still unclear?
JPMorgan gave no timeline for a safe way to let agents act on accounts, and it is piloting its own cash-management tool for customers. Other banks haven't been shown to follow the same policy; a search for similar Citi or Bank of America announcements turned up nothing. Treat this as one large bank's signal, not an industry rule.
The takeaway for your office: use AI to prepare payments, not to push them. The person who releases the money should still be a person you can name.
- Did JPMorgan ban AI agents from bank accounts?
- JPMorgan said it won't let outside AI agents operate customer accounts by logging in with a customer's banking credentials. Outside agents can still see some data, such as balances, through authorized connectors like Plaid, but cannot move money or pay bills. The bank's own internal AI use is not covered by the policy.
- Who is liable if an AI agent with my bank login makes a bad payment?
- According to coverage of JPMorgan's Oct. 13 comments, the bank's position is that a customer who gives an agent their login carries the liability for what it does. Check your own bank's online banking agreement, since terms differ by institution.
- Can a contractor still use AI for accounts payable?
- Yes, with limits. Use AI for reading invoices, matching them to POs and drafting lien waiver or pay-app paperwork, and keep payment release and bank-portal logins with a named person.
- Does JPMorgan's policy apply to business or treasury accounts?
- The reporting describes the policy in terms of customer and retail accounts. Commercial treasury terms were not detailed in the coverage, so ask your bank's treasury contact what it allows.