Ground Handling Invoice Reconciliation: AP Workflow Guide

Ground handling invoice reconciliation, sometimes framed as ground handling charges reconciliation, is the payment control process of matching a handler's invoice to turnaround records, SGHA or local rate terms, and approvals for any ad hoc services before payment. A sound review confirms three things on every charge: the service was performed, the agreement allows it to be billed, and the invoice used the correct charging basis.

That is why this workflow sits in a different lane from airport charges, fuel, or owner-side FBO billing. An airport charges reconciliation workflow is driven by tariffs and authority-issued billing rules. An aviation fuel invoice reconciliation process turns on uplift evidence, contract pricing, and fuel ticket support. Ground-handler invoice review depends on the service record for the turn, the station's governing agreement, and the exact inputs that triggered each billed service.

The AP question is therefore not just whether the flight took place. Finance needs to know whether the invoice reflects services that were actually delivered on that arrival or departure, whether those services sit inside the agreed handling package or outside it, and whether the handler used the right basis for pricing, such as aircraft category, passenger count, baggage volume, overtime window, or delay event.

Before reviewing any billed line, assemble the evidence packet that lets those questions be answered quickly: the handler invoice, the SGHA Annex B or local rate schedule, the turnaround or service report, flight references, passenger or baggage counts where they drive charging, approvals for extra services, and any open dispute or credit history tied to prior invoices. Without that packet, teams end up arguing from memory and spot-checking only the most obvious lines.

Build the evidence packet before reviewing any billed line

The invoice should be the last document in the packet, not the first. Finance can only test a handler bill properly when the agreement and the service evidence are sitting beside it. In practice, that means pulling together the invoice itself, the SGHA Annex B or local rate schedule that defines the station's billable services, the turnaround or service report for the flight, the flight reference details, passenger or baggage counts where they affect charging, approvals for ad hoc work, and any unresolved credit notes or dispute logs from prior periods.

Each item answers a different control question. The agreement shows what the handler is entitled to bill and how the price is meant to be constructed. The turnaround record shows what actually happened on the turn. Flight identifiers tie the charge to the right movement. Passenger, baggage, aircraft, delay, and timing inputs explain why a service fell into one charging bucket instead of another. Approval notes matter because many of the charges that cause the most friction are not routine ramp or passenger services but extras that someone requested under operational pressure and nobody documented well enough for AP later.

That agreement document is not background reading. According to IATA's overview of what SGHA Annex B contains, SGHA Annex B records the location, agreed-on services, negotiated details, and charges. For invoice review, that matters because Annex B or its local equivalent is where finance finds the service scope, the negotiated billing logic, and the station-specific pricing rules that turn a vague line description into something testable.

The packet also needs to be station-specific. One handler may bill a service as included at one airport and as an extra at another because the local agreement, aircraft mix, or service package changed. A reliable review process does not assume that one month's invoice explains the next one. It keeps the current agreement version, the current rate basis, and the supporting operational record together so the reviewer is checking the billed service against the right local logic.

Test each charge against the agreement, the turn, and the billing basis

Once the packet is complete, the review moves line by line. The first test is simple: does the billed service appear in the turnaround or service record for that flight. The second is contractual: is that service separately billable under the SGHA or local agreement, or is it already included in the package the operator pays for. The third is pricing logic: did the handler apply the correct basis for the charge that was allowed.

That billing basis is where many disputes start. A line may be correct in principle and still wrong in amount because the handler used the wrong aircraft category, the wrong weight band, the wrong arrival or departure event, the wrong passenger input, or the wrong overtime window. Delay and night surcharges need the same treatment. If the event record does not support the timing or service trigger used on the invoice, AP should not treat the charge as valid just because the service description looks familiar.

This is also where bundled versus ad hoc services need to be separated cleanly. A ground handler invoice audit should identify which lines belong to the agreed base package and which ones are extra-call items that require explicit support. Routine contracted services should map back to the service scope and inclusions in the station agreement, while extras should map back to a specific request, event, or exception that made them billable. If a service is already included, finance should not pay it again as a separate line. If it is genuinely outside scope, the packet should show why it was requested, who approved it, and which charging rule applies.

The discipline is similar to other aviation AP controls in that evidence and contract terms must meet before payment, but the documents are different. An aviation MRO invoice processing workflow depends on maintenance records, work scopes, and parts support. Handler billing is anchored to the turn, the local service agreement, and the operational inputs that determine whether each service line belongs on the invoice at all.

The discrepancies that deserve immediate exception review

Most airline ground handling billing discrepancies trace back to a small set of failures in the evidence chain. The aircraft or service basis may be wrong, so the handler billed against the wrong weight band or service category. Arrival and departure services may both appear twice. Overtime or delay surcharges may be present even though the event record does not support the billed timing. Passenger or baggage-driven services may use counts that do not match the final operating data.

Ad hoc charges deserve separate treatment because they often arrive with the weakest support. An effective ad hoc ground handling charges review asks for two things immediately: proof that the service was actually requested or performed, and proof that the agreement allows the handler to bill it outside the standard package. If neither exists, AP should not treat the line as a routine payable item. It is an exception that belongs in a dispute queue until the handler or station contact supplies the missing authorization.

Inclusive services billed again are another common source of leakage. A service may appear as part of the handling package in the agreement and still show up a second time on the invoice under a local description or station shorthand. Taxes and station fees can create similar noise when the billing basis is unclear or the same underlying cost is represented through multiple line labels. Credit carry-forwards also need attention, because a valid dispute resolved last month still creates overpayment if the promised credit never reaches the live invoice.

The point of exception review is not to build a catalog of every possible error. It is to map each discrepancy to the missing or conflicting evidence that would resolve it. Once finance can say whether the problem is a missing service record, an unsupported surcharge trigger, an unauthorized extra service, a duplicated inclusion, or an unposted credit, the dispute becomes actionable instead of turning into another vague email chain.

Build an exception-based workflow that scales across stations

A scalable review process starts by standardizing the packet before anyone debates the invoice. Pull the handler bill, agreement terms, turn data, approvals, and prior dispute history into one review set, normalize the invoice lines into a consistent structure, and flag only the mismatches that fail one of the core control tests. That keeps finance from rebuilding every turnaround manually and makes recurring station review more about exceptions than rekeying.

The best workflows keep source references attached to the structured data. When a line is flagged, the reviewer should be able to jump straight back to the invoice page, the supporting approval, or the underlying service record without hunting through email attachments and shared drives. That is the practical value of an invoice exception management workflow: the issue is defined by the missing or conflicting evidence, assigned to the right owner, and tracked until it is cleared or credited.

This is also where invoice processing automation workflows become useful. Invoice Data Extraction converts invoices and financial documents into structured Excel, CSV, or JSON files from a natural-language prompt, which helps teams normalize varied handler invoice layouts into one review format and pair that structured invoice output with turnaround and approval records already held elsewhere in the review pack. The platform also keeps source file and page references attached to each output row, so a flagged charge can be traced back to the original invoice quickly during review. That does not replace agreement judgment or station knowledge, but it does reduce the manual effort required to get inconsistent invoice data into a usable control table.

For teams handling multiple stations or handler formats, the operating goal is straightforward: standardize what can be standardized, preserve the evidence trail, and escalate only the lines that fail the agreement, service, or pricing test. When that structure is in place, month-end review becomes faster, disputes become easier to document, and payment approval is based on evidence instead of habit.