
Nepal runs on Bikram Sambat. Most software doesn't.
Salaries, rent, school terms and the fiscal year in Nepal all follow the Bikram Sambat calendar. The software we use is built around the Gregorian one.
01How it started
The first time it really annoyed me was on GymSewa. A membership does not expire on "31 June." It expires at the end of a Bikram Sambat month, and people will say "renew until Asar" as if that were a normal unit of time — which, here, it is. I reached for a quick formula and then remembered, again, that BS months are not a fixed length. You cannot just calculate them. You need the actual table.
Then the same need showed up in the next side project, and the next: an invoice date, a report "for Shrawan to Asar," a fiscal year that starts in Shrawan and ends in Asar. I was copying date tables between folders like a person who has not learned the lesson. Holidays and tithi were worse, because they change every year. A friend who was also fighting a calendar in their own app asked if I had "the one file." I did not. I had four slightly different ones.
02Two layers
So I split it on purpose. nepal-date-kit is the free, open-source toolkit: convert BS and AD, format dates in Nepali or English, build a month grid, and work out the fiscal year. It ships month lengths, not events. The Nepali Calendar API is for apps that need more — conversion, month calendars, the fiscal year, and public holidays, festivals and tithi. GymSewa uses BS dates for exactly this reason. Other people building payroll, school, booking or accounting apps for Nepal should not have to maintain that table alone.
03What it does now
The kit is on GitHub. The API is the fuller layer on top. I would rather a developer take the kit for basic conversion and only reach for the API when they need the year-by-year cultural calendar. That boundary is the product.
04What's still true
Software likes Gregorian dates because they are tidy. Nepal does not run on tidy. The work is not to pretend the months are even. It is to look the days up, carefully, and share the lookup.