Fiduciary software with real client tenants: why «log in to our environment» isn't enough in 2026

A fiduciary office doesn’t manage one company, it manages ten, thirty or eighty — each with its own accounting, its own deadlines and, crucially, its own data-protection perimeter. This is exactly where you can see whether a piece of fiduciary software was built for this, or just had a «fiduciary access» bolted on.

The difference shows up in daily work: twenty separate logins, client data that has to be kept apart in someone’s head, and a year-end handover that feels like a data export with a crowbar. Let’s look at which models the market offers — and what really matters in true multi-tenant software.

The client-tenant problem no spreadsheet can solve

Most fiduciaries have grown over the years into a patchwork of tools: one system for the larger mandates, a second for the smaller ones, Excel for everything in between. It works — until it doesn’t. The critical question is not «Can we run the accounting?», but «Can we run many client mandates cleanly, separately and verifiably — without the separation hanging on the discipline of individual employees?».

The three models on the market — honestly placed

The suite model (Abacus / AbaWeb)

With AbaWeb, Abacus is the established standard for cloud-based collaboration between fiduciary and client: powerful, modular according to a building-block principle, with time tracking and a deep feature set. The price is complexity — the solution is typically set up via partners and follows a classical licence and IT logic. For large, demanding fiduciary structures, this is often the right choice.

The invite model (Bexio & co.)

In the simpler segment, the client invites their fiduciary as a user into their account. That is low-barrier and good for small set-ups. The downside: one account per client, one access per client — and in depth it stays at invoicing and payroll, without a real ERP.

The client-tenant platform model

The third model flips the logic: each client receives a fully isolated platform of their own — and the fiduciary moves between them from a single access. Isolation without login ballast. This is exactly where hegyon.ai sits.

What matters in true multi-tenant software

Regardless of the vendor — these five points separate true multi-tenant software from a single-company tool with a client filter:

1. Real data isolation, not just a filter. At hegyon, every row in every table is separated by a tenant_id; one client tenant never sees the data of another. That is an architectural difference compared with a shared dataset sorted by filter — and a heavy one in data-protection terms.

2. One login, many client tenants. The fiduciary logs in once and switches between their client tenants without re-authenticating twenty times. Each client tenant has its own subdomain (tenant.hegyon.ai) and its own branding — the separation stays visible, the access stays convenient.

3. Clean, complete export. When a client leaves the office or a new one comes in, only one thing matters: can you get to all the data, complete and unmangled? hegyon delivers a full tenant snapshot as a download — for handovers and off-boarding. This is deliberately built against lock-in, i. e. against exactly what frustrates fiduciaries and their clients with many systems.

4. Tiered roles and visibility. Not every person needs everything. A role system (including tenant_admin) with row-level visibility lets you steer access per client tenant and per function — instead of all-or-nothing.

5. Per-tenant provability. For year-end reviews and towards the client, integrity is decisive: hegyon seals booking-relevant events per client tenant in a cryptographic hash chain. What that means technically and legally we covered in the post on audit-proof bookkeeping.

Data protection: the fiduciary is a data processor

As soon as a fiduciary processes client data in cloud software, the software vendor becomes a data processor. From that follow concrete duties: a data processing agreement is needed, and the processing must comply with the rules of the revised Federal Act on Data Protection (revFADP) on order processing. On top of that comes the professional duty of confidentiality towards clients.

Swiss hosting and true tenant isolation are not a marketing detail here, they support exactly these duties. If you want to consciously choose the data residency of your client data, the post on data residency Switzerland/EU/USA has the matching decision tree.

What the platform model is suited for — and what (not yet)

Honesty belongs here, otherwise the comparison is worth nothing. The client-tenant platform model plays out its strength when your mandates need a real, broad platform — accounting, receivables/payables, inventory, HR, CRM, tickets and wiki under one roof, per client tenant cleanly separated, with the AI assistant as a navigation layer.

What hegyon today does not cover is the classical practice-management of a fiduciary office — the time tracking and billing of the fiduciary’s own work across all client mandates. If that is a core requirement, a mature suite like Abacus serves you better. For fiduciaries whose value lies in the operational platform for their client mandates, on the other hand, the model is a real lever.

A note on format compatibility: direct exports to Bexio, Abacus or DATEV formats are on the roadmap and are not a delivery commitment at today’s state.

Conclusion

«Software for fiduciaries» means more in 2026 than a login into someone else’s account. It means real isolation, one access for many client mandates, a clean way out without lock-in, and provability that withstands a review. Which of the three models fits depends on your office — the questions above help with an honest assessment.

If you want to see what tenant switching from one login and the complete export feel like: hegyon.ai will set up a demo tenant for you, typically within 24 hours — and in a fiduciary conversation we discuss what a multi-tenant set-up could look like for your office.

This article is for general orientation and does not constitute legal or tax advice. Statements on data protection and order processing (revFADP) are kept general and are not exhaustive; please clarify the concrete duties of your office with qualified advice. Statements about third-party providers refer to mid-2026 and may change. Roadmap items are not delivery commitments.