Travel Agency Bookkeeping: How to Reconcile Ticket Sales, Refunds, and Airline Remittances

You can have a busy week, plenty of booked travel, and money in the bank—yet still be unsure how much of that cash belongs to your agency. That uncertainty is a warning sign, not a normal part of selling travel. A customer payment can include airfare you must remit, taxes and fees, your service fee, a later exchange, and perhaps a refund that does not hit your bank account on the same day.

The solution is not a bigger suspense account. It is a repeatable reconciliation that follows each ticket from sale through settlement. This guide explains how an ARC-accredited agency can build that process and see the cash, obligations, and earned revenue clearly.

Start with the right mental model: ticket proceeds are not all revenue​

When a client pays for an airline ticket, the total charge may be much larger than the income your agency earns. In many arrangements, the agency is collecting money that will be settled to an airline or through an industry settlement process. Your own revenue may instead be a commission, a separately disclosed travel-agent service fee, or a markup you are contractually entitled to retain.

That distinction matters because recording the whole card charge as sales can overstate revenue and make the subsequent remittance look like an expense. The income statement may show impressive volume while hiding a thin margin. It also makes it difficult to explain why the bank balance is lower than reported sales.

Use separate accounts that reflect the economic roles of the amounts involved. The exact names can vary, but a useful starting chart of accounts includes:

• Assets:Cash:Operating for bank deposits and withdrawals.
• Assets:Receivable:CardProcessor for client charges that have been authorized but not yet deposited.
• Liabilities:AirlineSettlementPayable for amounts owed through the settlement process.
• Liabilities:CustomerRefundsPayable for refunds you have approved or owe before the cash movement is complete.
• Income:TravelServiceFees for fees you earn for planning, ticketing, or servicing travel.
• Income:Commissions for commissions earned under your supplier agreements.
• Expenses:PaymentProcessingFees and Expenses:MerchantFees for costs your agency bears.

Your contracts, payment flows, and accounting method determine the correct treatment, so confirm the policy with a qualified accountant. The key operational rule is simpler: never let one gross ticket amount obscure the separate amounts owed to an airline, owed back to a traveler, and earned by your business.

Build a ticket-level record before you reconcile the ledger​

The general ledger tells you totals; a ticket register tells you why those totals exist. For every issued ticket or accountable document, keep a row with a durable document number and enough fields to follow it through its lifecycle.

Fields worth tracking​

At a minimum, include:

• Ticket or document number and booking reference.
• Issue date and the reporting period it belongs to.
• Traveler or client identifier consistent with your privacy policy.
• Original form of payment and amount charged.
• Fare, taxes, fees, commission, and your service fee as separate fields where applicable.
• Exchange, void, refund, or credit-memo document numbers linked to the original ticket.
• Status: issued, reported, exchanged, refunded, voided, disputed, or settled.
• Settlement report reference, report-period ending date, and actual bank draft or credit date.

Do not rely on a passenger name alone as the key. Names can be duplicated, abbreviated, or changed. Document numbers and transaction identifiers make matching reliable when a sale later becomes an exchange or refund.

Preserve the source documents​

Save the itinerary, invoice, card-processor detail, settlement report, exchange record, refund authorization, and any supplier memo in a linked folder or document system. Your ledger entry should point to the supporting record, not replace it. Timely records and documentary evidence are far easier to verify than a reconstruction at year-end.

For a team, decide who can alter a completed ticket register entry and require a note describing any post-settlement correction. That small control prevents a legitimate late adjustment from disappearing into an unexplained difference.

Record the sale in a way that keeps obligations visible​

Suppose a client is charged $1,250 for a ticket. Of that amount, $1,170 will be remitted through airline settlement, and your agency earns an $80 service fee. The initial entry might look like this:

2026-08-29 * "Client ticket sale" "Ticket document recorded"
  Assets:Receivable:CardProcessor       1250.00 USD
  Liabilities:AirlineSettlementPayable -1170.00 USD
  Income:TravelServiceFees               -80.00 USD

When the processor deposits the charge net of a $31 fee, clear the receivable rather than treating the deposit as new income:

2026-08-30 * "Card processor payout" "Ticket sale deposit"
  Assets:Cash:Operating                  1219.00 USD
  Expenses:PaymentProcessingFees           31.00 USD
  Assets:Receivable:CardProcessor       -1250.00 USD

The example is intentionally simple. A ticket can include commission arrangements, taxes, supplier incentives, client deposits, and charges on different payment methods. The principle remains: record each component to the account that explains its owner and timing.

Reconcile on a daily, weekly, and monthly cadence​

Travel transactions change after the first booking. A daily check catches missing or unauthorized activity early; periodic settlement and month-end work make the books dependable.

Daily: compare new transactions to your booking and reporting systems​

Export the previous day's tickets, refunds, exchanges, voids, and service fees. Match each item to the ticket register and check that the form of payment, gross value, and status agree.

Flag these items immediately:

• A document issued in the booking system but missing from the reporting file.
• A card charge without a matching ticket or approved fee.
• A refund or exchange that lacks a link to the original document.
• A service fee that was waived, refunded, or collected separately but was recorded as part of airfare.
• An unfamiliar ticket, void, or adjustment.

Daily does not mean you must close the books every day. It means discrepancies are still small enough to investigate while the agent, booking context, and source records are available.

Each reporting period: reconcile settlement, not just sales​

Your settlement report is a key independent record. Reconcile it to both your ticket register and the liability account, then compare the final net remittance to the bank draft or credit. Do not stop at “the report looks close.”

Work from three totals:

1. Gross ticket activity and adjustments in the ticket register.
2. The amount submitted or authorized in the settlement report.
3. The cash movement that actually cleared the bank.

Differences between the first two may be timing, a transaction that rolled to another period, a void, or an exception that needs action. Differences between the second and third are often draft timing, bank details, or an unrecorded memo. Put every unresolved amount on a reconciliation log with an owner and next action; never bury it in a generic “other” account.

Monthly: prove every balance-sheet account​

At month-end, reconcile the operating bank account and card-processor receivable. Then list every open item in Liabilities:AirlineSettlementPayable and Liabilities:CustomerRefundsPayable by document number and age.

An open payable should have a recognizable reason: it is awaiting settlement, held for a known adjustment, or disputed with supporting documentation. If it cannot be explained, investigate it before closing the month. Old credits can be a sign of a missed refund; old debits can indicate a remittance or processor transaction that was recorded incorrectly.

Treat refunds and exchanges as linked events, not negative sales​

Refunds and exchanges cause many agency books to drift because they affect the original ticket, a new document, a customer card, and settlement timing. The cure is linkage.

Refunds​

When a refund is initiated, identify whether the customer will receive money from your agency, a carrier, or through the original payment flow. Record the obligation at the time it becomes real, then clear it only when the refund is confirmed in the appropriate settlement or processor data.

If you return a service fee, record that separately from the airline-ticket refund. Combining them makes it hard to see whether the fare was correctly refunded, whether a fee policy was applied consistently, and which party funded the cash outflow.

Exchanges​

An exchange is usually a chain, not a replacement sale. Preserve the original ticket number, each new document number, any additional collection, and any refund. An even exchange can have no new cash while still changing the document history; an exchange with an additional collection or a card refund changes both the customer payment trail and the settlement record.

Create a register rule: no exchange is marked complete until someone has matched the old and new documents, the correct form of payment, and the settlement outcome. This is especially important for split-payment transactions, where the source of a refund may need to track the original forms of payment.

Do not confuse cash timing with profitability​

Settlement schedules can make a healthy agency look cash-poor for a few days—or make cash appear available when it is already committed. Maintain a short rolling cash forecast that separates:

• Available operating cash.
• Expected card-processor deposits.
• Scheduled settlement drafts or credits.
• Approved customer refunds.
• Payroll, rent, marketing, and other agency operating costs.

This forecast is more useful than looking at the bank balance alone. It tells you whether a promotional campaign, group booking, or unusually high refund week will create a working-capital squeeze before the draft hits.

Create a practical exception workflow​

No reconciliation process eliminates exceptions. A good one makes them visible and short-lived.

Use a shared exception list with these columns: date found, ticket or document number, amount, type, reporting period, suspected cause, assigned owner, evidence link, and resolution date. Review it before authorizing a settlement report and again at month-end.

Common exception categories include late reporting, void timing, duplicate card charges, partial exchanges, unprocessed refunds, debit or credit memos, chargebacks, and processor payout differences. The category is less important than the discipline: each item needs an evidence trail and a defined clearing entry.

Set escalation rules too. For example, require a second review for a refund over a chosen amount, a manual adjustment, a new bank instruction, or an exception that remains unresolved after one reporting period. These controls protect clients and help you spot workflow failures without treating every agent as a suspect.

Make the books useful for decisions​

Once ticket, settlement, and bank data reconcile, you can ask better questions than “Did we make sales?” Track service-fee revenue per booking, refund frequency, exchange workload, card-processing cost as a share of fees, and the age of unresolved exceptions. Break results down by booking channel or travel segment only if the data will lead to a decision.

This is also where plain-text accounting can help. A version-controlled ledger makes adjustments reviewable, lets you link entries to ticket records, and produces a clear audit trail for your accountant. Beancount’s documentation is a useful starting point for designing a ledger that keeps transactional detail without turning each month-end close into a detective project.

Simplify Your Financial Management​

Travel-agency profitability becomes much easier to see when ticket proceeds, settlement obligations, fees, refunds, and cash movements each have a clear home. Beancount.io offers transparent, version-controlled, AI-ready plain-text accounting so you can keep a reviewable record of how every reconciliation was resolved. Get started for free when you are ready to make your financial data easier to trust.