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.
Previous
Next
*GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally, and COOL VENDORS is a registered trademark of Gartner, Inc. and/or its affiliates and are used herein with permission. All rights reserved. Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.