ThematticStart a project

Software and apps for hr

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.

  • 01Leave and attendance
  • 02Payroll processing
  • 03Recruitment portals
HR deskLeaveAttendancePayrollHiringLeaveNewEmployeeTypeDaysStatusAnita K.Annual leave3ApprovedBikash R.Sick leave1PendingSunita M.Annual leave5Awaiting managerRamesh T.Work from home2ApprovedPriya S.Festival leave4PendingSynced just now

What slows hr down, and how we fix it

  1. Problem

    Leave requests and approvals buried in email and chat

    What we buildLeave and attendance

    Requests, approvals and balances, connected to biometric attendance devices.

  2. Problem

    Payroll rebuilt in spreadsheets every month

    What we buildPayroll processing

    Salary, tax and deductions calculated from attendance, with payslips sent automatically.

  3. Problem

    Attendance from devices never matches the payroll sheet

    What we buildRecruitment portals

    Job posts, applications and interview scheduling in one pipeline.

What we build for hr

01

Leave and attendance

Requests, approvals and balances, connected to biometric attendance devices.

HR deskLeaveAttendancePayrollHiringLeaveNewEmployeeTypeDaysStatusAnita K.Annual leave3ApprovedBikash R.Sick leave1PendingSunita M.Annual leave5Awaiting managerRamesh T.Work from home2ApprovedPriya S.Festival leave4PendingSynced just now
02

Payroll processing

Salary, tax and deductions calculated from attendance, with payslips sent automatically.

03

Recruitment portals

Job posts, applications and interview scheduling in one pipeline.

04

Employee self-service

Staff see payslips, balances and policies on their phones.

HR and payroll in one system

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.

Signs you have outgrown spreadsheets for HR

An HR system is worth a look when:

  • Payroll takes days each month and depends on one person who understands the spreadsheet
  • Attendance device reports need cleaning up before anyone can use them
  • Leave balances are disputed because nobody trusts the numbers
  • Employees ask HR for payslips, tax statements and balances by email
  • Staff work across branches or sites, and their records live in different places
  • Hiring runs through email inboxes and shared folders, and good candidates slip through

What an HRMS does for your team

The gains HR and finance teams notice first.

Payroll from real attendance

Salary is calculated from approved attendance, leave and overtime, not retyped from device reports.

Leave everyone can trust

Requests, approvals and balances in one place, with policies applied the same way to everyone.

Self-service for staff

Employees see payslips, balances and policies, and apply for leave, from their phones.

Fewer payroll errors

Allowances, deductions and tax rules are set once and applied consistently each month.

Clear records for audits

Contracts, changes, approvals and payslips are stored with a history of who changed what.

Time back for HR

Less data entry and chasing leaves more time for hiring, training and people.

HRMS and payroll software, explained

What to plan before you choose or build an HR and payroll system in Nepal.

Core features of an HRMS

Most organisations need the same core, then add modules as they grow:

  • Employee records: personal details, documents, contracts, positions, grades and reporting lines
  • Attendance: biometric and card devices, mobile check-in with location for field staff, shifts and rosters
  • Leave: leave types, accrual rules, carry-forward, approvals and public holiday calendars
  • Payroll: salary structures, allowances, overtime, deductions, tax, SSF and bank transfer files
  • Payslips, tax statements and year-end summaries sent to employees
  • Recruitment: job posts, applications, screening, interviews and offers
  • Performance: goals, reviews and appraisal cycles
  • Onboarding and exit checklists, final settlement and clearance

Payroll in Nepal: what the system must handle

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.

Integrations: devices, accounts and banks

An HR system saves the most time when it stops being an island. Common connections are:

  • Biometric and RFID attendance devices, through the maker’s SDK, API or exported files
  • Accounting systems such as Odoo, NAV or SAP, for salary journals and cost centres
  • Salary transfer files in the format your bank accepts
  • Email, SMS and chat notifications for approvals and payslips
  • Your careers page and job boards for recruitment
  • Single sign-on with Google Workspace or Microsoft 365, where you use them

Employee data privacy and access

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.

Rollout and training

A careful payroll rollout avoids paying anyone wrongly in the first month. Our usual sequence is:

  1. Map your policies, salary structures and approval chains in writing
  2. Import employee records and opening leave balances, then have HR check them
  3. Connect attendance devices and test a full month of data
  4. Run payroll alongside your current method for at least one cycle and compare every payslip
  5. Train HR, managers and employees on the tasks each will do
  6. Go live, then review any issues after the first live payroll

Odoo, a subscription HRMS or a custom build?

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.

Our HR and payroll toolkit

Platforms and tools we use to build HR systems that fit Nepali payroll.

  • Odoo HR and Payroll
  • Python
  • Django
  • React
  • Progressive web apps
  • PostgreSQL
  • Biometric device SDKs
  • Bikram Sambat dates
  • Bank transfer files
  • REST APIs
  • Role-based access
  • Email and SMS alerts
  • AWS

How much does HR and payroll software cost?

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:

  • The modules you need now and later, from attendance to appraisals
  • The number of salary structures, allowances and deduction rules
  • The number and type of attendance devices and sites
  • Integrations with accounting, banks and other systems
  • Migration of employee records and past payroll
  • Odoo Enterprise licences, if you choose Odoo, or hosting for a custom system
  • Training, parallel payroll runs and support after launch

Why choose Themattic for hr

A Kathmandu team that builds and supports HR and payroll systems for organisations in Nepal and abroad.

Payroll detail understood

We work through BS months, fiscal years, allowances and deductions with your finance team, line by line.

Odoo or custom, honestly

We implement Odoo and build custom software, so we recommend the option that fits.

Fixed quote and contract

Scope, timeline and price agreed in writing before work starts.

Your data and code

Employee data stays under your control, and the code we write for you is yours.

Parallel runs before go-live

New payroll is checked against your current method before anyone is paid from it.

Support after launch

Help with policy changes, new rates and year-end from the team that built it.

How the project runs

Every project follows the same route, so you always know where it stands and what comes next.

01

Discovery & strategy

We learn your business, goals, competitors and users, then agree the scope and plan in writing.

  1. 1

    Discovery & strategy

    We learn your business, goals, competitors and users, then agree the scope and plan in writing.

  2. 2

    UX & UI design

    User journeys and screens designed and reviewed with you before any code is written.

  3. 3

    Development

    Responsive, fast and secure builds, shared with you as they progress.

  4. 4

    Launch

    Testing, speed optimisation and analytics set up before the site or app goes live.

  5. 5

    Support & growth

    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 GCRamesh GCCEO, EcoTours Nepal

Questions about software for hr

Can’t find your answer here? Send us a message and we will reply.

Other industries

Build for hr with us

Share what you want to build. We reply with next steps and a time for a discovery call, then a written quote.

  1. 1
    We reply with next steps

    A short email from our team, usually with a few questions about goals and timing.

  2. 2
    Discovery call

    Thirty to sixty minutes on your business, users and what success looks like.

  3. 3
    Written proposal and quote

    Scope, timeline and a fixed price, before any work begins.

info@themattic.com

We use your details only to reply to this enquiry. See our privacy policy.