Skip to main content

๐Ÿ› ๏ธ Resolving Failed QTPOD Imports in X-1FBO

Failed QTPOD imports can disrupt fuel transaction processing and lead to issues like duplicate invoices or missing payments. This guide explains common errors and troubleshooting steps to ensure smooth QTPOD data integration.

Jessi McCombs avatar
Written by Jessi McCombs
Updated over a month ago

โš ๏ธ Common Issues and Fixes

๐Ÿ” Duplicate Invoices in AR Grid

  • Cause: Creating payments before the Import Operations queue finishes processing.

  • Fix: Wait until all items in the queue are fully processed before applying payments in Accounts Receivable.

  • Note: Duplicates may disappear once processing completes. Avoid premature payment creation to prevent visual duplication.

โŒ Missing Transactions

  • Cause: Improper CSV formatting or mismatched field values.

  • Fix: Double-check fuel type, pump name, tail number, and customer fields in the CSV. Ensure they match X-1 configurations exactly.

๐Ÿงพ Unapplied or Removed Payments

  • Observation: Payments may appear removed or unapplied overnight.

  • Recommendation: Document payment actions with timestamps or screenshots. If recurring, escalate to support for backend review.

๐ŸŸฅ Failed Transactions Highlighted in Red

When uploading a CSV file, any failed transactions will appear in red within the Pending tab. These typically indicate a mismatch in the payment method type.

๐Ÿ” Common Cause

  • The payment method listed in the CSV does not match any of the configured payment methods in your X-1FBO Payment Settings.

  • For example, if the CSV lists the payment type as "AvFuel" but your system recognizes "AvFuel Card", the transaction will fail.

๐Ÿ› ๏ธ How to Fix

  1. Open the CSV file in Excel or a text editor.

  2. Locate the column for Payment Method.

  3. Update the value to match exactly what is listed in your X-1FBO Payment Settings.

    • โœ… Example: Change "AvFuel" to "AvFuel Card" if thatโ€™s the configured method.

  4. Save the CSV file.

  5. Re-upload the corrected file via Fuel Management > Import Operations.


Did this answer your question?