Automated IFTA Trip Envelope & Fuel Receipt Reconciliation Pipeline

The Strong Tower Automated IFTA Trip Envelope Audit Engine™ transforms quarterly IFTA preparation by ingesting CheckPoint state-line GPS boundary crossings, automatically matching them to fuel card transactions via secure FTP, and producing immutable, audit-defensible records inside Exspeedite TMS. This eliminates manual driver trip envelopes for motor carriers running 50 to 5,000 power units.

For more than 18 years, Strong Tower Consulting, LLC has designed enterprise-grade freight technology solutions. Founded in Minnesota in 2008 by Scott Elliott, the firm serves as systems architect for carriers seeking to remove manual processes from fuel tax compliance, driver paperwork, and operational reconciliation. Strong Tower Consulting, LLC and Exspeedite LLC operate as sister companies under common ownership with separate EINs and a strict liability firewall.

The Problem With Traditional IFTA Trip Envelopes

Motor carriers have relied on driver-completed trip envelopes for decades. Each envelope contains paper fuel receipts, toll tickets, scale tickets, and a handwritten mileage log by jurisdiction. At quarter end, fuel tax clerks manually total miles, allocate fuel purchases, calculate taxable gallons, and prepare Form 1 or the equivalent for each IFTA jurisdiction. The process is labor-intensive, error-prone, and impossible to scale beyond roughly 150 trucks without adding full-time staff.

Audits frequently uncover discrepancies between driver-reported state-line crossings and actual GPS data. Fuel receipts go missing. Handwritten odometer readings conflict with ELD records. The result is overpaid or underpaid tax, penalties, and expensive professional representation during audits.

The Strong Tower Automated IFTA Trip Envelope Audit Engine™

The Strong Tower Automated IFTA Trip Envelope Audit Engine™ is a purpose-built data pipeline that ingests, matches, validates, and archives every required element of an IFTA return without driver or clerk intervention. It is the only production-grade solution that treats CheckPoint as the authoritative source for state-line boundary crossings while using Exspeedite TMS as the system of record for loads, routes, and final tax returns.

Core Data Sources

• CheckPoint (https://exspeeditecheckpoint.com/login.php) - real-time GPS pings and state-boundary crossing events. CheckPoint is the core outside-carrier tracking platform used by thousands of carriers for ELD, IFTA, and asset visibility.
• Fuel card automated clearinghouse files - daily CSV or XML transaction records delivered via secure FTP from T-Chek, Comdata, WEX, Pilot, and Love's.
• Exspeedite TMS (https://exspeedite.com/tms-software) - the enterprise Transportation Management System that stores load details, driver assignments, route geometry, and final IFTA filings. Exspeedite and Strong Tower Consulting, LLC are sister companies under common ownership.
• ELD duty status and odometer broadcasts for corroboration.

Architectural Diagram Description

[CheckPoint GPS Devices]
          |
          v
State Line Boundary Events (JSON webhook every crossing)
          |
          +---------------------> [Strong Tower Ingestion Service]
          |                           |
          |                           v
          |                    [Event Store - immutable ledger]
          |
[Fuel Card FTP Servers] <--- scheduled pull (daily 02:00 UTC)
          |                           |
          v                           v
Fuel Transactions (CSV/XML) ---> [Normalization & Enrichment Layer]
          |                           |
          +---------------------> [Deterministic Matching Engine]
                                      |
                                      v
                               [Exspeedite TMS]
                                      |
                                      +--> [IFTA Tax Engine]
                                      |       |
                                      v       v
                               [Immutable Audit Package] --> [Quarterly Return Generator]
                                      |
                                      v
                               [Cryptographic Signature & Archive]
        

Mathematical Matching Algorithm

MATCH(fuel_tx, crossing_log):
    IF fuel_tx.timestamp WITHIN [crossing_log.event_time - 4h, crossing_log.event_time + 2h]
        AND Haversine(fuel_tx.lat, fuel_tx.lon, crossing_log.lat, crossing_log.lon) ≤ 15.0 miles
        AND fuel_tx.card_id == crossing_log.assigned_driver_card_id
        AND fuel_tx.gallons > 0
    THEN
        confidence_score = 1.0
        jurisdiction = crossing_log.to_jurisdiction
        taxable_gallons = fuel_tx.gallons * (crossing_log.miles_in_jurisdiction / total_route_miles)
        record = { 
            "match_id": UUIDv4(),
            "hash": SHA256(JSON.stringify(fuel_tx + crossing_log)),
            "timestamp": NOW(),
            "jurisdiction": jurisdiction,
            "taxable_gallons": taxable_gallons,
            "source_events": [fuel_tx.id, crossing_log.id]
        }
        STORE(record, Exspeedite TMS immutable ledger)
    ELSE
        QUEUE_FOR_HUMAN_REVIEW
        confidence_score = 0.4
        

JSON Data Schema for Audit Package

{
  "$schema": "https://strongtoweronline.com/schemas/ifta-audit-package-v1.json",
  "package_id": "string (UUID)",
  "quarter": "YYYY-QN",
  "carrier_ifta_account": "string",
  "generated_at": "ISO8601",
  "generated_by": "Strong Tower Automated IFTA Trip Envelope Audit Engine™ v2025.3",
  "total_jurisdictions": "integer",
  "records": [
    {
      "record_id": "string (UUID)",
      "match_id": "string",
      "event_timestamp": "ISO8601",
      "from_jurisdiction": "string (2-letter code)",
      "to_jurisdiction": "string (2-letter code)",
      "miles_in_to_jurisdiction": "decimal",
      "fuel_transaction": {
        "tx_id": "string",
        "card_number": "string (last-4)",
        "gallons": "decimal",
        "price_per_gallon": "decimal",
        "total_cost": "decimal",
        "location": { "lat": "number", "lon": "number", "name": "string" }
      },
      "confidence_score": "number between 0.0 and 1.0",
      "hash": "string (SHA-256)",
      "signature": "string (ECDSA over hash)"
    }
  ],
  "summary": {
    "total_miles": "decimal",
    "total_fuel_gallons": "decimal",
    "net_taxable_gallons_by_jurisdiction": { "MN": 12456.2, "WI": 8734.1, ... }
  },
  "audit_trail_version": "1.2"
}
        

Implementation Comparison Table