Platform
VEYRA Approval Engine
Approval is not an email chain. Each commitment is routed through the organisation's delegated authority, and the approver, the reason and the time are retained with the decision.
Routing
What decides who approves
Routing is derived from the request itself, so it cannot be bypassed by sending it to a different person.
- Value of the commitment against the requester's own authority.
- Category, where certain categories require a specialist approver.
- Cost centre and budget position, including remaining uncommitted allocation.
- Site and project, where local authority applies.
- Procurement method, where a structured RFQ carries its own approval requirement.
- Policy exceptions, which require a stated reason and an entitled role.
Sequence
From request to authorised commitment
Approval chain · sample
The CFO step is added above $100,000 in this demonstration policy.
Authority test
Expected route
- User
- Maintenance Planner
- Category
- Mechanical consumables
- Site
- Site A
- Route
- Manager → Procurement
- 01
Request raised
Structured, attributed to a site, project and cost centre.
- 02
Controls evaluated
The Procurement Control Engine determines authority, budget and method.
- 03
Approval chain built
Steps are created in order, with each approver's limit checked.
- 04
Decisions recorded
Approve or decline, with commentary, against the specific step.
- 05
Award approval
Where the award itself requires authorisation, it is approved separately from publication.
- 06
Commitment proceeds
Only when every step is complete.
Segregation of duties
The person who raises a request, the person who approves it and the person who awards it can be required to be different people. Where an organisation permits an overlap, that permission is itself a recorded configuration.
Temporary delegation
Authority can be delegated for a defined period — leave, secondment, shutdown — with a start and end date. The delegation expires on its own and can be revoked early. Both the grant and the revocation are audited.
Authority test mode
Before go-live, an administrator can test a hypothetical purchase — user, category, site, value — and see exactly which limits apply and who would be asked to approve it, without creating a request.
Enforcement
Where the rules are applied
On the server
At the record level
With human authority
Approval configuration reflects the rules your organisation sets. VEYRA does not provide financial, legal or procurement advice on what those rules should be.
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.