4.2 Requisition-to-PO workflow for indirect procurement

Without a structured process, indirect procurement can suffer from “maverick spend”—unmanaged purchases, unapproved external services, and invoices that are difficult for Finance to reconcile. The Requisition-to-PO workflow provides a necessary and auditable path to convert a factory need into a formal corporate commitment.

The input gate: mandatory data

A Purchase Requisition (PR) initiates the procurement process. Ensuring the data is accurate upfront prevents delays later in the purchasing cycle.

Essential Elements of a Complete PR:

Clear Specification: The exact Manufacturer Part Number (MPN), a direct vendor web link, or a detailed Statement of Work (SOW). Vague descriptions should be returned for clarification.
Required Date: A clear calendar date indicating when the goods or services are needed.
Cost Center: The appropriate ERP budget code (e.g. Dept-901-Maintenance) that will absorb the cost.
Suggested Vendor: Providing supplier info or a direct link accelerates the buying process.
Budget Owner: The individual with P&L responsibility for the specified cost center.

The standard workflow

Establishing a standardized path helps efficiently process requests from “Need identification” to “Payment.”

Step 1: requisition (the user)

The Action: The requestor submits a formal PR in the ERP or E-Procurement system.
The Gate: The system automatically validates the budget code and required data fields.

Step 2: sourcing (the buyer)

The Action: The Indirect Buyer reviews the request.
- For Catalog Items: Confirms the request aligns with pre-negotiated corporate contracts.
- For New/Custom Items: Collects competitive quotes (if value dictates) or verifies the engineering justification for a single-source request.
The Output: Cost and vendor lead time are confirmed and updated in the Purchase Requisition (PR).

Step 3: financial approval (management)

The Action: The ERP routes the Purchase Requisition (PR) to the appropriate approver based on the Delegation of Authority (DoA) limits.
The Decision: Budget is verified, and the Purchase Requisition (PR) is formally approved or returned for review.

Step 4: PO generation (the system)

The Action: The approved Purchase Requisition (PR) converts into a legally binding Purchase Order (PO).
The Output: The Purchase Order (PO) document is transmitted to the vendor.

Step 5: goods receipt (warehouse/user)

The Action: Physical receipt of goods at the dock, or a digital “Service Entry” sign-off by the budget owner to confirm contracted labor was completed.
The Guideline: Payment should not be processed without confirmation of receipt.

Step 6: the 3-way match (accounts payable)

The Logic: Finance matches the Purchase Order (PO) Price, the System Receipt Quantity, and the Vendor Invoice.
The Result: If they match, payment is released. If there are discrepancies, the invoice is held for investigation.

The approval matrix (delegation of authority)

A structured Delegation of Authority (DoA) balances operational speed with appropriate financial oversight.

Threshold Value	Financial Scale	Expected Approver	Preferred SLA
< $$$500	Incidental	Shift Lead or Auto-Approval	Same Day
$$$500 – $$$2,500	Operational	Department Manager	< 24 Hours
$$$2,500 – $$$10k	Significant	Department Director	< 48 Hours
> $$$10k	Strategic	VP Operations + Controller	< 1 Week
Any IT Hardware	Cybersecurity	Global IT Management	Variable

The “no PO, no pay” guideline

Suppliers should be encouraged to align with systematic ERP processes.

The Guideline: Vendor invoices submitted to Accounts Payable without a valid, pre-approved PO number should generally be returned unpaid.

The Rationale: Bypassing this control validates unmanaged spend and encourages external vendors to circumvent internal procurement processes. Processing invoices without POs makes budget management highly inaccurate.

Handling exceptions

Operational realities occasionally necessitate deviations from the standard flow. These exception paths must be defined and controlled.

The “line down emergency” (after-hours)

The Scenario: An urgent facility failure (e.g. a burst pipe at 2:00 AM) requires immediate contractor response.
The Protocol:
- A controlled Corporate P-Card must be utilized if necessary to authorize the work.
- The Follow-up: The requestor must submit a formal “Post-Facto PR” the next business day with all receipts and service documentation attached.

The post-facto PR

The Scenario: Goods or services were ordered verbally by an employee without a PO, and an invoice arrives at AP.
The Protocol:
- Standard practice should not involve creating a silent PO just to clear the invoice.
- The responsible employee must be required to create a formalized PR, which should be routed through their management for transparency regarding the policy deviation.

Recap: Requisition-to-PO Workflow for Indirect Procurement

Parameter	Requirement	Action	Condition
Purchase Requisition (PR) Specification	MPN, vendor link, or detailed SOW. Vague descriptions are rejected.	Submit formal PR in ERP.	System validates budget code & data fields.
Financial Approval	Must align with Delegation of Authority (DoA) matrix based on value.	Route PR to approver per DoA.	Budget verified; PR approved or returned.
PO Generation	Approved PR converts to a legally binding PO.	Transmit PO to vendor.	PR must be fully approved.
Goods/Service Receipt	Physical receipt or digital Service Entry sign-off required.	Confirm receipt in system.	Mandatory prior to payment processing.
Invoice Payment (3-Way Match)	PO price, receipt quantity, and vendor invoice must match.	Release payment if match; hold for investigation if discrepancy.	Invoice must reference a valid, pre-approved PO.