Procurement cycle
The procurement cycle is the repeatable sequence a purchase follows from identified need to closed transaction: requisition, sourcing or quoting, purchase order, supplier confirmation, delivery and goods receipt, invoice matching, payment, and review. Mapping the cycle step by step exposes where requests stall, where data breaks, and which steps deserve automation first.
Examples
One part, one loop: An engineer requisitions 1,500 anodized heat sinks. The RFQ goes to three suppliers Monday and quotes return within a week ($6.10, $6.45, $7.20). The PO releases at $6.10, parts arrive in 8 weeks, receiving logs all 1,500, and the three-way match clears the invoice for payment on Net 45 terms.
Cycle-time audit: A buyer maps 90 days of POs and finds requisition-to-PO averages 11 days, of which 9 are approval queue. Moving approvals under $5,000 to a single approver cuts the average to 4 days without touching supplier lead time.
Definition
Most procurement work is not exotic; it is the same loop run thousands of times a year. A need surfaces and becomes a purchase requisition. If no contract or catalog price exists, a request for quote goes to suppliers. The award becomes a purchase order, the supplier confirms, goods arrive and are logged at goods receipt, the invoice is matched against order and receipt, payment is released, and performance data feeds the next cycle.
Two details separate clean cycles from messy ones. First, the match: checking invoice against PO against receipt catches price and quantity discrepancies before money leaves. Second, the review at the end: was the supplier on time, was the price right, should the next requisition route differently? Cycles that skip review repeat their mistakes on schedule.
The cycle also runs at wildly different clock speeds by step. A requisition approval might take 3 days, the RFQ 2 weeks, the supplier lead time 12 weeks, the invoice 60 days to pay. When teams map their cycle, the surprise is usually how much calendar time is internal queue time rather than supplier time.
Frequently asked questions
What is the procurement cycle?
The procurement cycle is the repeatable sequence a purchase follows from identified need to closed transaction: requisition, sourcing or quoting, purchase order, supplier confirmation, delivery and goods receipt, invoice matching, payment, and review. Most procurement work is this same loop run thousands of times a year.
What separates a clean procurement cycle from a messy one?
Two details separate clean procurement cycles from messy ones. The three-way match between invoice, purchase order, and receipt catches price and quantity discrepancies before money leaves, and the closing review asks whether the supplier was on time, the price was right, and the next requisition should route differently. Cycles that skip the review repeat their mistakes on schedule.
Where does the time actually go in a procurement cycle?
The procurement cycle runs at wildly different clock speeds by step: a requisition approval might take 3 days, the RFQ 2 weeks, supplier lead time 12 weeks, and the invoice 60 days to pay. When teams map their cycle, the surprise is usually how much calendar time is internal queue time rather than supplier time. One buyer found requisition-to-PO averaged 11 days, 9 of them approval queue, and cut the average to 4 by moving approvals under $5,000 to a single approver.
Why map the procurement cycle step by step?
Mapping the procurement cycle exposes where requests stall, where data breaks, and which steps deserve automation first. A full loop shows how each step hands data to the next: a requisition for 1,500 heat sinks becomes a three-supplier RFQ, an award at $6.10, receipt of all 1,500 units, and a three-way match that clears the invoice on Net 45 terms. Weak handoffs between those steps are where cycles quietly lose days.
Previous
Next