How to write a corporate agreement that does not end in a dispute

A corporate agreement is a promise about who pays for what. It sounds simple until a traveler orders a bottle of wine, puts it on the room, and three months later the company’s controller asks why they are paying for alcohol. The invoice is disputed, the relationship cools, and the problem was never the wine: it was that the agreement said “food and beverage” without saying which. This guide exists so that does not happen to you.

What an agreement has to answer

Before you write, be clear about the questions the server, the front desk agent and the controller are going to ask. A good agreement answers all of them without anyone having to call sales:

• What does the company cover and what does the guest pay out of pocket?
• Is there a cap per day, per stay or per person?
• What happens to anything above the cap?
• Who gets invoiced and with which details?
• What are the payment terms and what happens if the company does not pay?
• Who at the company can authorize exceptions?

Rule 1: write by category, not by phrase

“Food and beverage” is not a rule. It is a source of disputes. A well-written agreement splits consumption into categories and says, for each one, whether the company or the guest covers it. The minimum categories for a hotel with a restaurant are these:

Once the categories are written down, the hotel system can apply them on its own: the server posts dinner to the room and the system sends the food to the company folio and the beer to the guest’s personal folio. Without categories, that decision is made by the server, from memory, in a hurry. And the server never read the agreement.

Rule 2: the most specific rule wins

Categories will collide. “Non-alcoholic beverages: company” and “minibar: guest” collide when the guest drinks a bottle of water from the minibar. The way to settle it without an argument is a written hierarchy: the more specific rule beats the general one. The minibar water falls under minibar, because minibar is more specific than beverages. A wine at the company banquet falls under banquet, because the event is more specific than the alcohol category.

Write the hierarchy into the agreement in one line: “When two rules apply to the same item, the more specific one prevails: product over category, event over stay, written exception over general rule.” That line prevents more arguments than any other in the document.

Rule 3: tax is split the same way the consumption is split

This is where many reconciliation hours are lost. If a dinner of 1,000 (illustrative example) carries 800 of food paid by the company and 200 of wine paid by the guest, the tax on that dinner cannot go entirely to either one. It is split in the same proportion: the tax on the 800 goes to the company folio, the tax on the 200 to the guest folio. Each folio closes with the right base and the right tax, and each invoice shows only what belongs to it.

Write it into the agreement: “Taxes are allocated to each folio in proportion to the consumption that folio covers.” And make sure the hotel system does it that way, because if the point of sale sends the whole tax to a single folio, the agreement will say one thing and the invoice another.

Rule 4: a cap needs a destination for the excess

A cap without a destination is a question without an answer. “Food up to 500 per day” does not say what happens to unit 501. There are three options, and you have to pick one: the excess is paid by the guest at check-out; the excess is invoiced to the company on a separate line with authorization; or the excess is not allowed and the system rejects the charge. The first is the most common and generates the fewest disputes, as long as the guest knows about it at check-in.

Rule 5: names, terms and who authorizes

• Who gets invoiced: legal name, tax details, the email where invoices are received. If it changes, the agreement is updated in writing.
• Payment terms: counted from the date the account or the invoice is created, not from “whenever it arrives”. And what happens when it is overdue: notice, credit suspension, both.
• Who authorizes exceptions: one or two people with a name and an email. Any “my boss said yes” that does not come from them does not apply.
• Who can stay under the agreement: a list of names, a corporate email domain, or prior authorization per booking.

Sample clauses in plain language

An agreement does not need to sound like a contract to be one. These sample clauses are a starting point; adapt them and run them past your legal advisor.

The company covers lodging and food from the restaurant and room service up to 500 per guest per day (sample figure). Alcoholic beverages, minibar, laundry and any consumption above the cap are paid by the guest directly at check-out.Coverage clause, illustrative example

When two rules apply to the same item, the more specific one prevails: product over category, event over stay, and written exception over general rule.Hierarchy clause, illustrative example

Taxes on each item are allocated to the folio that covers that item, in the same proportion. Each invoice includes only the base and the tax of what that folio paid.Tax allocation clause, illustrative example

The property invoices each stay on closing and the company pays within thirty days of the issue date (sample term). Once overdue, the property suspends credit until the balance is current.Payment clause, illustrative example

The server test

Before signing, run this test: hand the agreement to a server and ask them who they charge for a wine, a breakfast and a laundry order from a guest of that company. If they have to ask, the agreement is badly written. If the hotel system can apply it without the server ever reading it, the agreement is well written, and it will actually be followed.

In Inn Restaurant the agreement is captured once, by category and with a hierarchy, and the system applies it on every charge: food to the company folio, beer to the guest folio, tax split between them. See how it is configured on the corporate accounts page (/cuentas-de-empresa) and how the corporate traveler experiences it (/viajero-corporativo). And the question for your next agreement: of every hundred corporate guests who slept with you, how many ate with you?