Purchase Order Template for Travel Agency

Standard Operating Procedure: Travel Agency Procurement & Purchase Order Execution

Document ID: SOP-TR-PRC-402
Effective Date: October 24, 2023
Version: 3.1
Review Cadence: Annual
Owner: Julian Vance, Chief Operations Architect, Template Registry

---

1. Executive Summary & Scope

1.1 Purpose

This Standard Operating Procedure (SOP) defines the institutional protocol for generating, authorizing, issuing, and reconciling Purchase Orders (POs) for travel agency operations. It ensures rigorous financial control, accurate vendor management, and strict compliance with corporate travel spend policies and statutory accounting standards.

1.2 Scope

This procedure applies to all operational units, corporate travel consultants, procurement specialists, and finance personnel within Template Registry and affiliated travel entities. It governs all external procurement, including GDS (Global Distribution System) aggregator fees, supplier allotments (hotels, airlines, destination management companies), technology licenses, and B2B ancillary services.

---

2. Prerequisites & Required Tools

2.1 Systems & Access

• ERP/Procurement Module: Integrated financial suite (e.g., NetSuite, SAP, or Coupa) configured with travel industry Chart of Accounts (COA).
• Mid-Office/Back-Office Travel Platform: Amadeus, Sabre, or Travelport integrated with the procurement ledger.
• Authentication: Multi-Factor Authentication (MFA) enabled for all financial system access.

2.2 Compliance & Regulatory Frameworks

• IATA (International Air Transport Association) Billing and Settlement Plan (BSP) standards.
• PCI-DSS v4.0 for any handling of transient supplier financial data.
• Internal Delegation of Authority (DoA) Matrix limits.

---

3. Roles & Responsibilities (RACI Matrix)

Legends:

• R = Responsible (The role that performs the activity)
• A = Accountable (The role with final approval authority)
• C = Consulted (The role providing advisory input)
• I = Informed (The role kept updated on progress)

---

4. Step-by-Step Procedure

Phase 1: Requisition and Specification

• 1.1 Access the procurement portal and initiate a new Purchase Order Requisition.
• 1.2 Select the correct vendor profile from the approved Travel Supplier Directory (verify active IATA/ASTA certification status).
• 1.3 Input the precise line-item details using standardized taxonomy:
  • Service/Product Code (e.g., TRV-AIR-GDS, TRV-HTL-ALL, TRV-DMC-SFT).
  • Detailed description including passenger PNR (Passenger Name Record) reference or group identifier if applicable.
  • Quantity, unit cost (net rates exclusive of commission markups unless structured as net-contract), and currency matching the vendor contract.
• 1.4 Assign the appropriate Cost Center and General Ledger (GL) account code.

Phase 2: Budget Verification & Authorization

• 2.1 System automatically verifies available departmental budget against the requisition total.
• 2.2 Route the requisition to the designated Department Head (DH) if the value falls within standard operational thresholds ($1,000 – $10,000).
• 2.3 Route the requisition to Financial Architecture (FA) for capital or unbudgeted expenditures exceeding $10,000, or for non-standard supplier contracts.
• 2.4 Verify that all supporting documentation (e.g., vendor quotes, group allotment agreements) is attached digitally to the requisition file.

Phase 3: PO Generation and Transmission

• 3.1 Upon final systemic approval, convert the requisition into an official, sequentially numbered Purchase Order (Format: PO-YYYYMMDD-XXXX).
• 3.2 Ensure mandatory legal terms and conditions (Net terms, cancellation SLAs, and force majeure clauses) are auto-appended to the PO document.
• 3.3 Transmit the PO electronically via EDI or secure PDF to the vendor’s designated accounts receivable contact.
• 3.4 Archive the confirmed PO state within the central document repository, locking the record against unauthorized modifications.

Phase 4: Goods/Service Receipt & Reconciliation

• 4.1 Upon delivery of travel inventory or completion of service, the Requester verifies fulfillment against PO parameters.
• 4.2 Execute a 3-Way Match within the ERP system comparing:
  • Original Purchase Order (PO) quantities and pricing.
  • Vendor Invoice (IV) detailing services rendered.
  • Receiving Report / PNR Fulfillment Log (RR).
• 4.3 Flag any discrepancies (variance threshold > 0.00% for base inventory, > 2% for fluctuating ancillary fees) for exception processing.

---

5. Quality Assurance & Verification

5.1 Key Metric Thresholds

• Cycle Time: Requisition-to-PO issuance must not exceed 4 business hours for standard allotments, and 30 minutes for urgent corporate ticketing overrides.
• Match Accuracy: 98.5% automated 3-way match success rate without manual intervention.
• Compliance Rate: 100% adherence to the Delegation of Authority (DoA) matrix; zero unauthorized commitments.

5.2 Common Operational Pitfalls

• Retroactive POs: Issuing a PO after the travel service has already been rendered or ticketed. This violates internal controls and triggers audit flags.
• Orphaned PNRs: Booking travel inventory without binding it to a verified, approved PO ID in the mid-office system.
• Currency Mismatch: Failing to lock in exchange rates at the time of PO issuance for multi-currency international GDS bookings.

5.3 Audit Verification Checklist

• Does every travel vendor disbursement trace back to an immutable, approved PO ID?
• Are tax calculations (VAT/GST) accurately segregated on the PO for cross-border services?
• Have all expired vendor certificates been purged from the active procurement directory?

---

6. Troubleshooting FAQ

Q1: What action is required if a vendor increases rates after the PO has been issued?

A: The system will automatically block invoices that exceed the PO unit price by more than 0.00%. The Travel Consultant (TC) must reject the invoice, contact the vendor to enforce the contracted rate, or—if market conditions necessitate an increase—cancel the existing PO and submit a change-order requisition requiring re-approval via the Delegation of Authority matrix.

Q2: How should an emergency corporate booking outside standard business hours be processed?

A: Utilize the Emergency Override PO protocol (SOP-TR-PRC-402-EXT). The consultant must generate a provisional "Emergency PO" tagged with code EMER-OFF-HOURS, which requires retroactive Department Head sign-off within 24 business hours of issuance. Failure to secure retroactive approval freezes the consultant's emergency booking privileges.

Q3: What happens when a multi-destination group tour PO requires partial cancellations?

A: Do not delete or overwrite the original PO. Execute a "PO Amendment / Partial Release" within the ERP system. Adjust the line-item quantities to reflect the net retained travelers, attach the supplier's cancellation credit memo, and generate a revised PO reference document for accounts payable synchronization.