Coming 1H 2027 · FuelTaxPRO™
FuelTaxPRO™ arrives in 1H 2027. It reports from the ledger FuelScanner™ and FuelCounter™ already post to. One record, written once. Four gates before it posts, and the evidence stays attached to every line.
Preview · sample data
One way FuelTaxPRO™ could lay out a reporting year, shown on sample data. It is not a live account and nothing here has been filed. The figures behind each period would come from the ledger FuelCounter™ posts today.
What we have announced for FuelTaxPRO™ is aviation fuel tax reporting from the same ledger. FuelDeck™ modules all read one record, written once, and share the same validation. So FuelTaxPRO™ starts from tickets FuelScanner™ has read and FuelCounter™ has checked and posted. Not from a second copy somebody re-keyed for tax.
Built on what posts today
Capture, Validate, Post and Deliver are in production now, and VersoData™ already answers questions over the ledger. In 1H 2027, FuelTaxPRO™ adds aviation fuel tax reporting on top of that record.
Excel, PDF and CSV files from handler portals, feeds and email get parsed as they arrive. A layout FuelDeck™ has not seen before is held for review rather than guessed at. Handwritten tickets and ramp photos are one input among several.
Your own field rules. Flight identity checked against live departure data. A mandatory match to the airline's published schedule. Then an anomaly screen against uplift history by route and aircraft type.
Every posted transaction keeps its source reference, the original document, the review decisions and the delivery status.
A4A and IATA standard XML for downstream fuel management and accounting systems, with per-customer mappings.
VersoData™ takes plain-English questions over the ledger and sends charts back.
FuelTaxPRO™ reports from the same ledger. Records already checked and posted, read once, no second round of data entry.
Why it starts from the ledger
A tax report is only as good as the record under it. That record exists today. FuelDeck™ collects fuel records, checks the quantities and the flight details, and hands traceable data to the teams and systems that reconcile and account for fuel.
Every ticket passes four gates before it posts. Fail one and the ticket is held, with the reason, next to the schedule leg it was checked against. It does not post and get found later.
Source figures stay as written. Gross, net, metered and ordered are only ever compared on the right basis, so a difference gets explained before anyone calls it a variance.
Each posted transaction keeps its source reference, the original document, the review decisions and the delivery status. When someone challenges a number, the answer comes from the record. Nobody goes digging through an inbox.
At a glance
| Status | Coming 1H 2027. Announced, not yet available. |
|---|---|
| What it will do | Aviation fuel tax reporting from the same ledger. |
| Data source | The checked, traceable ledger that FuelScanner™ and FuelCounter™ post today; one record, written once |
| Validation | Shared across the suite: four gates before anything posts |
| Quantities | Source figures preserved as written; compared only on the appropriate basis |
| Evidence | Source reference, original document, review decisions and delivery status on every posted line |
| Available today | FuelScanner™, FuelCounter™ and VersoData™ · free to start, no credit card · per-ticket pricing · nothing to install |
| Security | Built on Google Cloud · per-tenant isolation · role-based access control · audit logging of privileged actions · TLS 1.3 in transit · AES-256 at rest |
FAQ
Coming 1H 2027
Book a demo of what is live underneath it: a held ticket with its reason, next to the schedule leg it failed, and the evidence kept on every line. Ask on the call and we will tell you when FuelTaxPRO™ is ready, or send us a note.
Book a demo