What's new in Frappe HR v16: payroll, shifts, and team management

At a glance

Frappe HR v16 shipped alongside ERPNext v16 in January 2026, and its theme is unmistakable: automate the routine corrections HR teams do by hand. Overtime computed from check-in data instead of spreadsheets, arrears calculated automatically when a raise lands late, leave balances adjustable without workarounds, and benefits tracked in a ledger. We run this in production — our client Mr Goli Soda operates Frappe HR across 70 franchise locations with 300+ employees — so this is a practitioner's read, not a feature-list recital. The honest headline for US readers comes first: v16 does not change the US payroll tax answer. Frappe HR runs gross payroll and HR operations well; US tax filing still belongs with Gusto or ADP.

What are the biggest new features in Frappe HR v16?

Frappe HR v16's headline features are automatic overtime calculation from check-in and check-out data, automatic arrears when salary revisions apply retroactively, multi-currency expense claims and advances, flexible employee benefits with a Benefit Ledger, direct leave adjustments, scheduled earned-leave crediting, and holiday list assignments that preserve history. The theme across all of them is the same: less manual correction work for HR teams.

Everything in this post comes from the official Frappe HR v16 release page and the linked documentation, plus our own implementation experience — flagged as such where it appears.

Overtime management — from check-in data to payroll

This is the feature hourly and manufacturing workforces will care about most. In v16, overtime is automatically calculated from employee check-in and check-out times, assigned to shift-specific Overtime Types, and processed through Overtime Slips. HR reviews and approves the slips, and approved overtime generates Additional Salary entries that flow directly into payroll. The before-state this replaces is familiar: someone exports punch data, computes OT hours in a spreadsheet, and keys adjustments into payroll — monthly, by hand, with errors.

Two honest notes for US readers. First, the feature computes hours and gross amounts; the pay-rule logic — FLSA time-and-a-half thresholds, your state's daily-overtime rules if you have them — lives in how your Overtime Types are configured. Configured well, the math follows your policy; the compliance responsibility is in the implementation, not the box. Second, the whole pipeline starts from check-in and check-out data. If your people don't punch in through ERPNext check-ins or a synced biometric device, that prerequisite comes first — no check-in data, no automatic overtime.

Payroll gets self-correcting — arrears and LWP correction

Backdated changes are the quiet tax on every payroll team: the raise approved in March effective January, the salary structure fixed after two cycles ran wrong. In v15 and earlier, those meant manual arrears math and hand-entered adjustments.

In v16, when a Salary Structure Assignment is approved retroactively, the system calculates the arrears automatically and applies additional salary entries for the affected past months — with earnings, deductions, and accruals tracked in payroll and the Employee Benefit Ledger. Loss-of-pay correction is included in the release as well, covering the mirror case where attendance corrections change what was already paid.

Why this matters more than it sounds: in our experience late raises and backdated changes are the single biggest source of manual payroll patching, and manual patches are where payroll errors breed. Automating the recalculation doesn't just save time — it makes the correction auditable instead of artisanal.

Can Frappe HR run US payroll?

Partly — and we're direct about this. Frappe HR handles gross payroll well: salary structures, overtime, arrears, deductions, benefits. It does not file US federal and state payroll taxes, produce W-2s, or handle multi-state withholding natively. We implement Frappe HR for HR operations and pair it with Gusto or ADP for tax filing and compliance.

Nothing in the v16 release, the docs, or any roadmap coverage indicates a US tax engine — no 941s, no W-2 generation, no state e-filing, no multi-state withholding logic. Worth knowing for trajectory: at Frappeverse 2026, Frappe showed serious India payroll compliance work — statutory Provident Fund and professional tax rules embedded, quarterly TDS return filing run from the Frappe HR Desk. That's genuine evidence Frappe invests in payroll compliance, but it's country-by-country, India first, and the US isn't there. The income tax breakup on salary slip item on the v16 release page is likewise India-payroll-oriented; don't read it as US tax functionality. This limit is a standing entry on our honest-limits list, and v16 doesn't move it an inch.

The working architecture we implement: Frappe HR owns the people system — attendance, shifts, leave, expense claims, gross payroll computation — and Gusto or ADP owns tax calculation, filing, and year-end forms. Clean division, each tool doing what it's actually good at.

We'll map exactly which payroll pieces live in Frappe HR versus Gusto or ADP for your headcount. Book a free scoping call.

Shifts, attendance, and leave — quality-of-life wins

None of these is a headline; together they're hours of HR admin back every month.

Leave Adjustment: HR can now increase or reduce allocated leaves directly from an existing allocation, and the system auto-creates a Leave Adjustment record, so every balance change carries an audit trail. The old workaround — cancel and re-create allocations, or ledger gymnastics — is gone.

Earned Leave schedule: earned leave now auto-credits on the policy's schedule. Successful credits are highlighted green; failures are surfaced for a one-click fix instead of silently skipping an employee who notices three months later.

Holiday List Assignment: multiple holiday lists can be assigned to employees or the company, with past records preserved — so when someone moves teams or branches mid-year, leave calculations use the right list for the right period instead of rewriting history. For multi-location operations with different local holidays, this quietly removes a recurring source of leave-balance disputes.

• Half-days supported in holiday lists.
• A half-day attendance status.
• Employee check-in status visibility.
• Auto-updated last sync of check-ins.
• Income tax breakup on the salary slip (again: India-oriented).

Benefits and expenses

Flexible Employee Benefits: employees pick from employer-offered perks — health insurance contributions, pension plans, and similar — and benefits either accrue each payroll cycle or get claimed on demand, with everything tracked in the Employee Benefit Ledger. One sentence of honesty to prevent an overclaim: this is benefits payroll structure, not US benefits administration — there are no carrier integrations, no COBRA workflows, no ACA reporting. It organizes the money side of benefits inside payroll; your broker and benefits platform keep their jobs.

Multi-currency expense claims and advances: expense claims and employee advances now handle multiple currencies — amounts convert, exchange rates are tracked, FX gains and losses post to accounting, and multiple payments against one advance are tracked. For US companies with international staff, contractors, or regular overseas travel, this ends the convert-it-manually-and-attach-a-screenshot-of-the-rate era, and the accounting entries land correctly without a controller's cleanup pass.

Does Frappe HR scale to multi-location teams?

Yes — it's the deployment pattern we know first-hand. Our client Mr Goli Soda runs Frappe HR across 70 franchise locations with 300+ employees, covering attendance, shifts, and HR operations. v16's holiday list assignments and shift-based overtime types specifically make multi-location policy differences easier to manage without parallel spreadsheets.

The multi-location problem is never can the software hold 300 employee records — it's policy variance: this location observes different holidays, that one runs different shifts with different overtime rules. v16's structure maps those differences into configuration (holiday lists per location, Overtime Types per shift) instead of into tribal knowledge. That's the difference between an HR system and an HR system plus twelve reconciliation spreadsheets. More on the deployment in the full case study.

Should you upgrade to Frappe HR v16?

If you're on v15 and HR spends time on manual corrections — backdated raises, leave balance fixes, overtime spreadsheets — v16 pays for the upgrade effort quickly. Upgrade Frappe Framework, ERPNext, and Frappe HR together for compatibility. New implementations should start on v16 (or v16.50) directly.

One version note: the October 2026 v16.50 release covers Frappe HR too — the new navigation, print designer, kanban, and data import improvements all apply to HR workflows — and Frappe's guidance is to update all three apps together. If you're upgrading anyway, go to v16.50; we've covered what's in it and what it signals separately.

Bottom line

Frappe HR v16 is a correction-killer release: overtime from real check-in data, self-calculating arrears, auditable leave adjustments, scheduled leave crediting, benefits in a ledger, multi-currency expenses that post properly. What it is not — still — is a US payroll tax system, and anyone implying otherwise is selling you a compliance problem. The honest architecture works, at real scale: Frappe HR for people operations and gross payroll, Gusto or ADP for taxes, implemented as one coherent system.

Want HR, attendance, and payroll ops in one open-source system — with taxes handled the right way? We've done it at 70-location scale, with pricing from $4,000 and go-live in 6–8 weeks. Get started.