Leave and attendance
Requests, approvals and balances, connected to biometric attendance devices.
HR teams spend their week on attendance sheets, leave emails and payroll spreadsheets. We build HR systems that handle attendance, leave, payroll and hiring, so people get answers and HR gets its time back.
Leave requests and approvals buried in email and chat
Requests, approvals and balances, connected to biometric attendance devices.
Payroll rebuilt in spreadsheets every month
Salary, tax and deductions calculated from attendance, with payslips sent automatically.
Attendance from devices never matches the payroll sheet
Job posts, applications and interview scheduling in one pipeline.
Requests, approvals and balances, connected to biometric attendance devices.
Salary, tax and deductions calculated from attendance, with payslips sent automatically.
Job posts, applications and interview scheduling in one pipeline.
Staff see payslips, balances and policies on their phones.
An HRMS, or human resource management system, holds employee records and runs the routine work around them: attendance, leave, payroll, hiring, appraisals and exits. In many companies that work is split between a biometric device, a leave spreadsheet, a payroll workbook and a pile of email. Every month someone reconciles them by hand.
Payroll in Nepal adds its own detail. Salaries are often set by grade and allowance, deductions can include income tax, provident fund, Citizen Investment Trust and Social Security Fund (SSF) contributions, and many organisations work in Bikram Sambat months while their accounts follow the Nepali fiscal year. A system that only knows the Gregorian calendar and one tax table creates extra work.
Themattic builds HR and payroll software for companies, NGOs and staffing firms in Nepal and abroad. We implement Odoo’s HR apps where they fit, build custom HR portals and enterprise tools where they do not, and connect either to your attendance devices and accounting. Rules for tax, SSF and allowances are configured to your requirements and checked with your finance team or auditor.
An HR system is worth a look when:
The gains HR and finance teams notice first.
Salary is calculated from approved attendance, leave and overtime, not retyped from device reports.
Requests, approvals and balances in one place, with policies applied the same way to everyone.
Employees see payslips, balances and policies, and apply for leave, from their phones.
Allowances, deductions and tax rules are set once and applied consistently each month.
Contracts, changes, approvals and payslips are stored with a history of who changed what.
Less data entry and chasing leaves more time for hiring, training and people.
What to plan before you choose or build an HR and payroll system in Nepal.
Most organisations need the same core, then add modules as they grow:
Payroll is where generic HR software most often falls short for Nepali organisations. Before we build or configure anything, we list your salary components, allowances and deductions, and how each one is calculated. Typical items include basic salary and grade, dearness and other allowances, overtime, festival allowance, provident fund, gratuity, Citizen Investment Trust, SSF contributions and income tax by slab.
We set these up as rules your HR team can update when policies or rates change, rather than code only a developer can touch. Payroll can run in Bikram Sambat months, with the Nepali fiscal year used for tax and reports. Statutory figures are configured to your requirements and reviewed by your finance team or auditor before the first live run. We build the system; your advisers confirm the compliance.
An HR system saves the most time when it stops being an island. Common connections are:
HR data includes salaries, bank details, citizenship numbers, health notes and disciplinary records. We set role-based access so employees see only their own records, managers see their teams, and payroll figures are limited to the people who process them. Changes to salary and bank details are logged, sensitive documents are stored securely, and backups run on a schedule. Retention and access rules are configured to your policies.
A careful payroll rollout avoids paying anyone wrongly in the first month. Our usual sequence is:
Subscription HRMS products are a quick start for smaller teams with standard policies. Odoo suits organisations that also want accounting, inventory or sales in the same system. Its HR apps can be configured and extended for Nepali payroll, though payroll is part of the paid Enterprise edition.
A custom HR system makes sense for staffing companies, organisations with complex shift or project-based pay, and anyone whose rules do not fit a product. It can be built as a progressive web app, so staff use it on any phone without an app store. We help you compare all three, including the total cost over several years, before you commit.
Platforms and tools we use to build HR systems that fit Nepali payroll.
The cost depends on the modules you need, how complex your pay rules are, and whether we configure Odoo or build custom software. We give a fixed quote after mapping your policies. The main factors are:
A Kathmandu team that builds and supports HR and payroll systems for organisations in Nepal and abroad.
We work through BS months, fiscal years, allowances and deductions with your finance team, line by line.
We implement Odoo and build custom software, so we recommend the option that fits.
Scope, timeline and price agreed in writing before work starts.
Employee data stays under your control, and the code we write for you is yours.
New payroll is checked against your current method before anyone is paid from it.
Help with policy changes, new rates and year-end from the team that built it.
ERP, CRM and custom systems that connect finance, inventory, HR and operations in one place.
See the serviceWeb apps that install on a phone, work offline and load fast on slow networks, without an app store.
See the serviceTechnical consulting, product strategy and hands-on training so your team can choose and run the right technology.
See the serviceEvery project follows the same route, so you always know where it stands and what comes next.
We learn your business, goals, competitors and users, then agree the scope and plan in writing.
We learn your business, goals, competitors and users, then agree the scope and plan in writing.
User journeys and screens designed and reviewed with you before any code is written.
Responsive, fast and secure builds, shared with you as they progress.
Testing, speed optimisation and analytics set up before the site or app goes live.
Ongoing support, maintenance, training and improvements as your business grows.
Excellent communication and seamless project delivery — highly recommended for any business looking to build a strong online presence.
Ramesh GCCEO, EcoTours NepalCan’t find your answer here? Send us a message and we will reply.
The best fit depends on your size, your pay rules and whether you want accounting in the same system. Subscription products suit small teams with standard policies, Odoo suits companies that want HR and accounts together, and custom software suits complex rules. We compare the options with you before recommending one.
Yes. These are set up as configurable rules based on your policies and current rates, and checked by your finance team or auditor before the first live run.
Yes. We can run attendance, leave and payroll in Bikram Sambat months, and show BS and AD dates on screens, payslips and reports.
Most devices can be connected through their SDK, API or exported files. We check your model before we quote.
Yes. Employees can apply for leave, check in and download payslips from a phone browser or a [mobile app](/mobile-application/).
Yes. Employees can be assigned to branches, departments, projects or funded programmes, with payroll costs split for reporting.
Odoo payroll can be configured for Nepali salary structures, allowances and tax slabs. It needs careful setup and testing, which is the main part of our work on Odoo HR projects.
A focused setup of attendance, leave and payroll typically takes about six to twelve weeks, including at least one parallel payroll run. Larger or custom systems take longer.
Yes. We build careers pages and applicant tracking with job posts, application forms, screening and interview scheduling, linked to your HR records.
[Book a call](/talk-to-expert/) and share your payroll sheet structure, leave policy and attendance device model. We will map the work and send a written quote.
You do. When the project is complete we hand over the code and all intellectual property, and hosting and domains are registered in your name.
Yes. Every project has a written contract setting out the scope, timeline, price and support terms.
Order portals, ERP integration and automation for companies that sell to other businesses.
See solutionsAdmissions, learning platforms and school management systems for schools, colleges and training providers.
See solutionsOrdering apps, delivery tracking and kitchen systems for restaurants, cloud kitchens and delivery services.
See solutionsOpenMRS 3.x and Bahmni medical records, appointment booking, patient portals and hospital systems for hospitals, clinics and labs.
See solutionsDirect booking engines, guest apps and property systems for hotels, resorts and homestays.
See solutionsTrip booking, itinerary and operator systems for tour operators, trekking agencies and adventure businesses.
See solutionsNews sites, streaming, ticketing and content platforms for publishers, studios and event organisers.
See solutionsOnline stores, point of sale and inventory systems for shops, brands and multi-branch retailers.
See solutionsShare what you want to build. We reply with next steps and a time for a discovery call, then a written quote.
info@themattic.com