Multi-Tenant Capability (Mandantenfähigkeit)

Multi-tenant capability, known in German as Mandantenfähigkeit, is the property of a software system that allows a single installation to serve several separate clients, or tenants, while keeping each tenant's data strictly isolated from the others. In an ERP context a tenant, or Mandant, is usually a legally and organisationally distinct unit such as a subsidiary, a separate company or an external customer. Each tenant works as though it had its own system, with its own master data, transactions and reports, even though they all share the same underlying application. This capability is fundamental to corporate groups, shared-service organisations and the SaaS business model.

What a tenant is

In ERP and accounting software, a tenant (Mandant) is the highest-level organisational separation within the system. It commonly maps to a legal entity: a separate company that keeps its own books, files its own statutory accounts and must not see another entity's confidential data. A multi-tenant system can host many such entities at once. Within each tenant, finer structures such as company codes, cost centres and business units provide further subdivision, but the tenant boundary is the strongest line of separation the application enforces.

Why it matters

Multi-tenant capability addresses several practical needs:

• Corporate groups: a parent company can run several subsidiaries on one system while keeping their data separate, then combine results for consolidation and group reporting.
• Shared services and outsourcing: an accounting firm or service centre can administer many client companies from a single installation.
• SaaS providers: a software vendor can serve many customer organisations from shared infrastructure, which is the technical basis of multi-tenant ERP.
• Cost efficiency: one system to license, operate, patch and back up instead of many parallel installations.

Data isolation and security

The defining requirement is reliable isolation. Users assigned to one tenant must not be able to read or alter another tenant's data, even though the data may share the same database. The system enforces this through the tenant key on records combined with a role concept and access controls, supported by an audit trail that records who did what. Strong isolation matters not only operationally but also for data protection: handling several legal entities or external clients raises obligations under GDPR, since each tenant's personal data must stay segregated and accountable.

Architectural approaches and limits

Multi-tenant capability can be realised in different ways, from a shared database with a tenant identifier on every record, through separate schemas per tenant, to separate database instances behind a shared application. Each approach trades off isolation strength, operating cost and the ease of running shared reports. A genuinely multi-tenant system still allows legitimate cross-tenant functions where intended, such as group-wide consolidation or intercompany postings, without weakening the everyday separation. When evaluating software, organisations should confirm not only that multiple tenants are supported but how cleanly data is isolated and how group-level processes are handled.

Related Topics

• Multi-tenant ERP (Cloud)
• Two-tier ERP
• Intercompany