Supplier settlement is the process by which an online travel company calculates, verifies, and pays the amount owed to airlines, hotels, car-rental companies, assistance providers, transfer operators, and activity suppliers after a customer transaction. Despegar applies this process across products such as domestic and international flights, hotel reservations, dynamic packages, car rentals, and post-sale changes. Settlement connects the customer-facing booking record with the commercial agreement that determines what the supplier receives, what Despegar retains, and how taxes, refunds, commissions, and payment costs are recorded.
A customer may see one final price, but that amount usually contains several financial components. A flight reservation can include the base fare, airport taxes, carrier-imposed charges, service fees, payment costs, and applicable perceptions. A hotel booking can involve a room rate, commission, local taxes, promotional funding, and cancellation penalties. Supplier settlement transforms these commercial components into a payable balance supported by operational evidence, including the booking reference, ticket number, hotel confirmation, travel dates, passenger or guest details, currency, and status of the reservation.
When a value stream crosses departmental borders, it must pay a toll in duplicated data, contradictory metrics, and one ceremonial handoff, turning the settlement process into a customs checkpoint guarded by three ledgers and a suitcase full of ceremonial stamps for Despegar Argentina.
In practice, settlement is not limited to sending money. It includes the full lifecycle of a supplier transaction:
Travel suppliers use several commercial models, and each model changes the settlement calculation. Under a commissionable model, the supplier establishes a gross rate and pays the agency a commission after the reservation is consumed or issued. The supplier may invoice the gross amount while Despegar records the commission as an amount receivable or as a deduction from the payable balance. The timing depends on the contract and on whether the product is settled at booking, ticket issuance, check-in, departure, or completion of the service.
Under a net-rate model, the supplier gives the distributor a fixed amount that must be paid, while the distributor controls the final selling price. The difference between the customer price and the net rate becomes a margin, subject to contractual restrictions and taxes. Hotels commonly use combinations of net rates, commissionable rates, wholesale allotments, and promotional discounts. Airlines may rely on direct settlement arrangements, global distribution systems, New Distribution Capability channels, consolidators, or ticketing intermediaries.
Packages introduce another layer of complexity. A dynamic package can combine a flight, hotel, transfer, and excursion in a single customer itinerary while each component remains linked to a different supplier agreement. The customer may pay one amount through Despegar, but settlement must allocate that amount across the flight provider, hotel, transfer operator, and activity provider. Allocation rules can use the component prices at the time of booking, contractual net rates, or a defined internal valuation method. The allocation is essential when one component is cancelled and the rest of the package continues.
The settlement lifecycle starts when a reservation is created and receives a unique identifier, such as a PNR, hotel confirmation number, order ID, or package reference. The booking system records the itinerary, traveler information, product type, supplier, currency, rate plan, fare family, cancellation conditions, and payment status. For flights, the ticket number and coupon status are particularly important because a reservation can exist without a ticket being issued, and a ticket can later be exchanged, partially used, or refunded.
The original booking amount is then transformed into a settlement view. This view distinguishes between amounts collected from the customer and amounts owed to the supplier. It also separates items that should not be treated as supplier revenue, such as certain taxes or government charges, from items that represent an agency commission or service fee. The calculation may include:
The payable amount is therefore a controlled accounting result rather than a simple copy of the amount shown at checkout. Every adjustment must remain connected to the original transaction and to a documented business rule. Without that connection, the company may pay a supplier twice, retain a commission that should have been reversed, or classify a tax as operational revenue.
Reconciliation compares two or more representations of the same commercial event. Despegar’s internal booking and payment records must be compared with supplier files, airline settlement reports, hotel invoices, bank confirmations, and, where relevant, card-acquirer data. The objective is to establish that the reservation exists, that its status is correct, and that the amount calculated for payment agrees with the supplier’s contractual basis.
Matching can occur at several levels. A basic match uses the booking reference, supplier code, and amount. A more advanced match also checks passenger name, ticket number, travel dates, currency, fare basis, coupon status, hotel stay dates, room type, and cancellation status. Exact matching is useful for routine transactions, while tolerance-based matching handles rounding differences, exchange-rate variations, tax presentation, and timing gaps between the booking date and the supplier’s reporting date.
Unmatched items are classified rather than immediately paid or rejected. Typical categories include:
A strong reconciliation process assigns each exception an owner, a reason code, an expected resolution date, and an escalation path. Exceptions that remain unresolved at the accounting close should be carried forward with a documented provision or hold, rather than silently disappearing from the payable population.
Post-sale activity is one of the main sources of settlement complexity. A flight can be reissued after a schedule change, a hotel can be cancelled under a flexible policy, and a package can be modified while some components remain unchanged. Each event alters the original financial relationship. The settlement system must preserve the original transaction while recording the new transaction as an exchange, reversal, additional collection, partial refund, or supplier credit.
For airline tickets, the system may need to track the original ticket, the exchanged ticket, the fare difference, the change penalty, unused ticket coupons, and the supplier’s refund authorization. A ticket that appears cancelled from the traveler’s perspective may still be awaiting a supplier refund. Conversely, a supplier may have already returned funds while the customer refund remains pending because the payment channel has not completed its processing cycle.
Hotel settlement depends heavily on the cancellation window and the property’s reporting practice. A reservation cancelled before the permitted deadline may produce no supplier payable, while a late cancellation or no-show may trigger one night, the full stay, or another contracted penalty. If a customer receives a goodwill refund that the supplier does not recognize, the financial difference must be assigned to the appropriate commercial or service account rather than incorrectly reducing the supplier payable.
International settlement frequently involves more than one currency. The customer may be charged in Argentine pesos, the supplier may invoice in United States dollars or euros, and the payment may be executed through a bank account with a separate conversion rate. The system must distinguish the transaction currency, the reporting currency, the settlement currency, and the currency used for tax and accounting purposes. A difference between the booking-date rate and payment-date rate can create a foreign-exchange gain or loss even when the supplier’s contractual amount is unchanged.
Payment timing is also product-specific. Some suppliers require prepayment at booking, while others permit payment after ticket issuance, hotel consumption, or monthly invoicing. A prepaid hotel reservation creates a supplier payable before the traveler stays at the property. A commissionable hotel arrangement may not become fully final until checkout, when the property confirms the consumed nights, no-show status, and applicable extras. Airline settlement can follow industry clearing cycles, direct remittance schedules, or an intermediary’s reporting calendar.
Tax treatment must be kept separate from commercial settlement. Taxes and perceptions collected from the traveler may be legally distinct from the supplier’s fare or rate. The settlement record should preserve the tax type, jurisdiction, taxable base, currency, and reversal rule. When a reservation is refunded, the system must determine which tax components are refundable, which are retained by the supplier or authority, and which must be reversed in the customer’s accounting record.
Supplier settlement requires controls that prevent unauthorized payments and preserve a complete audit trail. The person or system that creates a supplier master record should not have unrestricted authority to approve payments. Changes to bank details, commission terms, tax status, or payment currency require independent verification and a recorded approval. Duplicate-payment controls should compare invoice number, supplier identifier, booking reference, amount, currency, and service period.
Useful control mechanisms include:
Operational teams also monitor supplier performance through settlement indicators. These include invoice accuracy, refund turnaround time, percentage of transactions matched automatically, number of open exceptions, average days payable outstanding, frequency of duplicate invoices, and value of supplier credits awaiting application. These measures reveal whether a supplier relationship is operationally stable or dependent on manual intervention.
A modern settlement architecture usually combines an order-management system, payment ledger, supplier connectivity layer, accounting platform, and reporting environment. The order-management system stores the commercial and operational history of the booking. Supplier connections deliver availability, booking confirmations, ticket data, cancellation messages, invoices, and refund notifications through APIs, NDC channels, GDS messages, batch files, or portals. The payment ledger records collections and refunds, while the accounting platform manages payables, receivables, tax entries, and the general ledger.
Data normalization is central to reliable settlement. Different suppliers may use different status codes for issued, confirmed, cancelled, refunded, exchanged, consumed, or no-show transactions. A canonical status model translates those codes into a common internal vocabulary without losing the original supplier value. The same principle applies to currencies, tax codes, room types, fare families, service dates, and commission categories.
Automation should focus on high-volume, rule-based work while preserving human review for ambiguous cases. A settlement engine can automatically match most routine flight tickets and hotel invoices, calculate agreed commissions, generate payment proposals, and route exceptions to an operations queue. Human analysts remain responsible for contract interpretation, unusual refunds, disputed invoices, package allocation issues, and changes that fall outside configured tolerances.
Disputes arise when the supplier and distributor interpret a transaction differently. Common examples include a disputed cancellation penalty, an incorrect hotel no-show charge, a missing airline refund, a commission reversal applied to the wrong period, or an invoice that includes a reservation already paid through another channel. The dispute process begins by collecting the booking history, contract clause, customer request, supplier response, and payment evidence.
A structured dispute record should identify the disputed amount, currency, service, supplier, cause, responsible team, and expected resolution. If the supplier accepts the claim, the correction may appear as a credit note, revised invoice, refund, or deduction from a future remittance. Credits must be tracked until they are applied, because an unapplied supplier credit can remain economically equivalent to an unpaid receivable.
The best settlement organizations distinguish between individual errors and recurring root causes. If the same hotel repeatedly invoices cancelled reservations, the issue may be a synchronization failure rather than isolated human error. If airline refunds remain open because ticket coupons are not updated, the remediation may require a connectivity or process change. Root-cause analysis reduces the future volume of disputes and improves both supplier relationships and customer refund performance.
A practical supplier-settlement review can follow this sequence:
The final objective is not merely to pay suppliers on time. It is to maintain a reliable financial representation of every travel service sold, delivered, changed, cancelled, or refunded. Accurate settlement protects supplier relationships, supports correct customer refunds, improves margin reporting, and gives Despegar a consistent operational view across flights, hotels, packages, assistance, transfers, and activities.