X-1FBO Updates V.2.4.54 – 23

Update: We added tenancy indicators across several invoicing workflows to make tenant identification clearer and more consistent. The new Tenancy icon is now displayed on invoice line items. When hovering over the icon, users can view the Tenancy Type and, when applicable, the ICAO code for network-based tenants. Additional improvements include:

Benefit: Provides clearer and faster tenant identification across invoicing, credit, refund, and search workflows, improving accuracy for FBOs managing network-based customers.

Update: We completed a major refactor of the Inventory Operation Log to improve clarity, consistency, and auditing across both PDF and Excel exports.

PDF improvements:

Excel improvements:
Added several new columns to enhance data visibility and reporting:

Benefit: Provides clearer fuel movement tracking, better audit support, and more useful data across operational, accounting, and compliance workflows.

Released as a Hotfix on November 18, 2025

Update: We updated the Download Invoice button in recurring invoice emails so that the invoice PDF is now directly downloaded, rather than opening in a new browser tab.
​Benefit: This prevents security issues, avoids popup-blocker errors, and ensures a smoother experience for all customers receiving monthly recurring invoices.

Update: When World Fuel is selected as Contract Fuel and the “WF Owns DLA Contract” setting is enabled, the World Fuel Profiles field now appears for AirCard payments.

Benefit: Allows proper profile selection and resolves the issue where the field did not display for WFS FBOs.

Update: We renamed the “Print Contract Fuel Invoice” option in the Invoice List to “Internal Contract Fuel Invoice” to better distinguish internal-use printouts from customer-facing options.

Benefit: Clearer print options and reduced confusion when selecting internal vs customer-facing invoice outputs.

Update: Added a new setting under Accounting > Settings > Invoice tab that allows FBOs to choose whether the Ready Date comes from the QTPOD transaction date or the import process date.

Benefit: Provides flexibility for customers who need the Ready Date to reflect the actual fueling date instead of the import date.

Notes: The setting is off by default.

Update: We optimized how the system retrieves real-time operational totals for the last 6 hours, including Active Devices, Fuelings, Jet A, and Avgas volumes.

Benefit: Faster dashboard performance, more accurate counts, and more reliable real-time data for operational monitoring.

Update: We improved how the system retrieves and processes invoice payments and refunds for multiple processors.

Benefit: Faster and more reliable payment and refund processing, with improved data consistency and reduced delays during invoicing workflows.

Update: We added a new process that allows the system to detect and load Avfuel fuel releases that were previously skipped due to missing merchant configurations.

Benefit: Ensures all historical Avfuel fuel releases are correctly loaded into X-1, preventing data gaps.

Update: We made several usability enhancements across X-1 Café to improve clarity when creating or editing Café products and inventory entries:

Benefit: These updates make Café product and inventory setup clearer, reduce errors, and help users understand how images and cost values should be entered.

Issue: Several QuickBooks (QBO V2 and V3) workflows were causing transactions to remain stuck in Syncing, generate duplicate or incorrect adjustments, misroute refunds, display unclear validation errors, or fail when applying or voiding AR payments. Some records also calculated the amount excluding sales tax incorrectly compared to QuickBooks expectations.

Fix: We resolved multiple issues across the QBO integration, including:

Issue: When performing the Daily Close, a deleted operation still appeared as the last meter reading for the truck. This caused inaccurate end-of-day readings and could misrepresent actual fuel usage or meter progression.

Fix: The system now correctly excludes deleted operations from the Last Reading view. Only valid, non-deleted operations are considered when determining the final reading for the Daily Close.

Issue: The Physical Balance displayed in the dashboard did not update after executing a Close Period or Daily Close. The dashboard continued showing outdated balance values because no refresh or recalculation occurred following the closing process.

Fix: The system now refreshes and updates the Physical Balance immediately after a Close Period or Daily Close. Users now see the correct, current fuel balance reflected in the dashboard without needing to perform any manual actions.

Issue: Entering special characters (such as HTML or certain symbols) in the Invoice Notes field caused the system to throw an unhandled server error:
“A potentially dangerous Request.Form value was detected…”
This interrupted invoice creation and did not provide a clear, user-friendly message.

Fix: The system now validates the Notes field and displays a clear warning when unsupported characters are entered:
​“The Notes field contains unsupported characters. Please use standard text only.”
This prevents errors and ensures a smooth user experience.

Issue: In certain cases, the tax amount on an invoice displayed correctly in X-1, but the value sent to AEG showed $0.00 instead of the actual amount. Because of this mismatch, AEG was unable to process those transactions.

Fix: The system now sends the correct tax amount to AEG in all scenarios. This ensures the invoice matches what is transmitted to the processor and prevents interruptions in AEG’s processing workflow.

Issue: The system incorrectly blocked users from linking an invoice to a fuel ticket when the invoice did not have an associated request or fueling. The validation assumed a fueling must always exist, preventing invoices from being linked even in valid operational scenarios where no request/fueling was involved.

Fix: The validation was updated so that invoices can be linked to a fuel ticket even when no request or fueling record exists. This restores the intended flexibility for workflows where fuelings are manually adjusted or removed.

Issue: When MSA processor was selected with the “Only QTPOD Enabled” option checked, invoices displayed the wrong payment method. Instead of showing the correct MSA processor, the system always defaulted to X1PAY, causing confusion and incorrect payment information on newly created invoices.

Fix: The system now correctly loads and displays the appropriate MSA payment method when the “Only QTPOD Enabled” option is active. Invoices no longer default to X1PAY and reflect the correct processor during invoice creation and processing.

Issue: Users were unable to process any payments in X-1Portal when selecting X-1PAY as the processor. Transactions would not initiate, preventing customers from completing payments through the portal.

Fix: Payment processing through X-1Portal has been restored. Users can now successfully complete transactions using X-1PAY Merchant Services without errors.

Issue: In X-1FBO, invoices captured through an X-1PAY terminal sometimes remained stuck in Processing instead of updating to Processed, even though the payment was successfully captured. This caused confusion and reconciliation issues.

Fix: The system now correctly updates invoice statuses after a successful X-1PAY terminal capture. Invoices reliably move from Processing → Processed.

This release brings clearer invoicing, more reliable payment and accounting workflows, stronger operational reporting, and a smoother day-to-day user experience across X-1. Together, these improvements enhance accuracy, reduce errors, and streamline key processes for FBOs.