ByapareKhata

About us

We started with a notebook, because most businesses here do

Byapar eKhata is built in Kathmandu by a small team of engineers and accountants who kept meeting the same problem: a business that is doing well, but cannot tell you how well, because its records live in five places.

12,400+
businesses keeping books on Byapar eKhata
18
reports, exportable to PDF, Excel and WhatsApp
14
transaction types on one accounting engine
4.7★
average rating on the Play Store

What we believe

Four principles we have not moved on

Plain language over accounting jargon

The app says udharo, not accounts receivable. It says cash in hand, not cash balance b/f. The accounting underneath is rigorous, but you should never have to learn our vocabulary to run your shop.

Works first, syncs later

If the app stops when the internet stops, it is not an app for Nepal. Offline is not a setting we added; it is the assumption the product was designed around.

Your data leaves when you want it to

Every report exports. A full export is a request, not a negotiation. We would rather earn your business each month than trap it.

Built to be checked

Double-entry, atomic transactions and an audit log mean that when a figure looks wrong, you can trace it back to the entry that produced it.

How we got here

A short history

2024

The first khata

Started after watching a hardware shop in Lalitpur run three separate notebooks, and lose money in the gaps between them.

2025

From khata to books

A double-entry engine underneath the simple screens — so the ledger, VAT and balance sheet all agree without being maintained twice.

2025

Offline, properly

Full offline billing with a local queue and automatic conflict handling, tested where load shedding is still part of the day.

2026

A network of referrers

Accountants, computer shops and consultants across the country now bring businesses to Byapar eKhata and earn from it.

Built in Nepal, for Nepal — and honest about it

We are not a foreign product with a Nepali price tag. Payments go through Nepali gateways, reminders run on Nepal time, VAT and PAN fields are part of the core schema, and support answers in Nepali. Everything else is a detail.