03 / My role
Contribution to the customization
- Configure native company and branch structures
- Integrate purchase allocation with budget tracking
- Test access boundaries and financial workflows across eight contexts
Personal Project · Odoo 18 Community
Organization / Purchase / Budget
Texarium · Multi-company, Branches & Budgets
Indonesia and Singapore company structures with branches and company-scoped purchasing budgets in Texarium on Odoo 18.
Odoo 18 CommunityTexariumPythonPostgreSQL
Texarium on Odoo 18 Community
View all Texarium videos →01 / Overview
The project context.
Indonesia and Singapore company structures with branches and company-scoped purchasing budgets in Texarium on Odoo 18.
Part of Texarium ERP, an independent learning and portfolio project developed and tested locally.
Business problem
Business units need separate company access, approval hierarchies and budget visibility.
02 / Key requirements
What the workflow needed to handle.
- 01Indonesia and Singapore companies
- 02Multiple branches in each country
- 03Company-scoped approvals
- 04Planned, committed, actual and available budget
04 / Solution
The Odoo approach
- Purchase commitments remain until billing or explicit commitment closure.
- Stock purchase budget actual comes from posted vendor bills; receipt valuation is not counted twice.
05 / Technical implementation
Relevant technical areas.
res.companypurchase.order.lineaccount.move.linecompany record rules
06 / Challenges
Technical considerations
- Preserve company isolation
- Distinguish purchase budget from inventory valuation
07 / Result & impact
Qualitative outcomes
- Saved eight-context budget and finance validations; integrated budget5m, actual2.25m and available2.75m.
08 / Technologies & modules
Technology focus.
Odoo 18 CommunityTexariumPythonPostgreSQL
Back to Projects