Triggers of a Suspicious Transaction

Overview

GMs, owners, and Chef users can review Suspicious Transactions to identify orders that depart from the expected order cycle.

The report flags actions such as post-payment voids and unusually large tip percentages. It includes the owner, acting user, order details, and reason for the flag.

A flag is a reason to investigate; it does not establish that fraud occurred.

Learn about the six different triggers that flag an Order as possibly having a Suspicious Transaction below:

Changes to the bill after it is printed with at least one cash payment

What Triggers it?
  1. The order contains items.

  2. A bill has been issued.

  3. Every item was entered before the bill was issued.

  4. The order changed between billing and the last payment.

  5. The order is seated.

  6. At least one payment is cash.

Why is it suspicious?

Cash entry does not establish exactly when the customer handed over the money.

One possible explanation to investigate:

  1. An employee altered the order after printing the bill.

  2. They could have entered a lower cash amount or different payment time and retained part of what the customer paid.

Example
  1. 7:00 pm - Order opens

  2. 8:00 pm: The customer receives a $50 bill.

  3. 8:05 pm: The customer leaves $50 in cash and departs.

  4. 8:07 pm: An employee cancels a $10 item.

    • The recorded balance falls to $40.

  5. 8:08 pm: The employee records $40 cash and closes the order.

    • The remaining $10 cash is retained by the employee in this example.

Cash refunds after a bill has been fully paid

What triggers it?
  1. The order contains items.

  2. A final payment is recorded.

  3. Every item was entered before that payment.

  4. The order changed after the last payment.

  5. The order includes non-refund payments.

  6. The final payment is a cash refund.

Why is it suspicious?

Changes after a customer has paid warrant review.

One possible sequence is:

  1. An employee changes the order after the final payment.

  2. The lower balance causes the PAD to initiate a refund.

  3. Selecting cash could allow the employee to retain that refund.

Example
  1. 7:00 pm - Order opens

  2. 8:00 pm: A $50 bill is presented.

  3. 8:05 pm: The customer provides a card to pay $50 with no tip.

  4. 8:05 pm: The card is charged $50.

  5. 8:05 pm: The card is returned.

  6. 8:06 pm: An employee cancels a $10 item.

    • The balance becomes $40.

    • A $10 refund is initiated to balance the order.

  7. 8:06 pm: The employee chooses a cash refund.

    • In this example, the employee retains the $10 cash.

  8. The order's remaining charge is $40.

  9. 8:07 pm - Order is closed

Items transferred to an employee table

What triggers it?

Items move to a table tagged employee.

Why is it suspicious?

Employee-tagged tables commonly contain many items during the day.

A possible misuse to investigate:

  • An employee moves a friend's items to an employee table in exchange for an off-record payment below their menu value.

  • The friend pays the employee directly, outside the restaurant's records.

  • The extra items may be harder to notice among normal employee-table activity.

Example
  1. 7:00 pm - Order opens

  2. 7:05 pm: A friend orders $50 of food.

  3. 7:50 pm: The meal is finished.

  4. 7:55 pm: $25 of items moves to an employee table.

    • The friend's balance falls to $25.

  5. 8:00 pm: A $25 bill is presented.

  6. 8:05 pm: The friend's card is charged $25.

  7. 8:06 pm - Order is closed

  8. 8:10 pm: The friend gives the employee $5.

    • The employee keeps that $5 cash.

    • The restaurant has lost $25 of sales in this example.

Tip percentage on the entire Order exceeds a set threshold

What triggers it?

The total tip exceeds the threshold for an order of that value.

Why is it suspicious?

An unusually high tip can be a reason to check whether an employee gave an unauthorized benefit at the restaurant's expense.

One possible explanation:

  • An employee reduces a familiar customer's bill in exchange for a larger tip.

Example
  1. 7:00 pm - Order opens

  2. 7:05 pm: The customer orders $100 of food.

  3. 7:50 pm: The employee applies a 70% VIP discount.

  4. 7:55 pm: A $30 bill is presented.

  5. 8:00 pm: The card is charged $80.

    • The payment covers the $30 discounted bill.

    • The other $50 is a tip.

    • That tip is 167% of the order value.

    • The example illustrates an employee receiving an inflated tip at the restaurant's expense.

  6. 8:01 pm - Order is closed

Tip percentage on a payment exceeds a set threshold

What triggers it?

An individual payment's tip percentage exceeds the configured threshold.

Why is it suspicious?

A high tip on one payment can also warrant review for an unauthorized benefit.

One possible explanation:

  • An employee reduces a familiar customer's bill in exchange for a larger tip.

Example
  1. 7:00 pm: An order opens for two guests.

  2. 7:05 pm: Each guest orders $50, totaling $100.

  3. 7:50 pm: The employee applies a $30 VIP discount to guest 1.

  4. 7:55 pm: Guests 1 and 2 receive bills of $20 and $50 respectively.

  5. 8:00 pm: Each guest's card is charged $50.

    • Guest 1's payment covers the $20 bill.

    • The remaining $30 is a tip on guest 1's payment.

    • The $30 tip is 150% of guest 1's discounted $20 bill ($30 ÷ $20 × 100). This example concerns the tip percentage on that guest's payment, rather than the total order.

    • The example illustrates an employee receiving an inflated tip at the restaurant's expense.

  6. 8:01 pm - Order is closed