Payroll Engine

Payroll Engine is a framework for building payroll processing into another software platform, rather than a ready-made payroll service. It suits HR-tech and EOR teams, payroll specialists, and integration engineers with the capacity to operate and configure it. Its developer-focused tools are a clear strength; commercial regulations and deployment responsibilities are important trade-offs.

Overview

The MIT-licensed framework takes wage-relevant case data, calculates wages in payruns, and produces outputs such as payslips and legal filings. Configurable, versioned regulation layers can be combined and shared across tenants. This gives product teams room to shape payroll around their own software, but the framework itself is only part of the system: country regulations are commercial, and teams must supply the surrounding product and operational setup.

Time-stamped case values with validity periods support retrospective recalculation and an audit history. Forecasts let teams explore what-if scenarios separately from legally valid payruns. These features are useful where payroll changes need careful handling, though audit trails must be configured rather than being active by default.

Key features

The REST API covers tenant and employee management, payrun jobs, result queries, report output, and backend event webhooks. That is a substantial integration surface for teams embedding payroll in an existing platform. It does not make Payroll Engine a turnkey employee-facing service: adopters need to build or maintain the broader experience themselves.

The.NET Client SDK includes typed REST clients, test runners, local script development tools, JSON schemas for regulation validation, and JSON and Excel import/export. Bulk operations and CLI extensions support automation workflows. No-Code case actions and C# scripting provide options for implementing rules, while automated tests can validate case data, payruns, and report results. This depth is valuable to engineering teams maintaining payroll logic, but the.NET-centered tooling is a less natural fit for teams that do not work in that ecosystem.

A browser-based management application handles tenants, employees, regulations, case data, payruns, reports, tasks, and developer logs. It complements the API and SDK with a way to manage payroll work, but does not change the infrastructure burden: the backend is designed to run locally or through Docker Compose, and its database must be provided separately.

Security needs deliberate setup. API key and OAuth authentication are supported but disabled by default, and the maker says the backend should not be used on the public Internet. Audit trails can be configured by category, but they too are disabled by default. Teams must account for these settings before deployment rather than treating them as ready-made protections.

Pricing

The Open-source framework plan costs nothing and includes the MIT-licensed framework, with no per-employee fees or runtime licenses. That makes it a practical starting point for teams evaluating or building an embedded payroll capability. The price does not include country regulations, which are commercial and offered through the companion payrollex.io marketplace; teams should factor that cost into a production decision.

Platforms

Payroll Engine supports API, Linux, macOS, self-hosted, web, and Windows platforms. Its local and Docker Compose deployment options suit teams that want to operate the backend themselves, while the separate database requirement means it is not a self-contained installation.

Who it's for

The strongest fit is an HR-tech or EOR platform adding payroll to its own product, or a payroll consultant or HR specialist working with DevOps and integration engineers. Those teams can benefit from configurable regulations, test tooling, and API coverage. Businesses seeking a hosted payroll service with minimal setup should look elsewhere: operating the backend, sourcing commercial regulations, and configuring security remain their responsibility.

For questions and feature requests, the project directs users to GitHub Discussions; bug reports go to GitHub Issues. It asks users to allow a few business days for responses.

Pros and cons

Pros: The MIT-licensed framework has no per-employee fees or runtime licenses, which can suit teams embedding payroll in a larger product.

Pros: Versioned regulation layers, time-aware records, forecasts, and automated testing support controlled changes to payroll logic.

Pros: The REST API,.NET SDK, and browser application give integration and payroll teams several ways to manage and automate work.

Cons: Country regulations are commercial, so the free framework is not the whole cost of a production payroll system.

Cons: A separate database is required, and authentication and audit trails need configuration before use.

Cons: The maker says not to expose the backend to the public Internet, limiting its suitability for teams expecting a directly accessible hosted service.

Alternatives

PHPPayroll is another open-source option with a free self-hosted edition; consider it if you want an alternative payroll product rather than this framework's embedding and integration approach.

Paybooks offers payroll processing, leave management, employee self-service, reports, and Indian statutory compliance; it may suit teams seeking those packaged capabilities. Dapplon Global Payroll has a Basic plan at $29 a month for up to 25 employees, including core HR and payroll, PF, ESI and TDS filing, and email support. Omni HR Payroll includes payroll calculations, digital payslips, statutory filing, accounting integration, and multi-country support. Rippling, ADP Workforce Now, Better HR, and BIPO HRMS Payroll are other paid options to compare.

For a broader comparison, see Global Payroll Software.

Verdict

Choose Payroll Engine if you are building payroll into a platform and have the engineering and operations capacity to manage the backend, regulations, and security configuration. Its open-source framework and testing and integration tools offer a strong foundation for that work. Look elsewhere if you want a ready-to-run service or expect the framework's free price to cover country regulations and deployment.