Agency production report: ranking partners by what they really bring

A travel agency production report ranks each agency and tour operator by what the hotel actually keeps, not by room nights alone: net revenue after contract costs, average rate by period, release and cancellation behavior, allotment use and days to payment, read together over a season. Room nights stay in the report as context, never as the ranking.

The year-end table ranks agencies by room nights, and the name at the top is the one that books the cheapest weeks, releases unsold rooms after the deadline and settles its invoice long after the season ends. The number is real. The ranking is not. After reading this article you will know which columns belong in a travel agency production report, how to build it from your reservation system and city ledger, and how to use it in the next contract round.

Why do room nights alone mislead when you rank agency partners?#

Room nights count volume, and volume is not value: a partner can fill rooms in the weakest weeks at the lowest contracted rate, hold allotment it never sells and pay months later, and still lead the table.

Room nights are period-blind. The same count in a low season and in a peak week is not the same contribution to the hotel, and an annual total hides which one happened. They also ignore the cost side of the contract: the hotel's own net rate, the services included at the hotel's expense, and any agreed extras that reduce what is left.

They ignore behavior. Rooms blocked and released after the deadline are inventory the hotel could have sold elsewhere; late cancellations leave a room empty with no time to refill it. They ignore cash: a booking is not money until it is collected, so days to payment changes the real value of identical revenue. And they ignore mix, because a partner that brings one source market in one season adds concentration, which is a risk column rather than a success column.

The fix is not to delete room nights. It is to place them next to value, behavior and cash in one table: one row per partner, one column per question.

What columns belong in a travel agency production report?#

Seven columns carry the argument: room nights, net revenue after contract costs, average rate by period, releases, cancellations, allotment use and days to payment.

Room nights should count nights actually stayed, not nights booked. Count no-shows and cancellations in their own columns so they cannot inflate the volume figure. Net revenue after contract costs is the amount the hotel keeps under its own contract terms: the agreed net rate, the inclusions the hotel pays for and any fixed fees. Never a generic commission assumption. Average rate by period should split the year into at least high, shoulder and low season, because a single annual average is the number that flatters the weakest partner.

Releases split into rooms returned unsold before the release deadline versus after it. The late column is the expensive one, because the hotel has lost the chance to resell. Cancellations carry a count and a value, split by how close to arrival they came: a cancellation thirty days out and one three days out are different events. Allotment use is rooms taken from a committed block divided by rooms blocked, per period; low use in a peak period is a different problem from low use in a quiet one. Days to payment runs from checkout or invoice date to cash received, averaged, with the worst open case shown next to it.

Add a contract reference column, so anyone reading the report knows which release period and which payment term applied when the numbers were produced.

Definitions to fix before the first report#

Agree the definitions in writing before the first build, or the report will be relitigated every month. Fix what counts as a "stay" (nights actually consumed), what counts as a "release" (the date the room returned to inventory, not the date the agency emailed), and where the payment clock starts. Fix the seasons and their boundaries. Fix the partner list, including which corporate accounts are billed through which agency.

Why net revenue needs the hotel's own terms#

Two hotels with the same partner and the same room nights can keep very different amounts, because contracts differ in net rate, inclusions and extras. A generic assumption, such as a fixed commission percentage applied to everyone, hides exactly the differences the report exists to expose. Start from the contracted net rate and deduct what the hotel provides at its own cost, such as transfers, board upgrades or agreed extras. Have finance confirm the treatment before the report becomes a negotiation document.

The table below shows the core columns; split it further by season when you build your own.

In your report, every cell should be traceable to a reservation or an invoice; the figures above are illustrative.

How do you build the report from the hotel system and the city ledger?#

Build it from two sources: the reservation system for what was booked, stayed, released and cancelled, and the city ledger for what was invoiced and paid. Join them on the partner account, not on the guest.

Segment codes come first. Every reservation must carry the agency or tour operator code, otherwise the report becomes a manual sorting exercise that nobody repeats next month. If you are starting from scratch, setting up segment codes correctly is its own project: see how to set up market segment codes.

Neither source is enough alone. The hotel system holds the reservation record and the release history; the city ledger holds the receivable and the payment. Net revenue and days to payment need both. Choose the date basis deliberately: stay date for volume and rate, invoice date for cash. Mixing them creates phantom months where revenue and payment land in different periods.

Handle the awkward cases by rule, not by argument: a guest who extends directly after an agency booking, a corporate account billed through an agency, a group split across two partners. Decide once, write the rule down, apply it every month.

Reconcile before ranking. Totals must match the night audit close and the ledger, or the first contract meeting turns into a debate about the report instead of the partnership. Keep the raw rows behind every summary: a figure that cannot be traced back to a reservation or an invoice will not survive a negotiation. Build monthly, read seasonally, compare yearly.

Three partners compared: a worked example#

In a labeled example, the partner with the most room nights is not the one that brings the most value, and the gap comes from period, release behavior and payment speed.

Take three fictional partners. Partner A brings volume in the low season, releases unsold rooms after the deadline and pays slowly. Partner B brings moderate volume concentrated in peak weeks and pays on time. Partner C brings small volume at a high rate, uses almost all of its block and pays quickly. The numbers below are for example only and are not benchmarks; your own contract terms, inclusions and release periods drive every number in your version of the table.

On room nights, A leads. On net revenue after contract costs, B leads, because its nights sit in the weeks where the rate holds. On allotment use, C is close to full, which is the strongest signal in the table: the hotel could commit more inventory to C next season without carrying the risk of unsold blocks. On days to payment, A is the outlier, and the open balance at period end explains why the same revenue is worth less from A than from B.

The reading order: net revenue by period first, then behavior columns, then cash columns, then room nights as context.

How do you read concentration and payment risk in the numbers?#

Read the report as a risk map: a large share from one partner, a large share in one season, and a long days-to-payment figure are three separate exposures that need three separate answers.

Concentration is what share of a period's rooms and revenue comes from the top partner. Dependency grows quietly, one good season at a time. The season shape of the dependency matters too: a partner that dominates the peak weeks is a different risk from one that dominates the quiet ones, and the contract response is different for each.

Payment is days to payment plus the open balance at period end. A partner that pays late but steadily is a cash-flow question; a partner whose balance keeps growing is a credit question. Allotment exposure counts rooms blocked and unsold at the release deadline: inventory the hotel reserved in advance for a partner that did not use it. Cancellation pattern matters because repeated late cancellations are behavior, not accident; whether they cost the hotel depends on the contract terms, which belong to the hotel's adviser. For the receivables side in depth, see protecting a hotel's receivables from tour operator payment risk.

What the reading produces is practical: credit limits, allotment sizes and release terms for the next round, and a conversation with the partner before renewal rather than after.

How do you use the report in contract talks and the sales plan?#

Bring the report to the negotiation as evidence: it turns a general request for a better rate into a specific statement about period, allotment and payment terms.

Open with the partner's own numbers: room nights by period, average rate, allotment use, days to payment. Partners negotiate differently when they see their own row. Trade along the columns: more allotment only with an earlier release or a shorter payment term; a lower rate only against committed volume in a named weak period.

Size next season's block from allotment use rather than from the partner's request, and write the release period into the contract so the report can test it later. The mechanics of how much inventory to commit are covered in allotment versus free sale. Place each partner in the yearly B2B plan with a target period, an expected allotment use and a review date, so the plan and the report measure the same thing; the structure for this is a yearly B2B sales plan.

Record what was agreed and which column it should move. Next year's report then becomes the check on the agreement, not a surprise. Keep the tone factual: the report is a shared document, and used as a weapon it closes the conversation the hotel needs to have. Contract wording, release clauses and any legal question belong to the hotel's adviser, not to the report.

What should a seasonal review look like?#

A seasonal review is a short, fixed meeting that reads the report period by period and ends with three decisions: how much inventory to commit, which terms to change and which partners need attention.

Build the report monthly, review it at the end of each season and once more before the contract round. The agenda is fixed: the top partners by net revenue, the top partners by room nights, the difference between the two lists, and any partner whose days to payment moved. The checks are fixed too: unresolved balances, rooms released after the deadline, cancellations inside the release window, and allotment blocks that went unused in a strong period.

The outputs are allotment changes for next season, partners to renegotiate, partners to leave as they are, and partners to reduce. Keep last season's report beside this one: a single season says little, and the direction of a column over two seasons says what to do. Use one page per partner and one page for the portfolio, so the meeting reads the same document every time.

What to do next#

Build the seven-column table for the last twelve months before the next contract round. The article moves in one line: volume shows who books, net revenue by period shows what the booking is worth, behavior and cash columns show what it costs to carry, and the seasonal review turns all three into allotment, terms and attention.