2026 年の ERPNext 人事および給与: セットアップ、給与構造、および複数国のコンプライアンス

ERPNext handles the full employee lifecycle — recruitment, onboarding, attendance, leave, payroll, taxation, and exit — through Frappe HR (the HRMS app), a free and open-source module that competes credibly with paid HR suites costing 5 to 15 dollars per employee per month. The catch is that HR and payroll are the most configuration-heavy area of any ERP: salary components, tax slabs, and statutory deductions differ by country, and a payroll run that posts wrong numbers erodes employee trust faster than any other system failure.

This guide walks through a production-grade ERPNext HR and payroll setup in 2026: installing the HRMS app, structuring the employee master, designing salary structures with formula-based components, executing monthly payroll runs, configuring income tax, and handling multi-country compliance for distributed teams.

Key Takeaways

• Since version 14, HR and Payroll live in a separate open-source app — Frappe HR (hrms) — installed alongside ERPNext on the same site; it is not in the core erpnext app anymore
• The setup chain is strict: Company → Departments and Designations → Employees → Salary Components → Salary Structure → Salary Structure Assignment → Payroll Entry — skipping a link causes blank salary slips
• Salary Components support condition and formula fields (e.g., basic as a percentage of CTC, overtime from timesheet hours), so most pay rules need zero code
• Payroll Entry generates draft salary slips in bulk for a pay period; review before submitting, because submitted slips post GL entries
• Income Tax Slabs are date-effective and country-configurable, with support for multiple regimes and employee-level declarations
• Multi-country payroll is handled with one Company (or branch) per jurisdiction, country-specific salary structures, and localization apps for statutory formats
• Leave and attendance feed payroll automatically via Leave Without Pay and attendance-based working days — configure them before your first run, not after
• Payroll posts to your real general ledger — involve your accountant in component-to-account mapping on day one

---

What ERPNext HR Covers in 2026 (and How It Is Packaged)

The most common installation mistake newcomers make: searching ERPNext's module list for "Payroll" and finding nothing. Since ERPNext version 14, the entire HR and payroll suite was moved out of core into Frappe HR — a standalone app (hrms) maintained by Frappe and installed with bench get-app hrms followed by bench --site yoursite install-app hrms. On Frappe Cloud, it is a one-click install. The app remains 100% open source with no paid tier.

Functionally, Frappe HR spans thirteen modules:

For a mid-market company, the realistic comparison set is BambooHR, Zoho People, or local payroll bureaus — and the economics favor ERPNext heavily at headcounts above 50, where per-employee SaaS pricing starts costing more annually than a full implementation.

---

Step 1: Foundation — Company, Departments, and the Employee Master

Payroll accuracy is downstream of master data quality. Before touching salary configuration:

Company and fiscal setup. Each legal entity that issues payslips should be an ERPNext Company with its own chart of accounts, default payroll payable account, and currency. The fiscal year matters for tax computation — India runs April–March while most of the Gulf and the West run January–December — and ERPNext supports both simultaneously across companies.

Organizational structure. Create Departments, Designations, Branches, and Employee Grades first. Grades are more useful than they look: a grade can carry a default salary structure, so new hires inherit correct pay configuration automatically.

Employee records. The Employee DocType is the hub every other HR document links to. The fields that bite later if skipped: date of joining (drives payroll eligibility and leave allocation), holiday list (drives working days), payroll cost center (drives GL analytics), bank account and salary mode (drives payment export), and tax ID fields for your jurisdiction. Bulk-load via the Data Import tool from a cleaned spreadsheet — and validate joining dates carefully, because a wrong year silently produces wrong leave balances and prorated salaries.

---

Step 2: Salary Components — The Building Blocks of Every Payslip

A Salary Component is a single earning or deduction line: Basic, House Rent Allowance, Transport Allowance, Overtime, Provident Fund, Social Insurance, Income Tax. Each component carries flags that control its behavior:

• Earning or Deduction — which side of the slip it appears on
• Condition and Formula — Python-like expressions evaluated per employee, e.g., a formula of base * 0.5 for Basic, or a condition of grade == "Senior" gating an allowance
• Depends on Payment Days — prorates the component for unpaid leave and mid-month joiners (correct for most earnings, wrong for fixed reimbursements)
• Is Tax Applicable — includes the component in taxable income
• Statistical Component — used in other formulas but never paid (e.g., CTC as a reference figure)
• Account mapping — the GL account per company this component posts to

Design advice from production deployments: keep the component list short and formula-driven. Twelve well-designed components with formulas beat forty hardcoded ones. Every component you add is a line your accountant must map, your payroll officer must explain, and your tax configuration must classify.

---

Step 3: Salary Structures and Assignments

A Salary Structure bundles components into a template — "Standard Full-Time KSA," "India Staff 2026," "Hourly Contractors" — and defines payout frequency (monthly, biweekly, weekly, daily). Structures support timesheet-based pay with an hourly rate for contractor models.

The Salary Structure Assignment then links an employee to a structure from an effective date, and critically, sets the employee's base figure — the anchor number all formulas reference. This separation is what makes ERPNext payroll scale: one structure serves hundreds of employees, each with an individual base, and a raise is just a new assignment from a new date with full history preserved.

Two operational rules:

1. Never edit a submitted structure to "fix" one person's pay. Use Additional Salary for one-off payments (bonus, arrears, deduction) or a new assignment for permanent changes.
2. Date-effectiveness is your audit trail. Backdated changes are possible but post-facto edits to submitted slips are not — get effective dates right at entry.

---

Step 4: Running Payroll — The Monthly Cycle

The Payroll Entry document executes payroll for a period in bulk:

1. Select company, payroll frequency, and posting date; filter by branch, department, or designation if you pay groups separately
2. Fetch employees — ERPNext pulls everyone with an active assignment matching the filters
3. Create draft salary slips — each slip computes earnings, deductions, taxes, payment days (factoring approved Leave Without Pay and, if enabled, attendance), and loan repayments from the Loan Management module
4. Review exceptions — new joiners, exits, employees with LWP, anyone whose net pay moved more than a tolerance vs. last month; this human review step is where payroll errors die
5. Submit slips — net pay and component-level amounts post to the general ledger against the payroll payable and expense accounts
6. Bank entry — generate the payment journal entry and export the bank file for salary disbursement

Speed expectation: a 200-employee monthly run takes the system minutes and a competent payroll officer under half a day including review — provided steps 1–3 of this guide were done properly. Companies that struggle with multi-day payroll cycles in ERPNext almost always have master-data problems, not software problems.

Email payslips automatically on submission (built-in setting), and use the Salary Register report for the consolidated monthly view your finance team will ask for.

---

Step 5: Income Tax and Statutory Compliance

ERPNext computes income tax through Income Tax Slabs — date-effective, currency-aware slab definitions with percentage bands, optional surcharge conditions, and support for multiple parallel regimes (relevant in India's old-vs-new regime choice, configurable per employee via their tax slab selection). The engine annualizes projected taxable earnings, applies declared exemptions from Employee Tax Exemption Declarations, and deducts tax monthly with a year-end true-up — including handling of proof submission against declarations.

Statutory deductions beyond income tax — provident funds, social insurance (GOSI in Saudi Arabia, ESI/PF in India, EOBI in Pakistan), pension schemes — are modeled as deduction components with formulas, usually a percentage of basic capped at a ceiling. The computation is rarely the hard part; the statutory reporting formats are. That is where country localization apps come in:

Honest guidance: ERPNext's payroll engine is genuinely multi-country, but filing-ready statutory output varies by jurisdiction. Budget implementation time for your country's formats — or run computation in ERPNext and filing through your existing accountant for the first cycles.

---

Multi-Country Payroll: The Architecture That Works

For companies paying employees in multiple jurisdictions, the proven pattern is:

• One ERPNext Company per legal entity / country, each with local currency, chart of accounts, and holiday lists
• Country-specific salary structures with local components and statutory deductions
• Country-specific income tax slabs, assigned via each company's payroll settings
• Consolidated reporting through ERPNext's multi-company financial statements, with currency translation handled by the accounting layer

Avoid the tempting shortcut of one global structure with conditional components per country — it becomes unreadable past two jurisdictions and makes statutory audits painful. Separate structures per country cost an hour each to build and save weeks of confusion.

For contractor-heavy global teams, a lighter pattern works: timesheet-based salary structures in the contractor's currency, paid through the same Payroll Entry mechanics without statutory components.

---

Leave, Attendance, and the Payroll Connection

Payroll correctness depends on two upstream modules being configured first:

Leave management. Define Leave Types (with the Is Leave Without Pay flag set correctly — this single checkbox is the link to salary proration), build a Leave Policy, allocate via Leave Policy Assignment, and assign Holiday Lists per employee or company. Approved LWP applications reduce payment days automatically in the salary slip.

Attendance. ERPNext supports manual attendance, bulk upload, Employee Checkin records from biometric devices (several integrations exist for common hardware), and auto-attendance rules that convert checkins into attendance against shift definitions. If you enable attendance-based payroll, run a month of parallel attendance capture before letting it drive pay — device sync gaps surfacing as salary deductions is the fastest way to lose employee trust in the new system.

---

Implementation Sequence and Where Projects Go Wrong

A realistic HR-and-payroll rollout for a 50–500 employee company runs 4–8 weeks:

1. Week 1–2: master data (employees, departments, holiday lists), leave types and policies
2. Week 2–3: salary components, structures, assignments; tax slabs and declarations
3. Week 3–4: parallel run — compute one full month in ERPNext alongside your existing payroll and reconcile to the cent
4. Week 4+: cutover, payslip distribution, attendance integration, then performance and recruitment modules as phase two

The non-negotiable step is the parallel run. Every payroll formula bug, rounding difference, and proration edge case surfaces there instead of in employees' bank accounts.

ECOSIRE delivers end-to-end ERPNext implementations with payroll parallel-run methodology built into the plan, builds country-specific statutory components and formats as upgrade-safe ERPNext customizations, and runs department-wise ERPNext training so your HR team owns the system confidently from the first unassisted payroll cycle.

---

Frequently Asked Questions

Is ERPNext payroll really free, even for hundreds of employees?

Yes. Frappe HR is open source under the GPL with every feature included — there is no per-employee fee, no payroll add-on tier, and no employee cap. Your real costs are hosting (modest — payroll is not resource-hungry) and implementation effort. At 100+ employees this is typically 70–90% cheaper over five years than per-employee HR SaaS, which is exactly the headcount where SaaS pricing starts to hurt.

Can ERPNext run payroll for employees in multiple countries?

Yes, with the right architecture: one Company per legal entity, country-specific salary structures and income tax slabs, and local statutory deductions as formula components. Computation works everywhere; filing-ready statutory report formats vary by country, with India having the deepest localization and other regions relying on community apps or custom formats. Plan jurisdiction-specific formats into the implementation scope.

How does ERPNext handle mid-month joiners and unpaid leave?

Through payment days. Each salary slip computes actual payable days from the joining/relieving dates, the employee's holiday list, and approved Leave Without Pay applications. Components flagged Depends on Payment Days prorate automatically, while flat components (like a fixed reimbursement) pay in full. The logic is automatic once leave types and holiday lists are configured correctly — which is why those come before payroll in the setup sequence.

Can we integrate biometric attendance devices with ERPNext?

Yes. Devices push (or a sync service pulls) punch data into Employee Checkin records, and auto-attendance rules convert checkins into daily Attendance against shift definitions — including late entry and early exit marking. Integrations exist for common biometric hardware, and custom device protocols are a small integration project. Run attendance in parallel for a full cycle before letting it drive salary deductions.

Does payroll post to ERPNext accounting automatically?

Yes — that is one of the strongest reasons to run payroll inside your ERP rather than a separate tool. Submitted salary slips (via the Payroll Entry) create GL postings: component expenses debit the mapped accounts per cost center, net pay credits the payroll payable account, and the disbursement journal clears it on payment. Your P&L reflects salary cost by department with no month-end import step.

What happens to a submitted salary slip with an error in it?

Submitted slips are immutable accounting documents — you cancel and amend rather than edit, preserving the audit trail. For a one-off correction discovered after disbursement, the cleaner pattern is an Additional Salary entry (positive or negative) in the next cycle. This is also why the draft-review step in the payroll run matters: catch it before submission and it is a ten-second fix.

---

Run Payroll Your Team Actually Trusts

A payroll system succeeds on the day nobody talks about it — slips are right, on time, and reconciled to the ledger. Getting there is a configuration and methodology problem, and it is one we have solved across jurisdictions and company sizes. If you are evaluating ERPNext for HR and payroll, or rescuing a half-configured instance, talk to ECOSIRE's ERPNext team — we will scope your country requirements honestly and get you to a clean parallel run.