How it works
Seven stages, each with a control and an artefact
A procurement event in VEYRA is not a single transaction. It is a sequence of controlled steps, each producing evidence that supports the next.
Simulation
Advance through a demonstration event
Move through the stages to see who acts, what they do, which control applies and what evidence is produced.
This is a front-end demonstration only. It does not process real tenders, transmit data to suppliers, or create binding commercial documents. All names and values shown are illustrative.
Demonstration mode
Stage 1 of 7 — illustrative only, no real tender is processed.
Stage 01
Configure buyer policy and authorities
Configuration happens once and is maintained centrally. Thresholds are expressed by value, category and department so approval routing does not need to be decided event by event.
- Role
- Chief Financial Officer and Procurement Manager
- Action
- Load the delegation of authority matrix, category taxonomy, standard quote conditions and evaluation settings, including any Indigenous or social procurement considerations.
- Control
- No event can be released outside the configured policy settings.
- Evidence produced
- Policy configuration record with version and authorising role.
Principles behind the sequence
Why the order matters
Each stage constrains what is possible in the next. Skipping a step removes a control and weakens the evidence produced at the end.
Configure before you buy
Qualify before you release
Evidence as you go
See the real workflow, configured to your policy
A guided demonstration uses your delegation thresholds and category structure so the process reflects how your organisation actually buys.