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

Hotel management software for Nepal

Reservations through night audit to posted revenue, with restaurant charge-to-room and city-ledger billing included.

What we hear

The problems that bring people to us

Hotels usually choose between a foreign property system that does not understand Nepali tax, and a local system with no real folio or night audit. Penahak gives you the hotel operation and posts it into the same ledger your restaurant and shop use.

Occupancy reports and revenue reports disagree

When the property system keeps its own figures and accounting keeps others, the monthly reconciliation never quite closes and neither number is fully trusted.

Guests get billed twice

A checkout that fails halfway — a timeout, a dropped connection — and a retry creates a second invoice for the same stay.

Company and agent balances go uncollected

City ledger kept on a spreadsheet ages quietly until a corporate account is well past its credit limit.

Restaurant charges never reach the folio

Outlet bills written on paper and carried to reception get lost, mistyped, or applied to the wrong room.

A day on Penahak

One chain of documents, start to finish

Each step below creates or references a real document. Nothing is retyped between them, and every figure at the end traces back to the action that caused it.

Read the step-by-step guides

Manager checks arrivals, departures, dirty rooms and open folios Morning
Front desk checks in arrivals: KYC, room, deposit, key count Afternoon
Dinner charged to the room; minibar posted by housekeeping Evening
Night audit posts room charges to folios, clears blockers, closes the business date Night
Checkout settles the balance and posts one sales invoice Morning
Company folio ages on the city ledger until settled Ongoing
Typical setup

The modules most businesses like yours run

A starting point, not a fixed bundle. Add or drop modules once we have seen how you operate.

What changes

What you should expect to be different

Not features — outcomes. If these are not true six months after go-live, something has been configured wrongly and we want to hear about it.

  • One folio produces exactly one invoice, however many times checkout is retried
  • Room nights post to the folio each night and reach the ledger on the check-out invoice (interim bills at month end)
  • City ledger ageing sits in the same receivables figure as every other debtor
  • Housekeeping status genuinely controls what reception can sell
  • The night audit pack shows blockers, waivers and reopen history for review
Reporting

The reports you will live in

Many totals open the document behind them.

  • Occupancy & availability
  • Revenue by room type & rate plan
  • Arrivals & departures
  • City ledger ageing
  • Night audit pack
  • Housekeeping & maintenance status
Compliance

Nepali obligations handled in the core

IRD-ready fiscal invoicing

Fiscal invoice behaviour is built into the sales invoice and POS paths themselves rather than added on top, with IRD synchronisation, VAT customer and vendor summaries, and an audit trail written as you trade rather than reconstructed afterwards.

Nepali fiscal year and dates

Bikram Sambat fiscal-year control, business-date close and dual-date handling throughout documents and reports.

Payment methods

Cash, card, bank transfer, QR and wallet payments are recorded against the bank account you choose. Penahak does not move the money.

English and Nepali

English and Nepali in the accounting, inventory, retail POS, HR and report screens. The hotel, restaurant and CRM screens are in English.

Controlled corrections

With IRD on, saved invoices cannot be changed: they are corrected by returns or same-day cancels. Approved, reconciled and locked documents cannot be edited, and edits are logged.

Role-based security

Granular roles and permissions, sign-in by listed IP addresses, account lock after wrong passwords, user activity logging and account start and end dates.

Getting there

How a go-live actually runs

01

Discovery

We map your outlets, books, stock locations and statutory obligations, and agree what go-live means.

02

Configuration

Chart of accounts, tax and bill terms, document numbering, godowns, roles and payment methods, checked before the first live day.

03

Migration

Masters, opening balances and opening trial imported and reconciled against your closing figures.

04

Training

Role-based sessions for owners, cashiers, front desk, kitchen, storekeepers and accounts, using your own data.

05

Go-live

One full test cycle end to end, then supervised go-live with a support engineer on hand.

06

Aftercare

Ongoing support, new releases, and the help centre’s step-by-step guides.

Help centre

Where your team starts

The guides your staff use after go-live, written from the Penahak screens.

Open the help centre

Built for Hotel, resort & homestay

Book 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.