Skip to main content
GullySystem
South Asia · Software for businesses in Nepal

Business software for Nepali hotels, trek operators, schools and cooperatives that work in Nepali and English.

Nepal runs on mountain tourism, schools, cooperatives, small factories and trade across a long open border. Our Bengaluru team has no office in Nepal and serves clients by video, email and WhatsApp. Software covers bookings, fees, members, invoices and receipts, with Nepali screens where staff need them.

At a glance

Working with a team in India from Nepal.

Nepali firms are small and family run. A guesthouse in Pokhara, a trekking agency in Thamel, a private school in Butwal and a savings cooperative in a hill town all keep records in registers and spreadsheets. Seasons are sharp. Tourist months bring a rush, and the quiet months are for fixing systems.

Our team sits in Bengaluru. Nepal has no office of ours and we hold no local licence, and no Nepali customers or partners can be named. Work happens over video calls. The time zone is nearly the same as ours, so scheduling is simple.

How the work runs

What changes when your business is in Nepal.

Hours, money, language and data are decided with you at the start, not discovered later.

Time zone and calls

Nepal is only fifteen minutes ahead of India. Your working day lines up with ours almost completely, so calls fit any slot, and urgent questions get a reply by message the same day. We agree response times in the support plan.

Nepali and English screens

Staff may prefer Nepali in Devanagari script, while tourists and foreign partners need English. Screens, receipts and vouchers carry both. We test Devanagari names and addresses in print and export before go-live, since a font that looks right on screen may fail in print.

Messaging apps

Viber and WhatsApp are both common, and Facebook Messenger is used for guest enquiries, while our messaging work is built on the WhatsApp Business platform. We check other channels separately before promising them.

Power and connection

Hill towns and trek routes may have weak internet or short power cuts, so we design screens to save work as you go and recover cleanly. For remote lodges, a simple offline note sheet that syncs later can be scoped.

Decisions and handover

One person at your end owns choices and signs off each stage. Training runs by shared screen, and sessions are recorded for staff who join later, so nobody learns the system from a rushed handover. Your data stays yours and can be exported at any time.

How the first stage runs

We begin with a call and a few of your real records, such as a trek booking, a fee receipt and a member passbook. A small first release then covers one task. Staff try it on live work. The order of the rest is yours to set.

Photos and files from phones

Guides and lodge owners send passport photos and payment slips by chat, and those images pile up in phone galleries. Each booking gets a place for its files instead. Staff upload straight from a handset. Access follows the role, so a porter’s wage sheet is not open to every user.

Changes saved for quiet months

We keep a running list of small changes noted during busy weeks, and we work through it when you can test properly. Peak days are for using the system. They are not for changing it.

Business in Nepal

What the software has to fit.

The filing cycles, payment habits and licences a small business there already works around.

VAT, PAN and invoices

Businesses register for a permanent account number, and larger ones charge value added tax. Billing software may need to meet rules set by the tax office, and those rules are revised from time to time. Confirm the requirement with your accountant before launch.

Local currency and foreign guests

Local sales are in Nepali currency, while trekking and hotel packages are quoted to foreigners in US dollars. An invoice may need both amounts. Rates are never fixed in the code, and your accountant decides the source.

Calendar and work week

Offices run Sunday to Friday, with Saturday as the weekly day off. Official dates follow the Bikram Sambat calendar, which differs from the English one, so reports and fee schedules should show both dates where staff expect it.

Festivals and seasons

Dashain and Tihar close most businesses for days, and staff travel home. Trekking peaks in spring and autumn. Schools follow their own academic year. We plan training and go-live around these breaks, never into them.

Payments and data rules

Mobile wallets such as eSewa and Khalti are widely used, and bank transfers are growing. Cash is still common in the hills. Nepal has an Individual Privacy Act, and sector regulators may add rules for cooperatives and banks. Ask your legal adviser what applies to you.

Trek bookings and group costs

A trek is sold as one package covering guides, porters, lodges, transport and permits. The booking record holds the group list, the route and each payment received. Unpaid balances show before the party leaves Kathmandu. Staff chase early.

School fees and member passbooks

Private schools bill fees by term, with transport and exam charges added, and parents pay in parts. Cooperatives record small deposits and loan repayments from members on set days. Both need a running balance for each person. A clerk must find it at the counter without turning pages.

Cities

Cities we write software for in Nepal.

Make an informed decision

Make the scope specific to your business.

Work through a real example from your operation and agree the handoffs, controls and support the project needs.

VAT, PAN and invoices

Can you explain the balance from its original documents?

Select a partly settled example in “VAT, PAN and invoices”. Ask for the invoice, allocated receipts and remaining balance to be shown together before agreeing the opening figures.

Background reading: ERPNext: outstanding invoices

Payments and data rules

Can the same receipt be allocated without counting the money twice?

Take an unallocated amount in “Payments and data rules” and apply it to the intended balance. Review the remaining amount and the original receipt reference together.

Background reading: ERPNext: payment allocation

Common questions

Questions from businesses in Nepal.

Do you have a team or office in Nepal?

No. Our work is done from Bengaluru, by video, email and WhatsApp, and we hold no Nepali licence and name no customers there. Your own person owns decisions.

Can receipts and screens use Nepali script?

Yes. Screens, receipts and vouchers can show Nepali and English side by side. We test Devanagari print and export with real names first, because that is where a wrong font shows.

Can a booking show dollars and Nepali currency?

Yes. Each booking keeps its quoted currency and shows the local total for the books, and rate sources are agreed with your accountant, so none are hard coded.

Will it work with weak internet in the hills?

Screens are built to save as you go and recover after a drop, and for very remote sites an offline sheet that syncs later can be scoped. We state the limits plainly in the plan.

Can the system show Bikram Sambat dates?

Yes, dates can display in both calendars on reports and fee schedules. Your team confirms the conversion rules in testing.

How do you handle tax billing rules?

The fields your accountant specifies are built, but rules change, so confirm the requirement with your accountant. Anything beyond a normal invoice is scoped before a quote.

Can one system serve a trek agency and a lodge?

Both can sit in one system if both are yours. Agency bookings and lodge rooms share one guest record, so a trekker’s deposit and room nights appear together. Separate businesses keep separate books. We agree that split with your accountant before any invoice is issued.

From Nepal

Tell us what you run.

Share your requirements and an engineer will read them before getting in touch, at an hour that suits your day.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements