Procurement SOP: a Guide to Purchasing & Vendor Management

Standard Operating Procedure: Procurement and Purchasing Operations

This Standard Operating Procedure (SOP) outlines the standardized framework for the Procurement Department to ensure transparency, cost-efficiency, and operational continuity. The objective is to establish a rigorous procurement lifecycle—from initial requisition to final vendor payment—thereby mitigating financial risk, preventing supply chain disruptions, and maintaining high standards of vendor compliance. All personnel involved in the purchasing cycle must adhere to these guidelines to maintain fiscal accountability and regulatory audit readiness.

1. Requisition and Approval Workflow

• Requirement Identification: Requesting department submits a formal Purchase Requisition (PR) detailing items, technical specifications, quantities, and required delivery dates.
• Budget Verification: Purchasing officer verifies that the requested item is within the allocated department budget.
• Approval Hierarchy: Ensure the PR is electronically signed by the budget holder and, if the amount exceeds the pre-defined threshold, by the Finance Manager/Department Head.
• Validation: Review PR for completeness; reject incomplete requests and return them to the originator with specific feedback.

2. Vendor Selection and Sourcing

• Market Analysis: For non-stock items, obtain at least three competitive quotes from pre-approved vendors.
• Vendor Evaluation: Utilize the Vendor Performance Scorecard to assess potential suppliers based on price, lead time, quality history, and payment terms.
• Negotiation: Negotiate pricing, shipping terms (Incoterms), and bulk discounts where applicable to optimize total cost of ownership.
• Due Diligence: Ensure the selected vendor is active in the Approved Vendor List (AVL). New vendors must complete a comprehensive vetting process (KYC, business registration, and tax certification) before engagement.

3. Purchase Order (PO) Issuance

• Drafting the PO: Generate the official Purchase Order incorporating final pricing, terms of service, and delivery timelines.
• Legal Compliance: Include standard Terms and Conditions (T&Cs) on the PO or attach a master service agreement (MSA).
• Transmission: Send the authorized PO to the vendor via the company’s ERP system.
• Acknowledgment: Obtain a formal written acknowledgment (email or signature) from the vendor confirming receipt and ability to meet the delivery timeline.

4. Delivery, Inspection, and Receipt

• Logistics Coordination: Monitor shipment status and communicate any delays to the requesting department.
• Physical Inspection: Upon delivery, the warehouse/receiving team must inspect goods against the PO and Packing Slip.
• Discrepancy Handling: Document any damaged, incorrect, or short-shipped items via a Goods Receipt Note (GRN) discrepancy report.
• Final Acceptance: Update the inventory management system to reflect received quantities.

5. Invoice Processing and Payment

• Three-Way Match: Conduct a rigorous match between the Purchase Order, the Goods Receipt Note (GRN), and the Supplier Invoice.
• Dispute Resolution: If costs on the invoice exceed the PO amount, place the invoice on hold and negotiate with the vendor.
• Payment Authorization: Forward the approved, matched invoice to the Accounts Payable department for payment execution according to agreed-upon net terms.

Pro Tips & Pitfalls

• Pro Tip (The "Just-In-Time" Strategy): Maintain a rolling lead-time log for critical materials to avoid rush shipping fees and stockouts.
• Pro Tip (Spend Visibility): Use a cloud-based ERP to track "off-contract" spending. High levels of off-contract spend indicate a lack of policy compliance.
• Pitfall (Split Requisitions): Avoid "splitting" large orders into smaller ones to bypass approval thresholds. This is a common indicator of internal fraud.
• Pitfall (Neglecting SLAs): Failing to document non-performance (late deliveries, damaged goods) in the vendor file makes it difficult to defend contract termination or vendor blacklisting.

Template Document: Procurement SOP: a Guide to Purchasing & Vendor Management

This document serves as the standardized procurement and purchasing procedure for all staff members involved in acquiring goods or services. It is intended for use by department heads, purchasing officers, and finance personnel to ensure consistent vendor management and financial oversight.

• Document owner: [Department Name]
• Effective date: [Date]
• Version: [Version Number]
• Applies to: [Department or Process Name]

Roles and responsibilities

Steps

1. Submit a formal purchase requisition form through the [Name of Software System] for any item exceeding [Currency Amount].
2. Obtain written approval from the [Department Manager Title] to confirm that the expense aligns with the [Fiscal Year] budget.
3. Identify at least [Number] potential vendors and request competitive quotes to ensure fair market pricing.
4. Evaluate vendor proposals based on cost, delivery timeline, and [Specific Quality Metric].
5. Generate a unique Purchase Order number in the [Accounting System Name] once the vendor is selected.
6. Send the finalized Purchase Order to the vendor via [Email Address or Portal] and request an order confirmation.
7. Verify the condition and quantity of items upon delivery at the [Delivery Location] within [Number] business days.
8. Document any discrepancies between the received goods and the original Purchase Order in the [Discrepancy Log Name].
9. Forward the signed delivery receipt and the vendor invoice to the accounts payable team by [Time of Day].
10. Reconcile the invoice against the Purchase Order to ensure the billed amount matches the [Agreed Price].
11. Authorize the final payment release once the [Verification Status] is confirmed as complete.
12. Archive all procurement documentation in the [Digital Folder or Physical Cabinet] for a period of [Number] years.

Record of completion

• Prepared by: [Full name]
• Reviewed by: [Full name]
• Date completed: [Date]
• Signature: ______________________
• Date signed: [Date]

FAQ

Q: What should be done if a vendor requests a change to the agreed price after the PO is issued? A: A price change constitutes a contract amendment. A new, revised PO must be issued and approved by the same authority levels as the original before the goods are shipped or the invoice is processed.

Q: How often should we audit the Approved Vendor List? A: Perform a formal review of the AVL annually. Remove vendors with consistent performance issues, expired certifications, or those who have had zero activity for 18+ months.

Q: Can verbal agreements with vendors be considered binding? A: No. All purchasing activity must be documented by a written Purchase Order. Verbal agreements are impossible to audit and pose a significant financial risk to the company.