Home / Products / FuelScanner™
Capture · FuelScanner™ · Available
FuelScanner™ reads the record in whatever form it shows up. Mostly that means files: Excel, PDF and CSV exports from handler portals, data feeds and email, parsed as they come in. Sometimes the record is the ticket itself. Then it reads 32+ fields in under three seconds.
When the record is the ticket
Most records arrive as files. Some arrive as the ticket itself: handwritten, printed, thermal, faxed, or a ramp photo taken in any phone's browser. FuelScanner™ reads those field by field. Anything it isn't confident about goes to one-click review, with the original right beside it.
The numbers behind FuelScanner™
The problem
Tickets come by portal, email, spreadsheet, scan and file drop. Every station on its own rhythm, every source in its own layout. Somebody has to read all of it, key it in again, and chase the ones that never showed up.
Portal exports, emailed spreadsheets, PDFs, scans. Each has its own columns and its own schedule. So the day fills up with chasing, and the coverage gaps go unnoticed.
Manual entry mixes up lookalike fields. Density 6.87, API 44.5. One swap, and every figure downstream is wrong.
A sizeable share of uplifts still arrive as handwritten, faded or thermal tickets and ramp photos. Keyed in by hand back at the office, they bring wrong quantities, wrong flights, wrong dates, and a backlog of corrections.
A download can succeed and still be empty, or stale. Skip the daily check and the gap only shows up at month end.
End-to-end intake
No new hardware, nothing to install. FuelScanner™ takes fuel records in the formats aviation fuel already uses, through the channels it already uses. A layout it hasn't seen before gets held for review. It is never guessed.
Excel, CSV and PDF files from handler portals, data feeds and secure file transfer. Reports and attachments sent to one intake email address. Scans from any office scanner, and photos from any phone's web browser, iOS or Android.
Files are parsed as they arrive. Ticket images get read field by field, 32+ fields in under three seconds, and any low-confidence field goes to one-click review next to the original.
Every feed gets checked daily. A quiet station is flagged, not trusted. From there each record goes through FuelCounter™'s four gates before anything posts.
Built for aviation
The AI behind FuelScanner™ was trained on real into-plane fuel tickets, not generic documents. When it isn't sure, it asks a person.
32+ structured fields from a ticket image in under three seconds. Handwritten, printed, thermal or faxed.
A low-confidence field goes to one-click human review with the original in view. It doesn't get posted quietly.
Net gallons, fuel temp, API gravity, density, ticket #, tail #, flight #, meter start/end, airport, FBO, supplier, date, time. And twenty more.
Excel, PDF and CSV exports are parsed as they arrive. A layout FuelScanner™ hasn't seen before is held for review and added on purpose, never guessed at.
Defuels and multi-hose meter readings are read as exactly that. They don't get filed as errors, and they don't get lost in the noise.
Several tickets on one scan? FuelScanner™ finds each one and splits the scan into separate records.
The field manifest
The four required fields below are read at 99.9% accuracy on every ticket. A low-confidence value goes to review. It is not estimated.
Plus 28+ contextual fields, including:
Part of the FuelDeck™ suite
FuelDeck™ collects aviation fuel records, checks quantities and flight details, and delivers traceable data to the teams and systems that reconcile and account for fuel. FuelScanner™ is where every record comes in. The modules all read one record, written once, and validation is shared across the suite.
Capture. Reads every fuel record in whatever form it arrives, then hands a single record to the rest of the suite. No re-entry.
Four gates before anything posts; one ledger with the evidence behind every line; A4A and IATA standard XML out.
Available · AskVersoData™Plain-English questions over the ledger, with tables and charts back.
Coming H2 2026DutyCounter™Duty and recovery reporting from the same record.
Coming 1H 2027FuelTaxPRO™Aviation fuel tax reporting from the same ledger.
Questions
Security
Your fuel data is sensitive. Here is what is in place.
Built on Google Cloud. Each company's data is walled off from every other's, and role-based access sets who can see and change what.
TLS 1.3 in transit and AES-256 at rest. Customer credentials are stored write-only and encrypted.
Privileged actions are audit-logged, and every posted record keeps its source reference, the original document and the review decisions.
Get started
Free to start, no credit card. See a handler's export file posted as it arrived, then a handwritten ramp ticket read and structured in under three seconds. Questions? Send us a note.