WorkflowAirport & Ground Operations

Ground Handling Invoice Reconciliation

Ground handling invoice reconciliation that ties every handler line to its turn, its rate and its approval before a dollar is paid

Every handler line tied to its turn, its rate and its approval before a dollar is paid.

See one case, screen by screen ↓
demo678lineson one station's monthly handler invoice, each stitched to its proof or left loose with a reason
demo$18,640on 119 lines with no matching turn or approval, found overnight on the sample Denver invoice
target100%of lines tied to turn, rate and approval, not a sample
target5daysbefore the due date, every invoice decided and the undisputed amount paid on time
In short

What is Ground Handling Invoice Reconciliation?

Ground handling invoice reconciliation is the airline's check that every line a ground handler bills was performed, is billable under the station's Standard Ground Handling Agreement (SGHA) Annex B and is priced at the rate in force that day, before the invoice is paid. Ground Handling Invoice Reconciliation adds seven agents that read every invoice in any format, stitch each line to its turn record, Annex B rate and ad hoc approval, and draft the short-pay for the cost controller to confirm and sign.

How to choose AI for airlines: a buyer's guide to agentic AI solutions →

Updated

The problem

Why ground handling invoices get paid on a sample

An airline pays a ground handler at every station it does not self-handle, each under its own SGHA Annex B rate card. Handlers bill monthly through IATA SIS as IS-XML, or as a PDF, a spreadsheet, an EDI file or a scan. Turn charges are predictable; ad hoc work — ground power, extra ramp agents, tows, delay standby — arrives on paper service records signed days late or not at all. To check a line, the cost controller has to pull the turn record, the cancellations, the delay codes, the Annex B in force on the service date and the station's request. With thousands of lines a month, finance samples about a tenth and pays the rest.

In ground handling charges, what slips through is what nobody had time to prove: a turn for a flight that never operated, the same turn billed twice, a new rate applied before its amendment took effect, delay standby on a delay the handler caused, extra agents no one requested — and the hardest one, a ground power unit billed on a turn that ran on the aircraft's own APU. "I can't prove a GPU wasn't plugged in, so I pay it."

demo$468,210of handler charges with no matching turn or approval across the network in one month, 1.48% of $31.62M billed, on the sample data
target$3.8–11.4Ma yearkept at 1–3% of a $380M handling bill
Where one station invoice's hours goestimated
By hand28 days
With the solution3.5 days
  • Logging the invoice and keying scanned service records3 → 0.2 d
  • Assembling turn records, cancellations, delay codes and the Annex B6 → 0.3 d
  • Checking lines — a sample by hand, every line with the agents8 → 1 d
  • Chasing the station for ad hoc requests4 → 0.5 d
  • Writing the short-pay and the SIS rejection3 → 0.5 d
  • Answering the handler's reply and matching the credit note4 → 1 d

Estimated split for one monthly handler invoice of several hundred lines, by hand with sampling and with the solution checking every line.

How it works

How an invoice moves

Seven agents stitch every line to its proof, check each other and draft the short-pay; the cost controller confirms line by line and signs.

What comes in
Invoices in212 invoices a month · IATA SIS, PDF, EDI, scans
Agents at work
Invoice readerany format
Then
Turn matcherturn, APU, gate power
Rate checkerAnnex B of the day
Ad hoc approval finderasks the station
Then
Verifierre-derives on its own
Then
Short-pay drafter
Dispute responder
A person decides
Ground Handling Cost Controllerconfirms, edits or keeps paying each line, and signs
What comes out
Signed short-pay
Undisputed amount paid
Every step logged
One case, step by step

Ground handling invoice reconciliation on one Denver invoice, screen by screen

Corvane Airways contracts handlers at 118 stations under 64 agreements. SkyRamp Services' September invoice for Denver — SRS-DEN-260930, $412,880.00, 678 lines, received through IATA SIS on Oct 3 with 41 scanned ad hoc service records, due Nov 2. Here is what happens next, in the working solution.

  1. 01Friday, 6:02 am

    The agents worked overnight; four things need her

    Megan Alvarez · Ground Handling Cost Controller

    Megan's Today screen shows 198 of 212 September invoices checked on every line — 186,400 lines — and $468,210.00 without proof across the network, 1.48% of $31.62M billed. The agents also found $7,940.00 the handlers forgot to bill, and listed it. The biggest item is SkyRamp at DEN: 119 lines hang loose, and the Verifier agrees on 118.

    “Good morning, Megan. The most valuable thing today is SkyRamp's DEN invoice: $18,640.00 with no matching turn or approval. Want me to open it?”

  2. 02Review the lines

    Every line stitched to its proof — or hanging loose

    Megan Alvarez · Ground Handling Cost Controller

    The invoice opens as plain lines grouped by service. Each one is tied by a thread to its turn record, the Annex B rate of the day and, for ad hoc work, its signed record. 559 lines, $394,240.00, are stitched. The loose ones are greyed: 46 ground power lines ($9,200), 62 A321neo turns at the new rate ($2,790), 5 delay standby ($2,725), 4 extra-agent shifts ($1,520) and 2 turn handling lines ($2,405).

    “I drafted a short-pay with a reason on each of the 119 lines. You decide; the letter only carries lines you confirm.”

  3. 03Watch the agents check

    Each agent works on its own, and shows it

    The agents

    The Invoice reader read 678 lines from IATA SIS and 41 scanned records at 99.4% confidence. The Turn matcher tied each line to one of 296 operated turns and found 1 canceled flight and 1 duplicate. The Rate checker priced every line from the Annex B of its service date: Amendment 3 takes effect Sep 15, and 62 lines used the new rate too early. The Ad hoc approval finder found 4 extra-agent shifts with no request and asked the station.

    “Nothing is withheld or sent until a person confirms. Every finding cites its source.”

  4. 04CV 1422 · Sep 17

    Ground power on a turn that ran on the APU

    Turn matcher

    Line 0412 bills 2 × 30 minutes of ground power, $200.00. The turn timeline shows the aircraft at gate B31 for 49 minutes, the APU running 13:54–14:51, the gate meter reading 0.0 kWh and GPU on and off left blank on SkyRamp's turn log. The same pattern shows on 45 other turns at gates B29–B35, all with fixed power. Megan confirms all 46 GPU lines in one tap.

    Verifier, on its own: “A GPU can run while the APU runs, so the APU alone would not prove it; the blank turn log and 0.0 kWh together do.”

  5. 05One dissent

    A second agent argues the handler's side

    Verifier

    Five delay standby lines were drafted as handler-caused. The Verifier re-derived each one from the records without seeing the first working, and disagrees on one: CV 1290 on Sep 25 was coded 41, aircraft defect — Corvane's own cause — for 72 minutes, and Annex B item 11 makes that billable. Both workings sit side by side. Megan keeps paying the $545.00 and confirms the other four.

    “CV 1290 was coded 41, aircraft defect — Corvane's own cause, 72 minutes. Item 11 makes it billable. I would pay $545.00.”

  6. 065:58 am, answered later

    One plain question to the station

    Tom Brandt · Station Manager, DEN

    Annex B pays extra ramp agents only on the station's written request. The service records say “per station call”, so the agent asked Tom one question. He answers yes and attaches his email of Sep 22, 04:52 asking for 2 agents. Lines 0502 and 0503 are stitched to his email and $760.00 will be paid. Sep 8 has no request and the Corvane signature is blank, so those two shifts stay on the short-pay.

    “Did DEN request 2 extra ramp agents for the 05:30–09:30 bank on Sep 22?”

  7. 07Build the letter

    A short-pay built only from confirmed lines

    Short-pay drafter

    Short-pay letter SP-DEN-2609 withholds $17,335.00 on 116 lines and pays $395,545.00 by Nov 2, under item 14 of Annex B. Each group carries its clause and examples: ground power billed where no GPU was connected (item 7), a flight canceled more than 2 hours before arrival (item 1.4), a turn billed twice, the A321neo rate before Amendment 3 took effect, delay standby not caused by Corvane (item 11) and extra agents without a written request (item 9). The two lavatory and water services SkyRamp did not bill, $180.00, are listed and not claimed.

    Not in this letter: “Every loose line is decided.” Paid after review: CV 1290, and lines 0502 and 0503 with proof attached.

  8. 08Signed

    She signs with a reason code

    Megan Alvarez · Ground Handling Cost Controller

    Megan signs with the reason code “Not supported by turn record or approval” and the statement that she has reviewed each line and its records. The letter is under the $25,000 co-sign threshold, so one signature is enough. It goes out as an IATA SIS rejection memo and an email to SkyRamp billing, and a hold is placed in the finance system.

    “I have reviewed each line in this letter and its records.”

  9. 09Oct 30 payment run

    The undisputed amount pays on time

    Andre Collins · Accounts Payable Analyst

    On Payments, Andre sees SkyRamp DEN with $17,335.00 held and $395,545.00 to pay — the short-pay is sent and the undisputed amount is due Nov 2. Harborline's MIA invoice is held for a Procurement co-sign, and SLC, NRT and SFO are clean, every line stitched to proof. He releases; the agents never do.

    “I prepared every hold; nothing is released without Accounts Payable.”

  10. 10The month after

    The pattern goes to the handler review

    Hannah Okafor · Procurement Manager, Ground Services

    Stations keeps the record Procurement and the VP Ground Operations negotiate from: $3,862,400 found without proof January to September, and $3,118,250 credited by handlers. DEN has grown every month since June, and 49% of September's DEN findings are GPU on APU turns at fixed-power gates. The agent offers to draft the SkyRamp talking points.

    “The pattern, in one line: Bills GPU on APU turns at fixed-power gates (B29–B35).”

Who it’s for

Built for everyone who touches a handler invoice.

The same invoice, seen by the five people who carry it — what their month looked like, and what it looks like now.

MA
Megan AlvarezGround Handling Cost Controller · Chicago O'Hare · signs short-pays to $25,000
Ground Handling Cost Controller
Before
Checks 212 handler invoices a month by sampling lines in spreadsheets and writes dispute emails by hand. “I can't prove a GPU wasn't plugged in, so I pay it.”
Now
Opens each invoice with every line stitched or left loose, confirms groups in one tap, keeps paying where the Verifier says the handler is right, and signs a letter built from her own decisions.
TB
Tom BrandtStation Manager, Denver (DEN)
Station Manager
Before
Signs ad hoc service records at the end of a shift, often days later. “If I asked for extra agents, I'll tell you — just ask me the day it happened.”
Now
Gets one plain question per missing request, answers yes or no, and attaches his email; the line is stitched on the invoice before the letter goes out.
AC
Andre CollinsAccounts Payable Analyst · finance shared services
Accounts Payable Analyst
Before
Releases payment runs twice a month and chases holds and credit notes. “Tell me what I can pay today and what I must hold.”
Now
Sees what each invoice can release, what stays held and why, releases the undisputed amount on time and posts holds to the finance system.
HO
Hannah OkaforProcurement Manager, Ground Services · co-signs above $25,000
Procurement Manager, Ground Services
Before
Owns 64 handler contracts and their amendments, and co-signs the large disputes. “A new rate starts on the date we signed, not the date they like.”
Now
Confirms each amendment's effective date once, sees every line priced from the rate of its service date, and co-signs the letters above the threshold.
SW
Sam WhitfieldFinance Systems Administrator · settings, roles and feeds
Finance Systems Administrator
Before
Connects IATA SIS, the operations system and the finance system, and sets roles and thresholds. “Set it once, then show me it's healthy.”
Now
Sets thresholds and rules once, every change logged, and sees each feed's health — such as the DEN gate-power feed running two days late.
Built on the engine

7 agents. Each with one job, and hard limits.

Seven agents stitch every line to its proof, check each other and draft the short-pay; the cost controller confirms line by line and signs.

Invoice reader

Reads handler invoices in IS-XML, PDF, spreadsheet, EDI and scanned service records into lines mapped to the IATA IS-XML fields, with a confidence for every field, and flags a file with the same number and total as one already received.

  • Never guesses a field below 90% confidence — it asks for a clearer copy
  • Never edits an invoice
Turn matcher

Ties every line to the operated turn — flight, date, tail and times — and to cancellations, the aircraft's ACARS APU record, the airport gate-power meter and the delay codes.

  • Never treats “the flight operated” as proof of an ad hoc service
Rate checker

Prices every line from the station's SGHA Annex B and the amendments in force on the service date, and checks the rate driver: aircraft type, weight band, event.

  • Never applies a rate Procurement has not confirmed
  • An amendment applies only from its confirmed effective date
Ad hoc approval finder

Finds the request and signature for every ad hoc line in signed service records, station mailboxes and the approvals log; when none is on file, asks the station manager one plain question with the date and the work.

  • Never approves ad hoc work
  • Never treats a handler's signature alone as a request
Verifier

Re-derives every finding from the source records on its own and argues the handler's side; a disagreement goes to a person with both workings.

  • Never sees the first working before it concludes
  • Never creates or resolves a finding itself
Short-pay drafter

Writes a reason with its clause on every loose line, then the letter, the IATA SIS rejection memo and the finance-system hold, and lists under-billing without claiming it.

  • Never sends anything
  • Never includes a line a person has not confirmed
Dispute responder

Reads handler replies and credit notes, re-checks new evidence on its own, proposes concede or hold per line, drafts the answer and matches credits to short-pays.

  • Never concedes or holds on its own
  • Never contacts a handler
Cost control

Confirms every withheld line; Procurement co-signs above $25,000. The agents propose; a named person decides.

Ask in plain words

Ask about any invoice, line, turn or station

Every screen has a conversation with its agent. Ask in plain words or say what to do; answers cite their sources, and a decision is always handed back to a person.

Why is SkyRamp's DEN invoice short $18,640?

Of 678 lines, 559 are stitched to their turn, rate and approval. The largest gap: 46 ground power charges on turns that ran on the APU, $9,200.00. Then the new A321neo rate used before Sep 15, $2,790.00, delay standby on handler-caused delays, and extra agents with no request.

Which stations bill GPU on APU turns?

DEN (46 turns in September) and PHX (6), both SkyRamp, at gates with fixed power; MIA has 32 at gates E8–E11. Annex B charges GPU only from connection to disconnection.

What can Accounts Payable release today?

Three clean invoices, SLC, NRT and SFO: $1,157,524.00. For DEN, MIA and LAX the undisputed amount can be paid on the Oct 30 run with the loose lines held, as Annex B item 14 allows.

Ask Tom about the Sep 22 extra agents

Done this morning at 5:58: “Did DEN request 2 extra ramp agents for the 05:30–09:30 bank on Sep 22?” The records say “per station call”, and I found an email from Tom that morning. His answer lands in Approvals.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

TodayGround handling invoice reconciliation at a glance: invoices checked on every line, charges without proof across the network, what the agents did overnight and what needs the cost controller.
The stitched invoiceA handler invoice as plain lines, each threaded to its turn record, the Annex B rate of the day and the aircraft's APU and gate power — lines without proof hang loose with a drafted short-pay.
The agents checkEach agent's step in view: the invoice read from IATA SIS, lines matched to operated turns, priced from the Annex B of the service date, ad hoc approvals found and every finding re-derived.
One turn, minute by minuteA GPU charges audit on one turn: the APU running, the gate meter at 0.0 kWh, the handler's turn log blank, and the billed ground power beside it.
The Verifier disagreesBoth workings on a delay standby line: drafted as handler-caused, while the Verifier reads IATA delay code 41 — the airline's own — and would pay.
Ad hoc approvalsAd hoc service record approval for the station manager: one plain question per missing request, answered yes or no with the email attached.
The short-pay letterA ground handler short-pay built only from confirmed lines, with the Annex B clause and examples per group, under-billing listed and the lines paid after review.
Sign and sendSigning the short-pay with a reason code and the review statement, before it goes out as an IATA SIS rejection memo, an email to the handler and a finance-system hold.
The payment runWhat Accounts Payable can release, what stays held and why — the undisputed amount paid on time and every hold with its reason.
Disputes and credit notesA handler's reply read and its new evidence re-checked, with concede or hold proposed per line, the answer drafted and credit notes matched.
StationsGround handling cost control station by station: found without proof, credited by handlers, month by month, and each handler's pattern in one line.
Rate cardsSGHA Annex B rate cards per station with every amendment and the date it starts, so each line is priced from the rate of its service date.
Rules and thresholdsCo-sign threshold, tolerance per line, reader confidence, automatic release, the locked-on Verifier and the delay standby rule — every change logged.
Governance

Built for handling spend: cited, signed, on the record.

Every value cites its sourceEvery line and every agent statement points to the passage it came from — the turn log, the ACARS APU report, the gate meter, the Annex B clause, the service record or the station's email — and a click opens it.
A person confirms every withheld lineThe cost controller confirms, edits, keeps paying or re-attaches proof line by line, and signs every short-pay with a reason code. Above $25,000, the Procurement Manager co-signs.
An independent VerifierThe Verifier re-derives every finding without seeing the first working, and argues the handler's side. It is locked on, and a disagreement reaches a person with both workings.
Letters only from confirmed linesThe letter, the IATA SIS rejection memo and the finance-system hold are generated only from lines a person confirmed. Under-billing is listed too, and not claimed.
Agents never move moneyThe agents never withhold, send, pay, approve ad hoc work, change a rate card or contact a handler. Accounts Payable releases, and the station manager approves.
A chained audit trailEvery read, finding, decision, letter and payment is recorded with who or which agent acted, when and the sources cited. Entries are chained, and the evidence pack exports for audit.
Configuration

Your handling policy, set once

Thresholds, rules and clocks are settings. Every change is logged and applies to the next run; the agents can fill a change in, but only a person saves it.

SettingDefaultChoose from
Co-sign threshold$25,000Any amount; short-pays above it need Procurement as a second signature
Tolerance per line$0Any amount; unsupported dollars below it are paid without a finding
Reader confidence90%Any percentage; below it on any field, the reader asks for a clearer copy
Release clean invoices automaticallyOffOn · Off
Verifier on every findingLocked onCannot be turned off
Delay standby only for Corvane-coded delaysOnOn · Off — IATA delay codes decide who caused the delay
Decide every invoice before it is due5 business daysAny number of business days
Handler reply window30 daysAny number of days (Annex B item 14)
Connections

Works with the systems a handler invoice already touches

IATA SIShandler invoices in IS-XML, rejection memos and credit notes
Operations systemturn records, schedule, cancellations and IATA delay codes
Aircraft APU dataACARS engine and APU reports per tail
Airport gate-power feedsfixed 400 Hz meters per gate and station
Rate cardsSGHA Annex B per station and every amendment with its effective date
Finance systemaccounts payable holds, payment runs and the vendor master
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
1–3%
of handling spend kept: $3.8–11.4M a year on a $380M handling bill
target
100%
of lines tied to turn, rate and approval, not a sample
every line
stitched or left loose
target
5days
before the due date, every invoice decided and the undisputed amount paid on time
Todaypaid unchecked or late
With agentsdecided early

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate. Standards named: IATA Standard Ground Handling Agreement 2023 (Annex B); IATA IS-XML Structure and Interface Specification for Ground Handlers (Sept 2014); IATA AHM 730/731 delay codes. Rates, clauses, thresholds and clocks shown are the sample airline's own. People, the airline Corvane Airways, handlers, flights and invoices named on this page are fictional — characters and sample data in the working solution.

Questions

What airlines ask about ground handling invoice reconciliation.

What is ground handling invoice reconciliation?

Ground handling invoice reconciliation is the airline's check that every line a ground handler bills was performed, is billable under the station's Standard Ground Handling Agreement (SGHA) Annex B and is priced at the rate in force that day, before the invoice is paid. Ground Handling Invoice Reconciliation adds seven agents that read every invoice in any format, stitch each line to its turn record, Annex B rate and ad hoc approval, and draft the short-pay for the cost controller to confirm and sign.

How do airlines audit ground handling invoices line by line?

A handling invoice audit ties each line to the operated turn in the operations system, to cancellations and delay codes, to the Annex B rate of its service date and, for ad hoc work, to the station's request. Lines with no proof are left loose with a reason, and an independent Verifier re-derives every finding before a person sees it.

How does it check ground power (GPU) charges?

The Turn matcher reads the aircraft's ACARS APU record and the airport gate-power meter as well as the handler's turn log. A GPU charge on a turn where the APU ran, the gate meter read 0.0 kWh and the log shows no connection is left loose — in the sample month, 46 such lines on one Denver invoice.

Does it read IATA SIS IS-XML invoices and scanned service records?

Yes. The Invoice reader reads IS-XML from IATA SIS, PDFs, spreadsheets, EDI files and scanned ad hoc service records, maps each line to the IS-XML fields and scores every field. Below 90% confidence it asks for a clearer copy instead of guessing, and it catches a re-sent invoice as a duplicate.

How does it apply SGHA Annex B rates and mid-contract amendments?

The Rate checker prices each line from the station's Annex B and the amendments in force on the service date. An amendment applies only from the effective date Procurement confirmed, so a new rate billed before it starts — 62 A321neo turns in the sample — is caught.

How are short-pays and disputes with the handler handled?

The short-pay letter, the IATA SIS rejection memo and the finance-system hold are generated only from lines the cost controller confirmed, with the Annex B clause for each. When the handler replies, the Dispute responder re-checks the new evidence, proposes concede or hold per line and matches credit notes; a person decides and sends.

Do people stay in control of what is withheld and paid?

Yes. The agents never withhold, send, pay, approve ad hoc work, change a rate card or contact a handler. The cost controller confirms each withheld line and signs with a reason code, Procurement co-signs above $25,000, station managers approve their own ad hoc work, and Accounts Payable releases the undisputed amount.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your handling agreements and Annex B rate cards, a month of handler invoices and the feeds for turns, APU and gate power — and it goes live once every quality gate has passed. We will walk you through it on your own invoices first.

See it on
your handler invoices.

We'll run Ground Handling Invoice Reconciliation on a month of your own handler invoices, turn records and rate cards.