Every trip, its cost centre and its CO₂e, ready to export
Reporting starts with every trip in one place. Bookings made in your GDS, on an airline's site or by email land in one register, each with its cost centre and the booking fields your finance team asked for. Filter it, save the view, and export it.
Flight emissions are estimated for every trip and totalled per client, per cost centre or per any booking field, for the period you choose.
The booking register
- Filter by status: upcoming, quotes, held, needs attention or closed.
- Search by our booking reference, the PNR, the airline confirmation, or a traveller's surname if your role may read names.
- Date ranges on the local day the trip departs, as the traveller would say it, or the day it was booked in US Eastern time.
- Saved views keep a filter under a name you choose, up to 20 each, visible only to you.
The register never shows net fares, markups or commission.
Exports your finance team can use
Any filtered register downloads as a CSV file, in one of two shapes:
| Shape | One row per | Columns |
|---|---|---|
| Roster | Booking | Reference, PNR, airline confirmation, status, client, lead traveller, number of travellers, route, first departure in local time, carrier, total, when it was booked, cost centre, and one column for each of your booking fields |
| Flight detail | Flight | Reference, PNR, status, client, lead traveller, number of travellers, flight, the airline operating it when that is another airline, from, to, local departure and arrival, cabin, cost centre, and your booking fields |
An export needs its own permission and a stated reason, and it is logged with its row count before any data leaves. Up to 5,000 rows go in one file; narrow the filter for more. A cell that a spreadsheet would read as a formula is written as plain text.
Spend figures need a recorded price. TripDesk365 does not price airline fares itself today, and a booking imported from elsewhere arrives without a price. Once your agency records what a trip was sold for, the Total column carries it. Until then, match the export to your own records on the booking reference or PNR.
Cost centres and booking fields
Your travel manager sets up cost centres on each corporate account, and booking fields for anything else finance needs on a trip: a project code, trip purpose, PO number or employee ID. A field is text, a number, a date, a list to pick from, or yes and no. It can apply to every client or to one, have a default, and be required.
- Values are set on the booking page at any time, so reporting can be corrected after the trip.
- A field is archived, never deleted, so last year's exports keep their columns and their values.
- A required field with no value is shown as missing on the booking, and stops a trip priced in TripDesk365 from being ticketed.
- A field cannot be set up to hold prices, and a value that looks like a card number is refused.
Flight emissions per client, cost centre or booking field
Each booking shows an estimate of CO₂e per traveller. The emissions report totals it for any period of up to 400 days: trips, traveller trips, distance, and kilograms of CO₂e with and without radiative forcing, with a CSV download. Cut it per client, per cost centre, or per any booking field, such as a project, a grant or a department.
- Trips with no cost centre or no value in the field are a row of their own, never left out, so every cut adds up to the same total.
- A trip counts in the period by the local day its first flight departs.
- Every flight is measured at its own cabin, then multiplied by the travellers on the booking.
- A trip that cannot be measured, such as one with an airport our table does not know, is counted as unmeasured, never added as zero.
The method: great-circle distance times the UK government's 2025 greenhouse gas conversion factors (DESNZ) for the flight's haul type and seat class. Those factors already include the uplift for routes longer than the great circle, so it is not added twice.
CO₂e here is an estimate from published average factors, not a measurement of the aircraft, load or route actually flown. Try the same method on our flight emissions calculator.
Digests and the read API
- A daily digest each morning from 07:00 ET: yesterday's disruptions and any still open.
- A weekly digest on Mondays: trips departing in the next seven days, open disruptions, and approvals waiting or decided. Digests go to people with reporting access, carry no traveller names and no prices, and a quiet day sends nothing.
- The read API returns the same register to your own reporting tools, with each booking's cost centre and booking fields. See integrations.
Bring last quarter's trips
Send us a few bookings and your cost centres before the demo, and we will show you the register, an export and the emissions report built from them.