Skip to main content

Configure Centralized Multi-Company Behavior

How to Configure Centralized Multi-Company Behavior in Muhasib ERP

Overview

This guide will help you select the primary company and configure which masters or transactions are shared/visible across companies.

Affected forms may use primary-company masters or expose cross-company transactions. Wrong settings can mix identities, numbering, stock, accounts, tax, or reports.

Who can do this

You need access to Global Configurations, relevant company permissions, and explicit multi-company data-governance authorization.

Before you start

Back up the database. Inventory each company's items, contacts/parties, payment accounts/types/terms, tax, terminals, sales, purchases, roles, numbering, and reporting obligations.

Before saving, check that the correct company is open and that you have permission to complete this task.

Where to find it

Back Office → Settings → Application/Global Settings → Centralize Company Settings.

Configure Centralized Multi-Company Behavior

Step 1: Confirm every company and choose the approved Primary Company

Step 2: Decide separately whether to centralize items, contacts, parties, payment accounts,

Decide separately whether to centralize items, contacts, parties, payment accounts, payment terms, payment types, tax, and terminals.

Step 3: Decide whether users may see purchases or sales from all companies

Step 4: Change one family at a time

Step 5: Save and restart/re-enter company context where required

Step 6: Test create, select, update, report, permission, and company-switch behavior in

Test create, select, update, report, permission, and company-switch behavior in every affected company.

Check your work

Use an explicit company-by-company matrix to prove allowed sharing and prohibited leakage. Compare and Confirm reports and record ownership.

Take a moment to check your work before closing the window. This small check can save time later.

If something goes wrong

  • Restore the prior value if records appear in the wrong company.
  • Do not repair cross-company effects with direct database edits.

What to do next

Back to top