Purchase Requisition (PR)

What is a Purchase Requisition?

A Purchase Requisition (PR) is the internal document that formally starts the procurement cycle. It is raised by the department or employee with the actual need — not by procurement itself — and states what is needed, how much, by when, and against which budget. A PR creates no external commitment; it only becomes a binding obligation to a vendor once it is approved and converted into a sourced Purchase Order.

The PR-to-PO separation is a deliberate control, not bureaucratic overhead. It keeps the person who wants something separate from the person who authorises company money to buy it, and it creates the first auditable record in the chain that a three-way match and later a procurement audit will trace back to.

What a well-formed PR contains

• Item or service description — specific enough that procurement can source it without a follow-up clarification round
• Quantity and unit of measure
• Required-by date — drives whether standard sourcing or expedited/emergency procurement applies
• Cost center and budget line — links the spend to a real, checkable budget
• Business justification — the "why," which is what an approver actually evaluates
• Preferred or suggested vendor, if any, and whether it's a repeat purchase or new sourcing

The requisition-to-PO workflow

• Raise — requester submits the PR with the fields above
• Budget check — validated against the cost center's remaining budget before it goes further
• Approve — routed through the DOA matrix, one or more levels depending on value and category
• Source — procurement selects or solicits vendors, often via RFQ for anything above a threshold value or without an existing preferred vendor
• Convert to PO — the approved PR becomes the basis of the PO sent to the winning vendor

Why PR discipline matters more than it looks like it should

Weak PR discipline shows up downstream, not at the point of failure. A PO raised without a proper PR behind it is one of the first things a procurement audit flags — it means spend authorisation happened informally, off the record, or after the fact. A PR with a vague description pushes ambiguity into sourcing, where it becomes harder and more expensive to fix. And a PR with no budget check creates the kind of overspend that only surfaces at month-end reconciliation, well after the commitment was already made.

Common PR failures

• Retroactive PRs — raised after the PO or even after the purchase, purely to satisfy an audit trail requirement, defeating the point of prior authorisation
• Vague specifications — "office supplies, various" instead of itemised needs, forcing procurement to chase clarification
• No budget linkage — approved on business justification alone, with the budget check happening (or failing) only at invoice time
• Approval bypass for "urgent" purchases — a legitimate emergency-procurement path exists in most policies; using "urgent" as a routine excuse to skip approval defeats the DOA matrix entirely

How TRAXX handles Purchase Requisitions

• Structured PR form enforcing the fields above — no free-text-only requests
• Live budget-remaining check at submission, not discovered later at invoice time
• Automatic routing through the configured DOA matrix, with visible status at every stage
• Direct PR-to-PO conversion, preserving the link for later matching and audit trace-back

Last updated: 2026-04-29