How to Get a Purchase Order

SOP-PUR-001: Procurement Initiation and Purchase Order (PO) Issuance

1. Document Control Block

2. Executive Summary & Scope

This SOP defines the standardized workflow for requesting, vetting, and issuing formal Purchase Orders (POs). The objective is to ensure fiscal transparency, vendor compliance, and accurate budgetary encumbrance. This policy applies to all departments authorized to procure goods or services exceeding the $500.00 materiality threshold.

3. Prerequisites & Required Tools

• ERP Access: Validated credentials for the Template Registry Procurement Module (NetSuite/SAP).
• Documentation: Signed Quote/SOW (Statement of Work) from a verified vendor.
• Compliance: Approved Vendor Master File status (KYB/KYC verified).
• Budgeting: Departmental Cost Center allocation code.

4. Roles & Responsibilities (RACI)

5. Step-by-Step Procedure

Phase 1: Requisition Submission

• Log into the Procurement Module and initiate a "New Requisition."
• Input vendor ID and verify payment terms align with internal standards (Net 30/60).
• Attach finalized Quote/SOW (PDF format only).
• Select appropriate General Ledger (GL) account code.

Phase 2: Administrative Approval

• Manager reviews item description for operational necessity.
• Manager confirms budget availability in the current fiscal period.
• Electronic signature/approval submitted via ERP workflow.

Phase 3: Procurement Vetting & Issuance

• Procurement Agent audits quote against contract pricing agreements.
• Agent verifies certificate of insurance (COI) if service-based.
• Convert Requisition to "Purchase Order" status.
• System triggers automated email dispatch to vendor contact.

6. Quality Assurance & Verification

• Metric Threshold: PO issuance turnaround time (Target: < 48 business hours).
• Audit Checklist:
  • Does the PO match the original Quote pricing?
  • Is the Cost Center code valid?
  • Are the terms and conditions attached to the PO?
• Common Pitfalls: Entering duplicate requisitions; using expired vendor credentials; missing budget center authorization.

7. Troubleshooting FAQ

Q: The system rejects my requisition due to "Budget Exceeded." How do I proceed?

• Solution: Contact your departmental Finance Business Partner (FBP) to request a budget transfer or verify if the allocation was entered incorrectly. Do not bypass the system by splitting requisitions.

Q: The vendor is not appearing in the drop-down menu. Can I use a different one?

• Solution: No. If a vendor is not listed, they have not completed the onboarding process. Submit a "New Vendor Request" form to the Procurement desk. POs issued to unverified entities are unauthorized and will not be settled by Accounts Payable.

Q: I received a "Data Validation" error on attachment upload. What is the cause?

• Solution: The file size likely exceeds 5MB or the file type is unsupported (e.g., .zip, .png). Convert document to a flattened PDF (max 2MB) and retry.

Authorized by: Julian Vance Chief Operations Architect Template Registry