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

ERP for services and institutions in Nepal

Service billing with CRM ticketing, staff attendance, payroll and elected-member pay runs.

What we hear

The problems that bring people to us

For a service business or an institution, the cost base is people and the revenue is time and agreements. Penahak links attendance to payroll to the ledger, and keeps service issues attached to the documents that caused them.

Payroll is built on a spreadsheet of hours

Attendance collected on paper and typed up at month end makes payroll slow, disputed and impossible to audit.

Service issues live in inboxes

A complaint about an invoice sits in one person’s email, so the next person to look at that invoice has no idea why it is unpaid.

Approvals have no trail

Leave, advances and expenses approved verbally leave nothing behind when the decision is later questioned.

Elected members are handled differently

Institutions with elected office-holders need a separate pay structure, which general payroll products do not accommodate.

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

Attendance recorded against shifts; lateness tracked Daily
Leave and advance requests routed through approval chains Daily
Service tickets raised against the invoice or receipt concerned Ongoing
Service invoices raised and settled Billing
Pay run generated from real attendance, reviewed and posted Month end
Payroll register and attendance summary reviewed Month end
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.

  • Payroll derives from attendance captured as it happened
  • Approvals for leave, advances and loans leave an auditable trail
  • Service issues stay attached to the document that caused them
  • Elected-member pay runs are handled separately from staff payroll
  • Employees self-serve payslips, leave balance and loan position
Reporting

The reports you will live in

Many totals open the document behind them.

  • Payroll register
  • Attendance summary
  • Late entry by month
  • Leave balance & requests
  • Ticket ageing & resolution
  • Loan & advance outstanding
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 Services & institutions

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.