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 billing with CRM ticketing, staff attendance, payroll and elected-member pay runs.
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.
Attendance collected on paper and typed up at month end makes payroll slow, disputed and impossible to audit.
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.
Leave, advances and expenses approved verbally leave nothing behind when the decision is later questioned.
Institutions with elected office-holders need a separate pay structure, which general payroll products do not accommodate.
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.
A starting point, not a fixed bundle. Add or drop modules once we have seen how you operate.
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.
Employee lifecycle, attendance, leave and payroll in one chain — payroll runs off real attendance, and the result posts straight into accounting.
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.
A dedicated reporting server with drill-down to source documents, scheduled generation and dashboard widgets — plus the statutory reports Nepali businesses are actually asked for.
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.
Every total drills down to the source document behind it.
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.
Bikram Sambat fiscal-year control, business-date close and dual-date handling throughout documents and reports.
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.
Interface translations and a localisation layer in both the web application and the reporting engine.
Every posting command carries an idempotency key. Corrections go through approved reversal or credit paths; posted truth is never edited in place.
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.
We map your outlets, books, stock locations and statutory obligations, and agree what go-live means.
Chart of accounts, tax and bill terms, document numbering, godowns, roles and payment providers, all checked against the setup gates before anything posts.
Masters, opening balances and opening trial imported and reconciled against your closing figures.
Role-based sessions for owners, cashiers, front desk, kitchen, storekeepers and accounts, using your own data.
One full test cycle end to end, then supervised go-live with a support engineer on hand.
Ongoing support, statutory updates, new-release rollout and periodic health checks.
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.