Built by QuantSpark Labs

Global Airport Services Operator

AI-Driven Revenue Recovery for Global Airport Services Operator

QuantSpark helped a global airport services operator identify £1.5M in potential revenue leakage within four weeks using a Generative AI-powered solution for invoice reconciliation.

21 April 20262 min read
Headline result
£1.5M
Potential Revenue Leakage Identified
At a glance
£1.5M
Potential Revenue Leakage Identified
4 weeks
Engagement length
Hero image for: "AI-Driven Revenue Recovery for Global Airport Services Operator". Topic: QuantSpark helped a global ...

Potential revenue leakage identified

£1.5M

  • £1.5M of potential revenue leakage identified within a four-week feasibility study
  • 42,000 invoiced lines processed for discrepancies
  • 16% discrepancy rate found across the processed lines
  • Solution applied across three airlines and two international airports, demonstrating cross-site applicability

The problem

A global airport services operator was losing an estimated millions of pounds a year to revenue leakage, principally through underbilling customers for services that had already been delivered.

Two root causes drove the leakage: inaccurate service capture information, meaning gaps and errors in recording what had actually been delivered, and flawed implementation of the contractual billing logic that should have converted that delivery into an accurate invoice, causing agreed terms and actual charges to drift apart.

Historically, recovering this lost revenue depended on manual reconciliation. That process was non-exhaustive and inconsistent between contracts, so it could only ever catch a fraction of the leakage and could not scale across the operator's wider operations.

How we delivered it

  1. Scope a time-boxed feasibility study

    QuantSpark scoped a four-week feasibility study to test whether a generative AI solution could reconcile invoiced revenue against expected revenue, rather than committing to a full build against an unproven hypothesis.

  2. Extract contractual terms with multi-modal LLM techniques

    Applied multi-modal large language model techniques to pull prices, clauses and conditions directly out of contract documents, including manually scanned PDFs that would defeat conventional text extraction.

  3. Match delivered service against contracted terms

    Used natural language processing techniques to dynamically map service capture records, what was actually delivered, against the extracted contractual information, what should have been billed.

  4. Reconstruct and compare invoices

    Generated a reconciled invoice from the matched data and compared it line by line against the invoices historically issued, surfacing discrepancies across the processed dataset.

  5. Categorise discrepancies by root cause

    Classified each discrepancy by its underlying driver, for example an agreed price change versus a billing logic inaccuracy, so findings could trigger and support financial and commercial audit investigations rather than sit as an undifferentiated list.

  1. Contract documents

    Prices, clauses and conditions extracted from contracts, including manually scanned PDFs, via multi-modal LLM techniques

  2. Service delivery records

    NLP-based matching maps what was actually delivered against what the contract says should have been billed

  3. Reconciliation engine

    Reconstructed invoices compared line by line against historically issued invoices to surface discrepancies

  4. Categorised findings

    Discrepancies classified by driver, for example price change versus billing logic error, to trigger audit investigation

From raw contract and service-delivery data to categorised, audit-ready discrepancy findings in a single AI-driven pipeline.

Built with

  • Multi-modal large language model (document extraction)

    Extracted prices, clauses and conditions from contract documents, including manually scanned PDFs

  • Natural language processing (service-capture matching)

    Mapped delivered-service records against the extracted contractual terms to identify what should have been billed

  • Automated invoice reconciliation and categorisation logic

    Compared reconstructed invoices against historically issued invoices and categorised discrepancies by underlying driver

Return on investment

Delivered return

£1.5M

Potential revenue leakage identified

What was delivered

  • £1.5M of potential revenue leakage identified within a four-week feasibility study
  • 42,000 invoiced lines processed for discrepancies
  • 16% discrepancy rate found across the processed lines
  • Solution applied across three airlines and two international airports, demonstrating cross-site applicability

How the return was measured

The £1.5M figure is the value of discrepancies the algorithm surfaced across the 42,000 invoice lines processed during the four-week study; it is an identified opportunity, not cash already recovered at the point the study concluded. Each discrepancy was categorised by driver, for example an agreed price change or a billing logic inaccuracy, which is what makes the figure defensible: a financial or commercial audit team can work through the categorised list, validate each finding against the underlying contract, and pursue recovery only where the audit confirms it. Realised recovery therefore depends on that downstream audit process and falls outside the scope of the reported feasibility-study results.

QuantSpark helped a global airport services operator identify £1.5M of potential revenue leakage within a four-week feasibility study, using a generative AI-driven algorithm to reconcile invoiced revenue against what should have been billed. The study processed 42,000 invoiced lines, found a 16% discrepancy rate, and proved the approach worked across three airlines and two international airports, turning an opaque billing problem into a defensible, categorised list the client's own audit teams could act on.

The operator was losing an estimated millions of pounds a year through underbilling: charging customers for less than the services actually delivered. Two things were driving it. First, the record of what had actually been delivered, the service capture data, was itself patchy and error-prone. Second, the contractual billing logic that should have converted delivery into an invoice was not being implemented consistently, so agreed terms and actual charges drifted apart. Historically, recovering this lost revenue depended on manual reconciliation. That process was slow, non-exhaustive and inconsistent between contracts, so it could only ever catch a fraction of the leakage and could not scale across the operator's wider operations.

QuantSpark's response was to scope a tightly time-boxed, four-week feasibility study rather than commit to a full build against an unproven hypothesis. The pipeline had three linked stages. First, impact document extraction: multi-modal large language model techniques pulled prices, clauses and conditions directly out of contract documents, including manually scanned PDFs that would defeat a conventional text-extraction approach. Second, service capture matching: natural language processing techniques dynamically mapped what had actually been delivered against the contractual terms just extracted, effectively answering "what should this have cost, given the contract, and what was it actually billed at?" for every line. Third, discrepancy identification: the algorithm reconstructed what the invoice should have been and compared it line by line against the invoice that was actually issued historically. Every discrepancy found was then categorised by its underlying driver, for example an agreed price change that had not been reflected in billing, versus a straightforward billing logic error, so the output fed directly into the client's own financial and commercial audit investigations rather than landing as an undifferentiated list requiring manual triage.

The technology involved sits in two categories: a multi-modal LLM layer for document extraction, and an NLP layer for matching delivered service against contracted terms, wrapped in an automated reconciliation and categorisation step. No specific proprietary system is named here because none was disclosed in the public source, and none should be inferred.

The headline £1.5M is best read as the value of the discrepancies the study surfaced across the 42,000 lines processed, not as cash the client had, at the point the study concluded, already recovered. That distinction matters for anyone citing this case study: the categorisation step is precisely what makes the number defensible, because it lets a human audit team work through each flagged discrepancy against its actual contract and pursue recovery only where that audit confirms the finding. Realised recovery sits downstream of the feasibility study, inside the client's own audit process, and is not itself part of the reported result.

What makes the case compelling is less the size of the number and more what it proves: that a generative AI pipeline can take a process that was manual, non-exhaustive and inconsistent, and turn it into something systematic, categorised and demonstrably applicable across multiple airlines and airport sites within a month, at a scale, 42,000 lines, that manual reconciliation was never going to reach.

Figures are drawn from completed QuantSpark engagements. Clients are anonymised by agreement; on a call we will walk you through how each number was measured and, where the client has agreed, put you in touch with a reference.

Ask about our work

Answers only from our documented case studies

Powered by the same applied-AI approach we deliver for clients

Solving something similar in Industrial & Aviation?

Get in touch. We will discuss your challenge and show you what is possible.