One moment
Payroll in Nepal has a calendar problem before it has a maths problem. Spreadsheets and software built elsewhere run on a Gregorian month, so the first thing an office does to pay salaries in Ashar is work out by hand which weeks of June and July that actually covers, every single month. SSF, provident fund, TDS and CIT then get calculated in a second sheet, or not at all, because the first one was never built to hold them.
No card, no demo call, and unlimited students on every plan.
Ashar 2083 ran from 15 June to 14 July 2026, not from the first of July to the thirty-first. A spreadsheet keyed to a calendar month either pays the wrong three weeks or needs a manual conversion redone every month by whoever is willing to do it. Attendance usually lives in a different sheet again, so the days somebody actually worked get typed into payroll from memory rather than read from a record, and nobody notices until a staff member disputes a deduction nobody can explain.
Everything below is in the product today. Open a free account and you will find it there.
Open a run for Ashar 2083 and it covers 15 June to 14 July 2026, worked out from the Bikram Sambat calendar rather than typed in by hand. Nepali month lengths vary year to year and are read from a calendar library, not a table somebody has to keep updated.
Starting a run reads each person's attendance for that month and fills in the days expected, present and absent before anyone types a number, rather than asking whoever runs payroll to copy it across from a different screen.
Each person's run carries basic, allowance and bonus on one side and SSF, the provident fund, TDS, CIT and advances on the other, entered once and totalled automatically, so a payslip shows what was deducted and why instead of one figure nobody can explain.
A draft can be corrected. A run that has been marked paid cannot, by anyone, because a payslip somebody can quietly edit after the fact is not a payslip. A mistake on a locked run is corrected in the next one, not inside it.
Staff clock in from inside a radius you set for each branch, not from the bus. A clock-in outside it is recorded as outside it, with the distance, rather than silently accepted, which is what makes the days payroll reads trustworthy in the first place.
Each branch's payroll opens as its own run, scoped to who is allowed to see that branch. Head office sees every branch's runs from one place without asking anyone to send a sheet.
Payroll reads this. Days in, hours, and which were clocked from outside the office radius, carried into the run instead of retyped.
A payroll keyed to July pays Ashar wrong, because the two months do not line up and the overlap shifts every year. Converting by hand is the kind of task that gets done correctly eleven months out of twelve, and the month it is wrong is the month somebody's salary is short. Running the actual month removes the conversion rather than asking somebody to get it right every time.