Handler B, invoice for September 2026, one station
| 12 | Turnaround A320, flight 402 | €1,180.00 |
| 13 | GPU, 2 hours, flight 402 | €190.00 |
| 14 | Pushback, flight 403 | €160.00 |
| 15 | Turnaround A320, flight 411 | €1,180.00 |
| 16 | Night surcharge, flight 417 | €295.00 |
| and 143 more lines | ||
| Total | €94,620 |
148 lines for 62 flights
Today Someone checks about 15 lines against the contract, and the rest is paid.Behind the scenesChecking one line means opening the contract's price annex, the flight record and the station log. With well over a hundred lines a month per station, there is no time to do them all.What it achievesChecking every line finds the small, repeated mistakes a sample misses.
Handling agreement, price annex
Turnaround. A320 family: A320 EUR 1,180, A321 EUR 1,340 per turnaround.
Ground power. EUR 95 per started hour, as logged at the stand.
Night. Services between 23:00 and 05:59 local time: plus 25%.
Not chargeable. No charge for flights cancelled more than 24 hours before departure, or for delays on the handler's account.
Rules the system appliesBehind the scenesA language model reads the price annex and fills a fixed rule table, quoting the clause behind each price. The station manager approves the table once per contract; after that the rules run as plain code.In this demoInvented annex of the standard shape. Prices are ours.What it achievesOther tools check invoices against a price model someone builds by hand. Reading the annex directly is where the set-up time goes.
Every line checked against three recordsBehind the scenesEach invoice line is matched to a flight by number and date, then to the station log by stand and time. The rule table gives the price the contract allows. Anything that does not agree is flagged with the record that disagrees.What is automatedMatching all the lines. People only look at what disagrees.
0 of 148 lines checked
What the records do not supportBehind the scenesThe same check confirms the lines that are right, so the airline pays them without argument, and finds lines where the handler undercharged. Only what the records contradict is queried.AssumptionThe mistakes and their share, 2.6% of the invoice, are modelled and ours, near the rates invoice checking vendors report.
Queried this month €2,502, 2.6% of the invoice, including €612 of smaller lines of the same kinds.
Draft to Handler B, invoice for September 2026
We have checked every line of your invoice against our agreement, our flight records and the station log. We query five lines and €612 of smaller items, €2,502 in all; the evidence for each is attached. We will pay the remaining €92,118 on the due date.
Sent the way the contract asksBehind the scenesThe letter is drafted from the findings only, with the evidence for each line attached, and sent within the notice period the agreement sets. The station manager approves it; the undisputed amount is paid on time.What it achievesThe relationship with the handler stays calm: the airline pays what is right, promptly, and queries only what it can prove.
0
invoices checked across 6 stations
0
lines, every one checked
€0
queried with evidence (modelled)
€0
credited back (modelled)
The same records serve the next conversation with the handler: which services cost most, where delays sat, and what to change at renewal.AssumptionInvented airline, handler, prices and mistakes. Modelled: a year of queries and credits, and 14 hours a month of checking cut to 2 hours of review.What it achievesThe real figures come from running your own last twelve invoices through the same rules.
Handling invoice, one station
148
lines, every one checked
Interactive demo
Watch it run in 87 seconds, or click through at your own pace. The i buttons show what happens behind the scenes.
That was one day
€2,502 queried with evidence on one station's invoice
Modelled on an invented airline. Your own invoices and records would give the real figure.