Why a catering deposit is not income until the event is served

A restaurant owner we work with took deposits on three private events in November. All three events were scheduled for December. By the end of November, the booking calendar showed $4,800 in deposits received and all three events confirmed.

Her November books showed $4,800 in event revenue.

In December, food and staffing for those three events ran $3,200. The events came off without problems. The December Profit and Loss report (P&L) showed almost no event revenue and a meaningful cost hit. She called in January asking why November looked strong and December looked thin when December was the month she actually worked.

Nothing was wrong with the business. The deposit accounting was wrong.

What a catering deposit actually represents

A deposit is not earned income. It is an advance payment for a service the restaurant has not yet delivered. Until the event is served, that money belongs to the customer in a meaningful sense: the restaurant still owes them an event, and if the event does not happen, the restaurant may owe the money back.

Recording the deposit as revenue on the day it arrives treats a future obligation as a completed sale. It makes one month look more profitable than it was and the next month look worse. It also hides the liability. If the restaurant carries $12,000 in open event deposits at year-end and the books show all of it as income, the balance sheet has no record that any of it might need to be returned.

Why deposit accounting goes wrong

Bank feed default categories. When the deposit hits the checking account, the bank feed suggests a transaction category. Most owners accept the suggested label and move on. The deposit posts to event revenue before anyone considers whether the event has actually occurred.

Event booking software records the wrong thing. Platforms that handle private dining or catering reservations often log the deposit as a completed sale at booking time. If the bookkeeping pulls from those records without reclassifying deposits, the wrong label moves from the booking tool into the general ledger.

No liability account on the chart of accounts. If the chart of accounts does not include a Customer Deposits or Deferred Revenue account, there is nowhere to put the deposit other than income. Most restaurant charts of accounts are set up without one because most bookkeepers never set it up.

Month-end close does not include a deposit review. A correct month-end close involves checking the deposit register against the event calendar and moving any earned deposits from the liability account to revenue. When that step is absent, deposits sit in income long after they were correctly earned, and newly received deposits for future events get added to income the moment they arrive.

What the books should show

Here is how the same three events should appear in the P&L for each month.

In November, the $4,800 posts to a Customer Deposits liability account on the balance sheet. Event revenue stays at zero for those events. In December, as each event is completed, the liability account is cleared and the corresponding amount moves to revenue. The $3,200 in food and labor matches against the $4,800 in December revenue. The actual gross margin on catering shows up in the correct month.

Why this matters beyond a timing difference

Three problems develop when deposits remain in income.

Spending decisions are based on incorrect numbers. An owner who sees $4,800 in November event income may adjust staffing levels, authorize supplier orders, or set a higher operating budget for December, all based on revenue that was not earned in November. The cash is real. The income is not.

Cancellation refunds hit the wrong account. If a deposit is sitting in November revenue and the customer cancels in December, the refund looks like a December loss with no connection to the original booking. Correct books show the refund as a reduction in the liability account. The P&L is untouched because the revenue was never recognized to begin with.

Year-end reports overstate revenue. Open deposits at December 31 are often the largest balance of the year because the holiday event season generates heavy advance bookings. If those deposits are in income rather than in a liability account, year-end revenue and profitability are overstated by whatever the open balance is.

What proper deposit accounting looks like

For restaurant clients with private dining or catering programs, we set up a Customer Deposits liability account at the start of the engagement and build the deposit register into the monthly close process.

Every deposit received posts to the liability account, not to revenue. The deposit register tracks each booking by customer name, event date, deposit amount, and status. At month-end, we reconcile the register against the event calendar. Deposits for events that have been served move from the liability account to event revenue. Deposits for future events remain on the balance sheet until those events occur.

The P&L only shows catering revenue when an event has been delivered. The balance sheet always shows the current total of deposits held on behalf of customers with future reservations.

Best practices for restaurants taking event deposits

A few practices that keep deposit accounting accurate across a busy events calendar:

• Set up a Customer Deposits liability account before the first deposit is recorded. Starting the correct way eliminates months of cleanup later.
• Maintain a deposit register that lists every open deposit by customer, event date, and amount. Update it each time a deposit is received, an event is served, or a refund is issued.
• Record revenue on the day the event is served, not the day the deposit was paid. If an event spans multiple service dates, recognize revenue on each date proportionally.
• Reconcile the deposit register to the event calendar at every month-end close. A mismatch between the two means a deposit was miscategorized or a served event was not cleared from the liability account.
• Review the open deposit balance before any discussion of monthly or annual profitability. A large balance in the liability account means a portion of future revenue has not been earned yet, regardless of how much cash came in.

Three questions worth asking

If you take deposits for private events, three questions to ask whoever manages your books:

1. When a deposit arrives, which account does it post to: a revenue account or a liability account?
2. Can you show a current deposit register listing every open deposit and its matching event date?
3. If a customer canceled today and we owed the deposit back, would the refund reduce our P&L or our balance sheet?

If any of those answers is unclear, the books are likely recording catering deposits as income before they are earned.

Correcting the setup takes one hour. Correcting several months of reports takes considerably longer. If you want a quick review, send one month of event deposits alongside the booking calendar. We will confirm whether the timing is correct and what, if anything, needs to be reclassified.