Purchase Order Template Deped

Standard Operating Procedure: Procurement Document Standardization (DepEd Framework)

Document Control Block

• Document ID: TR-OPS-PROC-DEPED-001
• Effective Date: 2024-05-22
• Version: 2.1.0
• Review Cadence: Semi-annual (Q2/Q4)
• Target Audience: School Property Custodians, Division Supply Officers, Procurement Units (DepEd)

---

1. Executive Summary & Scope

This SOP dictates the generation, validation, and archival of Purchase Orders (POs) within the Department of Education (DepEd) procurement framework. This document ensures compliance with RA 9184 (Government Procurement Reform Act) and COA (Commission on Audit) circulars regarding financial transparency and supply chain integrity. The scope encompasses all institutional templates utilized for the acquisition of goods, services, and infrastructure.

---

2. Prerequisites & Tool Requirements

• System Access: Verified credentials for the Government Electronic Procurement System (PhilGEPS) and local inventory management modules.
• Software: Adobe Acrobat Pro (PDF/A compliant), MS Excel 365 (for template data mapping).
• Regulatory Documentation: Active Approved Budget for the Contract (ABC) certification and the corresponding Purchase Request (PR) reference number.
• Certification: Personnel must hold valid authorization from the Bids and Awards Committee (BAC) or Head of Procuring Entity (HOPE).

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Operational Procedure

Phase I: Document Initialization

• Verify the Purchase Request (PR) against the Annual Procurement Plan (APP).
• Open the standardized DepEd PO Template (v.2024).
• Populate header data: Division, School ID, and Funding Source code.

Phase II: Data Mapping & Verification

• Input item descriptions strictly adhering to the technical specifications defined in the PR.
• Cross-reference unit costs against the Market Price Index or current PhilGEPS pricing.
• Calculate total aggregate value; verify against the allotted budget ceiling.

Phase III: Validation & Authorization

• Attach the signed Purchase Request (PR) as an immutable appendix.
• Route the drafted PO to the Accounting Office for "Allotment Available" certification.
• Execute digital signatures for the Procuring Entity and the Supplier.

Phase IV: Distribution & Archival

• Transmit the original signed PO to the supplier via official communication channels.
• File the electronic record in the centralized registry for audit trail retention (Retention Period: 10 years).

---

5. Quality Assurance & Verification Criteria

• Integrity Check: The PO total must equal the sum of line items within a margin of 0.00.
• Compliance Audit: PO must contain a unique tracking number linked to the fiscal year and the specific fund cluster.
• Tolerance Threshold: Zero tolerance for discrepancies in Supplier TIN (Tax Identification Number) or Item Code alignment.
• Acceptance Benchmark: Document is "Audit Ready" only if all signatory fields contain verified timestamps and digital or wet ink authentication.

---

6. Practical Troubleshooting Scenarios

Scenario A: PR Discrepancy (Cost Overrun)

• Issue: The calculated PO total exceeds the ABC specified in the approved PR.
• Corrective Action: Halt processing. Return the request to the requesting office for a Supplemental APP revision or a reduction in order volume. Document the return as a "Compliance Exception."

Scenario B: PhilGEPS Synchronization Failure

• Issue: PO Reference Number generated offline does not reconcile with the PhilGEPS online portal ID.
• Corrective Action: Do not finalize the document. Contact the IT/PhilGEPS administrator to perform a manual refresh of the transaction log. Re-sync before obtaining HOPE approval.

Scenario C: Signatory Absence

• Issue: Authorized HOPE is unavailable for signature, risking procurement lead time delays.
• Corrective Action: Utilize the designated "Officer-in-Charge" (OIC) via an officially issued Memorandum of Authority. Ensure the OIC status is noted in the remarks field of the PO.

---

Document drafted by Julian Vance, Template Registry.