Checkout is where hospitality hands over to accounting. It is the most carefully controlled operation in the module.
The flow
- Open the folio and review the charges with the guest.
- Apply any final adjustments through the proper void, comp or adjustment path.
- Take the balance: cash, card, bank, QR, wallet, or leave it on the city ledger for a company to settle.
- Confirm checkout.
What happens on confirm
Penahak builds a single idempotent checkout command and creates one central SalesBill carrying tax, service charge, discount, payment, city-ledger and round-off lines. The folio then locks with that SalesBill voucher ID attached.
Idempotency
If checkout fails partway — a network drop, a payment gateway timeout — retrying returns the existing reference rather than creating a second invoice. This is the single most valuable guarantee in the module: you cannot accidentally double-bill a guest by clicking twice.
Late charges
A charge that arrives after checkout requires the folio to be reopened, which is an approved and logged action, and results in a further document rather than an edit to the original invoice.
Checking the tie-out
After checkout, the folio shows its SalesBill reference. Accounts can open that document directly from the folio, and the revenue, tax and settlement lines will match. If they do not, the ledger mapping is wrong rather than the arithmetic.
Did this answer your question? If not, our support team can look at your actual configuration.
Contact support