Purchase Order Template for Word

Standard Operating Procedure: Procurement Document Standardization

Document ID: TR-OPS-PO-001
Effective Date: 2023-10-27
Version: 1.0.4
Review Cadence: Annual
Target Audience: Procurement Specialists, Accounts Payable (AP), Project Managers

---

1. Executive Summary & Scope

This SOP establishes the protocol for the deployment and utilization of the Template Registry standardized Purchase Order (PO) framework for Microsoft Word. Adherence to this procedure ensures consistent legal binding, fiscal audit readiness, and tax compliance across all institutional procurement activities. This document covers the lifecycle of PO generation, from template instantiation to final document extraction for ERP reconciliation.

---

2. Prerequisites & Tool Requirements

• Software: Microsoft Word 365 (Build 16.0+) or Microsoft Word 2019/2021.
• Access: Active Directory credentials with read/write permissions to the Secure Document Repository.
• Template Source: Official TR-Sourced .dotx file (Do not use legacy .doc files).
• Configuration: Enable "Developer" tab in Word for field locking.

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Operational Procedure

Phase I: Initialization

• Verify template version integrity against the Registry Master Index.
• Open the official .dotx template file (this automatically spawns a new Document1 instance).
• Verify that document protection is enabled to prevent inadvertent field manipulation.

Phase II: Data Input

• Populate header metadata: PO Number (System Generated), Date, and Currency.
• Input Vendor Details utilizing the verified Registry Vendor ID lookup table.
• Populate Line Item details: SKU/Part Number, Unit Price, Quantity, and Tax Code.
• Execute automated calculation fields via F9 (Refresh Field command).

Phase III: Review & Conversion

• Validate Total Sum against original Quotation or SOW (Statement of Work).
• Perform "Check for Issues" via Word’s Inspector to remove hidden metadata/PII.
• Save final document as PO_[Number]_[VendorName]_FINAL.pdf for transmission.

---

5. Quality Assurance & Verification Criteria

• Mathematical Precision: The sum of all line items must match the Grand Total with 0.00% variance tolerance.
• Tax Compliance: VAT/Sales Tax must be calculated based on the jurisdiction defined in the Vendor ID metadata.
• Formatting Integrity: All margins must remain set to 1-inch standard; fonts must be restricted to Arial or Calibri (11pt).
• Acceptance Benchmark: Document must pass the "Read-Only" signature test—all editable fields must be locked post-generation.

---

6. Practical Troubleshooting Scenarios

Scenario A: Calculation Field Error (Field Code #REF!)

• Root Cause: Item row was deleted, breaking the summation table index.
• Corrective Action: Do not manually overwrite the #REF! text. Delete the corrupted row, insert a new row from the "Template Registry Insert Menu," and re-input data to allow the formula to re-index.

Scenario B: Document Unlocks Automatically upon Save

• Root Cause: Template macro-security settings are insufficient.
• Corrective Action: Go to Review > Restrict Editing and ensure the "Enforce Protection" button is toggled. If password-protected, contact the System Architect for the temporary institutional override key.

Scenario C: Font/Style Drift during Export

• Root Cause: Compatibility issues between localized printer drivers and the Word template.
• Corrective Action: Utilize "Print to PDF" via the Microsoft Print to PDF driver rather than "Save As PDF" to force embedding of all document fonts and styles.

---

Authorized by: Julian Vance, Chief Operations Architect, Template Registry.