Skip to content
Penahak now runs hotels, restaurants and retail on one ledger.
Penahak

How a check moves from the table to the books

One picture of the whole job, and where each setting lives: on the restaurant screens, in Accounting, in Administration.

The journey of a check

A check is a table's open account. It lives from the moment you open the table until it is paid, charged to a room, or closed.

  1. Open the table
    Where
    Floor Plan > an available table > Open Table
    What changes
    The table becomes Occupied and the check opens with the guests, the order type and the waiter.
  2. Take the order and send it to the kitchen
    Who
    Waiter
    Where
    The table's order screen > Send KOT / BOT
    What changes
    The kitchen ticket (KOT) prints at the kitchen or bar stations and shows on the Kitchen Display.
  3. Kitchen prepares and marks dishes done
    Who
    Kitchen
    Where
    Kitchen Display; the Pass Board for pick-up
    What changes
    Each item moves from Pending to Done and then Served. The waiter sees "Food Ready for Pick-up".
  4. Bill and take payment
    Who
    Cashier or waiter
    Where
    The Bill panel > Confirm Payment
    What changes
    The bill is posted, the receipt prints, and the table becomes Needs Cleaning.
  5. Clean the table
    Who
    Waiter
    Where
    Floor Plan > the table > Mark Available
    What changes
    The table can be opened again.
  6. Close the shift
    Who
    Cashier
    Where
    Cash Shift > Close Shift
    What changes
    The cash drawer is counted against what the shift's bills say it should hold.

Where each setting lives

Most of the Restaurant POS is set up in the restaurant's own screens. A few things that decide the money live in Penahak Accounting, because the bill is an Accounting document.

WhatWhereUsed for
Floors, tablesConfiguration › FloorsThe floor plan
Stations and their product groupsConfiguration › StationsWhich kitchen or bar gets each dish
Modifiers, courses, combosConfiguration › Modifiers, Courses, CombosOptions on a dish, labels, combo meals
RecipesRecipeeWhat a dish takes out of stock
Order defaults, KOT prefix, void rule, printingConfiguration › SettingsHow the screens behave
The menu itself: names, prices, VAT, product groups, picturesAccounting > ProductsEvery dish is a product
VAT, service charge, discount and round-offAccounting > Bill TermsThe lines under the subtotal of every bill
Bill numbering, default bank, cash book, the branch's default storeAccounting > Configuration, document numbering, and the branch's storeThe invoice number, the ledgers, where stock leaves from
Users, roles, secret keyAdministration > Users, and the user's settingsWho can do what

Common questions

Is the restaurant a separate program from Accounting?

No. It is a module of the same product and the same company. The bill is an invoice in Accounting the moment it is posted.

Who changes a dish's price?

Whoever maintains products in Accounting. The menu on the Restaurant POS is read from the products: there is no second price list.

Can I use the Restaurant POS without a kitchen screen?

Yes. The Kitchen Display is optional. Tickets can print at the stations instead, or the kitchen can work from the printed ticket alone: see Printers for kitchen tickets and bills.

When does stock leave the store: when the order is sent or when it is paid?

When the bill is posted. Sending a KOT or voiding a dish does not touch the stock (What leaves stock when a bill is posted).

Related guides