Skip to main content
Skip table of contents

Triggers of a Suspicious Transaction

Overview

Suspicious Transactions allow GMs/Owners/Chef users to view transactions that aren’t on the expected path of the order cycle and may be suspicious.

Transactions with suspicious actions, such as voids performed after a payment has been made on the check, very large tip percentages, and more, are flagged and added to a Report with information about the Order’s owner, who performed the suspicious action, Order descriptions, reason it was flagged, and more.

Orders flagged under Suspicious Transactions are Orders that MAY require more scrutiny and do not automatically mean that fraud has taken place

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. Item/s in the Order

  2. Order has been billed

  3. All Items added before billed time

  4. Change/s between billed time and last payment time

  5. Seated Order

  6. At least one cash payment

Why is it suspicious?

When a payment is made in cash the actual payment time is uncertain.

The Server/Manager possibly:

  1. Made a fictitious change after printing the bill

  2. Falsified the timing and amount of the cash payment to pocket a portion of the actual cash amount paid by the customer

Example

  1. 7:00 pm - Order opens

  2. 8:00 pm - Bill of $50 given to customer

  3. 8:05 pm - Customer leaves exactly $50 cash and leaves the restaurant

  4. 8:07 pm - Server/Manager cancels an item for $10

    • Amount owed reduces to $40

  5. 8:08 pm - Server/Manager enters that the customer paid $40 and closes the order

    • Server/Manager pockets $10 cash

Cash refunds after a bill has been fully paid

What triggers it?

  1. Item/s in the Order

  2. Order has last payment

  3. All Items added before last payment time

  4. Change/s between after last payment time

  5. Inward payment/s (non-refund)

  6. Last payment is cash refund

Why is it suspicious?

It's very unusual for there to be changes to the bill after a customer pays.

Server/Manager may have:

  1. Made a fictitious change after the last payment time

  2. This would cause the PAD to initiate a refund to balance

  3. Selected cash for the refund type to pocket the refund amount in cash

Example

  1. 7:00 pm - Order opens

  2. 8:00 pm - Bill of $50 given to customer

  3. 8:05 pm - Customer hands the Server their credit card for exactly $50, ex: no tip

  4. 8:05 pm - Server charges the credit card for $50

  5. 8:05 pm - Server returns the credit card to the customer

  6. 8:06 pm - Server/Manager cancels an Item for $10

    • Amount owed reduces to $40

    • Refund of $10 initiated to balance

  7. 8:06 pm - Server/Manager selects cash for the refund type

    • Server/Manager pockets $10 cash

  8. Amount owed reduces to $40

  9. 8:07 pm - Order is closed

Items transferred to an employee table

What triggers it?

Item/s transferred to a table tagged employee

Why is it suspicious?

Tables tagged for employees usually have a lot of Items ordered on them every day

Server/Manager may have:

  • Transferred Items from a friend's table to an employee table for a price, where this price is less than the actual price of the Items ordered

  • The friend then pays the Server/Manager off the record and the Server/Manager keeps the payment for themselves

  • The restaurant may not notice a few additional Items at an employee table

Example

  1. 7:00 pm - Order opens

  2. 7:05 pm - Friend orders dinner to the value of $50 total

  3. 7:50 pm - Friend finishes eating

  4. 7:55 pm - Items with a price of $25 transferred to an employee table

    • Amount owed at friend's table reduces to $25

  5. 8:00 pm - Bill of $25 given to friend

  6. 8:05 pm - $25 charged on friend's credit card

  7. 8:06 pm - Order is closed

  8. 8:10 pm - Friend pays $5 to Server/Manager

    • Server/Manager pockets $5 cash

    • Restaurant loses $25 in revenue

Tip percentage on the entire Order exceeds a set threshold

What triggers it?

Total tips on an Order are higher than the threshold of an Order of that amount

Why is it suspicious?

Particularly high tips on an Order could indicate that a Server/Manager has been rewarded for favors to the customer at the restaurant's expense.

Server/Manager may have:

  • Changed a familiar customer's bill in return for an excessive tip amount

Example

  1. 7:00 pm - Order opens

  2. 7:05 pm - Customer orders dinner to the value of $100 total

  3. 7:50 pm - Server/Manager applies a discount of 70% with the tag VIP

  4. 7:55 pm - Bill for $30 given to customer

  5. 8:00 pm - $80 charged on credit card

    • $30 for the discounted bill

    • $50 as tip

    • Tip is 167% of the Order amount

    • Sever/Manage pockets undue tips at the restaurant's expense

  6. 8:01 pm - Order is closed

Tip percentage on a payment exceeds a set threshold

What triggers it?

Tip percentage on a payment is higher than the threshold

Why is it suspicious?

Particularly high tips on a payment could indicate that a Server/Manager has been rewarded for favors to the customer at the restaurant's expense.

Server/Manager may have:

  • Changed a familiar customer's bill in return for an excessive tip amount

Example

  1. 7:00 pm - Order opens for a table of 2 diners

  2. 7:05 pm - Customer order dinner to the value of $50 each, $100 total

  3. 7:50 pm - Server/Manager applies a discount of $30 to the customer 1's order with the tag VIP

  4. 7:55 pm - Bill for $20 and $50 given to customer 1 and 2 respectively

  5. 8:00 pm - $50 charged on each customers' credit card

    • $20 for the discounted bill for customer 1

    • $30 as tip for the payment of customer 1

    • Tip is 150% of the Order amount

    • Sever/Manage pockets undue tips at the restaurant's expense

  6. 8:01 pm - Order is closed

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close