Product Pricing Partners Demo Security Q&A Log in Start free
For bookkeepers and accountants

Your whole client roster
on one login

Talisk does the capture and the coding on every client, so the file that reaches you is already reconciled and tied out. You do the work only you can do.

How it works

You hold the subscription, your clients get real accounts

On the Partner plan you provision each client yourself. They are not rows inside your file: each one is a genuine account with its own books, its own database schema and its own encryption key, exactly like any other Talisk customer. You reach them through access grants, and you move between them from one login without signing out.

Their mail connects to their own inbox. Their receipts land in their own books. What you see is the finished coding, ready to review.

Your practice
Northside Cyclesreconciled
Bramble & Co2 to review
Harbour Supplyreconciled
Fielding TradesQ2 closed
Marchmont Studioreconciled
Each in its own isolated account
What you get

Built for the way a practice actually runs

Act as the client

Step into a client's books, do the work, step back out. No separate logins to keep, no password resets to chase.

Isolation you can point at

One client's data is never in another's tables, and never in yours. It is the same physical boundary that separates any two Talisk customers.

Working papers, not a shoebox

Trial balance plus the listings behind each balance: reconciliations, AR and AP detail, capital additions, what is sitting in prepaids and accruals.

The close, per client

Reconcile, clear what is unposted, lock the period. Talisk keeps a record of the figures filed, so a late entry cannot quietly rewrite a return.

Export to whatever you use

QuickBooks, Xero, IIF or xlsx, per client, whenever you want. Your clients' data is theirs, and it leaves cleanly.

Canadian by default

GST, HST, PST and QST by province, recoverable credits tracked properly, and a filing-period worksheet per client that matches what CRA and Revenu Québec ask for.

The part worth reading twice

Ending a client relationship is a revocation, not an extraction

Because each client's books live in that client's own account rather than inside yours, parting ways is administrative. You revoke the grant, or hand them their own subscription and keep the access they choose to leave you. Nothing has to be untangled, exported under pressure, or argued about.

It also works in the other direction. A business that already runs Talisk can invite you in on their own subscription, scoped how they like: view, edit or full access, limited to a date range or a single mailbox, with an expiry. They revoke it the same way, instantly.

A client graduates
Their booksstay put
Their encryption keyunchanged
Their subscriptionnow theirs
Your accessby their grant
No migration, no export scramble
Who sits in the chair

Three arrangements, all first class

01

You own the account

The Partner plan. You provision the client, you hold the subscription, and billing rolls up to you. The client can still log in to do what only they can do: photograph a receipt, log hours, photograph a job.

02

They own the account, you are invited in

The business pays for its own subscription and grants you access: a named login with view, edit or full access, or a token portal share bounded to a date range. You pay nothing for that client.

03

They run it alone, you see it at year end

No login for you at all. The owner captures, Talisk codes and reconciles, and what arrives is a year-end package with the working papers behind every balance.

Partner plan

One subscription, up to twenty clients

$179 CAD / month

Up to 20 client books, unlimited email connections, act-as-client mode, and a $40 monthly AI budget for your own practice. Extra client books are available if you outgrow it.

Talisk is in early access. Nothing is billing yet, and we'll give you notice before that changes.

Bring one client and see

Start free, set up a single client, and look at what lands on your desk at the end of the month.

Each client encrypted with a key of their own · isolated at the database level · never sold, and never used to train public models. How we protect your data