Multi Branch Operations

Companies with several branches need to separate operations and reports per branch without creating separate companies. This module adds a Branch master record and a branch field on partners, products, sales, purchases, transfers, warehouses, journals, accounts, moves and payments. Administrators define branches and assign them to users, and record rules limit what each user sees. It plugs into the Sales, Purchase, Inventory and Accounting apps and their reports. Consistency checks stop documents from mixing records of different branches. The benefit is branch-level control and analysis inside one company.

1. 1

   Define branches

   The administrator opens the Branches list and creates a branch with name, company, address, phone, email and website. The form has a Contact Information section and a search view that groups by company. Each branch belongs to one company.

   • Fields: Branch, Company, Address, Phone, Email, Website
   • Search grouped by Company
2. 2

   Assign branches to users

   On the user form a Multi Branches tab holds Allowed Branches and a Default Branch. A constraint rejects a default branch that is not among the allowed ones. Record rules use these fields to filter data.

   • Fields: Allowed Branches, Default Branch
   • Constraint on default branch
3. 3

   Branch on sales and purchases

   Sale and purchase orders get a Branch field taken from the user's default branch, with order lines following the order. Checks warn if the customer, vendor or a product belongs to another branch and raise an Unauthorised Branch error. The warehouse or picking type follows the branch.

   • Branch field on orders and lines
   • Consistency checks on partner and product
   • Warehouse follows the branch
4. 4

   Branch on stock

   Warehouses, picking types, transfers, stock moves, move lines and valuation layers carry a branch field. The branch of a transfer is computed from its picking type. Inventory reports and valuation can then be read per branch.

   • Branch on warehouse and picking type
   • Computed branch on transfers
   • Stored on moves and valuation layers
5. 5

   Branch on accounting

   Journals, accounts, journal entries, entry lines and payments have a branch. Checks block entries whose lines use accounts of a different branch and payments that belong to another branch, and the payment register wizard follows the branch. Journals are suggested according to the branch.

   • Branch on journals, accounts, moves, payments
   • Checks against mixed-branch entries
   • Payment register follows the branch
6. 6

   Branch access rules

   Record rules defined in the module restrict documents to the user's allowed branches, using the allowed branch lists computed on partners, products and orders. Users therefore see only their branch data. Administrators keep a wider view.

   • Record rules per allowed branch
   • Allowed branches computed on documents
7. 7

   Branch in analysis reports

   The sales, purchase and invoice analysis reports gain a Branch field. Managers group and filter these reports by branch to compare performance. Report headers also use branch data where relevant.

   • Branch in sales, purchase and invoice analysis
   • Group and filter by branch

Back to version applications