Invoice Template for Travel Agency

STANDARD OPERATING PROCEDURE: Enterprise Travel Agency Invoicing Architecture

Document ID: SOP-TR-INV-4092
Effective Date: October 24, 2023
Version: 3.2.0
Review Cadence: Annual
Author: Julian Vance, Chief Architect, Template Registry

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional standard for generating, validating, and issuing financial invoices within enterprise travel agency operations. The objective is to eliminate revenue leakage, ensure multi-jurisdictional tax compliance (VAT/GST/Sales Tax), maintain rigorous audit trails for GDS (Global Distribution System) bookings, and enforce brand consistency across all client touchpoints.

---

2. Scope & Prerequisites

2.1 Scope

Applies to all corporate, leisure, and group travel billing generated by internal agents, automated booking engines, and outsourced fulfillment desks.

2.2 Prerequisites & Environment

• ERP/Accounting Software: Integrated with Amadeus/Sabre/Galileo GDS feeds.
• Template Engine: Template Registry Travel Invoice Schema v3.x.
• Hardware: Certified workstation with secure TLS 1.3 connection.
• Required Data Elements: PNR (Passenger Name Record) locator, IATA/ARC number, supplier confirmation codes, and validated tax identification numbers (TIN).

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure

Phase 1: Data Aggregation & PNR Reconciliation

• Pull the master PNR locator from the GDS and verify all segments (air, hotel, rail, car, insurance).
• Cross-reference supplier invoices (BSP/ARC settlement sheets) against agent-quoted rates to confirm net vs. commissionable margins.
• Audit ancillary fees (baggage, seat selection, name changes) to ensure 100% capture before invoice assembly.

Phase 2: Template Initialization & Metadata Injection

• Instantiate the master template via the Template Registry engine (TR-INV-TRAVEL-CORP-v3).
• Populate Agency Header: Legal entity name, IATA/ARC certification number, physical address, and support desk coordinates.
• Populate Client Metadata: Corporate entity name, billing contact, physical address, and validated tax ID.
• Insert transactional identifiers: Unique Invoice ID, Issue Date, Payment Terms (e.g., Net 30, Due Upon Receipt), and PNR Locator.

Phase 3: Itemized Line-Assembly

• Format Airfare: Detail ticket numbers (13-digit format), routing, class of service, base fare, and applicable taxes/fees broken out by category (e.g., US Passenger Facility Charges, international departure taxes).
• Format Accommodation & Ground: Detail check-in/check-out dates, property name, confirmation codes, and nightly rates.
• Format Service Fees: Explicitly list agency booking fees, ticketing fees, or itinerary design charges as separate line items.
• Apply Commission or Markup Logic: Ensure corporate discounts or negotiated overrides are transparently accounted for if passing net rates.

Phase 4: Tax Calculation & Compliance Verification

• Determine the point of sale (POS) and point of taxation jurisdictions to apply correct VAT, GST, or local sales tax.
• Verify zero-rating eligibility for international itineraries where applicable under local tax authority statutes.
• Validate that all currency conversions use the GDS daily BSR (Banker's Selling Rate) if billing in a currency divergent from the primary supplier settlement.

Phase 5: Quality Gate & Authorization

• Execute automated schema validation via the Template Registry linting tool to check for missing fields.
• Route invoices exceeding $10,000 USD (or local currency equivalent) through the secondary finance queue for sign-off.
• Generate final immutable PDF/A artifact and log the cryptographic hash in the ledger database.

Phase 6: Distribution & Archival

• Dispatch the invoice via automated secure email gateway (TLS encrypted) to the designated corporate accounts payable contact.
• Archive the artifact in the enterprise document repository with retention metadata set for 7 years (or local statutory requirement).
• Update the ERP ledger status from Draft to Issued / Accounts Receivable.

---

5. Quality Assurance & Pro-Tips

Best Practices

• Never hardcode taxes: Always pull dynamic tax arrays from the GDS API to prevent regulatory fines due to outdated rate structures.
• Isolate service fees: Keeping agency service fees distinct from supplier costs prevents confusion during corporate expense audits and simplifies chargeback disputes.

Common Pitfalls to Avoid

• Orphaned PNRs: Issuing an invoice without linking the primary GDS PNR locator, which breaks the reconciliation chain during mid-office reporting.
• Mismatched Ticket Numbers: Failing to match the 13-digit electronic miscellaneous document (EMD) or air ticket number precisely, resulting in delayed corporate payments.

Metric Thresholds

• First-Pass Yield (FPY): $\ge 98%$ of invoices must pass automated validation without manual finance intervention.
• Cycle Time: Invoices must be dispatched within 24 hours of ticket issuance or service completion.

---

6. Frequently Asked Questions (FAQ)

Q1: How should we handle split-payment models where the corporate client pays the airline directly via UATP card, but pays the agency service fee separately?
A: Generate a dual-section invoice. Section A displays the ghost-billed or direct-billed supplier items with a "Paid Directly via UATP" status indicator (zeroing out the balance due for those lines). Section B captures the agency service fees and applicable taxes, establishing a clear subtotal for the net amount payable to the agency.

Q2: What is the protocol when a client disputes a GDS tax breakdown on an international multi-city itinerary?
A: Reference the GDS electronic ticket receipt (ETR) audit trail. Pull the specific tax calculation breakdown string from the ticketing server and attach the immutable log as an addendum to the invoice query ticket. Do not issue a manual credit memo until the GDS or airline validates the tax variance.