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

Wholesale & distribution

Order-to-dispatch with challans, agent commissions, multi-godown stock and receivable ageing that collections can act on.

What we hear

The problems that bring people to us

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.

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.

Credit extended without context

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.

Nobody owns the collection

Ageing exists as a report, but no named person owns chasing a specific balance, so the oldest debt keeps getting older.

Agent commission is calculated by hand

Without agent and area dimensions on the transaction, commission is reconstructed from spreadsheets each period.

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

Quotation raised; live balance and dispute context shown before approval Order
Converted to a sales order on acceptance Order
Challan issued, goods dispatched from the right godown Dispatch
Invoice raised; outstanding moves from delivery to receivable Billing
Collections work the ageing queue with named owners Collections
Agent, area and product analysis drills to the document Review
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.

  • Outstanding is visible at quotation, order and challan level, not just as a receivable
  • Credit decisions are made with live balance, ageing and dispute context on screen
  • Commission and territory reporting come from dimensions on the transaction
  • Multi-godown stock means dispatch draws from the right location
  • Every ageing figure drills to the specific unpaid document
Reporting

The reports you will live in

Every total drills down to the source document behind it.

  • Outstanding sales order / challan / quotation
  • Customer & vendor ageing
  • Sales analysis
  • Sales target vs achievement
  • Godown transfer summary
  • Collection ownership
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 Wholesale & distribution

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.