Invoice Template for Transportation Services

STANDARD OPERATING PROCEDURE: Enterprise Transportation Services Invoicing Protocol

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

---

1. EXECUTIVE SUMMARY & PURPOSE

This Standard Operating Procedure (SOP) defines the institutional baseline for generating, validating, and reconciling transportation services invoices within the Template Registry ecosystem. The purpose of this protocol is to eliminate billing leakage, ensure strict compliance with federal/state transit taxation frameworks, and maintain deterministic data structures across all logistics billing pipelines. Adherence to this SOP is mandatory for all finance, logistics, and billing operations personnel.

---

2. SCOPE & PREREQUISITES

2.1 Scope

This document governs all ground, air, and freight transportation billing events processed under Template Registry operational entities. It applies to both spot-market hauling and contracted fleet logistics.

2.2 Prerequisites & Tooling

• Core Software: Template Registry Billing Core v4.2+, Enterprise Resource Planning (ERP) Connector, and Microsoft Excel 365 (for local auditing).
• Hardware: Biometrically secured workstation with multi-factor authentication (MFA) enabled.
• Documentation Access: Access to current Master Service Agreements (MSAs), Bill of Lading (BOL) repository, and International Fuel Tax Agreement (IFTA) rate tables.
• PPE: Not applicable to digital administrative workflows; physical terminal data collection requires standard high-visibility vests and steel-toed footwear per safety protocol SOP-SAF-001.

---

3. ROLES & RESPONSIBILITIES

The following RACI matrix dictates accountability for the transportation invoicing lifecycle:

• Responsible: Completes the task execution.
• Accountable: Owns final sign-off and audit compliance.
• Consulted: Provides subject matter expertise on rates and regulations.
• Informed: Receives status updates upon completion.

---

4. STEP-BY-STEP PROCEDURE

Phase 1: Data Ingestion and Source Verification

• 1.1 Retrieve the executed Electronic Bill of Lading (eBOL) and proof of delivery (POD) timestamps from the telematics repository.
• 1.2 Cross-reference total mileage, weight, and dimensional metrics against the Master Service Agreement (MSA) rate card.
• 1.3 Verify vehicle and driver identification numbers against compliance logs to ensure regulatory adherence during the transit window.

Phase 2: Template Selection and Line-Item Population

• 2.1 Access the Template Registry portal and load the standardized TR-TRANS-INV-v3 schema.
• 2.2 Populate header metadata: Invoice ID, Vendor TIN, Client Billing Address, and Payment Terms (Net 30 standard).
• 2.3 Input base transportation charges (line-haul fees) categorized by zone or per-mile rate.
• 2.4 Calculate and append variable accessorial charges (e.g., detention time, loading/unloading fees, hazardous material surcharges, tarping).
• 2.5 Compute Fuel Surcharge (FSC) dynamically using the current Department of Energy (DOE) national average index matching the delivery date.

Phase 3: Tax, Toll, and Compliance Calculations

• 3.1 Apply jurisdictional sales or value-added taxes (VAT) strictly based on origin-destination state/provincial tax matrices.
• 3.2 Itemize verifiable road tolls, bridge fees, and weigh-station tariffs with attached digital receipt identifiers.
• 3.3 Validate total calculations against allowable weight limits to ensure no unbilled overweight permit fees exist.

Phase 4: Quality Assurance and Systemic Audit

• 4.1 Execute the automated discrepancy check script to flag variances greater than $\pm 0.01%$ between eBOL data and invoice totals.
• 4.2 Perform manual spot-checks on 10% of high-value freight line items.
• 4.3 Secure cryptographic hash sign-off from the Billing Operations Specialist.

Phase 5: Distribution and Archival

• 5.1 Export the finalized invoice into immutable PDF/A-3 format with embedded XML metadata structures.
• 5.2 Transmit the invoice via EDI 210 (Motor Carrier Freight Details and Invoice) transaction set to the client's gateway.
• 5.3 Archive all source documents, calculation sheets, and the final invoice in the write-once-read-many (WORM) compliance vault for a mandatory 7-year retention period.

---

5. QUALITY ASSURANCE & PRO-TIPS

5.1 Best Practices

• Dynamic FSC Alignment: Always pull the DOE index on the exact Tuesday preceding the load delivery date to prevent retroactive billing disputes.
• Accessorial Proof: Never list detention or layover charges without an automated geofence timestamp verifying truck arrival and departure from the dock.

5.2 Common Pitfalls to Avoid

• Stale Rate Cards: Relying on outdated local spreadsheets instead of pulling real-time rates directly from the centralized ERP database.
• Missing BOL Matching: Issuing invoices prior to the client countersigning the POD, which drastically increases DSO (Days Sales Outstanding).

5.3 Metric Thresholds

• First-Pass Yield (FPY): $\ge 98.5%$ of invoices must clear client audit without requiring a credit memo or re-issue.
• Cycle Time: Invoices must be generated and transmitted within 24 hours of POD verification.

---

6. FREQUENTLY ASKED QUESTIONS

Q1: What is the protocol if a client disputes a Fuel Surcharge calculation?
A: Pull the official DOE national average index for the specific operational week in question. Generate the automated audit trace log from the Template Registry billing core, highlighting the formula: $\text{FSC} = (\text{Current DOE Index} - \text{Base Index}) \times \text{Surcharge Multiplier} \times \text{Billable Miles}$. Provide this calculation packet to the client within 4 business hours.

Q2: How should unexpected third-party lumper fees be billed?
A: Lumper fees must be accompanied by the original scanned receipt showing the transaction ID. Input these costs directly into the "Accessorial - Non-Commissionable" field on the TR-TRANS-INV-v3 template to ensure they are excluded from standard brokerage commission calculations.

Q3: What happens if an eBOL is missing or corrupted at the time of invoicing?
A: Invoicing is strictly blocked until secondary telematics verification (GPS breadcrumb logs showing dock convergence) and a signed paper manifest override are approved in writing by the Logistics Coordinator and the Accountable Manager.