BankSync
Multi-client bank feeds

One dashboard for every client's bank data.

Stop juggling separate client accounts. With BankSync, each client connects their own bank, stays fully isolated, and rolls up into a single view, and a single AI agent. Built for accountants, bookkeepers, advisors, and tax preparers.

Start your free trialSee how Client Portals work
No credential sharingRegulated open bankingOne subscription

Every client connects their own bank; it all rolls up to you.

The short version

Multi-client bank feeds let one firm collect transactions, balances, and account data from many clients at once. Each client connects their own bank through regulated open banking, every client stays isolated, and the whole book rolls up into a single dashboard, and a single AI agent.

Switching between accounts isn't aggregating them.

Most tools give you “sub-accounts”: separate logins you flip between one at a time. BankSync rolls every client into one place. That difference changes what you can actually do.

Sub-accounts: switch one at a time
Client Aviewing
Client Blog out to view
Client Clog out to view

You can only ever see one client at a time. Cross-client questions mean exporting from each, by hand.

BankSync: all clients, one view
Client A4 banks
Client B2 banks
Client C3 banks

Every client rolls up into one dashboard with a portal chip. Filter, drill in, or query the whole book with one AI agent.

Job to be doneSub-accounts (switching)BankSync (aggregating)
See every client at onceSwitch between separate accounts, one at a timeOne unified dashboard, every client rolls up with a chip
Ask an AI across all clientsNot possible without manual export per accountOne API key + MCP scope=family reaches every client
Keep clients isolatedSeparate logins, no real isolation guaranteeCryptographic per-portal isolation + independent revocation
Per-client permissionsNone, every account is the sameGranular capability toggles + per-client resource caps
Where the data landsOften locked to one spreadsheet per accountGoogle Sheets, Excel, Notion, or Airtable, a different destination per client
BillingOne bill, but you still juggle accountsOne subscription, quota pools across the whole family

What makes BankSync multi-client feeds different

Each client is a full, isolated workspace, not a tag, not a label, not a row in a shared table. Everything that works for your own data works for your client's.

Aggregate, don’t switch

Every client’s connected banks roll up into one Banks list, each tagged with a portal chip. Stop logging in and out of accounts to answer one question across your book.

Each client connects their own bank

No credential sharing, ever. Clients authorize read-only access through regulated open banking in the US/CA, CDR (AU), PSD2 (EU), OBIE (UK). You never touch a login.

Cryptographic isolation per client

Each client is a full, isolated workspace with its own provider tokens, members, and audit trail. Revoke one client without touching another. No shared-table accidents.

One AI agent across every client

Add scope=family to one API key and Claude, Cursor, or ChatGPT can reason across your whole book: "find every unreconciled transaction over $500 across all my clients this quarter."

One subscription, family quota

Your plan covers the parent workspace and every client under it. Bank limits pool across the family, with no per-seat charge and no per-client invoice. Set per-client caps if you want.

Structured rows, not PDFs

Transactions arrive with merchant, category, balance, account, and date, as structured rows that sync straight to Google Sheets, Excel, Notion, or Airtable. No re-keying, no lost categorization.

The part nobody else has

One AI agent for your entire book

Because every client rolls up under one workspace, your AI agent can reason across all of them at once. Add scope=family to a single API key and Claude, Cursor, or ChatGPT sees every client's data. Sub-account tools can't do this. There's nothing to aggregate.

Explore the MCP server
Claude · BankSync MCP

you › Across all my clients, which invoices are unreconciled this quarter?

claude › Querying GET /v1/feeds?scope=family …

Acme Co · 3 unreconciled · $4,210

Smith LLC · 1 unreconciled · $880

Vertex Pty · 5 unreconciled · $12,540

Built for every client-services practice

If you manage other people's money data, multi-client bank feeds fit your workflow. See the playbook for your role.

Accountants

Stop chasing PDFs across 40 clients. Send a link, they connect, it rolls up.

See the workflow

Bookkeepers

Run a multi-client practice from one workspace with per-client caps.

See the workflow

Financial Advisors

Every client’s holdings, trades, and balances in one consolidated view.

See the workflow

Tax Preparers

Onboard 80 clients in a week, sync the full year, archive when filed.

See the workflow

Go deeper

All clients in one Google Sheet

A tab per client, auto-synced from each client’s own bank.

All clients in one Excel workbook

A worksheet per client, refreshed on your schedule.

How to collect client bank data

The secure way: regulated open banking, no shared logins.

Frequently asked questions

What are multi-client bank feeds?
Multi-client bank feeds are automated bank-data connections that let one firm collect transactions, balances, and account data from many clients at once. Instead of chasing PDF statements or juggling separate logins, each client connects their own bank through regulated open banking, and every client’s data rolls up into a single dashboard the firm controls. BankSync delivers this through Client Portals: one isolated workspace per client, all aggregated under one parent subscription.
How is this different from sub-accounts?
Sub-accounts (the model used by tools like Fintable) are separate accounts under one bill that you switch between one at a time, and each is usually locked to a single spreadsheet. BankSync aggregates instead of switching: every client’s banks roll up into one unified dashboard, you can query all clients with a single AI agent (scope=family), each client is cryptographically isolated with independent revocation, and data can land in Google Sheets, Excel, Notion, or Airtable (and be read back via the API or MCP). Switching is not the same as aggregating.
Who are multi-client bank feeds for?
Accountants, bookkeepers, tax preparers, financial advisors, virtual CFOs, fractional finance teams, and family offices, any firm that needs ongoing access to multiple clients’ bank, brokerage, or investment data. If you currently chase PDF statements, add clients to a shared workspace, or run separate subscriptions per client, multi-client bank feeds replace all three.
Do my clients have to share their bank login with me?
No, and they never should. Each client authorizes read-only access through their own bank’s consent screen via regulated open banking (open banking in the US/Canada, CDR in Australia, PSD2 in the EU, OBIE in the UK). BankSync never stores banking credentials. Each client’s tokens live on their own isolated portal, so revoking one client never affects another.
Can I see all my clients’ data in one place?
Yes, that’s the entire point. Every connected bank from every client rolls up into your Banks list, tagged with a portal chip ("via Acme Co"). Filter by client, drill into a single portal, or export everything at once. Feeds, integrations, and AI queries all work across the whole family.
How does billing work for multiple clients?
One subscription on your parent workspace covers every client portal under it, with no per-seat or per-client charge. Your plan’s bank limit pools across the family, and you can set per-client caps so no single client consumes your whole quota.
Can AI assistants like Claude or ChatGPT query across all my clients?
Yes. The BankSync MCP server understands portals natively. Use one API key from your parent workspace, pass scope=family on supported endpoints, and your AI agent can reason across every client at once, perfect for AI bookkeeping workflows that need a view of the whole book.
Which regions and banks are supported?
Every region BankSync supports: the US and Canada (Plaid), Australia (CDR via Fiskil, accreditation ADRBNK000246), the UK (Open Banking via Salt Edge), and the EEA (PSD2 via Salt Edge), spanning 11,000+ institutions. Mix regions freely: an Australian client uses CDR, a US client uses Plaid, and your dashboard shows both side by side.

Bring every client into one dashboard

Sign up, create a portal per client, send the invite. They connect their own bank in minutes and roll up into your unified view. One subscription covers them all.

Start free trialHow Client Portals work