Multi-company management: choose the right boundary
Illustrative group: company A sells in IQD and company B sells in USD. Shared products or staff do not mean shared legal books or automatic consolidated statements.
Separate the seller, access and reporting decisions
Illustrative group: company A sells in IQD and company B sells in USD. Shared products or staff do not mean shared legal books or automatic consolidated statements.
A: seller and ordinary role
A invoice identifies A as seller and posts to A books in the configured company currency. A operator can work on allowed A records; test denial of B-sensitive records.
B: independent books
B invoice identifies B, its own currency, tax configuration and invoice sequence. Cross-company users need intentionally configured access and explicit company selection.
Group reporting
Illustrative A sales 900,000 IQD and B sales 600 USD are separate source totals. Do not add them directly. Translation date/rate, eliminations and consolidated statements are specialist scope.
Workspace/service boundary
A company inside one business database differs from a separate subscribed Workspace. Each separate database has its own subscription; one runtime can serve several databases. Service account ownership is separate from ERP company permissions.
Organise your companies, users and reporting responsibilities in one clear structure.