Payments6 min read

How to Invoice Clients as a Restaurant

How restaurants invoice catering, private events and corporate accounts — from headcount and deposits to service fees, tax, gratuity and balance reminders.

Farhad, founder of GHL Spark
Farhad · Founder, GHL Spark
Cover illustration — an itemized invoice outline on a dark green background, marked GHL Spark, Payments

In short

Most of a restaurant's revenue settles instantly at the table, so many owners never build a real invoicing habit — until catering, private events and corporate accounts arrive and the money suddenly has to be quoted, deposited, contracted and collected weeks apart. That is a different discipline from ringing up a check. A catering or event invoice is not one number; it is a headcount-driven estimate with per-head food pricing, a service or venue fee, rentals, delivery, tax and gratuity, split across a deposit that locks the booking and a balance that comes due on a fixed date. Getting it right means quoting clearly up front, attaching the invoice to a simple contract, sending a deposit payment link the client can tap the same day, and letting an automated reminder chase the balance before the event rather than after the food has already gone out. Corporate clients who order every week want something different again — a recurring monthly statement or account billing rather than a fresh invoice each time. This guide walks through what belongs on a restaurant catering invoice, how to structure deposit-plus-balance billing, how contracts and payment links fit together, and how to keep clean records so every event is accounted for and nothing is collected late or forgotten.

Key takeaways

  • A restaurant invoice is not a check — catering, events and corporate accounts need a quoted estimate, a deposit, a contract and a balance with a due date.
  • Build every event invoice from headcount — per-head food pricing plus service fee, rentals, delivery, tax and gratuity gives the client a total they can trust.
  • Split billing into deposit and balance — the deposit locks the booking and pulls cash forward, the balance comes due on a fixed date before the event.
  • Send a payment link, not a paper bill — a link the client taps clears in minutes and lets automated reminders chase the balance before the food goes out.
  • Corporate accounts want recurring statements — bill weekly orders on a monthly account rather than issuing a fresh one-off invoice for every delivery.

Some links to tools we rate — including HighLevel — are affiliate links. If you start a trial through them we may earn a commission, at no extra cost to you. We only recommend tools we would set up for our own clients.

Most of what a restaurant sells is paid for instantly — a guest finishes a meal, taps a card at the table, and the transaction is done. So it is easy to go years without ever writing a real invoice. Then catering, private events and corporate accounts arrive, and suddenly you are quoting a total weeks ahead, taking a deposit, and collecting a balance days before the food goes out. That is a different skill from ringing up a check. The short answer: a restaurant invoices whenever money is agreed before the meal, and a good catering or event invoice is a headcount-driven, itemized document split into a deposit that locks the booking and a balance that comes due on a fixed date.

This guide covers when to invoice, what belongs on the invoice, how deposit-plus-balance billing works, how contracts and payment links fit in, how to follow up before the event, how to bill recurring corporate accounts, and what records to keep.

When does a restaurant need to invoice a client?

Not at the table — the POS already handles that. Invoicing matters wherever the money and the meal are separated in time:

  • Catering — an order quoted and confirmed ahead of a drop-off or delivery.
  • Private events and buy-outs — a party, wedding or corporate dinner that ties up a section or the whole room.
  • Large group bookings — where a no-show costs you a night of covers.
  • Corporate accounts — companies ordering regularly on standing terms.

In each of these, the client commits early, pays part now and part later, and needs a written document showing what they are buying and what is still owed. For the cash-flow side of this — deposits, contracts and gift cards that pull revenue forward — see our guide to getting paid faster for restaurants.

What goes on a restaurant catering invoice?

A catering or event invoice is never a single number. It is built up from the headcount and shown line by line, so the client can see exactly how the total was reached. Here is what each element does.

Invoice elementWhy it mattersExample
HeadcountThe base almost everything else scales from80 guests, guaranteed count due 5 days prior
Per-head food or packageThe core charge, priced per guest80 x per-head buffet
Service or venue feeCovers staffing, setup, use of the spaceFlat fee for a private-room buy-out
Rentals and equipmentTables, linens, chafing dishes, glasswareLinen and chafing-dish hire
Delivery or travelOff-site catering costs to get thereDelivery within a set radius
TaxPrepared-food and catering tax on the taxable linesApplied to food and fees per local rules
GratuityService charge, often auto-added for large eventsPercentage added for parties over a set size
Deposit paidShows what has already been collectedDeposit received, dated
Balance dueThe remainder and its due dateBalance due, with a fixed date

Two rules keep this clean. First, label service fees, tax and gratuity as separate lines — never bury them in the food price, or the client feels misled. Second, tie the food total to a guaranteed headcount deadline: a date after which the count can rise but not fall, so you are not left having prepped for 80 when the client trims to 60 the day before. To collect the event details that feed all of this accurately, a structured brief helps — see restaurant intake form templates.

How do deposits and balances work?

Split every event into two payments. The deposit — usually a fixed percentage of the estimate or a flat booking fee — is collected upfront. It holds the date, commits the client, and pulls cash forward while protecting you against a late cancellation that would otherwise wipe out the booking. The balance is everything still owed, due on a date you set.

For private events and buy-outs, collect the balance before the event — a few days ahead or on the day — because once the party is over your leverage to collect drops fast. For catering, payment on delivery is common. For trusted corporate accounts, short terms and monthly billing are reasonable. The general rule: the larger the event and the newer the client, the earlier you collect.

Do I need a contract with the invoice?

For anything bigger than a routine drop-off, yes. The invoice says what is owed; the contract says what happens around it — the cancellation and refund policy, deposit terms, the guaranteed-headcount deadline, and any rules about the space or timing. Agreeing those in writing when the booking is made removes nearly every awkward conversation later, because there is nothing left to argue about after the fact.

What is the fastest way to send invoices and get paid?

A digital invoice with a built-in payment link. Instead of printing a bill or waiting for a cheque, you send a link the client opens on their phone and pays by card in under a minute — and the payment is recorded against the invoice automatically. It suits the deposit-then-balance flow perfectly: one link for the deposit now, another for the balance later, each tied to the same event.

One option that keeps this in a single place is HighLevel, which builds and sends event invoices, takes deposit payment links, and runs automated reminders alongside a CRM that stores every client and event. Honestly, its value is not being the cheapest line item — it is that quotes, deposits, balances, contracts and follow-ups live against one client record instead of scattered across a spreadsheet, a payment app and a calendar. If that consolidation fits how you run events, you can start a free HighLevel trial. It is one route, not the only one — plenty of restaurants run fine on a standalone invoicing app. Compare where our own service fits on the pricing page.

How should I follow up before the event?

Before the event, not after. Set up a short reminder sequence tied to the balance-due date: a friendly note when the balance comes due, a firmer nudge a few days before the event, and a confirmation on the day. Automating it means a manager never has to make the uncomfortable call, and the balance is collected while the client is still engaged. Collecting before the food goes out is always easier than chasing weeks afterward.

How do I bill recurring corporate accounts?

Set repeat corporate clients up as an account, not a stack of one-off invoices. For a company ordering weekly lunches or standing catering, issue one consolidated monthly statement with every order itemized and a single balance to pay — or bill a fixed recurring amount automatically if the order does not change. Their accounts team approves one payment instead of ten, your admin drops, and an occasional buyer becomes predictable monthly revenue. Those same account relationships are worth nurturing when they go quiet — see win-back campaign ideas for restaurants.

What records should I keep?

For every event, keep the signed contract, the original quote, the final itemized invoice, proof of both the deposit and balance payments, and any change to headcount or menu. Store them against the client's record rather than in scattered inboxes, so you can pull up a past event in seconds, reuse it to quote the next one, and see which clients book again. Clean records protect you in a dispute and make tax time far simpler.

Invoicing is where a restaurant's highest-value work — catering, events and corporate accounts — actually turns into money in the bank. Quote clearly, split into deposit and balance, pair the invoice with a contract, send a payment link, and let reminders do the chasing. For more on running the marketing and operations side of a hospitality business, browse the Restaurant & Hospitality Marketing hub, or book a call to talk through your setup.

Frequently asked questions

When does a restaurant actually need to send an invoice?
Whenever money is agreed ahead of the meal rather than settled at the table. Everyday table service does not need an invoice — the POS handles it the moment the guest pays. Invoicing matters for catering orders, private and buy-out events, large group bookings, and corporate accounts, where a total is quoted in advance, a deposit is taken to hold the date, and a balance is collected later. In all of those cases the customer needs a written, itemized document that shows what they are paying for, what they have already paid, and what is still owed. That document is your invoice, and it doubles as the record you rely on if there is ever a dispute.
What should a catering or event invoice include?
At a minimum: your restaurant's name and contact details, the client's details, the event date and location, a confirmed or estimated headcount, the menu or package with per-head pricing, any service or venue fee, rentals and equipment, delivery or travel charges, applicable tax, gratuity, and the grand total. It should then show the deposit already paid and the remaining balance with its due date. Every figure should trace back to something the client agreed to, so there are no surprises. A clear, itemized invoice is not just for billing — it is what makes the final total feel fair, because the client can see exactly how it was built.
How does headcount affect the invoice?
Headcount is the number almost everything else is calculated from. Most catering and event pricing is per-head, so the food total moves directly with guest count, and staffing, rentals and portions follow it. Because final numbers often are not confirmed until days before, many restaurants invoice the deposit against an estimated headcount, then finalize the balance once the guaranteed count is locked — commonly a set number of days before the event, after which the count can go up but not down. Spelling out that guaranteed-count deadline on the invoice and contract protects you from a client who trims numbers at the last minute after you have already bought and prepped for the original figure.
What is the difference between a deposit and the balance?
The deposit is an upfront payment that holds the date and commits the client; the balance is everything still owed, collected closer to or on the event. A deposit is usually a fixed percentage of the estimated total or a flat booking fee, and it pulls cash forward while protecting you against cancellations. The balance is the remainder, due on a date you set — often before the event for private parties, or on delivery for catering. Splitting the invoice this way is standard because it shares the risk fairly: the client is not paying everything weeks ahead, and you are not doing the work before any money has changed hands.
Should the balance be due before or after the event?
For private events and buy-outs, collecting the balance before the event — often a few days ahead or on the day — is safest, because once the party is over your leverage to collect drops sharply. For catering, payment on delivery or shortly after is common, especially with trusted repeat clients. For established corporate accounts you might extend short terms and bill monthly. The right answer depends on how well you know the client and how much revenue is at stake, but the general rule is simple: the larger the event and the newer the client, the earlier you should collect.
Do I need a contract as well as an invoice?
For anything larger than a routine catering drop-off, yes. The invoice says what is owed; the contract says what happens around it — the cancellation and refund policy, the deposit terms, the guaranteed-headcount deadline, what the deposit does and does not cover, and any rules about the space or timing. Pairing a short, clear contract or event agreement with the invoice protects both sides and removes almost every awkward conversation before it starts, because the terms were agreed in writing when the booking was made rather than argued about after something goes wrong.
How should service fees, tax and gratuity appear on the invoice?
As separate, clearly labeled lines — never rolled silently into the food price. A service or venue fee, tax and gratuity are each calculated differently and often on different bases, so listing them individually lets the client see exactly what each one is. Be transparent about whether gratuity is automatically added for large events, since that is common and expected but should never be a surprise. Check the tax rules that apply to prepared food and catering in your area, because they can differ from dine-in, and getting the tax line right on the invoice keeps your records clean at filing time.
What is the best way to actually send the invoice and collect payment?
A digital invoice with a built-in payment link is the fastest, most reliable option. Instead of printing a bill or waiting for a cheque, you send the client a link they can open on their phone and pay by card in under a minute, and the payment is recorded against that invoice automatically. It clears far faster than a mailed cheque, it is easy for the client, and it makes the deposit-then-balance flow simple because you can send one link for the deposit now and another for the balance later, each tied to the same event.
How do I invoice a corporate client that orders every week?
Set them up as an account rather than invoicing every single order separately. For a company that orders weekly lunches or standing catering, issuing a fresh invoice each time is slow for both sides. Instead, record each order through the period and send one consolidated statement — usually monthly — with all orders itemized and a single balance to pay, or bill a recurring amount automatically if the order is fixed. This reduces admin, makes it easy for their accounts team to approve one payment, and turns an occasional customer into predictable recurring revenue.
How far ahead should I follow up on an unpaid balance?
Before the event, not after. The most effective pattern is a scheduled sequence of reminders — a friendly note when the balance becomes due, a firmer one a few days before the event, and a final confirmation on the day — so the money is collected while you still have leverage and the client is still engaged. Automating those reminders means a manager never has to make the awkward call, and the balance is far less likely to slip past the event into weeks of chasing. Collecting before the food goes out is always easier than collecting after.
What records should I keep for each event I invoice?
Keep the signed contract or agreement, the original quote, the final itemized invoice, proof of the deposit and balance payments, and any change to headcount or menu along the way. Together these show what was agreed, what was paid, and when — which you will need for your own bookkeeping and tax, and for settling any dispute. Storing everything against the client's record rather than in scattered emails means you can pull up a past event in seconds, reuse it to quote the next one, and see at a glance which clients book with you again.
Can one tool handle quoting, deposits, balances and reminders together?
Yes. Rather than juggling a spreadsheet for quotes, a separate payment app for links, and a calendar for follow-ups, an all-in-one platform can build the event invoice, take the deposit, send the balance link and run the reminder sequence — all attached to the same client record and event. That way the deposit, the balance, the contract and every message live in one place, so nothing about an event is scattered across tools or lost between the booking and the bill.

About the author

Farhad, founder of GHL Spark

Farhad

Founder, GHL Spark

Farhad is the founder of GHL Spark, where he builds and white-labels GoHighLevel SaaS platforms for agencies and SaaS operators. He writes about the parts of GoHighLevel that actually break in production — A2P registration, onboarding, support load and automation.

More from Farhad

Want this handled for you?

We set up, configure and white-label your GoHighLevel SaaS — so you can sell it instead of building it.

Fixed quote · No lock-in · Launch-ready in ~7 days