Accounting & Finance
The financial engine every other module posts into.
Explore module
Accounting & Finance
Since 2019
Trusted by 1,500+ businesses across Nepal
Cloud accounting and ERP software built for Nepal
Run the whole business on one ledger.
Penahak connects accounting, inventory, sales, retail and restaurant POS, hotel PMS, CRM, HR, attendance, payroll, production and reporting in one platform — for a single outlet, a growing company or a multi-branch enterprise.
IRD-ready fiscal invoicing · Bikram Sambat fiscal years · VAT & TDS
Trusted by 1,500+ businesses across Nepal
1,500+
businesses across Nepal
10
integrated modules
2019
established in Nepal
2
languages in core screens: 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 works on 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
Statutory and operational 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 leaves once, on the invoice
- 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
Night audit posts the room charge to the folio
Checkout posts one sales invoice
Ingredients leave stock with the invoice
One ledger
Ten modules, one set of books
Every module that sells writes into the same accounting core.
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 company with branch-level documents and company-wide reports. The same application runs in a browser, or as a desktop app where thermal printing is needed. Updates reach every user without installing anything.
Corrections are controlled, not quiet
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
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.
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
Each counter bill is a sales invoice in the same ledger the moment it is saved, with its tax, and its payments follow a moment later. There is one set of records; check cash refunds on returns the same day.
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, sales by agent and area, 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 and payroll post into the same ledger, and production moves stock in the same books, so operational and financial reports read the same records.
A hotel retry never double-charges
Hotel check-out, room-night posting and no-show fees carry a retry key. Press again after a failure and check-out gives back the same invoice; a room night or a fee is never posted twice.
Printing that survives reality
Kitchen tickets are queued on the server and printed by the desktop app next to the printers. A ticket whose printer is off waits and prints when it is back, and any receipt can be reprinted.
Traceable and logged
Many reports open the document behind a row, and edits and approvals are logged with the user.
Built for Nepal
Bikram Sambat fiscal years, AD and BS dates on every document, IRD-ready fiscal invoicing, and VAT and TDS handling.
Setup checks, not surprises
The hotel and the till check their setup before they let you trade, and name what is missing.
Platform
One application, wherever the work happens
Back office in the browser, the counter on a desktop with real thermal printing — the same application, and the same ledger behind both.
Web application
The full system in a modern browser. Nothing to install on each machine, nothing to upgrade desk by desk, and the same books whether you open it from the office, the shop floor or home.
Desktop app & printing
A desktop app for Windows, macOS and Linux, with the same screens plus a printing service that runs on the machine itself. It drives thermal printers directly, so a receipt or kitchen ticket does not depend on a browser print dialogue.
Reporting
The statutory pack and the operational reports come back print-ready and export to Excel or PDF, and many of them open the document behind a row.
Multi-company & multi-branch
Each company has its own database and sign-in address. Within a company, each branch keeps its own documents and numbering, and the company’s reports cover all branches or one.
Scheduled jobs
Scheduled notifications (customer outstanding, cheques due) and IRD sending run by themselves; the hotel’s night audit is a guided close the night auditor runs.
Security & deployment
Role-based access, sign-in limited to listed IP addresses, account lock after repeated wrong passwords, activity logging, account start and end dates, and on-demand backup with download.
Notifications & SMS
Common and custom notification templates, with SMS for invoices, receipts, payroll and leave approvals, and outstanding reminders.
Whatever size you are
One outlet, a growing company, or a group of branches
The same platform underneath. You switch on what you need now, and it is still the right system when the second branch opens.
A single outlet
Start with the counter and the books. Sales post straight into accounting, stock moves as you sell, and your VAT position is a report rather than an evening’s work.
A growing company
Add stock control, purchasing, CRM and payroll as the team grows. Because it is all one ledger, switching on a module later is configuration — not another migration.
A multi-branch group
Branch-level documents and numbering, company-wide reports across the branches, segregation of duties, approvals and an activity log.
Built for Nepal
Compliance in the engine, not bolted on
Fiscal years, VAT and TDS treatment and IRD sending are part of the central posting paths, so every module inherits them.
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.
Implementation
How a go-live actually runs
We do not hand over a login and wish you luck. Configuration is checked before you trade, and your opening balances are reconciled first.
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
See how it works before you buy
425 step-by-step guides, written from the Penahak screens. Start with the accounting process every module feeds.
Setup
Customers, suppliers, numbering, sales and purchase adjustments, approvals, the fiscal year and the settings that change selling and buying.
SetupSales
From quotation and order to delivery, invoice and return, getting paid, and the daily sales reports.
SalesIRD
IRD-ready invoices, how bills reach the IRD, and what to check when one does not.
IRDPurchases
Buying from suppliers: requisitions, quotations and orders, goods received and purchase invoices, returns, paying suppliers and the…
PurchasesBanking and period end
Receipts, payments, journals, cheques and bank work, the books, closing a year, fixed assets and TDS.
Banking and period endInventory and production
How stock is kept, moved and valued; products and their units, groups, opening stock and tools; warehouses and negative stock; transfers…
Inventory and production
Questions
The things people ask first
Yes. Modules are licensed individually, so you can begin with the counter or the books and switch the rest on later. Because everything shares one ledger and one customer and supplier list, adding a module later does not mean migrating your data again.
Bills, posting and reports need a connection. A kitchen ticket whose printer is off waits in the queue and prints when the printer is back, and a saved bill can always be reprinted.
Fiscal invoice behaviour, VAT summaries, the audit trail and IRD synchronisation are built into the sales invoice and POS paths themselves. IRD-ready describes how the system builds and sends your invoices; it is not a statement by the IRD about your company. Your configuration is verified against your own registration during onboarding.
Yes. Branches within a company share one set of books, each with its own document numbering, and reports cover all branches or one. Separate companies are separate databases, each with its own sign-in address and licence.
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.