How to Give Your Accountant Read-Only Bank Access Without Sharing Passwords (2026 Guide)

Search for "give accountant read-only bank access" right now and most of what you'll find are US bookkeeping services selling a done-for-you monthly contract. That's one way to solve it. It's also the expensive way, and it hands your financial data to yet another middleman.

If you just want your accountant to see your transactions — without sharing a password, and without signing anything — PSD2 open banking does this natively. This guide is the self-serve version: what read-only actually means, and the exact steps to set it up yourself in under an hour.

What read-only access actually means under PSD2

Under PSD2 (and the UK's Open Banking standard), a regulated Account Information Service (AIS) can pull your balances and transactions only with your explicit consent. That consent is a contract between you and your bank, enforced by the bank itself — not a promise from some app.

Three properties matter here:

• Consent is scoped. You approve exactly which accounts are shared, and for how long. Nothing outside that scope is visible.
• It's read-only by construction. An AIS consent contains no payment-initiation rights. The accountant — or any tool connected on their behalf — cannot move money, even accidentally. Seeing and sending are legally separate services.
• Consents expire on a 90-day cycle. Access renews only when you re-authenticate, so stale access can't linger silently for years.

Compare that with a shared login, where "read-only" is a hope, not a mechanism.

The old way vs the PSD2 way

Most small businesses still do one of these:

• Shared passwords. Breaks your bank's terms, gives full payment rights, and every person with the password is indistinguishable in the audit log.
• PDF and CSV exports. Safer, but stale on arrival. Quarter-end becomes a scramble of downloads, emails, and "which version is current?"

The PSD2 way replaces credentials with a scoped consent. Your accountant's tool authenticates against the bank with a token that can only read, you can revoke it in your banking app at any time, and the data is always fresh — no export ritual. Crucially, it also means no contract with a bookkeeping service just to get the plumbing.

(A middle option exists: many business portals let you add your accountant as a read-only sub-user. It works, but it's per-bank, the role is enforced by a checkbox rather than a consent, and someone still exports statements by hand at quarter-end. It's fine as a stopgap — PSD2 just does it properly.)

How to set it up step by step

Every provider words things slightly differently, but the flow is the same everywhere.

1. Pick an AIS tool and create an account. Choose a regulated provider with self-serve signup — no sales call, no minimum contract. Registering takes minutes; you'll get your own API keys or dashboard login.
2. Connect your bank via the SCA redirect. The tool sends you to your bank's own login page. You authenticate with your bank (strong customer authentication — 2FA or your banking app's approval), then approve a consent screen that lists precisely which accounts are in scope. The tool never sees your password.
3. Keep the scope read-only. You're granting account information access — nothing else. If a setup flow ever asks you to approve payment initiation for bookkeeping, stop: that's not needed and you shouldn't grant it.
4. Invite your accountant as a viewer. In most tools this is a seat or a shared dashboard with view rights. Your accountant gets live transactions in one place, without ever holding a credential of yours.
5. Revoke when the engagement ends. Kill the consent in your banking app and remove the seat. Two clicks, no awkward conversations.

Repeat step 2 for each additional bank — one consent per bank, all surfaced in the same tool. Your accountant's view stays unified even when your money doesn't live in one place, which is exactly the situation sole traders and small agencies tend to end up in.

What to check when choosing a tool

• Bank coverage, including neobanks. Check the provider's coverage list for your exact banks before paying — especially Revolut Business, N26, Wise, and smaller regional banks, where coverage varies most.
• Pricing per connection. Some providers charge per bank connected, others per API call. Know which model you're signing up for before you connect bank number three.
• Who holds the keys. Prefer tools where you hold your own credentials and can rotate or revoke them yourself, rather than everything running through someone else's account.

One more: make sure the output fits your accountant's workflow. CSV export is the universal fallback; direct sync into accounting software like Xero or QuickBooks saves a step if you use them.

A worked example

A common setup: a sole trader with a business account at a regional bank plus a Revolut Business account.

Both get connected through the SCA redirect in step 2 — roughly a minute each. The accountant receives a viewer seat and checks transactions whenever needed, and at quarter-end you export a clean CSV from the same dashboard instead of emailing statements. Total standing cost: open-banking.io starts at ~€3/mo per connection, so two banks land around €3–6/mo — and because the provider is already regulated, you never have to think about eIDAS certificates.

Full disclosure: I maintain open-banking.io, a self-serve open-banking tool, so that's the example I know best — but the steps above are generic and work with any regulated AIS provider. If you're comparing options, I've written a detailed piece on Plaid alternatives in Europe and what changes when you switch, plus a running comparison of the cheapest open banking APIs in 2026.

The point isn't which tool you pick. It's that in 2026, giving your accountant read-only access is a consent you grant and can revoke — not a password you share and regret.