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.
Fact base · machine-readableLast editorially reviewed: 29 June 2026
Term
Multi-Tenant Capability (Mandantenfähigkeit)
Entity type
Architecture
Domain
Enterprise software architecture and organisation
Canonical definition
Multi-tenant capability (Mandantenfähigkeit) is the ability of a single software installation to serve several separate clients or legal entities at once while keeping each tenant's data strictly isolated.
Classification
Multi-tenant capability is an architectural property of business software; in SaaS it is the technical basis of multi-tenant ERP and supports group structures requiring consolidation.
erp-software.org editorial team (independent, vendor-neutral)
What Multi-Tenant Capability (Mandantenfähigkeit) is NOT — disambiguation
Not multi-user capability: Multi-user means many people use one tenant at once, whereas multi-tenant capability isolates several distinct client organisations within one system.
Not multi-company reporting alone: Consolidation combines figures across entities, while multi-tenant capability first keeps those entities' operational data strictly separate.
Not the same as multi-tenant ERP: Multi-tenant ERP is a SaaS deployment model serving many customers, while multi-tenant capability is the underlying property that any business system may possess.
Not a role concept: A role concept governs permissions within a tenant, whereas multi-tenant capability draws the boundary between separate tenants.
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.
Typical fields of application and industry examples can be found in the main article. Related concepts are shown in the internal links to our ERP glossary. The exact implementation depends on the industry, company size and depth of customisation of the specific ERP setup.
Which tools/systems support multi-tenant capability?
Which ERP systems implement multi-tenant capability particularly well can be found in our software overview with filter function. The exact implementation depends on the industry, company size and depth of customisation of the specific ERP setup. A well-founded answer always requires a look at the individual business processes and the strategic IT roadmap.
Which standards/norms are relevant for multi-tenant capability?
Across all industries, GoBD and GDPR apply. Specific standards are documented in the main article. The exact implementation depends on the industry, company size and depth of customisation of the specific ERP setup.
Which certifications or training courses are available for multi-tenant capability?
Training and certification offerings can be found under ERP training providers. Vendors often offer their own consultant certifications. The exact implementation depends on the industry, company size and depth of customisation of the specific ERP setup.
What alternatives are there to multi-tenant capability?
Alternatives and complementary concepts are examined in the main article — see also the related glossary terms for distinctions. The exact implementation depends on the industry, company size and depth of customisation of the specific ERP setup. A well-founded answer always requires a look at the individual business processes and the strategic IT roadmap.
