A hotel and homestay operating module wired directly into Penahak accounting. Hospitality owns operational state; the ERP owns financial truth — so occupancy reports and revenue reports finally agree.
Most hotels run a property system that does not post to their books, then reconcile the two by hand every month and quietly accept that they never quite match. Penahak Hospitality owns the hotel operation but never keeps its own set of books: at checkout, one folio produces exactly one invoice in the central ledger.
Not a feature list — the sequences your team runs day to day.
Everything here works on the same customers, products and books as the rest of Penahak.
These are not integrations between separate products. They are modules on one ledger, one party master and one product catalogue.
Checkout creates one sales invoice per folio with its room nights, charges, service charge and VAT; payments are receipts on the same account, and a city-ledger balance moves by journal.
Outlet bills charge to the room folio, carrying the item, tax and outlet references.
Minibar items charged to a folio leave the minibar store (else the main store) on the guest’s invoice.
Companies and regular guests bill to their own customer accounts in Accounting; walk-ins share the hotel’s guest account.
Many reports open the document behind a row, and export to Excel or PDF.
The same guides your team uses after go-live, written from the Penahak screens.
Choose dates and rooms, let the rate calendar price every night, find or add the guest, and save. Deposits and routing follow.
Make a bookingGive each booked room a real room, register the guests, and open their folio. Not-ready rooms, upgrades and fee waivers ask a manager.
Check in a guestA folio collects everything a guest (or a company, group or event) owes and has paid. At check-out each folio with charges becomes one invoice.
Folios, the guest's billEvery folio of the stay ends at zero, either paid or billed to a company. Then each folio with charges gets one invoice.
Check out a guest and issue the invoiceThe night audit checks the day, posts tonight's room charges, prints the pack and moves the business date to the next day.
Run the night audit and close the dayEach room has a front-office status (vacant or occupied) and a housekeeping status (clean, dirty, pickup, inspected). Check-in looks for a ready room.
Room status and inspectionEach checkout carries a safe-retry reference built from the property, the business date and the stay. If it fails and is retried, the system returns the invoice it already created instead of raising a second one.
Yes: homestay is a property type. A walk-in is a booking saved and checked in at once; ID is asked only when the property requires it.
The folio is reopened as an approved, logged action, and the late charge results in a further document rather than an edit to the original invoice.
The financial engine every other module posts into.
Accounting & FinanceStock truth across every godown, counter and kitchen.
Inventory & StockQuotation to invoice to settlement, with nothing falling between.
Sales & PurchaseA counter that keeps selling, then reconciles to the rupee.
Retail POSBook a walkthrough and we will demo the modules that match how you actually trade — not a generic slide deck.
No obligation. Typically 30–45 minutes.
