Lab 01 · Set up the multinational group

Scenario: The group opens a new Saudi company and wants it to share a product catalogue with UAE while keeping local books, tax, users, and branches separate.

Design before clicking

Draw the scope first: tenant → organisation → legal company → branch → warehouse. A branch is an operating location; a company is a legal accounting boundary. Do not use a branch as a substitute for a separate legal company when local reporting, tax, or ownership requires separation.

Configuration exercise

1. Create the organisation and legal company.
2. Choose the company's base currency and financial year.
3. Set the local tax profile only after confirming the jurisdiction and reporting responsibility.
4. Add Riyadh Central as a branch and Saudi Regional Warehouse as its source location.
5. Add users with least-privilege access: country accountant, branch manager, warehouse operator, cashier, and read-only group analyst.
6. Configure numbering and document prefixes so a reviewer can identify company and branch from a document.
7. Add the group reporting convention as a documented reporting decision; do not silently replace the legal company's base currency.

Example control matrix

User	Can do	Must not automatically do
Cashier	Sell, accept permitted payments, close own shift	Change tax setup or approve refunds outside policy
Warehouse operator	Receive, pick, dispatch, count	Post accounting adjustments without approval
Country accountant	Post, reconcile, close periods	View another company's private payroll without scope
Group analyst	Read approved reports across companies	Edit local masters or post vouchers
Implementation consultant	Configure in a controlled project company	Work around tenant/company permissions

Evidence and negative cases

Record the company ID, currency, financial year, branch, warehouse, role assignment, and expected access. Test that a Riyadh user cannot edit an unrelated India company, that a closed period refuses a posting, and that a branch transfer cannot be mistaken for an inter-company sale.

Status: The Academy describes the design and the repository's known controls. Country-specific statutory configuration and a runtime walkthrough must be verified against the deployed OSERP release.