When you create a new file in TravelMind, you must select a file type — Business, Leisure, or Group.
This determines which functions are available (e.g., invoicing, agreements, deposits).
Business (BUS)
Use this type for corporate travel or company invoicing.
Main characteristics:
You can only create invoices (no travel agreements or deposits).
Designed for quick processing and simple documentation.
Common for air tickets, hotels, or car rentals booked for business travelers.
Examples:
A company books flights for an employee’s business trip.
A client books a hotel directly billed to their employer.
💡 Tip: Always make sure the company profile exists in the Thirds tab before creating the dossier.
Leisure (LEI)
Use this for holiday trips, personal travel, or individual clients.
Main characteristics:
Allows creation of quotations, travel agreements, deposit invoices, and final invoices.
The most flexible and detailed file type.
Suitable for all standard B2C or mixed bookings.
Examples:
A family holiday to Spain.
A honeymoon trip including flight, hotel, and insurance.
A voucher-based booking for a private client.
💡 Tip: Always use Leisure for group travel — even if it’s multiple travelers — since “Group” is not supported in the same way.
Group (not in use)
Although the dropdown shows “Group,” this type should not be selected.
Group trips are managed under Leisure files because it allows travel agreements and multiple deposits.
When to treat a booking as a group:
When several travelers share the same itinerary but need separate invoices or agreements.
When you use the copy service function to duplicate services between dossiers.
📌 Screenshot: [New dossier type selection placeholder]
Summary table
Dossier Type | Use Case | Features | Notes |
Business | Corporate or company travel | Invoices only | No travel agreements |
Leisure | Holiday / private trips | Quotes, deposits, final invoices | Use also for group trips |
Group | (Not used) | — | Always select “Leisure” instead |
💡 Tip: Choosing the correct type at creation avoids rework later — changing types after invoicing is not allowed.