Home > > > PR vs PO: Two Documents, One Control Gate

PR vs PO: Two Documents, One Control Gate

Author : purchase pro | Published On : 21 Sep 2026

A Purchase Requisition (PR) asks for permission to buy.

A Purchase Order (PO) makes the purchase.

The two documents can look similar on paper. Both may contain items, quantities, vendors and dates. But they sit on opposite sides of one of the most important controls in procurement.

A purchase requisition is an internal request. A purchase order is the formal purchasing commitment sent to a supplier.

Understanding the difference between PR vs PO helps organisations separate two decisions:

Should we buy this?

and

How should we buy it?

 

 

What Is a Purchase Requisition?

A Purchase Requisition (PR) is an internal document used to request approval for a purchase.

For example:

  • Production needs raw material.

  • IT needs laptops.

  • Maintenance needs spare parts.

  • Administration needs office supplies.

The requester raises a PR explaining:

  • What is required

  • Quantity

  • When it is required

  • Why it is required

  • Requesting department

The requisition then moves through the organisation's approval process.

The supplier does not receive the PR.

In simple terms:

PR = Request

The source article describes the PR as an internal request that stays within the organisation and goes through internal approval.

 

 

What Is a Purchase Order?

A Purchase Order (PO) is the formal purchasing document issued to the supplier.

Once the purchase has been approved, procurement determines:

  • Which supplier to use

  • What price applies

  • What quantity is being ordered

  • What delivery terms apply

  • When delivery is expected

  • What commercial conditions apply

The PO is then sent to the supplier.

Once accepted, it becomes the formal purchasing commitment.

In simple terms:

PO = Commitment

The source article describes the PO as external: it goes to the supplier, goods move against it and invoices reference it.

 

 

PR vs PO: What's the Difference?

The easiest way to understand PR vs PO is to look at their purpose.

Feature

Purchase Requisition (PR)

Purchase Order (PO)

Purpose

Request approval to buy

Commit to the purchase

Created by

Requesting department / employee

Procurement / purchasing team

Direction

Internal

External

Supplier sees it?

No

Yes

Main question

Should we buy?

How should we buy?

Approval

Internal approval

Based on approved requirement and commercial terms

Supplier commitment

No

Yes

Commercial terms

Usually not the final supplier commitment

Specifies agreed purchasing terms

Audit purpose

Shows purchase authorization

Shows supplier commitment

Workflow position

Before PO

After approved PR

The core distinction can be reduced to one sentence:

A PR is a request made inside the organisation; a PO is a commitment made outside it.

 

 

Why Are PR and PO Separate?

The two documents exist because two different decisions need to be made.

Decision 1: Should we spend the money?

This is the approval question.

The organisation needs to determine:

  • Is the need real?

  • Is the timing right?

  • Is the requested quantity justified?

  • Is the budget available?

This decision belongs to the relevant cost-centre owner or approving authority.

Decision 2: How should we spend the money?

Once the requirement has been approved, procurement determines:

  • Which supplier?

  • At what rate?

  • Which delivery date?

  • What commercial terms?

This requires supplier knowledge, rate information and category expertise.

The source article explicitly separates these two decisions between the cost-centre owner and procurement.

 

 

What Happens When PR and PO Decisions Collapse?

When the two decisions are combined into one step, procurement controls can weaken.

For example:

The person requesting the purchase may end up selecting the supplier without procurement's category knowledge.

Or procurement may end up deciding whether the purchase itself is justified without the operational context of the requesting department.

The source article identifies both as potential consequences of collapsing the two decisions.

The separation therefore creates a basic control:

The right decision goes to the right person before money leaves the organisation.

 

 

When Should a Purchase Requisition Be Required?

Not every purchase necessarily needs a PR.

The source article identifies examples such as:

  • Petty cash

  • Standing orders for recurring consumables

  • Emergency repairs

as situations that may not require the same PR treatment.

However, the purchasing policy should clearly define the threshold.

Examples mentioned in the article include:

  • New vendors

  • Purchases above a defined value threshold

  • Spending outside an approved category

The important point is not that every transaction must follow exactly the same process.

The important point is that the organisation should define where the approval gate applies.

 

 

Three Rules for a Clean PR-to-PO Workflow

Once the approval threshold is established, three disciplines help maintain the PR to PO process.

1. Auto-convert approved PRs to POs

Procurement should not manually retype information that the requester has already entered.

An approved PR should populate the PO with the relevant item details.

Procurement then adds the required supplier and commercial information.

This reduces duplicate data entry and keeps the approved requirement connected to the resulting PO.

 

 

2. Never Raise a PO Without a PR

If the PR is the approval gate, creating a PO directly can bypass that control.

A useful exception report should therefore identify:

POs without a parent PR

This gives procurement and finance teams a way to identify purchases that may have bypassed the intended approval process.

The source article explicitly recommends tracking open POs without a parent PR as an exception.

 

 

3. Close Cancelled PRs

An approved PR that is later cancelled should not remain open indefinitely.

For example, if a PR was created for 500 units and the requirement is later cancelled, leaving the PR open can distort the organisation's view of open commitments.

It can also create confusion downstream, including during the GRN process.

The source article recommends formally closing cancelled PRs to keep commitments and downstream workflows accurate.

 

 

PR to PO Automation

A well-connected PR to PO process can automate the movement from approved requirement to supplier commitment.

A typical workflow is:

Purchase Need → PR Created → PR Approved → PO Generated → PO Sent to Supplier → Delivery → Invoice

The source article's visual on page 6 shows this workflow and highlights approval routing, automatic PO creation, exception alerts and audit-trail controls.

This is where purchase requisition software and procurement workflow automation can reduce manual work.

 

 

How PurchasePro Automates the PR-to-PO Workflow

According to the source article, PurchasePro:

  • Links PRs to POs

  • Routes approvals

  • Automatically converts approved PRs into POs

  • Flags unlinked POs as exceptions

  • Tracks the approval workflow

The result is a connected procurement trail from the initial request through supplier commitment.

The article positions this as a controlled workflow rather than simply document automation.

 

 

Why Linking PRs to POs Matters

Connecting the PR and PO creates a clearer audit trail.

It helps organisations:

  • Trace the purchase back to the original request

  • Confirm that approval happened

  • Identify POs created without proper approval

  • Reduce duplicate data entry

  • Improve budget control

  • Maintain procurement visibility

The source FAQ specifically states that linking PRs to POs creates an audit trail from request through approval to supplier commitment.

 

 

PR vs PO: Why the Control Gate Matters

The PR–PO distinction is not simply about maintaining two documents.

It separates two fundamentally different procurement decisions:

PR asks:

Should we buy?

PO asks:

How do we buy it?

The separation allows the requesting department to establish the business need while procurement handles supplier and commercial decisions.

That creates a clearer procurement workflow and makes it easier to identify exceptions.

 

 

What Happens If a PO Is Raised Without a PR?

If an organisation requires PR approval before purchase commitment, a PO without a parent PR should be treated as an exception.

It may indicate that the normal approval process was bypassed.

Instead of manually discovering these cases during an audit, organisations can track them through exception reporting.

This makes the PR to PO workflow easier to monitor continuously.

 

 

PR vs PO and Procurement Audit Trails

A connected PR and PO workflow creates a record of:

Request → Approval → Purchase Commitment

That trail can help procurement and finance teams understand:

  • Who requested the purchase

  • What was requested

  • Who approved it

  • Which supplier was selected

  • What commercial terms were applied

  • Which PO was created

The source article emphasizes that the paper trail should exist because the system maintains it rather than relying on someone to remember to file it.

 

 

Final Takeaway

The PR vs PO distinction is simple:

A Purchase Requisition requests permission to buy.

A Purchase Order creates the purchasing commitment.

The real value comes from keeping the two connected without making them the same thing.

Start with one procurement category.

Define when a PR is required.

Track POs without parent PRs.

Automatically convert approved PRs into POs where appropriate.

Close cancelled requisitions.

Then measure the exceptions.

As the source article concludes, the objective is to separate the “should we buy” decision from the “how do we buy” decision.

 

 

FAQs

1. What is the difference between a Purchase Requisition and a Purchase Order?

A Purchase Requisition is an internal request for approval to buy goods or services, while a Purchase Order is the formal document issued to the supplier to make the purchase. A PR requests approval; a PO creates the purchasing commitment.

2. What is a Purchase Requisition used for?

A Purchase Requisition communicates an internal purchasing need and obtains the required approval before spending money. It can include the requirement, quantity, expected delivery date, reason and requesting department.

3. What is a Purchase Order used for?

A Purchase Order formally communicates purchasing terms to a supplier, including supplier details, items, quantities, prices, delivery terms and other commercial conditions.

4. Should a Purchase Order be created before or after a Purchase Requisition?

A Purchase Requisition should normally be created and approved before the Purchase Order. The PR establishes authorization, while the PO converts the approved requirement into a supplier commitment.

5. Why should companies link PRs to POs?

Linking PRs to POs creates an audit trail from the original request through approval to supplier commitment. It can also help prevent unauthorized purchases and identify POs raised without proper approval.