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.
Solution
Hotel, resort & homestay
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.
Guests get billed twice
A checkout that fails halfway — a gateway 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.
Manager checks arrivals, departures, dirty rooms and open folios
Front desk checks in arrivals: KYC, room, deposit, key count
Dinner charged to the room; minibar posted by housekeeping
Night audit posts room charges, clears blockers, closes the business date
Checkout settles the balance and posts one SalesBill
Company folio ages on the city ledger until settled
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.
Hospitality & Hotel PMS
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.
- Room types, rooms, floors, features, images and operational status
- Reservations, walk-ins, group bookings, tape chart and room moves
- Check-in with guest KYC, deposits, key count and registration card
- Room rack shared by front office and housekeeping
Explore module
Hospitality & Hotel PMS
Restaurant POS
Table service built around a floor map, station-routed kitchen tickets and durable print jobs that survive a printer going offline mid-service.
- Interactive floor map and floor-plan editor with table sessions
- Order panel and bill panel built for fast, repeated service
- Kitchen Display System (KDS) and pass display for expo
- Customer-facing display (CFD) at the counter
Explore module
Restaurant POS
CRM
Not a separate contact database bolted on beside your books. Penahak CRM reads live ERP signals — balances, disputes, deliveries, returns — so every screen tells someone what to do next.
- Leads, opportunities and quotations with pipeline stages
- Customers and contacts drawn from the same party master as accounting
- Activities, follow-ups and an operator work queue with clear ownership
- Support tickets tied to the invoice, delivery or product that caused them
Explore module
CRM
Accounting & Finance
A double-entry core with a real chart of accounts, cost centres, fiscal-year control and immutable posting. Every sale, folio, payroll run and stock movement in Penahak resolves to a source document here.
- Chart of accounts with multi-level groups, sub-ledgers and general-ledger IDs
- Journal, day book, receipts, payments, contra and cash/bank vouchers
- Credit notes, debit notes and approved reversal paths — posted documents are never edited in place
- Cost centres, classes, areas, agents and user-defined fields for dimensional reporting
Explore module
Accounting & Finance
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 revenue, tax and service charge post to the ledger the night they are earned
- 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
Every total drills down to the source document behind it.
Compliance
Nepali obligations handled in the core
IRD-ready fiscal invoicing
IRD-approved, with fiscal invoice behaviour in the central SalesBill and POS paths, IRD sync, VAT customer and vendor summaries, and an audit trail built for inspection rather than reconstructed after the fact.
Nepali fiscal year and dates
Bikram Sambat fiscal-year control, business-date close and dual-date handling throughout documents and reports.
Local payment providers
eSewa, Khalti, Fonepay, card, bank, QR and wallet adapters, with verification evidence required before a provider goes live. Cash stays simple: no merchant ID, no callback URL.
English and Nepali
Interface translations and a localisation layer in both the web application and the reporting engine.
Immutable audit trail
Every posting command carries an idempotency key. Corrections go through approved reversal or credit paths; posted truth is never edited in place.
Role-based security
Granular roles and permissions, IP address whitelisting, two-factor authentication, user activity logging, time-based account expiry, and stage-based setup gates that block posting until configuration is safe.
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 providers, all checked against the setup gates before anything posts.
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, statutory updates, new-release rollout and periodic health checks.
Other industries
Not quite your business?
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.