Most event budgets are a single number in a spreadsheet cell, and the number is wrong by the second week. Not because the estimate was bad, but because "spent" is four different quantities that move at different times, and a one-cell budget silently averages them.
Here is the structure that does not fall apart, and a template at the end you can copy.
The four numbers
Budget is what you were given. It is the only one of the four that does not change on its own, and the only one you should ever quote to finance without a date attached.
Booked is value that is committed but not yet charged. A flight held on a company account, a hotel reserved on a pay-at-hotel rate, the rooms in a block you accepted. This number is the one most organizers do not have, and it is the one that tells you whether you are about to go over, because it moves days or weeks before the money does.
Paid is value that has left the company: prepaid hotels, card charges that have settled, invoices paid. Your finance team recognises this one and tends to treat it as the whole truth, which is exactly how an event that is 40% paid and fully booked reads as "well under budget" a week before it starts.
Remaining is budget minus the commitments you have taken — not budget minus what has been paid. The distinction decides whether you can approve the airport transfers.
Travel Code's budget screen states the definitions on the page itself, and they are worth copying whatever tool you use: booked is confirmed or issued bookings at the client price, paid is the booked ones paid in full, spent is approved or submitted expenses charged to the event — and cancelled bookings and rejected expenses are not counted in any of them. The last clause is the one that keeps a budget honest: a cancelled flight that still counts as booked is how a budget drifts without anyone making a mistake.
A fifth quantity shows up after the event and deserves its own name: spent on site. Per-person card spend, taxis, dinners, the things nobody can plan to the dollar. If the people on the trip carry cards with limits, this becomes visible as it happens instead of arriving as a pile of receipts two weeks later.
Why one number is not enough
Three failure modes, all of them common:
The invisible commitment. Hotels are reserved, nothing is charged yet, and the budget shows plenty of room. Then the prepaid charges land in the same week as the flights, and the overrun is discovered after it is unavoidable. Booked-but-not-paid is the number that would have warned you.
The double count. Someone books their own flight, expenses it, and the organizer also has it in the plan as an estimate. Now one trip is in the budget twice — or, worse, it is in the expense report of a cost center that has nothing to do with the event.
The attribution argument. The event closes, the total is known, and nobody can say which department carried what. Three weeks of email follow, which is a cost nobody put in the budget. If the split by cost center and department is not captured at booking time, it cannot be reconstructed from the total afterwards.
Split the budget by the dimensions people will ask about
Four splits cover almost every question an event budget gets asked:
- By category — flights, accommodation, transfers, rail, car rental, on-site spend. This is the one that tells you where to cut if you have to.
- By participant — the number that makes an unevenly distributed budget visible. A group where four people flew long-haul and twenty took trains has a per-person average that describes nobody.
- By cost center — the split finance will ask for, and the one that has to exist at booking time, not at reporting time.
- By department — the split the business will ask for, which is usually not the same as the cost center split, and that is fine as long as both are carried.
Add the legal entity if the company has more than one. An event where participants belong to different entities is an invoicing question, not a reporting question, and it is cheaper to answer before the bookings than after the invoices.
One more column people forget: the currency
An event budget is denominated in something, and for an international group that something is not what everybody spends in. The flights are bought in one currency, the hotel invoices in another, and the taxis on site in a third. If the budget has one currency and the lines have several, the total is a conversion, and a conversion done at an unstated rate on an unstated date is an argument waiting to happen with finance.
Two habits avoid it. State the budget's currency explicitly when you set the budget, and set per-person spending limits in the currency people will actually pay in on site, rather than making each participant do the arithmetic at a card terminal.
The approval rule you set once
Budget control at event scale is not vigilance, it is a rule you set before the invitations go out. There are three sensible shapes:
- Approve only what breaks policy. The default for most events: bookings inside the rules go through, anything outside them comes to you.
- Approve everything. For a first event, or a tight budget, or a group that has not travelled together before.
- Approve above an amount. The pragmatic middle: the long-haul flights and the suites come to you, the trains do not.
Whichever you pick, decide who approves before you need it. An approval queue with one person in it is a queue that stops when that person is on a plane.
The structure that holds up
If you are keeping this in a spreadsheet — and plenty of good event organizers do — these are the columns that make it survive contact with the event:
| Column | Why it is there |
|---|---|
| Participant | the unit the budget is actually consumed by |
| Department / cost center | the two splits you will be asked for, captured at entry |
| Departure city | explains why two people on the same trip cost different money |
| Estimate | what you planned per person, before anyone books |
| Booked | committed, not yet charged |
| Paid | money that has left the company |
| On-site spend | card spend and receipts during the event |
| Outside window? | a flag, not a cost — but it predicts the costs that surprise you |
| Status | invited / accepted / declined, because a declined participant is a line to remove, not a line to total |
Totals per column; the four headline numbers above the table; and one rule for using it: update Booked when the reservation is made, not when the invoice arrives. A template maintained from invoices is a historical record, not a budget.
How this works in Travel Code
In a company event in Travel Code, the four numbers are the top of the Budget tab: total budget, booked and spent, paid, remaining. They are not typed in — they are what the event's own bookings add up to, so they move when a participant books rather than when someone updates a sheet.
Underneath, spend splits by category, participant, cost center or department, with recent transactions listed and CSV export when the number has to go into a spreadsheet anyway. The legal entity, cost center and departments are carried for attribution, so event spend lands in the same reports as the rest of the company's travel instead of needing to be matched to it.
The commitment side is covered by the participant list rather than the budget: each person shows their estimate next to what they have booked and spent, and a flag when their bookings fall outside the event's travel window. For companies using Travel Code cards, each participant can carry a virtual card with its own limit and currency — the card spend becomes an expense with a receipt in the normal flow, counts against the event budget and is invoiced to the company.
The short version. Track four numbers, not one: budget, booked, paid, remaining — and treat booked as the early warning, because it moves first. Capture the cost center and department at booking time; they cannot be recovered from a total. Set the approval rule before the invitations, and name more than one approver.
More on running company events
- Room blocks for company events: how they work and what to check in an offer
- Corporate offsite and retreat planning: the checklist, and the one decision it hangs on
- Planning a sales kickoff: the agenda, the travel, and the spreadsheet you can drop
- Inviting external guests to company travel
- Travel Code vs Navan Events for company events: what each one actually does
- Travel Code vs Perk (formerly TravelPerk) for company events
The product these articles describe is Company Events in Travel Code: one workspace for the people, the travel rules, the room blocks and the budget of a company trip.
