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

Services & institutions

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 agreement 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

Every total drills down to the source document behind it.

  • 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

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.

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.