Clients and Mandates

Clients or mandates separate business entities inside one installation.

A user must usually have both a module role and a client assignment to see client-specific documents, tasks, reports, or master data.

Client Role Pattern

Many installations use a role naming pattern similar to:

mandant - <number> - <name>

Example:

mandant - 0001 - Arlesheim

Some older or customer-specific installations may use different names. The permission logic must therefore be checked against the actual configuration and user roles in the installation.

Client Fields on Documents

Invoice documents commonly use fields such as:

Field	Purpose
cq_client_accounting	Accounting client or mandate of the invoice.
cq_accounting_area	Accounting area or business unit.
obj_acl	Effective object access list. Often contains users, roles, client roles, and functional roles.

If cq_client_accounting and the user's client role do not match, the document may be hidden even if the user has general Invoice access.

Client Visibility Checklist

When a user cannot see a client-specific document:

• Compare the document's cq_client_accounting with the user's client roles.
• Check whether the client role appears in obj_acl.
• Check whether the user has the application role for the module.
• Check whether the current dashboard or table filters by client.
• Check whether the user has a default client that limits the view.

Master Data and Client Defaults

Client master data may also define defaults such as accounting area, internal bank, ERP connection, or export behavior. These values can influence later processing even after the document is visible.

For Invoice support cases, always capture both the user's roles and the document's client/accounting fields.