Purchase Order Sample Malaysia

Standard Operating Procedure: Purchase Order (PO) Execution and Compliance (Malaysia Jurisdiction)

1. Document Control Block

• Document ID: SOP-OPS-PO-MY-004
• Effective Date: 2023-10-27
• Version: 2.1.0
• Review Cadence: Biannual (Every 6 months)
• Target Audience: Procurement Officers, Finance Department, Legal Counsel, External Auditors

2. Executive Summary & Scope

This SOP establishes the mandatory framework for the generation, validation, and issuance of Purchase Orders (PO) within the Malaysian regulatory environment. It ensures compliance with the Malaysian Companies Act 2016 and adherence to SST (Sales and Service Tax) requirements as mandated by the Royal Malaysian Customs Department (JKDM). This procedure applies to all domestic procurement activities conducted by Template Registry entities operating within Malaysia.

3. Prerequisites & Tool Requirements

• Software: ERP System (SAP/Oracle/NetSuite) with active SST configuration.
• Access: Verified Vendor Master File (VMF) credentials and Cost Center authorization.
• Regulatory Documentation: Copy of Vendor’s SST Registration Certificate (if applicable) and Business Registration (SSM).
• Safety/PPE: N/A (Administrative Function).

4. Roles & Responsibilities (RACI Matrix)

(R=Responsible, A=Accountable, C=Consulted, I=Informed)

5. Step-by-Step Operational Procedure

Phase 1: Initiation and Validation

• Verify internal requisition form is signed by the authorized budget holder.
• Cross-check Vendor details against SSM (Suruhanjaya Syarikat Malaysia) records to ensure legal entity status.
• Confirm product/service specifications match the quote attached to the requisition.

Phase 2: PO Drafting and SST Compliance

• Generate PO in the ERP system using the approved vendor ID.
• Input specific line items, including SKU, unit price, and quantities.
• Apply correct SST tax code (e.g., 6% or 8% depending on service/product classification).
• Attach vendor's SST Certificate verification to the digital audit trail.

Phase 3: Authorization and Issuance

• Submit PO for digital workflow approval by the Finance Department.
• Verify "Budget Remaining" threshold before final electronic signature.
• Dispatch finalized PO via encrypted transmission to the vendor’s registered email address.

6. Quality Assurance & Verification Criteria

• Audit Checklist:
  • PO number sequence integrity (no gaps).
  • SST value calculation matches the tax rate declared by JKDM.
  • Terms and Conditions (T&C) reference current Template Registry standard service agreement.
• Tolerance Thresholds: Zero tolerance for price variances exceeding 0.5% of the initial quote without an approved Change Request (CR) form.
• Acceptance Benchmark: 100% data correlation between PO, Vendor Quotation, and Goods Received Note (GRN).

7. Practical Troubleshooting Scenarios

Scenario 1: Vendor SST Status Invalid

• Detection: ERP validation fails during vendor look-up.
• Corrective Action: Halt PO generation. Request a valid SST certificate copy from the vendor. Update the Vendor Master File; if the vendor fails to provide documentation, elevate the case to the Finance Manager for "Non-SST" status flag.

Scenario 2: Price Discrepancy (PO vs. Quote)

• Detection: System-automated price variance alert at the time of final approval.
• Corrective Action: Flag the PO as "Pending Clarification." Contact the vendor to request a revised quote. If a price hike is justified by market conditions, secure a written addendum signed by the department head before resuming the approval flow.

Scenario 3: Unauthorized Vendor Selection

• Detection: Procurement attempt by a department without VMF approval.
• Corrective Action: Immediate rejection of PO. Instruct user to submit a "Vendor Onboarding Request" to compliance. Re-initiate PO workflow only after the vendor completes KYC and due diligence checks.

Julian Vance Chief Operations Architect Template Registry