Platform
VEYRA Procurement Control Engine
Decide who can buy, what they can buy, how much they can spend and who must approve it — before the commercial commitment is made.
How it evaluates
Ten tests, applied in order, on every request
A purchase request is not a message asking for permission. It is a record evaluated against the rules the organisation has already set, so the answer is consistent whoever raises it.
User
Role
Category
Site / Project
Cost Centre
Budget
Spend Limit
Procurement Method
Approval
Purchase
Where rules live
Rules can be set at any level of the organisation
A policy set at organisation level applies everywhere. A tighter rule at site, project or user level applies on top of it.
Worked example
A Tier-1 maintenance request, evaluated
Illustrative scenario using a fictional site and cost centre.
The request
- Requester
- Maintenance Planner
- Site
- Site A
- Cost centre
- MECH-402
- Allowed categories
- Mechanical consumables, bearings, lubricants and PPE
- User authority
- $20,000 ex GST
- Available budget
- $150,000 ex GST
- Request value
- $72,000 ex GST
What VEYRA determines
- Category
- Permitted
- Budget
- Available
- Authority
- Exceeded
- Method
- Structured RFQ
- Approval
- Department Manager → Procurement Manager
Illustrative scenario using a fictional site and cost centre. Figures are examples, not a customer outcome.
Households
The same architecture, without the enterprise complexity
A household sees three simple settings, not a delegation matrix.
- 01
A parent creates the household
- 02
A family member is added
- 03
Allowed categories: groceries, school supplies, household goods
- 04
Monthly budget: $2,400
- 05
Recorded spending: $1,425
- 06
Remaining before request: $975
- 07
Member authority: $100
- 08
$180 school supplies request needs owner approval
Enterprise
What larger organisations configure
- Delegated authority by value, category and department.
- Segregation of duties between requester, approver and awarder.
- Cost centres and budgets, with committed spend visible against each.
- Sites and projects, so spend is attributable to the work it supports.
- Procurement thresholds that decide when a structured RFQ is required.
- Supplier panels and category permissions.
- Policy exceptions recorded with a reason and an authorising role.
Why it matters
Control before commitment, not after
Fewer retrospective corrections
Consistent answers
Evidence by default
See a structured procurement event end to end
Request a guided demonstration and we will walk through configuration, supplier release, comparison, approval and the audit record produced.