Sub-agent management is the way a master travel agency onboards, funds, prices, and controls the smaller agencies that book through its B2B portal. It covers agent hierarchy, credit limits, markups, ticketing permissions, and ledger tracking. This ensures each sub-agent can sell independently while the master agency maintains control of risk, margin, and settlement.
For a consolidator in Dubai, Riyadh, Jakarta, or Kuala Lumpur, adding sub-agents is the fastest way to grow ticket and hotel volume without opening new branches. However, the risk grows at the same speed. A partner with too much credit, the wrong markup, or unrestricted ticketing rights can create losses that only appear at month-end.
This guide explains how sub-agent management works in practice: the hierarchy, onboarding, funding, pricing, permissions, approvals, and the ledger that ties them together.
What Is Sub Agent Management in Travel?
A sub-agent is a smaller travel agency or independent seller that books through a larger master agency instead of holding its own airline accreditation, GDS contract, or bedbank agreements. The master agency supplies inventory, pricing, and settlement, while the sub-agent brings the customers.
In the Gulf and Southeast Asia, this model allows small agencies to sell flights and hotels with access they could not achieve alone. For the master agency, every sub-agent is both a sales channel and a credit risk. Effective sub-agent management treats both sides seriously, with rules the system enforces rather than relying on memory.
How the Agent Hierarchy Works
Every B2B network needs a clear chain of ownership. Each booking should trace back to a named user, a sub-agent, and the master agency above it.
| Level | Who it is | What it controls |
|---|---|---|
| Platform | The B2B portal and its administrators | Suppliers, global rules, system settings |
| Master agency | The consolidator or host agency | Partner approval, credit, markups, settlement |
| Sub-agent | A partner agency in the network | Its own users, customer bookings, deposits |
| Booking user | A staff member at the sub-agent | Searches, bookings, and requests within assigned rights |
| Booking | A flight, hotel, or other reservation | Price, status, ticket, and ledger entries |
The chain Platform → Master Agency → Sub-Agent → Booking User → Booking decides who can see a booking, who pays for it, and who is accountable when something goes wrong. A flat network, where every user sits at the same level, cannot apply different credit or pricing rules per partner.
How to Onboard a Sub-Agent
Onboarding sets the rules before the first booking. A fixed checklist prevents the most common problem: a partner who starts ticketing before anyone has approved its credit or pricing.
- Collect company details. Trade license, contact persons, address, tax registration where required, and bank details for refunds.
- Assign a status. Keep the new partner in a pending state until the review is complete.
- Create the account and users. Give each person a named login; never a shared one.
- Set the funding model. Deposit only, credit limit, or both.
- Apply a pricing group. Attach the markup and commission rules from the agreement.
- Set permissions per user. Decide who can search, book, issue tickets, and request refunds.
- Run a test booking. Confirm the price, the balance deduction, and the ledger entry before activation.
Partner statuses should carry operational meaning:
- Pending: registered, cannot book.
- Active: can book within its limits.
- On hold: can view bookings but cannot create new ones, often used for overdue balances.
- Suspended or closed: no access; open bookings are serviced by the master agency.
Credit Limits and Deposits
Funding is where sub-agent networks lose the most money. The master agency needs to know, at any moment, how much each partner can still book.
A simple formula works for most networks:
Available credit = Approved credit limit + available deposit − unsettled exposure
For example, a Dubai sub-agent has an approved credit limit of AED 50,000 and a deposit of AED 10,000. Unpaid bookings total AED 42,000. Available credit is AED 50,000 + AED 10,000 − AED 42,000 = AED 18,000. Any booking above that amount should stop or require approval.
Credit review cycles, top-up methods, and overdue actions belong in a separate credit policy. The key control here is timing: the limit must be checked automatically at the moment of booking, not reviewed at month-end.
Markups and Commission Rules
Each sub-agent should see a price built from clear rules, not manual edits. Most master agencies use pricing groups: one markup for new partners, a lower one for high-volume partners, and product-specific rules for flights, hotels, and ancillaries.
Three principles keep pricing under control: rules sit at the pricing-group level, not on single bookings. Any manual override needs a reason and a record. Commission owed to a sub-agent posts to the ledger automatically when the booking is ticketed. Markup strategy itself is a wider topic; this guide stops at the control points.
Ticketing Permissions and Least Privilege
Not every user at a sub-agent needs every action. The NIST definition of least privilege is a sound rule: restrict each user's access to the minimum needed for the assigned task.
| Action | Booking user | Sub-agent admin | Master agency finance | Master agency operations |
|---|---|---|---|---|
| Search and hold | Yes | Yes | No | Yes |
| Issue ticket | Only if granted | Yes | No | Yes |
| Request void, refund or reissue | Yes | Yes | No | Yes |
| Approve refund payout | No | No | Yes | No |
| Change credit limit | No | No | Yes | No |
| Edit markup | No | No | No | Yes, with approval |
| View sub-agent ledger | Own bookings | Full | Full | Full |
Ticket changes follow airline rules as well as internal rights. Travilo's guide to void vs refund vs reissue explains which action fits which case. Hotel bookings need the same permission logic, covered in the guide to hotel booking software for travel agents.
Approvals and Separation of Duties
The person who requests money should not be the person who releases it. In a sub-agent network, that means:
- a sub-agent can request a refund, but master agency finance approves the payout;
- operations can propose a credit increase, but finance approves it;
- one user proposes a markup change, and another approves it;
- Every approval stores the user, the time, and the reason.
This separation stops honest mistakes as well as fraud, and it provides auditors with a clean trail.
The Sub-Agent Ledger
Every sub-agent needs its own running ledger. Each booking, ticket, void, refund, reissue fee, deposit, commission, and payment should create a dated entry against that partner's balance.
A clean ledger answers three questions quickly: what the sub-agent owes, what it has paid, and which bookings are still open. It also feeds the master agency's own airline settlement. When a sub-agent's refund or reissue does not match the airline side, the difference surfaces during BSP reconciliation, so both processes should share the same booking and ticket references.
Exception Alerts Worth Setting Up
Alerts catch problems before month-end. Useful triggers include:
- available credit below 10% of the approved limit;
- a booking blocked by credit or permission rules;
- a deposit recorded but not yet verified by finance;
- a refund pending approval for more than 48 hours;
- a manual price override;
- a sub-agent with an overdue balance still trying to book.
Example: A Dubai Master Agency With Five Sub-Agents
A master agency in Dubai manages five sub-agents: two in Dubai, one in Sharjah, one in Riyadh, and one in Muscat. Each has its own users, pricing group, and credit limit.
On a Thursday, the Sharjah partner reaches 90% of its limit. An alert goes to master agency finance, and a pending AED 6,000 booking moves to approval instead of ticketing automatically. Finance checks the ledger, finds a deposit recorded that morning, verifies it against the bank statement, and releases the booking.
No one had to remember to check a spreadsheet. The hierarchy, the limit, the alert, and the approval did the work.
How Travilo Handles Sub Agent Management
Travilo runs the entire partner network from its B2B Portal and Finance System, from onboarding to the running balance.
1. Partners, users, and roles in one hierarchy. Travilo's partner management lets the master agency create sub-agents, set partner status, and assign role-based rights to each user.
[Screenshot: Travilo partner list with status and credit balance columns]
2. Credit, deposits, and wallets tracked live. Travilo records deposits, credit balance, and wallet transactions per partner and checks available funds when a booking is made.
[Screenshot: Travilo partner wallet and credit balance screen]
3. Pricing and reporting per partner. Travilo's fare management rules handle commissions, markups, and partner incentives. The agency balance summary report shows each sub-agent's position in one view.
[Screenshot: Travilo agency balance summary report]
For the wider portal setup, see Travilo's guide to B2B travel portal software for small agencies. To compare full platforms, read the best travel booking software guide for agencies.
Running a sub-agent network? See how Travilo's B2B travel portal controls agents, credit, and pricing and book a demo with the product team.
Frequently Asked Questions
What is sub-agent management in travel?
Sub-agent management is the process a master travel agency uses to onboard partner agencies, set their credit and pricing, control what each user can do, and track every booking in a ledger. It enables a B2B network to grow through partners while the master agency retains control of risk, margin, and settlement.
How should a master agency set a sub-agent's credit limit?
Start from the partner's expected monthly volume, trading history, and deposit. Many agencies begin new partners on deposit only, then add a small credit line after a few clean settlement cycles. The system should calculate available credit at every booking and block anything above it or send it to approval.
Can a sub-agent issue airline tickets directly?
Only if the master agency grants that permission. Many networks let sub-agent users search and hold bookings while ticketing is reserved for approved users or the master agency. The tickets are still issued under the master agency's accreditation, so it remains responsible for fare rules, voids, refunds, and any airline debit memos.
What is the difference between a sub-agent and a B2B customer?
A sub-agent is part of the master agency's managed network, with its own users, pricing group, credit limit, and ledger. A B2B customer is often a corporate or occasional buyer booking at agreed rates. Sub-agents resell to their own customers, so they need deeper controls on pricing, permissions, and settlement.
Which reports should a master agency review every week?
The most useful weekly reports include the agency balance summary, overdue balances, bookings blocked by credit or permission rules, pending refunds, manual price overrides, and sales by sub-agent. Together, they show which partners are growing, which carry risk, and where margins or controls are slipping before month-end.