An accounting firm managing cash for several client files on Sage Intacct quickly ends up juggling as many bank portals as clients. Each team member memorizes their own logins, each file has its own habits, and nothing guarantees that a transfer gets validated by the right person for the right client. This isn't a volume problem, it's an organizational one: isolation between files relies entirely on human discipline.
The problem: one portal per client, isolation held together by individual vigilance
Without a dedicated tool, a team member handling 15 client files has to remember 15 different logins, with 15 different permission levels depending on what each client allows. Picking the wrong file when validating a transfer can never be fully ruled out — and it's hard to detect without any centralized log.
Multi-tenant isolation: what it actually guarantees
Arkaio structures each client as an isolated entity: its bank accounts, payments, statements and reconciliation rules only exist within its own scope. A team member only sees the files they're explicitly assigned to — isolation is no longer a matter of individual vigilance, it's structural.
Fine-grained delegation of rights per team member and per client
Rights are configured per person and per file: a junior team member can prepare payments without validating them, a partner can validate for specific clients only, and firm management keeps an overview of everything. This granularity matches how a firm actually organizes its teams — by file, not by tool.
Consolidated view: managing cash across all files from a single screen
Instead of opening one portal per bank and per client, the firm gets a single dashboard listing the cash position of all its Sage Intacct files: payments awaiting validation, today's reconciliations, anomalies to handle. What used to be a round of successive logins becomes one overview.
Measurable time savings for a typical firm
For a firm managing around thirty files, removing repeated bank portal logins and payment re-keying typically frees up several hours per week per team member — time that goes back into client advisory work instead of tool handling.
How to get started on a first client file
Rollout happens file by file: EBICS or Open Banking connection for the first client, rights configuration for the relevant team members, then progressive extension to other files at the firm's own pace — no big bang, no disruption to what's already in place.
In summary
- Strict isolation between client files, structural rather than dependent on individual vigilance
- Configurable rights per team member and per client, matching how the firm actually organizes itself
- Consolidated cash view across all files from a single screen
- Progressive rollout, file by file