Multi-Client Capability
Multi-client capability is a software's ability to manage several organisationally separate units (clients or entities) – such as companies, subsidiaries or brands – in one shared installation, while each client's data stays strictly separated from the others.
Multi-client capability refers to a software's ability to run several independent organisational units – so-called clients – within one and the same installation without their data mixing. A client here is a self-contained accounting and data circle: typically a legally independent company, a subsidiary, a location or a brand. Each client works with its own master data, its own number-range and document handling and its own accounting, while technically only a single program instance is operated and maintained.
In the ERP context, multi-client capability is decisive because many companies run more than one legal or economic entity. Instead of setting up a separate system for each company, a multi-client ERP bundles all clients under one roof – with separate reporting per client and, optionally, a consolidated view across all of them. A distinction has to be drawn between in-house multi-client capability (one customer runs several of their own companies) and the vendor's multi-tenancy, where many external customers share a single SaaS instance.
At a glance
- One installation manages several separate companies (clients)
- Strict data and posting separation per client, shared maintenance
- Own master data, number ranges and reports per client
- Saves costs compared with several separate standalone systems
- To be distinguished from the SaaS vendor's multi-tenancy
What a client is in an ERP
A client is the top organisational separation level within an ERP system. It comprises a self-contained data set – customers, suppliers, items, documents, postings – assigned to a specific legal or economic entity. Whoever is logged into a client sees only its data; switching to another client requires an explicit selection and the corresponding authorisation.
The term originally comes from accounting: a tax advisor or a group accounting department maintains a separate "client" for each company it looks after, with its own chart of accounts and separate annual financial statements. Modern ERP systems have extended this principle to all modules – from inventory management and purchasing through to shipping. The client is therefore far more than an accounting layer: it is a complete, sealed-off business context.
How multi-client capability works technically
So that the data of several clients does not mix, a multi-client system separates them logically from one another. In practice this is usually done via a client identifier (tenant ID) that is attached to every record and automatically applied as a filter on every query. Alternatively or additionally, some systems use separate databases or schemas per client. For the user this mechanism stays invisible – they always work only in their currently selected client.
Separated and shared data
Not everything has to be separated per client. Client-specific data typically includes master data such as the customer and item master, documents, postings and number ranges. Shared – that is, cross-client – data, by contrast, can often be maintained centrally: system settings, user accounts, permission roles or central lookup lists (such as country or currency tables). Well-designed systems let you decide per data type whether it is shared or separated.
Permissions and visibility
A central element of multi-client capability is the permission system. It controls which user may access which clients. A clerk might work in only one client, while management or central accounting may report across several. Client separation is thus at the same time a security and compliance feature: it ensures that one company's documents and figures are not unintentionally visible in another.
Why multi-client capability matters
The practical benefit of multi-client capability lies in efficiency and consistency. Instead of licensing, hosting and maintaining a separate system for each company, one installation is enough. Updates, backups and administration are carried out once for all clients. This noticeably lowers operating and licensing costs and reduces administrative effort – an important factor in the total cost of ownership (TCO).
Equally valuable is the consolidated view: because all clients sit in one system, key figures can be brought together across several companies, for example for group reporting or a shared stock analysis. At the same time, each unit stays cleanly separated, so that annual financial statements, tax returns and legal obligations are mapped correctly per company. Multi-client capability thus combines two seemingly opposing requirements: strict separation and central control.
Multi-client capability in the ERP system
Almost every professional ERP supports multiple clients today – but the scope differs considerably. What matters in the ERP selection is therefore not only whether a system is multi-client capable, but how deep the separation goes and how conveniently cross-client work succeeds. Questions on this belong in every requirements specification: Can master data be copied between clients? Can documents such as intercompany deliveries be settled between clients? How granular is the permission system?
For DACH companies, multi-client capability is closely interlinked with accounting. Each client usually runs its own chart of accounts (such as SKR03 or SKR04) and its own DATEV connection, so that the tax advisor can process the companies separately. The requirements of the GoBD also apply per client: documents must be stored per company in an unchangeable, traceable and audit-proof manner. A multi-client system must maintain this separation right through to archiving.
Distinction: multi-client capability vs. multi-tenancy
Multi-client capability and multi-tenancy are often used synonymously, but they refer to different perspectives. Multi-tenancy is an architectural feature of the software vendor: with a SaaS solution, many external customer companies share a single, centrally operated instance while their data stays technically separated. Here each customer is a "tenant". This separation serves the vendor for cost-efficient scaling and is usually invisible to the individual customer.
Multi-client capability in the sense meant here, by contrast, describes a function that benefits the customer themselves: a company runs several of its own companies as clients within its system. Both concepts can coincide – a cloud ERP can be multi-tenant at the vendor and at the same time allow the customer to create several of their own clients within it. In the contract and licence it is therefore important to clarify whether additional own clients are included or charged separately.
Example
Practical example: retailer with two brands and a sales GmbH
An online retailer operates two independent shop brands and, for wholesale, additionally founds a separate GmbH. Legally and fiscally these are three separate entities – each needs its own accounting, its own invoice numbers and its own annual financial statement. Instead of running three separate ERP systems, the retailer creates three clients in their multi-client ERP.
Each client has its own customers, items and documents; accounting hands three separate DATEV exports to the tax advisor. At the same time, management can pull a consolidated revenue analysis across all three clients. As one brand grows, users and warehouses are expanded without a new system being needed – updates and backups continue to run once for all clients.
Frequently asked questions
Matching ERP systems
Related services
Sources
Questions about Multi-Client Capability in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.