Vantly Get a custom quote

Closing the Books After a Company Offsite: Actuals, Vendors and Next Year's Ask

By the Vantly team · Research checked October 2026

The offsite is over, the photos are in the company channel, and the invoices are still arriving. Somewhere between the venue's final folio, the caterer's revised bill and a handful of card charges nobody flagged, the number Finance approved has quietly become a different number. Closing the books properly is not admin for its own sake. It is how next year's budget ask stops being a guess. The method is short: match every invoice to the PO, explain each variance against the approved estimate, classify the fees nobody expected, record how the contingency was used, score each vendor on what they promised in writing, and turn all of it into a one-page closeout memo and next year's brief. This guide is written for the controller or finance partner who owns the close, with the EA and People Ops lead who hold the receipts, the emails and the memory of what actually happened on site.

Get a custom quoteSee sample events
A colleague writes event plans in a notebook by a window.
Photo: Vlada Karpovich / Pexels

The offsite is over, the photos are in the company channel, and the invoices are still arriving. Somewhere between the venue's final folio, the caterer's revised bill and a handful of card charges nobody flagged, the number Finance approved has quietly become a different number. Closing the books properly is not admin for its own sake. It is how next year's budget ask stops being a guess. The method is short: match every invoice to the PO, explain each variance against the approved estimate, classify the fees nobody expected, record how the contingency was used, score each vendor on what they promised in writing, and turn all of it into a one-page closeout memo and next year's brief.

This guide is written for the controller or finance partner who owns the close, with the EA and People Ops lead who hold the receipts, the emails and the memory of what actually happened on site.

Why the closeout decides next year's budget

When a retreat request reaches Finance next year, the first question will be some version of "what did it cost last time, and why?" If the honest answer is "roughly what we approved, plus some extras," the new request starts on the back foot. If the answer is a single page that shows the approved estimate, the actual, the three lines that moved and why, the conversation is about the event instead of the numbers.

Capital requests and project approvals work the same way, a topic r/FPandA returns to often (see Sources): a request backed by a clear record of how past spend landed against plan is easier to approve. An offsite is a small project, but the logic holds. A credible closeout is the evidence behind the next ask.

It also protects the people who planned it. An EA who can show that the overrun came from a late headcount increase approved by leadership, not from planning mistakes, is in a much better position next year. Our companion guide on getting the retreat PO approved in the first place covers the packet this closeout reconciles against.

Who owns what in the close

The close goes faster when the three roles split the work rather than passing one spreadsheet around.

Role | Owns | Hands over

Finance / controller | PO status, invoice matching, variance analysis, accruals, closing or releasing the PO | The closeout memo and the budget baseline for next year

EA or event lead | Contracts, change emails, final headcount and room lists, on-site sign-offs, card receipts | The evidence pack and the first draft of the vendor scorecard

People Ops | Attendance by day, pulse survey themes, what to keep or change | The "why" behind scope changes and the next brief's priorities

The split above is a suggested default. What matters is that each piece has one named owner and that Finance sets the date by which the evidence pack is complete.

Step 1: Build the evidence pack

You cannot reconcile what you cannot see. Before matching anything, collect every document in one folder, named consistently:

  • The approval packet and the approved estimate, including the contingency line and any options that were approved separately.
  • Every PO raised for the event, with change orders.
  • Signed contracts and the final quotes they reference, including any addendum or revised quote.
  • Written change approvals. Emails or messages where someone approved a headcount change, an extra night, an upgraded menu or added transport. These explain most variances later.
  • Delivery evidence. Final room list, final headcount given to the kitchen, the venue's event order or run sheet, transport manifests, and anything signed on site.
  • Every invoice, including deposits, interim invoices, final invoices and credit notes.
  • Off-PO spend. Corporate card charges, attendee expense claims for travel and meals, and any petty cash.

The EA usually holds most of this, scattered across an inbox. Keeping one running folder and one change log from the first booking, the kind of habit assistants swap in event-planning cheat sheets on r/ExecutiveAssistants (see Sources), stops the close from becoming an archaeology project. If that did not happen this year, put it on next year's brief.

Step 2: Match every invoice to the PO

For each vendor, line up three things: what was ordered (the PO and the contract), what was delivered (your delivery evidence) and what was billed (the invoice). This is the familiar three-way match, applied to an event. Event invoices are harder than most because the "order" changes up to the day itself, so the written change approvals from Step 1 are part of the order.

Common mismatches and what to do with each:

What you find | Likely cause | What to do

Invoice higher than PO | Approved scope change not reflected in a PO change | Find the written approval, raise a PO change, note it as a scope variance

Invoice higher than PO, no approval found | Charge added on site or after the event | Query the vendor in writing and ask for the contractual basis

Line billed for more people than attended | Billing on guaranteed headcount or room commitment | Check the attrition and final-headcount terms in the contract

Deposit not credited on the final invoice | Deposit applied to the wrong account or missed | Ask for a corrected invoice showing deposits applied

Invoice from a vendor with no PO | Booked directly by someone on the team | Decide with your policy whether to raise a retrospective PO; log it as off-process spend

Invoice lower than PO | Unused options, lower attendance, or a pending late invoice | Confirm nothing is still to come before releasing the balance

A lower-than-expected invoice deserves the same care as a higher one: a missing line often means a late invoice, not a saving.

Step 3: Actuals vs estimate, line by line

Once the invoices are matched, build the variance view against the approved estimate, not against the original quote and not against what someone remembers. Keep the same line structure as the approval packet so each line maps straight back.

Line | Approved estimate | Actual | Variance | Driver | Controllable? | Note for next year

Lodging | | | | | |

Meeting space | | | | | |

Food and beverage | | | | | |

Transport | | | | | |

AV and WiFi | | | | | |

Activities and facilitation | | | | | |

Taxes, service charges and fees | | | | | |

Off-PO spend (cards, expenses) | | | | | |

Contingency released | | | | | |

Total | | | | | |

Working template. Use your own chart of accounts and line structure where they differ.

Give every variance one main driver. A small set of categories makes the memo readable:

  • Headcount. More or fewer people than planned, or a different mix of overnight and day attendees.
  • Scope change. Something added or removed after approval: an extra night, an upgraded dinner, added transport.
  • Price change. Same scope, different price, for example because a quote was indicative rather than firm.
  • Fee not in the estimate. A charge that was not in the approved number at all (see the next section).
  • Timing. A cost that belongs to this event but will land in a later period, or a deposit paid in an earlier one.

Then add a per-person view based on actual attendance, not invited headcount. That figure, with its definition stated, is the most useful single number for next year.

Surprise fees: classify them before you argue about them

Every offsite close has a few charges that make Finance ask "what is this?" Before disputing any of them, sort each into one of three buckets.

  1. Quoted and expected. It was in the contract and in the estimate. Not a surprise, even if it is large.
  2. Quoted but missed. It was in the contract or the quote, but nobody carried it into the approved estimate. The vendor is usually right; the estimate was incomplete.
  3. Not quoted. It does not appear in the contract, the quote or any written change approval. This is the bucket worth querying.

The usual suspects across all three buckets:

  • Service charges and gratuity. A service charge is not always a gratuity paid to staff; it may be a house or administrative charge. Check which lines it was applied to.
  • Taxes on lodging, food, services or the service charge itself.
  • Attrition or minimum-spend shortfalls when fewer people came than were guaranteed.
  • Staff or AV overtime when sessions or dinner ran late.
  • Extra transport, waiting time or late-arrival runs.
  • Cleaning, damage or facility fees, and card processing fees.
  • Room incidentals that were meant to go to attendees but landed on the master bill.

We deliberately give no percentages or typical amounts: they vary by city, state, venue and contract, and only the vendor and your contract can say what applies. How you record service charges, gratuities and sales or lodging taxes in your books is a question for your finance or tax advisor.

For bucket 3, query in writing, cite the contract clause or the absence of one, and ask for the basis of the charge. Keep it factual. For buckets 1 and 2, the fix is upstream: next year's quotes should list these lines explicitly. Our guide on what to ask in a custom event quote has the question list.

Contingency used: log it, don't spend it

The approval packet should have carried a contingency as its own line, with a named person who could release it. At close, record every release:

Date | Risk or reason | Released by | Amount | Was this risk on the original list?

Working template.

This log answers two questions next year. First, was the contingency the right size? Base the answer on this event's evidence, not a rule of thumb. Second, were the releases for the risks you listed, or for things nobody anticipated? Unlisted releases are the best input for next year's risk list.

Unused contingency is not a saving to spend on something else. Report it as unused and return it according to your policy. Showing that a reserve was released only for listed reasons is one of the strongest credibility signals you can give the people who approve the next one. Our companion guide on Finance approval and POs covers how to set up contingency in the first place.

Close the PO and the period

Before you call the event closed, confirm:

  • No invoices are outstanding. Ask every vendor in writing for confirmation that the final invoice has been issued.
  • Deposits are applied on final invoices, and any credit notes or refunds have actually been received, not only promised.
  • Off-PO spend is captured, including attendee expense claims that arrive weeks later.
  • The PO is closed or the balance released so the unused amount does not sit as a commitment.
  • Cross-period costs are handled. If the event and its invoices straddle a month or quarter end, follow your company's accrual practice.

If a vendor dispute is still open, note it in the memo with the amount in question rather than holding the whole close.

The vendor scorecard, from Finance's side

The People Ops or EA scorecard covers whether each vendor delivered a good experience. Finance needs a second lens: was this vendor accurate, predictable and easy to pay? Score against what was promised in writing.

Criterion | Vendor A | Vendor B | Evidence

Quote matched the contract | | |

Invoice matched the quote and approved changes | | |

Fees were disclosed before signing | | |

Invoices arrived on time, correctly addressed to the PO | | |

Queries answered promptly and in writing | | |

Delivered what was contracted (rooms, meals, AV, transport) | | |

Vendor setup and documents were straightforward | | |

Rebook, rebook with changes, or do not rebook | | |

Working template. Use a simple scale your team agrees on.

Keep it fair. A vendor who billed a fee you missed in your own estimate did nothing wrong. A vendor who added a charge with no contractual basis, then corrected it quickly when asked, may still be a good rebook. Our debrief guide covers the experience side of the scorecard.

The one-page closeout memo

Pull everything into a single page for the CFO, the budget owner and whoever will plan next year:

  • Event: purpose, dates, format, actual attendance by day.
  • Headline: approved estimate, actual total, variance, and per-person cost on actual attendance.
  • Top variance drivers: the three lines that moved most, with their driver category.
  • Surprise fees: totals by bucket, and any open disputes.
  • Contingency: amount approved, amount released, for what, and amount returned.
  • Vendors: rebook, rebook with changes, do not rebook, with one-line reasons.
  • Process findings: what slowed the close (missing POs, late invoices, approvals not in writing).
  • Recommendation: the starting baseline for next year's ask.

Keep the full workbook as an appendix. Most readers only need the page.

Turning actuals into next year's ask

Next year's request should start from this year's actuals, not from this year's estimate and not from a new from-price. Then adjust openly:

  • Headcount: expected attendance, with the overnight and day split.
  • Scope: what you are keeping, cutting or adding, based on the pulse themes and the decision log.
  • Destination and dates: a new region, season or format changes nearly every line, so say which lines are carried over and which need fresh quotes.
  • Known fees: every line from buckets 1 and 2 goes into the estimate this time.
  • Contingency: sized from this year's release log and next year's risk list.
  • Core vs options: keep approved options as separate lines, as you did in the packet.

Then write the next brief, so the planner and every quoting vendor start from the same facts:

  • Purpose and success measures.
  • Headcount range, dates or date window, and the room rule (private bedrooms or sharing).
  • Region and travel limit.
  • Dining model, transport and AV needs.
  • Fees and terms you need itemized in every quote: taxes, service charges, deposits, attrition and cancellation.
  • How many contracts and invoices Finance is prepared to manage.
  • Vendor notes from the scorecard.
  • The budget envelope and the named budget owner.

Our debrief guide includes a fuller next-year brief template you can merge with this list.

Where a local event designer helps

The cleanest close starts with a quote that already answers the questions Finance asks at the end. That is how Vantly works. Every event is tailor-made: a local event designer who knows the destination first-hand builds the plan around your brief, with inclusions, options and fees laid out so they can be carried straight into an approval packet and reconciled afterward. Our intent is that you work with one point of contact and receive one invoice for the event, rather than matching separate bills from the venue, the caterer and the transport company. We started in the New York region, so that is where our designer network is deepest today.

If you are planning next year's company offsite or leadership retreat, you can share this year's closeout memo and scorecard as part of the brief. For a sense of what a produced event looks like, see sample events. They are examples a local designer tailors to your group, not fixed packages.

Frequently asked questions

How do you reconcile an offsite budget?

Collect every PO, contract, written change approval, delivery record and invoice in one place. Match each invoice to its PO and to what was delivered, then compare actuals to the approved estimate line by line, giving each variance one main driver.

What is the difference between actuals vs estimate and invoice vs PO?

Invoice vs PO checks that each bill matches what was ordered and delivered. Actuals vs estimate checks whether the whole event landed where the approved budget said it would, including off-PO spend and contingency.

How should Finance handle surprise fees after an event?

Classify each one: quoted and expected, quoted but missed in the estimate, or not quoted at all. Query only the last group, in writing, citing the contract. Book service charges, gratuities and taxes the way your accounting policy already treats them.

What should an event vendor scorecard include for Finance?

Quote accuracy, invoice accuracy against approved changes, fee disclosure, invoice timeliness, responsiveness to queries, delivery against the contract and ease of vendor setup, with a rebook decision and evidence for each vendor.

What happens to unused contingency?

Report it as unused and return it according to your policy. Log every release with the reason and approver, so next year's contingency can be sized from evidence.

How do you build next year's offsite budget?

Start from this year's actuals, adjust openly for headcount, scope, destination and dates, add every fee that surprised you this year, size contingency from the release log, and send every vendor the same brief.

Need next year's numbers to start clean?

Send us your dates, your group and what the event needs to do, along with anything this year's close taught you. A local event designer will come back with a tailor-made plan, with options and fees itemized so Finance can approve it and reconcile it afterward. Get a custom quote.

Sources