Use Case: Accountants

Manage many clients from one place, without losing separation

The right accountant model is one entity per client business. That keeps numbering, branding, exports, and compliance rules scoped correctly while your team switches context instead of juggling accounts.

Start free sandbox View accountant docs

Who This Is For

One accounting team manages invoicing for many client businesses

You need instant context switching with strict client separation

You may later give clients limited visibility or self-service access

Not A Fit

You only operate one business

You want all clients in one shared document pool

You need a full ERP or bookkeeping suite rather than invoicing infrastructure

Recommended Path

Use one account, many client entities

Accountants and finance teams should keep operational control on one account while each client business lives in its own entity. Add client-facing access only when there is a clear need for it.

Internal control

One team account switches between client entities.

Client access later

Use entity keys or user-based access when needed.

Entity Model

One client business = one entity

Each entity holds its own customers, items, numbering, exports, and compliance rules. That is what makes switching easy without breaking auditability or client boundaries.

Client isolation Strict

Switching Single account

Exports Per entity

First Sandbox Milestone

Prove switching and exports before scaling

The first test should prove that your team can switch client context, issue documents, and export or render by client without confusion or leakage.

Create two or three sandbox client entities

Switch between them and issue one invoice per client

Render or export documents by client

Decide whether clients get no access, entity-key access, or user-based access

Operational Gotchas

Keep one entity per client even when client businesses look operationally similar

Do not let exports span entities accidentally unless aggregation is intentional

Country and legal business details must be right before first live issuance

Compliance Notes

Each client entity follows its own country and business rules. Accountant convenience should never flatten per-client numbering or compliance behavior.

Sandbox is the right place to validate exports, switching, templates, and country-specific behavior across multiple client profiles.

Choose client access model See export and rendering docs

Start with one workflow, not a whole rewrite

Free sandbox with no time limit. Prove one entity and one invoice flow before deciding how much UI, compliance, and rollout surface you want to own.

Start free sandbox See platform architecture