Hi.
I searched for this issue and I gather that Frappe is focused on the Gregorian dates. The Nepali compliance system is based on local system that has uneven number of days. So, the usual 17th July, 2025 to 16th July, 2026 will not automatically translate to local month ends.
I saw the Nepali Compliance app too as that claims to solve the problem. But, I am wary of other overriding consequences of using that app. Is there a way to know whether it changes the core logic of ERP system or it just builds some layer so that other built in functions of the ERP system will work.
Also, is it that difficult to customize fiscal year so that I get correct month endings and somehow notify the month end gregorian dates to the system too?
Thank you for the help.
Hi there,
I don’t use the Nepali compliance app, so I can’t speak to how it works there, but at my organization we’ve been using the Nepali fiscal year five or six years now without major problems. Your mileage may vary, of course!
The HRMS app was a bit more trouble for us, as payroll years are a bit more rigid in their structure. We only do monthly salary, though, so we were able to get away with using Gregorian months for pay periods.
Hi peter,
We intend to only do payroll for starting the ERP migration. But, quickly got stuck in the very beginning when we found out that there is no way to “just” set Gregorian periods like “17th July, 2025 - 16th July, 2026” and also have them operate with correct Nepali month end date.
Because, leave management to payroll calculation involving TDS will get botched up no?
Could you guide me on how could I approach it, or how you did it?
I don’t have much experience or advice, unfortunately, since my organization does accounting on Bikram Sambat but payroll periods on the Gregorian calendar. It might take a lot of work to make the HRMS app work correctly for you. It’s a lot less flexible than ERPNext generally is, in our experience.