How Do You Politely Ask for a Purchase Order

DOCUMENT CONTROL BLOCK

• Document ID: SOP-TR-FIN-042
• Effective Date: October 24, 2023
• Version: 3.2
• Review Cadence: Annual
• Owner: Julian Vance, Chief Operations Architect

---

1. Executive Summary & Scope

1.1 Purpose

This Standard Operating Procedure (SOP) defines the institutional protocol for formally requesting a Purchase Order (PO) from external clients or internal procurement departments. The objective is to secure binding fiscal authorization while maintaining professional rapport, mitigating accounts receivable (AR) aging, and ensuring compliance with GAAP/IFRS revenue recognition standards.

1.2 Scope

This procedure applies to all revenue-generating units, Account Executives (AEs), Customer Success Managers (CSMs), and Project Management Officers (PMOs) at Template Registry. It governs all transactions requiring formal invoicing backed by a client-issued PO prior to the commencement of billable work or delivery of goods.

---

2. Prerequisites & Required Tools

2.1 Required Tooling & Access

• Enterprise Resource Planning (ERP): NetSuite / SAP (read/write access to Sales Order and Billing modules).
• Customer Relationship Management (CRM): Salesforce (Opportunity and Quote stages).
• Communication Suite: Microsoft Outlook / Google Workspace (using verified corporate domain signatures).
• Template Repository: Access to the standard FIN-PO-Req-Template-v3 library.

2.2 Compliance & Documentation Standards

• Fully executed Master Services Agreement (MSA) or Statement of Work (SOW).
• Validated client billing profile (Legal entity name, tax ID, physical address, accounts payable contact details).
• Zero-tolerance policy for initiating service delivery without an approved PO number (unless explicit Executive Exception Form EE-FIN-09 is filed).

---

3. Roles & Responsibilities

• Responsible (R): Executes the specific phase or step.
• Accountable (A): Ultimate ownership and sign-off authority.
• Consulted (C): Provides input, compliance checks, or template validation.
• Informed (I): Kept updated on procedural milestones.

---

4. Step-by-Step Procedure

Phase 1: Pre-Request Verification & Data Gathering

• 1.1 Verify that the underlying contract (MSA/SOW) is fully countersigned by authorized signatories from both Template Registry and the client entity.
• 1.2 Access the CRM opportunity record and confirm the final financial figures, payment terms (e.g., Net 30), and billing line items match the SOW.
• 1.3 Identify the exact client Procurement or Accounts Payable contact responsible for issuing POs.

Phase 2: Drafting the PO Request Communication

• 2.1 Select the approved PO request template corresponding to the relationship tier (FIN-PO-Req-Standard or FIN-PO-Req-Enterprise).
• 2.2 Populate all dynamic fields within the template: Company Name, SOW/Quote Reference Number, Total Fiscal Value, and Billing Schedule.
• 2.3 Attach the fully executed SOW and the formal Quote/Invoice preview to the outbound communication to eliminate administrative friction for the client.

Phase 3: Transmission and Follow-Up Cadence

• 3.1 Send the formal PO request via email to the verified client AP/Procurement contact, copying the internal AR queue (ar@templateregistry.internal).
• 3.2 Log the PO request date and tracking status in the CRM opportunity timeline.
• 3.3 Execute follow-up communications according to the institutional escalation matrix if no PO is received within the defined SLA (Day +3, Day +7, Day +10).

---

5. Quality Assurance & Verification

5.1 Key Metric Thresholds

• PO Capture Rate: $\ge 98%$ of invoiced revenue backed by a valid PO prior to invoice generation.
• Request-to-Issuance Cycle Time: $\le 5$ business days from SOW execution to PO receipt.

5.2 Common Pitfalls

• Pitfall: Sending the PO request to the project sponsor instead of the designated Procurement/AP department. (Result: Delays due to administrative routing).
• Pitfall: Failing to reference the exact SOW or Quote ID in the subject line. (Result: Manual sorting overhead for client AP).

5.3 Audit Checklist

• Is the PO number verified against the client's ERP portal or physical document?
• Does the PO value match or exceed the contractual billing milestone?
• Are the billing terms on the PO aligned with the executed SOW?

---

6. Troubleshooting FAQ

Q1: The client states they do not use Purchase Orders and refuses to issue one. How do we proceed?

• Solution: Confirm whether an alternative financial commitment mechanism exists (e.g., countersigned SOW with explicit credit card authorization on file or direct debit mandate). If the contract terms mandate a PO, escalate to the Director of Finance to invoke the Alternative Payment Authorization Protocol or execute an addendum modifying the payment terms to prepayment.

Q2: The client issued a PO, but the monetary value is lower than the executed SOW. What is the operational action?

• Solution: Do not process invoices against the partial PO. Immediately notify the client AP contact via email, highlighting the delta between the SOW value and the issued PO. Request an amended PO or a supplemental PO covering the remaining balance before releasing any additional billable deliverables.