Accounting & Finance
The financial engine every other module posts into.
Explore module
Accounting & Finance
Since 2019
Trusted by 1,500+ businesses across Nepal
Run the whole business on one ledger
Penahak is a complete business management platform: accounting, inventory, retail and restaurant POS, hotel PMS, CRM, HR and payroll. Ten modules, one source of financial truth, built for Nepali compliance.
IRD-ready fiscal invoicing · eSewa, Khalti & Fonepay · English & Nepali
Trusted by 1,500+ businesses across Nepal
1,500+
businesses across Nepal
10
integrated modules
150+
built-in reports
2
languages: English & Nepali
The platform
Ten modules. One ledger.
Most businesses end up with a till that does not talk to the books, a hotel system that does not talk to either, and a spreadsheet holding it together. Penahak replaces that with one platform where every module posts into the same accounting core.
Inventory & Stock
Stock truth across every godown, counter and kitchen.
Explore module
Inventory & Stock
Sales & Purchase
Quotation to invoice to settlement, with nothing falling between.
Explore module
Sales & Purchase
Retail POS
A counter that keeps selling, then reconciles to the rupee.
Explore module
Retail POS
Restaurant POS
Floor, kitchen and bar working off the same order.
Explore module
Restaurant POS
Hospitality & Hotel PMS
Front desk to night audit to posted revenue.
Explore module
Hospitality & Hotel PMS
CRM
Accounting-native CRM. It knows what the customer owes you.
Explore module
CRM
HR, Attendance & Payroll
From the shift roster to the posted salary journal.
Explore module
HR, Attendance & Payroll
Production
Bill of materials in, costed finished goods out.
Explore module
Production
Reports & Analytics
Over 150 reports, and every figure traces to a document.
Explore module
Reports & Analytics
Why it matters
A guest orders dinner. Watch where the money goes.
In most setups this is four systems and three manual re-entries. In Penahak it is one chain of documents, each one referencing the last, ending in a posted invoice that reconciles to the rupee.
- No duplicate entry between the outlet, the front desk and accounts
- Stock for the ingredients moves as the order is served
- Retrying a failed checkout returns the same invoice, never a second one
- Every line traces back to the person and the terminal that created it
Order taken at the table
Kitchen ticket routed to the station
Charged to the guest room folio
Ingredients issued from stock
Night audit posts the room charge
Checkout posts one SalesBill
One ledger
Ten modules, one set of books
Every module writes into the same accounting core. There is nothing to reconcile between them, because there is only one set of records.
How we are different
The problems we solve differently
Most Nepali businesses replace a familiar setup when they move to Penahak. These are the specific things we do differently, and why it matters once you are live.
Not locked to one computer
How it usually works
Accounting sits on a single desktop in the back office. The owner cannot see today’s numbers from anywhere else, a second branch means a second disconnected copy, and the backup is whatever someone remembered to take.
With Penahak
One cloud tenant with branch-level books and consolidated reporting. The same application runs in a browser, or as a desktop app where thermal printing is needed. Backups and updates are handled on the platform.
Posted figures cannot be quietly edited
How it usually works
Many systems let a user reopen and change a posted voucher. It is convenient, and it means last month’s reported profit can change without anyone knowing — which is exactly what an auditor is looking for.
With Penahak
Posted documents are immutable. Corrections go through credit notes, debit notes or reversing journals, each recorded with the approving user, the reason and the original document. The trail is complete by construction.
The till and the books are one system
How it usually works
POS is a separate product that exports a daily total into accounting. Someone reconciles the two, the numbers rarely agree exactly, and the difference gets written off as a rounding or shortage entry.
With Penahak
The counter posts source documents straight into the ledger with their tax and settlement treatment. There is nothing to reconcile between them because there is only one set of records.
Hotels and restaurants are not an afterthought
How it usually works
Hospitality means either a foreign property system priced for a chain and unaware of Nepali tax, or a local system with no real folio, night audit or city ledger. Restaurant and hotel usually do not talk to each other at all.
With Penahak
Full folio, night audit, housekeeping and city-ledger handling, with restaurant charge-to-room built in — and checkout posting one invoice into the same ledger your retail counter uses.
Solutions
Configured for how your industry trades
The same platform underneath, set up differently. Pick the closest fit and see the modules, workflows and reports that come with it.
Retail & supermarket
Multi-counter selling with barcode, schemes, loyalty and gift cards, closing each shift with a cash handover that reconciles.
Retail & supermarketRestaurant, café & bar
Floor map service, station-routed kitchen tickets, KDS and cash shifts, with recipe stock consumption behind every plate.
Restaurant, café & barHotel, resort & homestay
Reservations through night audit to posted revenue, with restaurant charge-to-room and city-ledger billing included.
Hotel, resort & homestayWholesale & distribution
Order-to-dispatch with challans, agent commissions, multi-godown stock and receivable ageing that collections can act on.
Wholesale & distributionManufacturing
Bill of materials, raw-material consumption, quality pass and finished-goods costing that flows into real inventory value.
ManufacturingServices & institutions
Service billing with CRM ticketing, staff attendance, payroll and elected-member pay runs.
Services & institutions
Built differently
The parts nobody demos, that decide whether you trust the numbers
Any ERP can show you a dashboard. These are the design decisions that determine whether the dashboard is still right in eighteen months.
One source of financial truth
POS, hospitality, payroll and production do not keep their own books. Every module posts into the same ledger, so operational reports and financial reports cannot drift apart.
Idempotent by design
Checkout, night audit, payment callbacks and stock issues all carry stable idempotency keys. Retry a failed posting and you get the same document reference back, never a duplicate.
Printing that survives reality
Kitchen and receipt printing runs through durable job queues and a local bridge with retry. A printer that dies mid-service does not silently lose a ticket.
Auditable end to end
Every figure drills down to a source document ID, and every correction leaves a reversal trail with the approving user and reason attached.
Built for Nepal
Bikram Sambat fiscal years, IRD-ready fiscal invoicing, VAT and TDS handling, and native eSewa, Khalti and Fonepay support.
Setup gates, not surprises
Stage-based configuration checks block posting until ledgers, tax terms and numbering are mapped, so nothing lands in the wrong account on day one.
Platform
One application, wherever the work happens
Back office in the browser, the counter on a desktop with real thermal printing, and a handheld in the aisle — all the same application and the same ledger.
Web application
The full ERP in the browser — a React progressive web app on a .NET service layer. Works on any modern desktop, with no install and no per-machine upgrade.
Desktop app & print bridge
An Electron application for Windows, macOS and Linux that pairs the same interface with a local bridge service. The bridge polls for durable print jobs and drives thermal printers directly, so receipts and kitchen tickets never depend on a browser dialog.
Reporting server
A dedicated reporting service renders the statutory pack and every operational report, print-ready and exportable, with materialised views behind the heavy summaries.
Multi-tenant & multi-branch
Tenant, company, branch and licence management with per-tenant database scripts, module entitlements, report formats and SMS gateway configuration.
Background job server
A dedicated job server handles night audit, scheduled posting, notification delivery and report generation without blocking the people using the application.
Security & deployment
Role-based access control, IP address whitelisting and two-factor authentication, with user activity logging, time-based account start and expiry, and automatic plus manual backup and restore.
Notifications & SMS
Common and custom notification templates with an SMS gateway layer for booking confirmations, payment receipts, payslips and approval alerts.
Compliance
Made for Nepali books, not translated into them
Fiscal years, tax treatment, payment rails and audit expectations are built into the core rather than bolted on as a regional add-on.
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.
Implementation
How a go-live actually runs
We do not hand over a login and wish you luck. Configuration is verified against setup gates before anything posts, and your opening balances are reconciled before you trade on it.
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.
Questions
The things people ask first
Yes. Modules are licensed per tenant, so you can begin with the counter or the books and switch the rest on later. Because everything shares one ledger and one party master, adding a module later does not mean migrating your data again.
The desktop application keeps printing from the local bridge and queues durable print jobs, so service continues. Posting resumes automatically once connectivity returns, and idempotency keys make sure nothing is duplicated in the process.
Fiscal invoice behaviour, VAT summaries, audit trail and IRD sync are built into the central SalesBill and POS paths. Configuration is verified against your registration during onboarding.
Yes. Tenant, company and branch structures are first-class, each with their own books, document numbering, report formats and licence entitlements, plus consolidated reporting across them.
See Penahak on your own numbers
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.