Most accounting and financial firms already have a portal of some kind, and clients still send documents by email. A bank statement arrives as an attachment, the corrected version arrives as a reply to a different thread, and nobody is sure which one was used. Clients forget their portal password and fall back to email. When a client asks who downloaded their return, the firm can’t say.
The other half of the problem is the reverse direction. Finished work, such as financial statements and computations, is sent as attachments and then lost in the client’s inbox, so the firm sends it again next month.
When a custom portal beats SaaS and no-code
There are three ways to get a client portal, and each fits a different firm.
- Practice platforms (TaxDome-style tools) bundle a portal with CRM, workflow and billing. If their workflow is your workflow, buy one.
- No-code builders are quick for an upload form and a file list. They get hard to trust once access depends on the record, such as one client’s entities, one staff member’s assignments or one document’s status, because those checks have to run on the server for every request.
- A custom portal makes sense when it has to show data your own systems produce, when your roles and approval steps are specific to your firm, or when you need an audit trail you control.
The real case: Lekhavo’s client portal
Lekhavo is our bookkeeping and practice platform for Indian chartered-accountant practices, built and run in production by Tembrant. Its client portal is the basis of this page, and every claim below comes from its code.
Document requests
The firm asks a client for a document, optionally for one entity (a person, their trust or their company) and with a due date. The request moves through clear states: pending, uploaded, then accepted or rejected with a review note, or cancelled. Nothing is “somewhere in email”.
Shared documents
Finished documents are shared with the client through the portal, next to the client’s own profit and loss and balance sheet, which they can download as spreadsheets or print. Clients get notifications in the portal, and on their phone if they turn on push notifications.
Clients answer their own questions
With the right role, a client can open their own transactions and categorize them, so the firm’s question about a payment is answered where the payment is. Our page on software for accounting firms covers the bookkeeping side.
Sign-in without passwords
Clients choose one of four ways in:
- Google, using the verified email address the firm registered
- An SMS code, valid for five minutes
- An email code, stored only as a hash
- A passkey, set up from the client’s own details page
Sending and checking codes are rate limited, so a code can’t be guessed by brute force. A client’s portal access can be revoked by the firm, and the revocation is itself recorded.
The security model
Tenant isolation
Every record belongs to the firm that created it. Each request that touches a resource is checked against the ownership chain, from the record to its entity, its client and the firm, before the handler runs. Portal handlers take the client from the signed-in session, so a forged ID returns zero rows. There is no admin bypass, and a change that could leak data across firms blocks the release.
Least-privilege roles
A client user holds one role for one client: owner, editor or viewer. On top of the role, the firm can grant or deny single areas: reports, documents, categories, transactions, and the right to make changes. Denials are applied last, so they always win. Inside the firm, staff see only the clients assigned to them, while partners and head staff work on every client.
Audited access
- Every portal sign-in is logged with its method.
- Every document upload and download is logged with who did it and from which IP address.
- Every data change records the actor, the record and which fields changed. The values themselves are never stored, and the history survives even if the person’s login is deleted.
- Audit entries never carry client financial data such as payees or amounts.
Files handled defensively
An uploaded file’s contents must match its declared type, or the upload is refused. File names are cleaned before they are stored, and storage paths are generated, never built from the name a user typed. Large files go straight to storage through a signed upload URL that expires after ten minutes, and uploads that are started but never finished are deleted after a day. The session cookie is HTTP-only and SameSite, so page scripts can’t read it and other sites can’t send it with their requests.
What you get
- A portal shaped to your firm’s clients, entities and roles
- Document requests, shared documents and notifications
- Passwordless sign-in suited to your clients
- Tenant isolation, least-privilege roles and an audit trail you own
- Integration with your practice software, document store or ledger, such as statement imports through a bank statement parser
- Source code, a written spec and tests your team owns
How we work
Tembrant builds with an AI software factory: many agents work in parallel, held to fixed gates. Each piece starts from a written spec in your firm’s own terms, tests are written first, every change gets independent reviews, and a person signs off before it ships. For a portal, the spec also lists who can see each record, and the tests check that everyone else can’t.
If your clients still email you their documents, tell us how your firm works today.
