Delivered but never billed
Goods leave on a challan and the invoice is raised later, or not at all. Nobody has a single list of what has gone out and not been charged.
Order-to-dispatch with challans, agent commissions, multi-godown stock and receivable ageing that collections can act on.
Distribution loses money to leakage rather than theft: goods delivered but never invoiced, a challan never converted, a quotation nobody chased. Penahak tracks outstanding at every stage so the leak has somewhere to appear.
Goods leave on a challan and the invoice is raised later, or not at all. Nobody has a single list of what has gone out and not been charged.
An order is approved for a customer who is 90 days overdue with an open dispute, because the person approving it could not see either.
Ageing exists as a report, but no named person owns chasing a specific balance, so the oldest debt keeps getting older.
Without agent and area dimensions on the transaction, commission is reconstructed from spreadsheets each period.
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.
Full order-to-cash and procure-to-pay cycles with challans, dispatch, returns and outstanding tracking at every stage — so you always know what is quoted, ordered, delivered, billed and unpaid.
One inventory engine serves retail, restaurant, hotel minibar and manufacturing. Movements are vouchered, costed and reconcilable back to accounting.
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.
Every total drills down to the document that produced it, reports can be scheduled to generate overnight, and dashboards keep the daily numbers in front of you — 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.
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.
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.
Posted figures are never edited in place. Corrections go through an approved reversal or credit note, each recorded with the user, the reason and the original document.
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.