What is a void, and why it must be recorded

A manager notices that the bar's takings are lower than its busy nights suggest. The stock count shows more spirits used than the till recorded. Looking through the till's history, she finds a pattern: rounds of drinks rung up, then voided after the guests had paid in cash, always on the same shift. Without a record of every void, with its time and the person who made it, she would never have found it.

What is a void? In a restaurant or bar, a void cancels an item, or a whole bill, before it is paid, so that the guest is not charged for it. Voids are a normal part of every service: a server presses the wrong key, a guest changes their mind, the kitchen cannot make a dish. They are also the most common way for money to disappear from a till, which is why every one must be recorded.

This guide covers what a void is, the three legitimate reasons for one, how voids differ from comps and refunds, what belongs in the audit trail, the patterns that point to problems and how to review voids each week without treating the team as suspects. Every venue and figure in it is an example.

A void removes an item from a bill before payment, as if it had never been charged. The record of the void stays, showing what was voided, when, by whom and why, but the guest does not pay for the item.

A void can apply to a single item, several items or a whole bill. It is used when the charge should never have been there, not when the venue decides to give something away.

The most common reason for a void is a mistake when the order was entered: the wrong dish, the wrong quantity, the wrong table or a dish entered twice. The server notices, or the guest does, and the item is voided and, if needed, entered again correctly.

Mistakes at entry are normal, and a quick void is the right fix. A high number of them may point to a till that is hard to use, a menu layout that invites the wrong key or a new member of staff who needs more training.

The second reason is a dish the kitchen cannot make after it was ordered: it has run out, an ingredient is missing or a piece of equipment has failed. The dish is voided, and the guest is offered something else.

These voids are a sign that the 86 did not reach the server in time. Our guide to what 86 means in a kitchen, and why covers how to make sure dishes that have run out stop being ordered.

The third reason is a guest who changes their mind before the dish is made: they cancel a course, swap a dish or decide they ordered too much. If the kitchen has not started the dish, the void costs nothing but a moment.

Once the kitchen has started, the decision is different. A dish already cooked and then cancelled is a cost to the venue, and whether it is voided or charged is a matter for the venue's policy and the manager's judgement.

Comps and voids are different, and the records should keep them apart. A void says the charge should never have existed: a mistake, a dish never made, an order cancelled. A comp says the item was served and the venue chose not to charge for it, for a reason.

A dish sent back because it was wrong, then remade and served, is not a void of the first dish; it is a remake, and the venue may comp the first if the guest was inconvenienced. Our guide to what a comp is, and who should approve it covers the other side.

Voids and refunds are different too. A void happens before payment; a refund returns money after payment. Once a bill is paid, removing an item is no longer a void: it is a refund, and it should be handled as one, with its own record and approval.

Keep the line clear. A till that lets staff void items after a bill has been paid makes it possible to take cash and then erase the sale, which is exactly what the manager in the opening found.

Every void must be recorded because a void removes a sale from the till's total. Without a record, a voided sale is indistinguishable from a sale that never happened, and the venue cannot tell honest corrections from money that has gone missing.

The record also protects the team. When a void is questioned, a record showing the time, the reason and the person makes it easy to explain. Without one, suspicion falls on whoever happened to be working.

The audit trail is the record of every change to an order: who entered each item, when, who voided it, when and why. A good audit trail cannot be edited after the fact, and every entry is linked to the person who made it.

For the trail to mean anything, each person must use their own sign-in on the till. A till where everyone uses the same login, or where a manager's card is left in the machine all night, records actions without knowing who took them.

Ask for a reason with every void, from a short list: entered by mistake, not made, guest changed their mind, other. A reason makes the review possible: a month of voids "entered by mistake" tells a different story from a month of "guest changed their mind".

Keep the list short so the reason is quick to choose. A void process that takes a minute will be skipped on a busy night; one that takes two seconds will be used every time.

Decide who can void, and when. Many venues let servers void items before they are sent to the kitchen, and ask for a manager's approval once the kitchen has started or for a whole bill. Others let anyone void but review every void the next day.

Whichever rule the venue chooses, apply it consistently. A rule that changes with who is on shift is no rule at all.

Review voids each week, looking for patterns rather than single events. Voids concentrated on one person's shifts; voids made after a bill was printed; voids of items that were clearly served, such as drinks at the bar; voids clustered at the end of a shift; a rising number of voids week after week.

Each pattern has an innocent explanation as often as not: a new server, a difficult till layout, a menu change. The review is about finding the explanation, not assuming the worst.

Till fraud is rare in most venues, but voids are where it most often hides. The classic pattern is a sale rung up, paid in cash, then voided, with the cash kept. Others include voiding items from a bill before printing it for the guest and charging the full amount anyway.

Our guide to till fraud: the six patterns worth watching covers the signs. The best defence is a till that refuses voids after payment, an audit trail linked to each person and a weekly review everyone knows about.

A void after a dish has been sent to the kitchen should tell the kitchen to stop. A kitchen that keeps cooking a voided dish wastes food and time, and may send it to the wrong table.

Make sure the void reaches the kitchen at once, on the ticket or the screen. The cooks should see that the dish has been cancelled, not discover it when the server refuses to take it.

Voids and the stock count are linked. A dish voided after it was made used stock that the till shows as unsold. A drink voided after it was poured did the same. If those voids are not recorded with their reasons, the stock count shows a loss that nobody can explain.

When the stock count shows a variance, look at the voids for the same period. Often, part of the answer is there.

Train every member of the team on voids: what a void is, when to use one, how to record the reason, when to ask a manager and why the records matter. Explain that the records protect them as well as the venue.

A team that understands voids uses them correctly and without embarrassment. One that thinks every void is a mark against them may hide mistakes instead of correcting them.

The weekly review should feel routine, not like an investigation. Share the totals with the team, thank them for accurate records and talk about patterns that point to fixable problems, such as a confusing till layout.

When a pattern does need a conversation, have it privately and calmly, with the records. Most of the time, the explanation is simple, and the conversation ends with a fix rather than a dispute.

The same principle, that events must be recorded rather than assumed, applies across the venue. A no-show must be marked as a no-show, a walk-in recorded as a walk-in and a void recorded as a void. Our guide to what a no-show is, and when it counts applies the same idea to the diary.

A venue that records what really happened can explain its own figures. One that relies on memory cannot.

Voids rise on busy nights, when servers are rushed and mistakes are easy. That is normal, and the review should expect it. A Friday with twice the voids of a Tuesday, on twice the orders, is not a problem.

Compare voids with the number of orders, not just in total. A void rate that stays steady as the venue gets busier shows the team coping well; one that jumps on busy nights may point to a till that is hard to use under pressure.

When a guest says they did not order an item, or did not receive it, the manager has to decide quickly. If the item was never served, a void is right. If it was served and the guest is unhappy with it, a comp may be right instead.

Check the order history before deciding: when the item was entered, by whom and whether it reached the kitchen. A clear record turns a difficult conversation into a simple one.

Voids made at the end of the night, after the last orders, deserve a second look. Most are honest: tidying up an open check, removing a drink that was never poured. But the end of a shift is also when a void is least likely to be noticed.

Review end-of-shift voids as their own group in the weekly review. If they are rare and explained, there is nothing to worry about; if they are frequent, ask why.

New members of the team make more voids, because they are learning the till and the menu. That is expected, and their voids are a guide to where they need more training.

Look at a new person's voids with them in their first weeks, kindly. A pattern of the same mistake points to a single thing to teach, and the voids fall quickly after.

A void after the kitchen has cooked a dish is not free: the food has been used, and the stock count will show it. If the dish cannot be served to someone else, it is waste.

Record these voids with their reason, and count their cost. A venue that knows how many dishes are cooked and then voided each week can see whether its order process, its kitchen communication or its guests' changes of mind are the cause.

The best way to keep voids low is to prevent the mistakes behind them: a till laid out so the right key is easy to find, a menu the team knows well, orders read back to the guest and 86s that reach every server at once.

Fewer voids mean fewer awkward moments, less waste and records that are easier to read. The aim is not to stop voids, but to make every one of them necessary.

Before printing a bill for the guest, check that any voids are correct: the voided items removed, nothing voided that the guest received and nothing left that should have gone. A bill that is wrong at the table is far harder to fix than one checked before it arrived.

Make the check a habit for the server: a quick look at the check against the table before bringing the bill.

When a party moves table, or two checks are merged, items can end up on the wrong check, and voids follow as the server tries to correct it. Move checks with the till's own tools rather than voiding and re-entering items.

A check moved properly keeps its history; one rebuilt by voiding and re-entering leaves a confusing trail and more chances for mistakes.

Look at voids by item as well as by person. A dish that is voided far more than others may be confusingly named, placed next to a similar dish on the till or often unavailable. The fix may be a change to the menu or the till layout, not to anyone's behaviour.

The item view often explains patterns that the person view cannot.

Tell the team that voids are reviewed every week, and why: to find mistakes that can be prevented and to protect everyone from suspicion. A review the team knows about deters dishonesty and encourages honest records.

Share what the review finds and what changed as a result. A team that sees the review leading to a better till layout or clearer menu names trusts it.

An invented bar notices that its takings are lower than its busy nights suggest, and its stock count shows more spirits used than the till recorded. It moves every bartender to their own sign-in, asks for a reason with every void and sets the till so that nothing can be voided after a bill is paid.

The first weekly review shows most voids are honest mistakes at entry, concentrated on a new bartender, who is given more training on the till. It also shows a cluster of drink voids at the end of one late shift; a private conversation with the records follows. Within a month, voids fall by half and the stock variance closes.

In servearound, a line or a whole check can be voided on the till with an optional reason. The voided line stays on the check, struck through, and the kitchen is told to stop, and each void raises a notification to the team. On shared screens, each person signs in with their own name and four-digit PIN, so every order, void and change is recorded as theirs until the screen locks. A void on a check that already has a payment recorded is refused, and there is no refund screen for guest bills.

Anyone who can take orders can void: there is no separate permission or manager-approval step. Order analytics show the void rate and the voided checks and their value, and payment analytics show voids and comps by member of staff. See point of sale and kitchen.

Cancelling an item, or a bill, before payment, so the guest is not charged.

A mistake at entry, a dish the kitchen cannot make and a guest who changes their mind before it is made.

A void says the charge should never have existed; a comp says the item was served and given free.

A void is before payment; a refund returns money after it.

Because a void removes a sale, and only the record shows whether it was honest.

The record of every change to an order, with who made it and when.

Voids concentrated on one person, after bills are printed or paid, at the end of shifts, or rising every week.

Every week, routinely and without suspicion.

What is a void? It cancels an item or a bill before payment. The three legitimate reasons are a mistake at entry, a dish the kitchen cannot make and a guest who changes their mind before it is made. Keep comps and voids apart, and voids and refunds apart, so the records show what really happened.

Record every void with a reason, give every member of the team their own sign-in so the audit trail means something and refuse voids after payment. Review voids each week for the patterns that point to fixable problems, and the rarer ones that point to till fraud, and compare them with the stock count.