Bank data, every client, one dashboard.

Xero and QuickBooks are accounting ledgers — they want you to do your full books inside their platform. BankSync is bank-data infrastructure: we pipe regulated open-banking data into wherever your books actually live. Most accounting firms use BankSync to feed working papers, Notion CRMs, custom Sheets dashboards, or Airtable workflows — without replacing their ledger. Client Portals are the same idea applied at scale.

Yes — that's the typical pattern. Use Karbon, Ignition, or Practice Ignition for client comms and engagement letters. Use Xero or QBO as your ledger. Use BankSync to fill the gap between "client signs engagement letter" and "transactions are categorized and reconciled" — without manual statement collection.

Yes. BankSync covers 11,000+ institutions: every CDR-accredited bank in Australia (Big 4, Macquarie, ING, Up, Bankwest, neobanks, mutuals), 11,000+ US institutions via open banking, RBC/TD/Scotia/BMO/CIBC/National plus credit unions in Canada via open banking, CMA9 + neobanks in the UK, and 2,500+ banks across 30 EEA countries via PSD2.

A few things to point at: (a) we never see or store banking credentials — clients authorize via their bank's own consent screen; (b) in Australia we operate as a CDR Representative under Fiskil, an ACCC-accredited Data Recipient (ADRBNK000246); (c) in other regions we route through licensed open-banking providers (Plaid and Salt Edge); (d) data is encrypted in transit and at rest; (e) clients can revoke consent any time from their bank app. Send them to /security for the full breakdown.

Nothing extra — your plan covers all portals. Your bank quota pools across the family. A 15-bank Professional plan supports about 10 typical small-business clients (each with 1–2 accounts). Enterprise plans go higher. Talk to us if you need to support 50+ clients.

Yes. Anyone with admin or owner role on your parent workspace has implicit owner-level access to every portal — no per-portal invitations needed. Junior staff with editor role on the parent get scoped read access to portals you grant. Portal members (clients you invited) only ever see their own portal.

You delete their portal. BankSync revokes the open-banking tokens immediately, soft-deletes the portal data, and runs a full purge after 30 days. The client's historical data is yours to keep in any sheet/Notion/Airtable you exported to — bank-data infrastructure is one-way out by design. If they later want their portal back, that's a new portal.

Two approaches. (a) One portal per entity — clean isolation, separate consent per entity, ideal for clients with truly distinct legal structures. (b) One portal per client group, multiple bank connections inside — fewer portals to manage when the entities share a controlling person. Both are supported; you can mix them.

Yes. Every portal records member changes, bank connections, consent grants, and capability toggle changes. Family-scoped reads require admin+ on the parent workspace, so junior-staff actions are attributable. Provider-side audit (open banking, CDR, etc.) lives at the bank and is separately auditable by your client.