Corporate deals signed on share nobody can prove.
A corporate agreement gets signed in March. The discount is loaded into distribution by April, and from that point the airline's own systems know more about the customer than the person who sold to them. We build the sequence back into one place — bid, contract, account code, flown revenue against target — with cargo and loyalty running as their own pipelines and the PSS left where it belongs.
Sales works in the CRM. Revenue lives in the PSS.
Corporate sales keeps the deal in a spreadsheet. Distribution loads the account code. Share actuals leave the warehouse six weeks late and only for the agency channel, so direct and NDC volume is estimated. When the quarterly review asks what an account flew last month, three people answer with three numbers and none of them can name a source.
The account code is the customer.
Airlines — corporate salesWhat it takes to see corporate revenue by account.
One company, every account code
Account codes, tour codes and corporate IDs mapped to a single company record with effective dates, so a TMC change or a subsidiary rename does not open a second account and split the contract history.
Share against target, sourced
Share and volume targets stored as contract terms on the account, with actuals loaded from the warehouse across agency, direct and NDC channels, and the reporting lag stated on the record instead of argued about in the room.
Cargo on its own pipeline
Forwarders and BSA holders modelled separately from passenger accounts: allotment requests, contracted lanes and spot quotes as their own stages, with capacity questions routed to the people who can answer them.
Lounge, bags and entitlements
Corporate programme enrolment, lounge and bag entitlements, and negotiated ancillary terms sit on the company record. The account manager sees what was promised without opening the loyalty platform.
IROPS with an owner
IROPS affecting a contracted account raises an owned case, not an inbox thread. Recovery, waivers and goodwill are logged against the account and appear at renewal, where they belong.
Itineraries stay in the PSS
PNR-level passenger data stays in the PSS. The CRM holds the company, the contract and aggregated flown revenue, so retention and privacy obligations do not follow copies of itineraries into a marketing system.
From account code to renewal.
Line check
Two weeks with corporate sales, cargo, revenue management and the distribution team. We trace one live account from bid to quarterly review and find every place its identity changes hands.
Route map
One data model: company, account codes with effective dates, contract terms, share targets, cargo agreements. We write down what the CRM owns and what the PSS and the warehouse keep.
Proving flights
Build it in HubSpot, wire the warehouse feed for flown revenue and share, connect cargo and loyalty at the account level, and set the reporting the commercial director signs off on.
Entry into service
Your team runs it. Documented objects, named owners for each feed, and a stated refresh cadence so the number in the quarterly review has a source anyone can check.
The corporate ID changes. History detaches.
A customer merges, moves TMC, or spins out a subsidiary, and the account codes are reissued. The new code opens as a new account. The old one keeps three years of flown history. The share baseline written into the contract now measures a company that no longer exists, and the renewal is negotiated blind. Codes need versioned mapping to one record.
