CBHC
Multi-company procurement across six Priority companies
A group of organizations adopted one procurement model — with every approved order opening automatically in the Priority company of the organization it belongs to.
- Priority ERP
- Procurement
- Multi-company
- Budget control
- Sector
- Group of organizations
- Status
- Running in full production across six Priority companies.
The challenge
A group in which each organization runs its own Priority company faces a question with no good default answer: how to hold one procurement process without merging the organizations. When each works separately, each develops its own practice — and nobody can say what is happening at group level.
Why a standard implementation was not enough
Each organization could work directly in the ERP, but the requisitioners are role-holders in those organizations rather than ERP users, and the requirement that every procurement line carry its own budget item makes direct entry error-prone. A separate system per organization could be built, but that reproduces exactly the same fragmentation.
Architectural approach
One procurement application above six separate Priority companies. The user is identified by their organizational association, and what they may see and select follows from it: they choose the budget item through a multi-level budget tree whose final level is derived automatically from the one before it. The order passes approval according to the approver's authority, and only then is a purchase order opened in that organization's Priority company — not in any other.
What was delivered
- One procurement model across six separate Priority companies
- Budget-item selection through a multi-level budget tree
- User identification by organizational association
- Order approval according to approver authority
- Automatic purchase-order creation in the correct Priority company
- Budget control on an annual cumulative basis
- User and permission management by budget-tree level