Home / Products / FuelCounter™
Validate · Post · Deliver · FuelCounter™ · Available
FuelCounter™ checks every fuel ticket before it reaches the ledger. Your own field rules first. Then flight identity against live departure data, a mandatory match to the airline's published schedule, and an anomaly screen against uplift history. A ticket that fails is held, with the reason, next to the schedule leg it was checked against.
| Flight | Airport | Net gal | Sched. leg | Status |
|---|---|---|---|---|
| XA286 | SFO | 18,420 | ✓ 10-21 | checkingPosted |
| XB104 | JFK | 12,065 | ✓ 10-21 | checkingPosted |
| XC142 | ATL | 21,900 | 10-20 | checkingHeld · wrong day |
| XA418 | IAD | 33,180 | ✓ 10-21 | checkingPosted |
| XD931 | LHR | 27,540 | none | checkingHeld · no flight |
| XB202 | JFK | 41,260 | ✓ 10-21 | checkingPosted |
One ledger
FuelCounter™ posts every ticket that clears the gates to one ledger. The rest are held, with the reason, beside the schedule leg each was checked against. Quantities stay on their own basis. Copies, corrections and split deliveries are kept apart.
| Flight | Tail | Airport | Gross gal | Net gal | Schedule | Status |
|---|---|---|---|---|---|---|
| XA286 | N286XA | SFO | 18,610 | 18,420 | on schedule | ✓ posted |
| XB104 | N104XB | JFK | 12,190 | 12,065 | on schedule | ✓ posted |
| XC142 | N142XC | ATL | 22,130 | 21,900 | leg on 10-20 | ⚠ held · wrong day |
| XA418 | N418XA | IAD | 33,520 | 33,180 | on schedule | ✓ posted |
| XD931 | N931XD | LHR | 27,820 | 27,540 | no flight found | ⚠ held · no scheduled flight |
| XE023 | N023XE | JFK | 30,020 | 29,710 | on schedule | ✓ posted |
| XA286 | N286XA | SFO | 18,610 | 18,420 | on schedule | ⌥ copy · already posted |
| XB202 | N202XB | JFK | 41,690 | 41,260 | on schedule | ✓ posted |
| XF707 | N707XF | ORD | 38,450 | 38,050 | on schedule | ✓ split delivery · 2 trucks, 1 uplift |
| XC410 | N410XC | SEA | 16,040 | 15,880 | on schedule | ✓ posted |
| XG046 | N046XG | YVR | 31,750 | 31,420 | on schedule | ⌥ revised by source · held for review |
| XH002 | N002XH | SFO | 44,560 | 44,100 | on schedule | ✓ posted |
Illustrative ledger, sample records. Every posted line keeps its source reference, the original document, the review decisions and the delivery status. When a number is challenged, or a chargeback lands, the answer comes from the record and not from an inbox search.
The validation gates
Every ticket answers four questions before it reaches the ledger. Fail one and the ticket is held, with the reason, beside the schedule leg it was checked against. Not posted and found later.
Each company's own field rules run first. Every validation rule and handling decision is written down, reviewed and signed off by experienced fuel accountants. Field corrections feed back into validation, so the knowledge stops living in a few people's heads.
Asks: does this ticket meet your rules?The flight and tail on the ticket are checked against live departure data. Fuel doesn't get booked to a flight that never took it.
Asks: did this flight operate, with this aircraft?Nothing posts without a match to the airline's published schedule. If a held ticket's flight didn't operate, it is re-matched against the schedule and live flight data and heals onto the flight that actually fuelled. When a schedule changes, tickets are checked again. Nothing heals past a material difference in quantity.
Asks: which scheduled flight is this?Each uplift is screened for anomalies against history by route and aircraft type. Behind that sit two decades of field data and more than half a million historical records. This gate is advisory. It informs the reviewer. It doesn't block.
Asks: is this uplift typical for this route and aircraft?Live fuel tickets for airline customers at 51 stations, most of them in North America and the Caribbean, July 1–October 21, 2026. No human touch = reached validated or posted with no person pinning a fuel day, flight or tail, editing a field, overriding or re-validating; a person clicking Post on a machine-validated ticket is not a touch. Nobody at a keyboard = posted by the scheduled job after the nightly sweep with no one logged in. Needed a person = any of those acts, counted once per ticket. The figures measure the absence of human intervention, not first-time correctness. Download the case study.
Who we serve
Airlines consume tickets, into-plane agents produce them, airports and consortia hold the fuel farm. Each asks a different question of the same checked, traceable record.
Every uplift is matched to a scheduled flight and screened against two decades of history before it posts. Copies, corrections and split deliveries are kept apart, so you don't pay for fuel that went on the wrong flight. Or pay for it twice.
The ticket is checked against the airline's schedule before it leaves, so fewer come back. It goes out as one validated record in each airline's own standard, not six formats done by hand. The original, every correction and the delivery status stay on the record, ready for the chargeback.
The statement comparison is built in. Receipts, transfers and inventory statements sit on the same ledger as the uplifts, inventory is set against uplift by airline and airport, and every feed is watched daily.
Behind every posted line
What happens after the gates, and why a difference gets explained before anyone calls it a variance.
| What FuelCounter™ does | What it answers | |
|---|---|---|
| Quantities | Source figures kept as written; gross, net, metered and ordered compared only on the appropriate basis | A difference is explained before it is called a variance. Never automatically a loss |
| Copies & corrections | A re-sent report, a changed ticket and two real deliveries to one flight treated as three different things | No inflated totals, no real uplift thrown away |
| Revisions | A source revision after posting tracked, held for review where the rules say so, and carried through to delivery | Source, ledger and delivered file don't drift |
| Evidence | Source reference, original document, review decisions and delivery status on every posted line | A chargeback answered from the record, not an inbox search |
| Inventory | Receipts, transfers and inventory statements on the same ledger as the uplifts; a Verify view against the fueller's report | Stock and statements compared in one place |
| Dashboards | By airline, airport, route and period | One view across stations, no spreadsheet |
| Delivery | A4A and IATA standard XML for fuel management and accounting systems, with per-customer mappings | The file that leaves is the ledger that was reviewed |
FAQ
Book a demo
Three exceptions, start to finish. A ticket on the wrong day, held against the schedule leg it failed. Quantities on different bases, explained before anyone calls it a variance. And a copy, an amendment and a genuine second truck, each handled differently. Start with an exploratory call.
Book a demo