WorkflowNetwork Planning & Revenue Management

Airline Revenue Integrity

Airline revenue integrity that reads every booking every night and puts held seats back on sale before departure

Every booking read every night, and held seats back on sale before departure.

See one case, screen by screen ↓
demo318storiesbuilt overnight from 1,862,400 bookings and 2,412 flags, in 72 minutes
demo14seatsback on sale at $312 on CV 220 with one approval, 22 days before departure
demo32storiescleared overnight by the second look as innocent, each with its reason
target100%of bookings read every night, not a sample
In short

What is Airline Revenue Integrity?

Airline revenue integrity is the work of finding bookings that are not real demand — churned bookings, duplicate bookings, fictitious names, inactive and passive segments — and putting the seats back on sale before departure. Airline Revenue Integrity is revenue integrity software that does it with seven agents: they read every booking every night, link the related bookings into one cited story, rule out the innocent explanation first and propose each action, for a revenue integrity analyst to approve and sign.

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

Updated

The problem

Why airline revenue integrity still works one booking at a time

Airline revenue integrity starts from a hard fact: a network airline holds millions of live bookings, and some of them are not real demand. An agency cancels and rebooks the same passenger to get around the ticketing time limit. The same traveler is booked twice through two channels. Seats are held under TEST/TEST or MOUSE/MICKEY. Canceled HX, UN and NO segments sit in bookings where the distribution system keeps billing for them. Each of these unproductive bookings keeps a seat off sale, inflates the revenue management forecast and costs a GDS segment fee.

Revenue integrity analysts work rule queues one booking at a time, open the booking history, search for the related bookings by name, phone or agency office by hand, and sample the rest. A churn pattern spread over ten bookings and three weeks is easy to miss. A rebook after the airline's own schedule change, or a group re-sending its name list, looks exactly like churn. And an agency debit memo (ADM) built on a screenshot instead of the chain loses in dispute. A seat released two days before departure rarely resells.

typical3%of revenue lost to airline revenue leakage, at the high end
typical$150Ma year spent by the industry managing agency debit memos
Where a churn case's hours goestimated
By hand6.3 days
With the solution1 days
  • Finding the related bookings by name, phone and office1.5 → 0.1 d
  • Reading each booking's history1 → 0.2 d
  • Ruling out schedule changes, groups and the 24-hour rule0.8 → 0.1 d
  • Valuing the seats and checking the agency booking policy0.5 → 0.1 d
  • Building the memo's evidence and the agency warning1.5 → 0.3 d
  • Answering the agency's dispute1 → 0.3 d

Estimated split for one churn story worked by an analyst, by hand and with the solution.

How it works

How a night of bookings moves

Seven agents read every booking, link the chains, argue the innocent case first and propose each action; analysts approve and sign.

What comes in
Every booking1,862,400 bookings · reservations, feeds, inventory, policy
Agents at work
Booking readerwith history
Then
Churn and duplicate finder
Name checker
Segment sweeper
Then
Second-look checkerinnocent first
Then
Case builder
Agency liaison
A person decides
Revenue Integrityapproves and signs
What comes out
Seats back on sale
Memos with evidence
Audit trail
One case, step by step

Airline revenue integrity, one churn story from overnight flag to signed decision

Corvane Airways runs about 300 aircraft from its Chicago O'Hare hub. On Thursday, October 15, its revenue integrity analyst opens the day the agents prepared overnight. Here is what happens next, screen by screen, in the working solution.

  1. 018:40 am CT

    What needs her, in the agents' order

    Dana Whitfield · Revenue Integrity Analyst

    Dana's Today screen shows 12 of the team's 41 stories that need a person, $60,070 at stake in hers. Overnight the agents found 318 stories in 1,862,400 bookings; 1,146 seats went back on sale this week, and 32 stories were cleared by the second look. The top one is a churn on CV 220 ORD–SEA; the second, nine bookings on CV 640 past the TSA Secure Flight 72-hour mark at 6:15 am.

    “Distribution feed 3 arrived 41 minutes late; its bookings were read at 3:05 am.”

  2. 022:00 – 3:12 am

    Seven agents, each checking the last

    The agents

    The booking reader read every active booking departing in the next 330 days, with its history, from reservations and three distribution feeds. The churn and duplicate finder checked 14,280 chains, the name checker set aside 47 loyalty members as real people, and the segment sweeper cleaned up 236 inactive segments and expired web holds under standing rules R5 and R6. The case builder grouped 2,412 flags into 318 stories; the agency liaison drafted 19 memos and 11 warnings and sent none.

    “Anything that touches an agency waits for a person.”

  3. 03One click

    Ten bookings, one name: the churn drawn as a chain

    Churn and duplicate finder

    Lakeshore Travel Group, office 7KQ2, booked SMITH/J MR and 13 unnamed seats on CV 220, Fri Nov 6, ten times between Sep 22 and Oct 14. Each booking was canceled just before its 72-hour ticketing limit and rebooked 3 to 9 minutes later. Dana clicks link 3: B2NV6L, canceled Sep 30 at 3:20 pm and rebooked as T8JD4Q 4 minutes later. Fourteen seats in class L have been held for 23 days, never ticketed; class L closed to new sale on Oct 1, and the same seats sell today at $312.

    Every sentence of the reading cites the booking line it rests on — 14 seats, 23 days, $592.90 in GDS fees paid, $4,368 at today's fare.

  4. 04Before she sees it

    The innocent explanations, ruled out first

    Second-look checker

    Did Corvane change the flight? No time, routing or cancellation change for Nov 6 since Aug 4. Is it a group with a contract? None for CV 220. Are these real, named travelers? Thirteen of the 14 seats have never had a name. Could the DOT 24-hour rule explain the cancels? No: they came 2 to 3 days after booking, and no seat was ever ticketed.

    The second-look checker clears a story only with a reason, and cannot change a rule.

  5. 05In conversation

    She asks “Why $1,350?” and gets the policy

    Dana Whitfield and the agency liaison

    The case builder proposes three actions: cancel the 14 held seats and return them to sale, a $1,350 debit memo to Lakeshore, and a second warning copied to its sales manager. Dana asks why $1,350. The agency liaison answers that policy §4.2 sets $150 for each cancel-and-rebook cycle, there were nine, and Corvane's GDS cost for the same bookings was $592.90 — it can switch the memo to that amount if she prefers.

    “I propose three actions. Anything that touches the agency waits for you.”

  6. 068:51 am

    Approved: 14 seats back on sale

    Dana Whitfield · Revenue Integrity Analyst

    Dana approves the first proposal with her e-signature. P9XH3D is canceled and the 14 seats are back on sale in class M at $312. Revenue management has the update, and Lakeshore gets a notice with the ten booking lines. The decision is on the audit trail with her name and the time.

    Agency liaison: “Done at 8:51 am. P9XH3D is canceled and 14 seats are back on sale in class M at $312.”

  7. 07The flight

    CV 220 shows the seats come back

    Case builder

    On the A321neo's flight view, economy booked drops from 150 to 136, held without a ticket from 14 to 0, and open to sell rises from 26 to 40, with class M open at $312. Revenue management still forecasts 22 more economy bookings before departure, so the seats are likely to sell — 22 days out, not two.

  8. 08To Sales Audit

    A $1,350 memo with an evidence pack built for a dispute

    Elena Ruiz · Sales Audit Specialist

    Over $1,000, so the memo goes to review. ADM-26-10-0418 reaches Elena Ruiz with reason code BK-CHURN and a seven-item evidence pack: the ten linked bookings, the first and last booking histories, policy §4.2 and §4.1–§4.7, the distribution billing and the agency file. She issues it through ARC or BSP settlement with her own signature, returns it to the analyst, or changes the amount.

    “In the last six months, 26 of 31 disputed churn memos were upheld.”

  9. 09The agency

    The second warning, seen first by the sales manager

    Agency liaison

    Lakeshore Travel Group has 23 stories in 90 days and a churn warning from Mar 12, 2026. The agency liaison drafted the second warning to its branch manager, citing the ten bookings, policy §4.2 and the March warning. Nothing goes until Dana approves it, and Owen Price, Corvane's agency sales manager for Lakeshore, sees it for 4 hours before it is sent.

  10. 10Later that day

    A rule that learns from what people cleared

    Marcus Bell · Revenue Integrity Manager

    In September analysts cleared 18 churn stories that were school and tour groups re-sending their name lists. The second-look checker proposes an exception to R1 Churn for bookings under a group contract still before its name-list date. Replayed on the last 90 days: 3,412 stories become 3,394, none of the 18 reach a person, and no story that led to a memo is missed. Only Marcus can approve it.

    “Rule changes need the Revenue Integrity Manager.”

Who it’s for

Built for everyone in airline revenue integrity.

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

DW
Dana WhitfieldRevenue Integrity Analyst · decides 30–50 stories a day
Revenue Integrity Analyst
Before
“Show me the story, not 2,000 flags — and show me why it isn't innocent.” Opened queue entries one booking at a time and searched for the rest by hand.
Now
Starts at 8:30 am with what the overnight run found, sees each pattern as one chain with every line cited, and approves, edits or rejects each action with a reason.
MB
Marcus BellRevenue Integrity Manager · owns the rules and the monthly report
Revenue Integrity Manager
Before
“I tune the rules. Nobody, human or agent, changes one without a replay.” Tuned thresholds from experience, usually without a measured replay.
Now
Signs rule changes only after a 90-day replay, approves memos over $5,000, and signs the monthly results the case builder drafts with every figure cited.
ER
Elena RuizSales Audit Specialist · issues memos through ARC and BSP
Sales Audit Specialist
Before
“If a memo can't survive a dispute, I don't send it.” Received memos backed by screenshots, and rebuilt the evidence when an agency disputed.
Now
Reviews every memo over $1,000 with its evidence pack, issues it with her signature, and answers disputes from a reply the agency liaison drafts from the booking lines.
OP
Owen PriceAgency Sales Manager · owns the agency relationships
Agency Sales Manager
Before
“Tell me before you write to my agency.” Heard about warnings after the agency called him.
Now
Sees every warning to his agencies 4 hours before it goes, with the agency's full record of stories, memos and patterns beside it.
TO
Tom OkaforAdministrator · systems and roles
Administrator
Before
“If feed 3 is late, I want to know before Dana does.”
Now
Is told the moment a connected system is late or down, sees each feed's status in the run and in Settings, and manages roles — but never decides a story.
Built on the engine

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

Seven agents read every booking, link the chains, argue the innocent case first and propose each action; analysts approve and sign.

Booking reader

Reads every active booking departing in the next 330 days, with its history, from the reservations system, inventory and three distribution feeds.

  • Read-only
  • Reports a late feed instead of skipping it
Churn and duplicate finder

Links bookings across days, channels and agencies by name, phone, office, flight, date of birth and loyalty number, and draws each pattern as one chain.

  • Never decides — it flags with a confidence
Name checker

Finds fictitious, test and placeholder names such as TEST/TEST and MOUSE/MICKEY, excluding loyalty members, and checks Secure Flight status.

  • Never touches a named, ticketed passenger
Segment sweeper

Finds inactive (HX, UN, UC, NO), passive (GK) and expired segments, and removes them on its own only under standing rules R5 and R6.

  • Acts alone only under the two standing rules the manager approved
  • Never acts on an agency booking
Second-look checker

Tries the innocent explanation first — the airline's own schedule change, a group contract, a real loyalty member, the DOT 24-hour rule — and proposes rule changes, each with a 90-day replay.

  • Clears a story only with a reason
  • Cannot change a rule
Case builder

Groups flags into stories, values the held seats at today's fare from inventory and the revenue management forecast, and proposes each action with the money at stake and the evidence.

  • Proposes only; a person decides
  • Never acts on an agency
Agency liaison

Drafts notices, warnings and debit memos with evidence packs, tracks disputes and drafts the replies from the same booking lines.

  • Nothing reaches an agency without a person
  • Agency sales managers see warnings first
Revenue Integrity

Analysts approve every action; Sales Audit issues memos. The agents propose; a named person decides.

Ask in plain words

Ask the agents, in your own words

Ask about any booking, flight, agency or memo — or tell the agents what to change. Each answer cites its sources and opens the item.

Why is SMITH/J on CV 220 a churn and not a group?

Ten bookings under SMITH/J MR, same phone and office 7KQ2, each canceled before its 72-hour limit and rebooked 3 to 9 minutes later. Lakeshore has no group contract for CV 220, and 13 of the 14 seats have never had a name.

Which stories can't wait?

Four. S-4471 first: the chain will churn again before its limit on Oct 17, and its 14 seats sell today at $312. Then S-4447, nine bookings on CV 640 past the Secure Flight 72-hour mark at 6:15 am, and S-4457 and S-4452, which reach their ticketing limits tomorrow morning.

What are the seats worth?

The 14 seats sell today in class M at $312, about $4,368. Revenue management expects 22 more economy bookings before departure, so they are likely to sell.

How much did we return to sale in September?

18,430 seats went back on sale before departure in September, and 214 debit memos were issued for $312,600. Distribution fees avoided are an estimated $684,200.

Every screen

The working solution, as it ships.

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

TodayThe revenue integrity analyst's day: stories that need her with the money at stake, the agents' overnight summary of every booking read, and ask the agents.
Last night's runSeven agents step by step from booking read to churn, duplicate, fictitious-name and inactive-segment findings, with the status of each feed they read.
The churn story as a chainTen churned bookings on a 23-day axis, minutes between each cancel and rebook, the held seats, the plain reading with citations and the agents' proposals.
The second lookSchedule change, group contract, named travelers and the DOT 24-hour rule — each innocent explanation checked and ruled out with its source.
Working with the agentsThe analyst asks why the debit memo is $1,350 and the agency liaison answers from the agency booking policy and the GDS billing.
Seats back on saleOne approval cancels the churned booking and returns 14 held seats to sale at today's fare, with revenue management told.
The flight viewEconomy seats booked, held without a ticket, open to sell and still to come, each fare class, and the seats the churn chain held day by day until they went back on sale.
Agency debit memo with its evidence packA churn ADM in Sales Audit review, with the amount, reason code and the seven-item evidence pack that goes to the agency.
The agency fileAn agency's stories, memos, warnings and booking patterns over 90 days, with the drafted second warning its sales manager sees first.
Rules with replayEleven revenue integrity rules — churn, duplicate bookings, fictitious names, inactive and passive segments — and a change the agents propose, replayed on 90 days.
ResultsSeats back on sale before departure, debit memos issued and collected, the upheld rate in dispute, and estimated held seats resold and GDS segment fees avoided.
Audit trailThe revenue integrity audit trail: every read, proposal and signed decision by people and agents, kept seven years, with an evidence pack export for an agency debit memo dispute.
Thresholds and approvalsConfidence to raise a story, memo review limits, warning and escalation counts, the churn amount per cycle, and agency actions locked to a person.
Governance

Airline revenue integrity on the record: cited, signed, replayed.

Every statement cites its sourceEach sentence and value points to the booking history line, policy section, inventory, forecast, GDS billing, group desk or Secure Flight record it rests on, and a read-only copy stays with the story for disputes.
Agency actions always need a personThe agents never cancel an agency booking or send a notice, warning or memo on their own. The setting is locked on and cannot be turned off; only standing rules R5 and R6 act alone, approved by the manager.
Approve, edit or reject — with a reason and a signatureEvery decision carries an e-signature and a reason code. A rejection's reason goes into the agents' next run, and an edit is recorded on the audit trail in the analyst's own words.
Memos reviewed above $1,000Debit memos over $1,000 go to Sales Audit before they reach the agency through ARC or BSP settlement; over $5,000 the manager signs too. Agency sales managers see warnings 4 hours before they go.
Rules change only after a replayA rule or threshold change — from an analyst or proposed by the agents — is replayed on the last 90 days and signed by the Revenue Integrity Manager. Old versions are kept.
Seven years on the audit trailEvery read, proposal and decision by people and agents is recorded and cannot be edited. Any story exports as an evidence pack with its chain, its sources and every signed decision.
Configuration

Your agency booking policy, not ours

The thresholds every story is checked against are settings. Changes go to the Revenue Integrity Manager for approval and are on the audit trail.

SettingDefaultChoose from
Raise a story when the agents are at least80% confidentAny level; changes need the manager's approval
Memos above this go to Sales Audit review$1,000Any amount; changes need the manager's approval
Memos above this also need the manager$5,000Any amount; changes need the manager's approval
Warn an agency after2 stories of one pattern in 90 daysAny count
Escalate to the agency's sales manager after3 warnings in 12 monthsAny count
Churn memo amount, per cycle (policy §4.2)$150Your published policy amount
R1 Churn — same lead name, flight and agency, canceled and rebooked≥ 3 cycles in 14 daysTuned with a 90-day replay, then approved by the manager
Agency actions always need a personAlways onLocked — cannot be turned off
Connections

Works with the systems your bookings already live in

Reservations systembookings and their history, read nightly; cancels only after a person approves
Inventory and revenue managementseat counts by fare class, the forecast, and returned seats reported back
Distribution feedsagency bookings and segment billing from three GDS feeds
ARC and BSP settlementdebit memos sent and tracked, after Sales Audit signs
Group desk, loyalty and agency directorygroup contracts and name-list dates, loyalty records, agencies and their sales managers
TSA Secure Flight statuswhether passenger data reached TSA before the 72-hour mark set by 49 CFR 1560.101
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.86M
bookings read every night, not a sample
1,862,400 of 1,862,400
Oct 15 overnight run
estimated
$27.9M
a year of held seats resold before departure at a 300-aircraft carrier
estimated
$8.2M
a year of distribution fees avoided on churn and inactive segments

“demo” = seen in the working solution, on its sample bookings · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (the Airline Revenue Integrity Group, quoted in a 2017 industry paper: leakage up to 3% of revenue; an IATA study, May 2020: managing agency debit memos costs the industry about $150M a year; 14 CFR 259.5(b)(4); 49 CFR 1560.101; IATA Resolution 850m). Corvane Airways, its agencies, people, flights and booking locators named on this page are fictional — characters and sample data in the working solution.

Questions

What revenue integrity teams ask us.

What is Airline Revenue Integrity?

Airline revenue integrity is the work of finding bookings that are not real demand — churned bookings, duplicate bookings, fictitious names, inactive and passive segments — and putting the seats back on sale before departure. Airline Revenue Integrity is revenue integrity software that does it with seven agents: they read every booking every night, link the related bookings into one cited story, rule out the innocent explanation first and propose each action, for a revenue integrity analyst to approve and sign.

What is churning in airline bookings?

Booking churning is canceling and rebooking the same passenger, usually just before the ticketing time limit, to hold seats without paying for them. Each booking looks normal on its own; the pattern only shows across the chain. In the demo, ten bookings under one name held 14 seats for 23 days, each rebooked 3 to 9 minutes after its cancel.

How does it tell churn from a group booking or a schedule change?

Before any story reaches a person, the second-look checker tries the innocent explanations: the airline's own schedule change, a group contract, a real loyalty member and the DOT 24-hour rule in 14 CFR 259.5(b)(4). When one applies, it clears the story with its reason; in the demo, 32 stories were cleared that way overnight, all visible.

Does it find duplicate bookings, fictitious names and inactive segments too?

Yes. The churn and duplicate finder matches travelers across channels by name, date of birth and loyalty number, and flags speculative bookings, where the same travelers are held on several flights in one market on one day (GDS misuse that agency booking policies prohibit); the name checker finds test and placeholder names while excluding loyalty members; and the segment sweeper finds inactive HX, UN, UC and NO segments, passive GK segments and expired holds. Inactive segments keep GDS segment fees running until they are removed.

How do you make an agency debit memo hold up in a dispute?

Each memo is built from the story itself: the linked bookings, their booking histories, the agency booking policy section and the distribution billing travel with it as an evidence pack. Under IATA Resolution 850m and, in the US, the ARC Agent Reporting Agreement, an airline may debit an agency for breaches of the booking policy it has published, and the agency may dispute. Memos over $1,000 go to Sales Audit before they are issued through ARC or BSP settlement, and when an agency disputes, the agency liaison drafts the reply from the same passages.

Does it cancel bookings or write to agencies on its own?

No. Agency actions — cancels, notices, warnings and memos — always need a person, and that setting cannot be turned off. The agents act alone only under two standing rules the manager approved: removing inactive segments and releasing expired unticketed holds on the airline's own website. Every decision is approved, edited or rejected with a reason and an e-signature.

Can we set our own rules and thresholds?

Yes. The 11 rules, their thresholds, the confidence to raise a story, memo review limits, warning and escalation counts and the churn amount per cycle come from your agency booking policy. Every change is replayed on the last 90 days and signed by the Revenue Integrity Manager.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your agency booking policy, your rules and a sample of booking history — and it goes live once every quality gate has passed. First-time setup includes a dry run on the last 30 days, with nothing canceled or sent, before the manager signs go-live.

See it on
your bookings.

We'll run Airline Revenue Integrity on a sample of your own booking history and agency booking policy.