Frappe HR and payroll implementation with ERPNext

Each country or tax regime you pay people under adds its own salary components, statutory deductions, tax slabs and year-end forms, so effort grows with every jurisdiction. Frappe HR handles payroll through salary structures and components that you configure, but the statutory logic for each country has to be confirmed with your payroll or tax advisers and tested against real pay cycles. Ask a partner to quote per jurisdiction, and confirm whether country-specific payroll support already exists in the Frappe HR release you plan to run. One-time work covers the rule design and testing; recurring work covers tax table updates each year, which your payroll owner or an adviser must confirm before each cycle.

Pay groups, salary structures and components set how earnings and deductions are calculated, so each new combination needs a design decision, a test case and sign-off. The effort comes from the number of distinct pay rules, not the number of employees. Map every allowance, deduction and exception before configuration starts, and treat each unusual rule (for example, a bonus with a special tax treatment) as its own work item. Ask for a quote that lists pay groups and components as separate line items so you can see which ones drive the price.

Device integrations add effort because each attendance device, its data format and its connection method must be understood, tested and maintained. Attendance feeds the payroll run, so errors in punch data become errors in pay. Confirm which device models and protocols you use, who supplies the device integration, and how missing or duplicate punches are corrected before payroll is locked. Recurring cost comes from keeping the connector working after device firmware or network changes, which your IT team or partner should own explicitly in the contract.

Poor source data is usually the largest hidden cost in an HR payroll build. Duplicate employees, missing bank details, inconsistent job titles and outdated tax declarations all need cleaning before they can be imported. Frappe's Data Import tool accepts CSV or Excel files and child table rows, and its documentation advises importing only a few thousand records at a time, so large employee histories need batched loads and validation rounds. Ask the implementer to profile your data first and to quote the cleanup as a separate phase, since it is labor your team or the partner performs before any configuration is useful.

Custom logic adds cost when a payroll rule cannot be expressed with standard configuration. Frappe's documentation says Server Scripts run Python on document events or as API endpoints, and from version 15 they are disabled by default and must be enabled with the server_script_enabled setting. Frappe Cloud public shared benches do not allow them, so confirm your hosting tier before design. Frappe Cloud shared site hosting starts at 5 US dollars per month and dedicated servers at 125 US dollars per month, according to the ERPNext pricing page, but hosting cost is only one part of the total. Custom apps need code review, testing, upgrades on every ERPNext release and a named owner after go-live. Ask for the custom code separately in the quote, with its maintenance terms.

Identity integration changes scope because employee logins, roles and deprovisioning must match your directory. ERPNext supports LDAP login against Active Directory or OpenLDAP, with SSL/TLS options and automatic mapping of LDAP groups to ERPNext roles at each login, and Social Login Key lets users sign in through configured OAuth or OpenID Connect providers. Each option needs testing with real accounts, role mapping rules and a plan for leavers. Confirm with your identity team which method you will use before the build, since changing it late means retesting access for every role.

A parallel run pays staff through the existing system and the new one at the same time, then compares net pay, tax and ledger postings line by line. Its length depends on how many pay cycles your payroll owner needs to trust the results, including any year-end or bonus cycle that the new system must handle. Frappe documentation does not supply a duration, so set the length with your payroll and finance leads. Your team pays for the payroll staff time, and the implementer pays for fixes it introduced. Ask the quote to state who performs reconciliation and how many correction rounds are included.

Cost depends on the scope agreed in writing, so no fixed figure applies to every team. The main drivers are the number of employees and entities, how many salary structures and pay components you run, how many countries and tax regimes apply, how many systems payroll must feed (accounting, attendance devices, bank files), and whether you need custom reports or scripts. Expect one-time work for design, configuration, data loading and testing, and recurring costs for hosting, upgrades and support. The Frappe Cloud pricing page lists hosting starting at 5 US dollars per month for shared sites and 125 US dollars per month for dedicated servers, while self-hosting ERPNext itself is free. Ask any provider for a quote that separates these items and states what is excluded.

Duration is set by scope and by the readiness of your inputs, not by the software alone. The longest steps are usually confirming payroll rules with your advisers, cleaning employee and leave data, and running parallel payroll cycles until the results match your current process. Timelines lengthen when attendance devices, shift patterns, expense approval chains or several countries must be integrated, and when more than one ERPNext company shares the same employee base. Ask for a plan with phases, the dependencies between them, and the decisions that must be made by named people before each phase can close.

Yes, a capable internal team can implement it using the official documentation, provided it has someone who knows ERPNext and someone who knows your payroll rules well. The work is mostly configuration rather than code, but it demands careful testing, because a wrong tax slab or leave rule shows up as a pay error. Be realistic about capacity: the team must also run parallel payroll, handle go-live support and keep up with releases. A partner is most useful when the team lacks ERPNext experience, when deadlines are fixed, or when integrations and custom reports must be built and maintained.

Each group owns decisions that the software cannot make. HR supplies the employee master data, the leave and attendance policies, shift rules and the approval hierarchy for leave and expenses. Payroll supplies the salary components, deduction rules, statutory calculations and a set of past payroll runs to reconcile against. Finance decides how payroll and expense claims post to the chart of accounts, cost centers and bank accounts in ERPNext, and signs off the journal entries. Name one owner per group, agree how sign-off is recorded, and schedule their time for testing before the project starts, since delays in these reviews are a common cause of slippage.

Frappe HR is built to run on ERPNext, so it is normally installed on the same bench or site rather than as a stand-alone product. Expense claims post to ERPNext accounting, and payroll journal entries depend on accounts, cost centers and companies that exist there. You can start with HR and payroll and leave other modules for later, but the accounting setup must be complete enough to receive postings. Confirm with your provider and the release notes for your ERPNext version which app versions are compatible, because version support follows the Frappe support policy.

Confirm every statutory rule with your tax adviser and payroll authority before configuring anything. This includes income tax slabs and their effective dates, social security or pension contributions and their ceilings, employer contributions, statutory leave, public holidays, reporting obligations and any required payslip content. Ask whether the Frappe HR payroll features already cover your country's rules, and whether a country-specific app or a custom salary component is needed. Keep the source of each rule on file and agree who approves changes, because tax rates and thresholds change during the year.

Most payroll work is configuration: salary structures, components, formulas, leave types, shift and attendance rules, and print formats. Custom work appears when the rules fall outside the standard model, such as unusual bonus calculations, device integrations, bank file formats or reports for an auditor. Server Scripts can run Python on document events, but from version 15 they are disabled by default and must be enabled with the server_script_enabled setting, and Frappe Cloud public shared benches do not allow them. Confirm the hosting model before designing any script-based logic.