ERPNext version 16 landed on 12 January 2026, and it arrived after one of the longest development cycles in the product’s history. Roughly two years separated it from the last major stable release, and Frappe has described it as the most stable and secure version of ERPNext shipped so far. It carries contributions from a global community of more than 600 developers and introduces over 50 new features across accounting, manufacturing, stock, subcontracting, and point of sale.
Six months on, version 16 has continued to mature through a steady stream of patches and refinements on the version-16 branch. That matters for anyone weighing an upgrade. A release that has been in the field for two full quarters, with real production traffic behind it, is a very different proposition from a release note published on day one.
This article walks through what actually changed, module by module, and then answers the question every finance head and operations director eventually asks: should we upgrade now, and what does the upgrade path look like?
If you are evaluating this for a live implementation, the short version is that v16 is the first release in a while where the headline improvements are not cosmetic. The gains sit in three places: financial reporting flexibility, manufacturing planning depth, and raw system performance.
This is the single most requested capability we hear from Indian finance teams, and v16 finally delivers it properly.
Standard financial statements in earlier versions were fixed in structure. If your auditor wanted a particular grouping, if you needed an IFRS-aligned layout, or if a regional compliance format demanded a specific schedule, you were either living with a workaround or paying for a custom report.

Version 16 introduces a financial report template framework, supported by two new doctypes, Financial Report Row and Account Category. Profit and loss and balance sheet statements become formula-driven and fully customisable. You define the rows, you define the calculations, and you reuse the template across companies in a group structure.
Why this matters commercially: every ERPNext implementation we deliver uses budget effort for at least one or two custom financial statements. That effort now largely disappears into configuration.

Working out the true cost of goods sold has always involved a degree of reconstruction. Purchase costs sat in places that did not surface cleanly in reporting, and finance teams reconciled manually.

v16 adds Purchase Expense Account and Purchase Expense Contra Account at the company and item defaults level. Purchase receipts and invoices can now be presented as purchases in financial reports without disturbing the net balance. You can also set a default COGS account per item, item group, or brand.
The practical effect is that validating COGS takes fewer clicks and produces fewer arguments between finance and operations.

Businesses using periodic inventory accounting have historically endured a painful month end. Calculate stock values, reconcile against accounts, pass the journal entry, and hope nobody fat-fingered a number.
v16 adds a periodic accounting feature that lets companies record stock-in and stock-out balances through journal entry. Press “Get Balance” and the stock differences post directly to the general ledger.

Multi-entity groups previously pulled reports from each subsidiary, handled currency conversion by hand, and merged the results in a spreadsheet.
The new Consolidated Trial Balance report displays combined account balances for selected companies in a single view. Figures from different company currencies are converted into the parent’s reporting currency, and any exchange rate gap is recorded in a Foreign Currency Translation Reserve line so the totals still balance.
Related to this, the company now carries a Reporting Currency field, and GL Entry and Account Closing Balance records store exchange rate-based debit and credit amounts in that currency.


This is where v16 earns its keep for discrete and process manufacturers, and it is the area we field the most questions about from clients in Pune, Ludhiana, and the wider Indian engineering belt.
Material planning was previously buried inside the Production Plan and driven only by Sales Orders or Material Requests. That made genuine MRP awkward and close to useless for medium-term planning.

Version 16 introduces dedicated Master Production Schedule and Material Requirements Planning views. These calculate upcoming production and purchase requirements from sales order schedules, blending forecasts, delivery dates, and lead times into a consolidated picture of demand against available stock.
For a manufacturer that has been running planning in Excel alongside ERPNext, this is the feature that closes the gap.

Almost every ERP supports outward subcontracting, where you send raw material to a job worker. Very few support the reverse.
v16 introduces Subcontracted Sales Order and Subcontracting Inward Order documents. You can now receive customer-supplied raw materials, reserve that stock, launch work orders, manufacture finished goods on the customer’s behalf, and track the return or delivery of those goods along with the related invoices. Dedicated stock entry types and validations keep warehouses, quantities, and serial or batch details consistent through the flow.

The capability technically existed in v15, but the process was manual and fragmented. In v16 it is a supported workflow. For job work in heavy Indian manufacturing, this is significant.

When a customer complaint arrives, the first question is always which batch the product came from, and the second is where else that batch went.
The new Serial No and Batch Traceability report lets you trace backward to the raw materials and batches consumed in a product and forward to every customer and location that received it. Serial No records now store source document details, so the report links straight back to the originating transactions.
For anyone operating under a quality management system or facing a recall scenario, this single report justifies the migration.


4.The outcome is straightforward. Production no longer halts because a critical component was quietly consumed by another order.

Freight, handling, and duties frequently surface after subcontracted goods have already been received. If those charges cannot be applied retrospectively, product valuation is simply wrong.
v16 allows Landed Cost Vouchers to be linked to both Work Orders and Subcontracting Receipts, so additional charges become part of the finished item’s cost. A new Landed Cost Report lists each voucher with its linked purchase vouchers and vendor invoices, and vendor invoices can now be referenced directly on the voucher. Submission is no longer blocked when the total vendor invoice cost and total landed cost differ.


ERPNext runs on the Frappe Framework, and the framework release is where the speed comes from. Frappe has cited roughly twice the performance of the previous version, built on contributions from more than 750 developers.
Smaller additions include SQLite support, background report download, custom permission types, and an awesome popup bar.

For clients running HR and Payroll on the Frappe stack, v16 concentrates on the workflows that generate the most manual correction work.
Also included: half-day attendance status, automatic update of last check-in sync, employee check-in status, and an income tax breakup on the salary slip.

These will not appear in a sales deck, but they are the reason large deployments should pay attention.
Version 16 also introduces version-specific deprecation alerts. When you use a feature scheduled for removal, ERPNext tells you exactly when that feature becomes an error and when it will disappear, escalating from warning to error as the date approaches. This is the first release that makes forward planning around deprecations practical.

Frappe’s own position is that there is no rush. Automatic updates will not be pushed for at least six months from release, and most customisations will carry across with only small adjustments.
Our position, as an implementation partner who has migrated production systems across several major versions, is more specific.
One point deserves emphasis. The Frappe framework should be updated alongside ERPNext v16. The two are versioned together, and running mismatched versions is the fastest way to discover which of your customisations were relying on undocumented behaviour.
1. Inventory your customisations. List every custom app, custom script, server script, custom field, and custom print format. This document is the backbone of the entire upgrade.
2. Read the deprecation warnings on your current instance. v16 flags features scheduled for removal. If you are on a recent v15 build, some of these signals are already visible.
3. Clone production into a staging environment. Never test against live data on live infrastructure.
4. Run the migration on staging. Update Frappe Framework and ERPNext together, then run bench migrate and review every patch that fails.
5. Test the customisations, not the standard features. Frappe tests the standard features. Nobody but you tests yours.
6. Validate financial reports against a closed period. Run Trial Balance, Profit and Loss, and Balance Sheet for a completed month on both versions and reconcile to the rupee.
7. Test the integrations. Payment gateways, e invoicing, e way bill, bank feeds, and any external system pulling from the API.
8. Retrain on the new workspace. The Framework v16 desk looks different. Ten minutes of walkthrough saves a fortnight of support tickets.
9. Schedule the production cutover with a rollback plan. Take a verified backup, agree a go or no go checkpoint, and know exactly how you revert.
10. Monitor for a fortnight. Watch background job queues, error logs, and report execution times.

Under-the-Hood PerformMost Indian SMEs adopting ERPNext are replacing a patchwork of Tally, spreadsheets, and standalone tools. For that profile of buyer, version 16 changes the calculus in two specific ways.
First, the manufacturing depth has caught up with the marketing. MRP, inward subcontracting, phantom BOMs, and stock reservation across the production chain move ERPNext from “capable with customisation” to “capable out of the box” for a large class of engineering and job work businesses.
Second, the financial reporting flexibility removes a recurring implementation cost. Templates replace code, which means your statutory formats, your management reporting pack, and your auditor’s preferred layout are configuration decisions rather than development tickets.
The performance work is the quiet third factor. It is the difference between an ERP your team tolerates and one they actually open on a Monday morning.
We are a Frappe partner based in Pune, and we have been implementing ERPNext, Frappe CRM, and Frappe LMS for manufacturers, distributors, service firms, and non profits across India and the Gulf.
If you are weighing an ERPNext v16 upgrade or evaluating ERPNext against your current system, we are glad to walk through it with you. Reach out for a no-obligation assessment of your instance and a realistic view of effort, timeline, and cost.
When was ERPNext version 16 released?
ERPNext v16.0.0 was released on 12 January 2026, roughly two years after the previous major stable release. The version 16 branch has continued to receive fixes and refinements since.
How many new features are in ERPNext v16?
Frappe cites more than fifty new features, contributed by a community of over six hundred developers, alongside a large body of performance and refactoring work.
Will my ERPNext customisations work in version 16?
Most will carry across, though some require small updates. Custom apps, server scripts, and print formats should be tested on a staging instance before any production migration.
Do I need to update Frappe Framework alongside ERPNext v16?
Yes. Updating the Frappe Framework together with ERPNext v16 is required for full compatibility across features, APIs, and customisations.
Is there a deadline to upgrade to ERPNext v16?
No. Frappe has indicated that automatic updates will not be pushed for at least six months following the release, so you can plan the migration around your own operational calendar.
What is the biggest reason to upgrade to ERPNext v16?
It depends on your business. Manufacturers upgrade for MRP, inward subcontracting, and serial and batch traceability. Finance teams upgrade for Financial Report Templates and the Consolidated Trial Balance. Large instances are upgraded for the performance improvements.