Krayuv

Approval matrix, routing rules, and an approver inbox

Procurement approval workflow software for requisitions, POs, and invoices

Procurement approval workflow software routes purchase requests, purchase orders, contracts, invoices and payments to the right approvers, in the right order, and keeps a record of every decision. In Krayuv, you define multi-step workflows with routing rules, test which workflow a record would follow, and let approvers act from a single inbox.

Requisition
Approval
Purchase order
Supplier
Delivery
Invoice
Reconciliation

What you get

  • Multi-step workflows

    Chain approvers in order, with all-must-approve or any-one-approves at each step.

  • Conditional routing

    Rules by value or type, with priority and a default workflow.

  • Approval inbox

    Preview, approve or reject with notes, delegate, and view a timeline.

  • Approval history

    Who approved, at which step, with notes and date, kept on the document.

01

What procurement approval workflow software does

Procurement approval workflow software replaces forwarded emails and signature sheets with defined approval paths, so each purchase document reaches the right people and the outcome is recorded.

Approval is where many purchases slow down. A requisition waits in an inbox, nobody is sure who must sign a high-value order, and a manager on leave blocks everything behind them. Later, an auditor asks who approved a purchase and the answer is a search through email.

A workflow system turns the approval matrix, meaning the rules about who approves what, into configuration. Documents follow the matrix automatically, approvers see only what is waiting for them, and the history stays on the record. It operates across the procure-to-pay flow, from request to payment.

02

What can be routed for approval

Krayuv applies approval workflows across the documents that commit money or change a commitment, so a single approach covers the whole chain.

  • Purchase requisitions, including consolidated requisitions
  • Purchase orders and their amendments
  • Contracts
  • Goods receipt notes
  • Invoices, including those from invoice matching
  • Payments
  • Supplier catalogs submitted for approval

Approvals on a requisition carry an approval history, and the same pattern applies to later documents. For the difference between the first two documents in the chain, see purchase requisition vs purchase order.

03

How to build an approval matrix

An approval matrix is the set of rules that decides who approves a purchase document, based on conditions such as its value or type.

  1. Step 1: List the document types

    Decide which of requisitions, POs, contracts, receipts, invoices and payments need approval.

  2. Step 2: Define the conditions

    Choose what changes the route, for example the value or the type of request.

  3. Step 3: Design the steps

    For each route, set the approvers in order and decide whether each step needs all approvers or any one.

  4. Step 4: Set priority and a default

    Order the rules by priority and set a default workflow for anything that matches no rule.

  5. Step 5: Test before you rely on it

    Use the test or simulate option to see which workflow a given record would match.

  6. Step 6: Review regularly

    Adjust the matrix when roles, limits or locations change.

Keep the first version simple. Most teams start with a few value bands and a default route, then add conditions as real exceptions appear.

04

Routing rules, steps, and approver choices

Each workflow has one or more steps, and every step is set to one of two modes. In an all-must-approve step, every listed approver has to agree. In an any-one-approves step, a single approval moves the document on. This lets you require two signatories for sensitive items and a single reviewer for routine ones.

Routing rules decide which workflow applies to a record. They use conditions such as value or request type, carry a priority, and fall back to a default when nothing matches. Because the test option shows the matched workflow for a sample record, you can find gaps before they affect live requests.

Step modes and when to use them
Step modeHow it behavesUse it for
All must approveEvery approver in the step has to approveHigh-value or high-risk items needing joint sign-off
Any one approvesThe first approval moves it forwardRoutine items where any authorized reviewer can act
Multiple stepsSteps run in order, one after anotherChains such as department head, then finance, then director
05

The approver inbox and delegation

Approvers work from an Approval Inbox that lists what is waiting for them, with the history of what they have already handled.

From the inbox, an approver can preview a document, approve or reject it with notes, and delegate it to someone else. A timeline view shows where the document sits in its workflow. Delegation matters in practice, since leave and travel are the most common causes of stalled approvals.

Approvers include anyone named in a workflow step, not only procurement staff. A site manager, a finance reviewer and a department head can all act on the same chain without needing access to everything else. Users see a role-based in-app alert ticker for activity relevant to them. Krayuv does not currently send approval requests by email, so approvers should check the inbox.

06

Approval history and audit

Every approval records who acted, at which step, what they decided, any notes and the date. This approval trail appears on purchase requisitions, purchase orders, invoices and payments. Purchase order amendments keep a revision history, and contracts keep version history.

That gives finance and internal audit a way to answer who approved this, and on what basis, without reconstructing it from messages. It also supports clean handovers: a new approver or buyer can read the history on a document and understand what already happened.

  • Approver, step, action, notes and date on each decision
  • Approval history visible on the document
  • PO revision history for amendments
  • Contract version history
07

Where approvals sit in the buying flow

A typical chain starts with a purchase requisition from a department or site, with its type, criticality, required-by date, budget and cost center. Approved requisitions can be consolidated by a buyer, and the consolidation itself goes for approval before it becomes an auction or one or more purchase orders. The purchase order is approved, sent to the supplier, received against, invoiced, matched, approved and finally scheduled for payment, which has its own approval.

Sourcing sits alongside this. A purchase can come from an RFQ or an auction win before the order is raised. The wider Source-to-Pay page shows the full sequence.

08

How to evaluate approval workflow software

  • Can you set conditions, priorities and a default route, and test them before going live?
  • Does it support both all-must-approve and any-one-approves steps?
  • Can approvers delegate, and is there a clear inbox for pending and past items?
  • Does one system cover requisitions, POs, contracts, receipts, invoices and payments?
  • Is there an approval history on the document itself?
  • Does the supplier side, such as catalog approval, use the same engine?
  • Is it clear how approvers are notified, and does that suit your teams?

For a view of how approval time shows up in reporting, see procurement analytics, which tracks cycle times from requisition to order and approval compliance. Related reading includes what is procurement software.

Approval workflow software vs email approvals

Approval workflow software compared with approvals by email and signature
Approval workflow softwareEmail and signature sheets
RoutingRules send each document to the right stepsThe requester decides who to forward to
VisibilityApprover inbox and timeline of pending itemsStatus known only by asking
Cover for absenceDelegation and any-one stepsWork waits for the person to return
RecordApprover, step, notes and date on the documentSearching email threads later
ConsistencySame matrix applied to every requestVaries by requester and manager
CoverageRequisitions through to paymentsUsually only some documents

Frequently asked questions

What is procurement approval workflow software?

It is software that routes purchase requests, orders, contracts, invoices and payments through defined approval steps and keeps a record of each decision, replacing email and paper approvals.

What is an approval matrix in procurement?

An approval matrix is the set of rules that states who must approve a purchase document, usually based on conditions such as value or type. Krayuv expresses it as routing rules with priority and a default workflow.

Which documents can go through approval?

Purchase requisitions, purchase orders, contracts, goods receipt notes, invoices, payments and supplier catalogs.

Can a step need more than one approver?

Yes. Each step is set as either all must approve or any one approves, and a workflow can have several steps in order.

Can I test a workflow before using it?

Yes. You can simulate which workflow a record would match, which helps you catch gaps in the rules before live requests are affected.

What happens when an approver is away?

Approvers can delegate items from the Approval Inbox. You can also design any-one steps with several approvers so one absence does not stop the request.

Is there an approval audit trail?

Yes. Approval history records who acted, the step, the action, notes and date, on requisitions, purchase orders, invoices and payments. Purchase orders also keep revision history for amendments.

Does it check the budget automatically?

No. Requisitions carry a budget, cost center and GL code entered by the requester, but there is no automatic budget check. Use an approval step to apply budget review.

How are approvers notified?

Approvers see pending items in the Approval Inbox and a role-based in-app alert ticker. Approval requests are not sent by email at present.

Map your approval matrix in Krayuv

Share how approvals work today. We'll configure a sample workflow with routing rules and show the inbox from the approver's side.