Vercentlabs

Glossary

LEXICON / TERM

Purchase Requisition

An internal request to buy goods or services, the first step in a governed procure-to-pay process before sourcing or a purchase order exists.

Author
Vercentlabs Product Team
Published
August 7, 2026
Reviewed
August 7, 2026
01

Definition

A purchase requisition is an internal request from an employee or department to buy goods or services — the starting document in a procurement process, distinct from the purchase order that later goes to a supplier.

02

Why it matters

Requiring a requisition before a purchase order gives an organisation a governed checkpoint — someone requests, someone else (by policy) approves — rather than any employee committing company spend directly to a supplier.

03

How it works

A requisition typically moves through a state machine (draft, submitted, approved, executed) before it can become a purchase order, with the option to route through competitive sourcing (RFQ/bids) for larger or non-routine spend.

04

Example

An employee drafts a requisition for replacement equipment; it's submitted, approved by a designated approver (not the requester), and only then does a buyer convert it into a purchase order sent to a supplier.

VERCENTLABS / APPLICATION

How the term becomes an operating control.

A requisition in Vercentlabs is drafted and submitted, entering a governed draft → submit → approve → execute state machine, with self-approval blocked structurally at every stage — the same person who creates a supplier, purchase order, or receipt cannot also approve or qualify it.

Open Procure to Pay runbook →

Lexicon cross-reference

Related terms

CTA

See how Vercentlabs implements Purchase Requisition on your own data.

Book a Demo

See it on your workflow

30-minute working session

Book a Demo