This is a temporary site for Procure.az. Official site: procure.az

Multi-step role-based approvals — Your delegation of authority, enforced by the system

Live Last updated:

Every procurement follows the approval route its value, category and legal entity require, and cannot skip a step.

The country’s largest companies trust us with their procurement

SOCARSOCAR UpstreamSOCAR MidstreamSOCAR DownstreamSOCAR «Azneft» İBSOCAR «Azərkimya» İBAzəriqazKapital BankPASHA BankPASHA HoldingPASHA InsurancePAŞA Həyat

Multi-step role-based approvals — your delegation of authority, enforced by the system

Role-based approval workflows let buying organisations encode their delegation of authority directly into the procurement system, so every requisition, sourcing event or award follows the exact route its value, category and legal entity require. Built on a modular architecture, approval routes are configured around your own thresholds and organisational structure rather than a generic template. Steps can run sequentially or in parallel, roles rather than named individuals hold approval authority so that staff changes never break the chain, and stand-ins cover absences automatically. Segregation of duties is enforced by design: the person who raises a requirement cannot approve its award, and that control is structural rather than procedural — it cannot be bypassed by editing a record or reassigning a task informally. Every decision made within the workflow is timestamped and attributed to the approver who made it, and any reversal is recorded as a new step with a stated reason rather than an overwrite of the original. This gives auditors a complete, tamper-evident trail from first request to contract award without any additional effort from the procurement team. Reminders and escalation rules fire automatically when a step goes stale, so timelines stay on track without manual chasing. Because the module sits within a single digital system that covers the full procurement lifecycle — from supplier identification through to contract awarding — an approved requirement moves directly into sourcing or award without re-keying data, eliminating the gaps and handoff errors that arise when approval and sourcing tools are separate.

Why teams choose approval workflows on Procure.az

Your delegation of authority is enforced by the system, not by individual discipline or memory, so policy is applied consistently regardless of who is handling a transaction.

Approval routes adapt automatically to combinations of value threshold, spend category, legal entity and budget owner, removing manual routing decisions and the errors they introduce.

Role-based assignments mean a staff change, vacancy or unplanned absence never stalls a procurement — stand-ins inherit queues automatically and delegation can be set in advance.

Segregation of duties is built in structurally: raisers and approvers are always distinct, reducing fraud risk and conflict-of-interest exposure without relying on procedural controls.

A full, timestamped audit trail — including stated reasons for every rejection and reversal — supports internal audit, external review and regulatory compliance without generating extra administrative work.

Automatic reminders and escalation to a configured fallback role keep approvals moving and ensure that a stale step is surfaced and resolved rather than silently delaying the procurement.

What the approval workflow module does

Configurable routing rules

Routes are built from combinations of value thresholds, spend category, legal entity and budget owner. Each combination can produce a different approval chain, so a low-value consumable and a high-value services contract follow entirely different paths without any manual intervention.

Sequential and parallel steps

Some approvals must happen in strict order; others can run simultaneously to save time. The module supports both patterns within the same workflow, and the two can be mixed across different stages of a single procurement.

Role-based assignment with delegation and stand-ins

Approval authority belongs to a role, not a named person. When someone is absent, a stand-in inherits their queue automatically. Delegation can be set in advance, so no approval step is ever blocked by a holiday or a vacancy.

Enforced segregation of duties

The system prevents the person who raised a requirement from approving its award. This control is structural, not procedural — it cannot be bypassed by editing a record or reassigning a task informally.

Timestamped, attributed audit trail

Every approval decision — granted, rejected or reversed — is recorded with a timestamp and the identity of the approver. A reversal is not an edit; it is a new step that requires a stated reason, preserving the full history of every decision.

Reminders and escalation

When an approval step goes stale, the system fires reminders to the responsible role and, if the step remains unactioned, escalates to a defined fallback. Procurement timelines stay on track without manual chasing.

How an approval workflow runs in practice

  1. A buyer raises a requirement. The system reads its value, category, legal entity and budget owner, then selects the matching approval route automatically.
  2. The first approval step — sequential or parallel — is assigned to the relevant role. Named individuals holding that role receive a notification and can act from within the platform.
  3. If a step goes unanswered, reminders fire on schedule. Continued inaction triggers escalation to the configured fallback role, keeping the process moving.
  4. Each approver reviews the submission, then grants or rejects it. A rejection requires a stated reason and returns the item to the raiser; a reversal of an earlier decision is logged as a new step, not an edit.
  5. Once all required steps are complete, the procurement advances — to sourcing, award or contract — and the full approval chain is preserved in the audit trail alongside every other system-recorded event.

Frequently asked questions

Can we have different approval chains for different legal entities within the same organisation?

Yes. Routes are built from combinations of value threshold, category, legal entity and budget owner, so each legal entity in your group can have its own distinct chain without overlap or conflict with others in the same organisation.

What happens if the designated approver is on leave and no stand-in has been set?

The escalation rule fires after the configured stale period and routes the step to the fallback role defined during setup. Configuring stand-ins in advance is strongly recommended, but the escalation path ensures no approval is permanently blocked by an unplanned absence.

How does the system prevent the person who raised a requirement from approving it?

Segregation of duties is enforced structurally: the platform will not present an approval action to a user whose identity matches the raiser of that requirement. The control cannot be circumvented by reassigning roles informally or editing a record.

Is it possible to reverse an approval that has already been granted, and what is recorded when that happens?

A reversal is permitted but is treated as a new approval step, not an edit to the original decision. The approver must supply a stated reason, and the reversal is timestamped and attributed in the audit trail alongside the original grant, so the full decision history is preserved.

How do approval workflows connect to the rest of the procurement process?

The approval workflow module is part of a single digital system that covers the procurement lifecycle from supplier identification through to contract awarding. Once all required approval steps are complete, the requirement moves directly into sourcing or award without re-keying data, eliminating handoff errors that arise when approval and sourcing tools are kept separate.

See your delegation of authority in action

Talk to the Procure.az team about configuring approval workflows that match your organisation's structure, thresholds and compliance requirements.

Request a demo

Talk this through against your own process

Fill in the short form and we’ll tailor a demo to how you buy.

Book a demo slot

All information is protected by our Privacy Policy.